Consolidated addition, removal, and listing of locks under a single narratio locks command

docs/roadmap/operations.md

@@ -22,22 +22,22 @@ The operator helper command set is no longer conceptual. Current behavior is doc
 - `narratio artifacts list`
 - `narratio artifacts list --remote`
 - `narratio locks`
-- `narratio lock <source>`
-- `narratio unlock <source>`
+- `narratio locks add <source>`
+- `narratio locks remove <source>`
 
 ## Implemented Decisions
 
 - Helper output is text-only. No JSON schema exists yet.
 - `status` remains a top-level command.
 - `session validate`, `session init`, and `artifacts list` are nested helper commands.
-- `lock`, `unlock`, and `locks` are top-level commands.
+- `locks` is the single top-level command for listing, adding, and removing archive promotion locks.
 - Remote session initialization requires explicit `--remote`.
 - Local session initialization requires `--output`.
 - Remote artifact availability is opt-in with `artifacts list --remote`.
 - Mutable locks are source-based and stored at `{session_prefix}/locks.yml`.
 - The remote lock store uses strict YAML with top-level `locks`.
 - Static `pipeline.archive.locks` and remote locks are merged; static locks win on duplicate sources.
-- `unlock` removes only remote locks.
+- `locks remove` removes only remote locks.
 - Ordinary execution `--force` does not override locks.
 - Remote lock writes use existence checks and `--force` for updates; there is no compare-and-swap protection.
 
@@ -50,4 +50,3 @@ These are intentionally not implemented:
 - Rich remote artifact availability across historical run-local objects.
 - Session-lock acquisition for remote mutation helpers.
 - Broader campaign helper commands such as `campaign validate` or `campaign publish`.
-