docs: update all documentation to resource-first command syntax

Update all user-facing documentation to use the new resource-first
CLI syntax per RFC-0002 and ADR-0018.

**Files updated:**
- README.md: Quick start examples
- docs/guide/getting-started.md: RFC and clause creation
- docs/guide/rfcs.md: All RFC operations (list, finalize, advance, bump)
- docs/guide/adrs.md: ADR operations (new, accept, deprecate, supersede, list)
- docs/guide/work-items.md: Work item operations (new, move, add, remove, tick, list)

**Command changes:**
- `govctl rfc new` (was `govctl new rfc`)
- `govctl work move` (was `govctl mv`)
- `govctl clause edit` (was `govctl edit`)
- `govctl work add` (was `govctl add`)
- `govctl rfc list` (was `govctl list rfc`)
- And all other resource-specific operations

**Fixed errors:**
- Corrected ADR editing docs (use get/set, not edit)
- Updated filter syntax to positional arguments

Author: lucifer1004

CHANGELOG.md

@@ -36,7 +36,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 - Remove 'normative = frozen' validation constraint (WI-2026-01-19-006)
 - Update .claude/CLAUDE.md to use --dry-run without -n (WI-2026-01-19-009)
-- Update assets/*.md files to use resource-first command syntax (WI-2026-01-19-010)
+- Update assets/\*.md files to use resource-first command syntax (WI-2026-01-19-010)
 
 ### Removed
 

README.md

@@ -41,12 +41,12 @@ Day 30: Two incompatible caching layers, no spec, nobody knows why
 ### With govctl
 
 ```
-Day 1:  govctl new rfc "Caching Strategy"
+Day 1:  govctl rfc new "Caching Strategy"
 Day 2:  RFC-0015 defines: Redis, TTL policy, invalidation rules
-Day 3:  govctl advance RFC-0015 impl
+Day 3:  govctl rfc advance RFC-0015 impl
 Day 7:  Implementation complete, traceable to spec
-Day 10: govctl advance RFC-0015 test
-Day 14: Tests pass, govctl advance RFC-0015 stable
+Day 10: govctl rfc advance RFC-0015 test
+Day 14: Tests pass, govctl rfc advance RFC-0015 stable
 ```
 
 ---
@@ -105,7 +105,7 @@ cargo install govctl --features tui
 govctl init
 
 # Create your first RFC
-govctl new rfc "Feature Title"
+govctl rfc new "Feature Title"
 
 # Validate
 govctl check

docs/guide/adrs.md

@@ -5,7 +5,7 @@ ADRs (Architectural Decision Records) document significant design choices. They
 ## Creating ADRs
 
 ```bash
-govctl new adr "Use Redis for caching"
+govctl adr new "Use Redis for caching"
 ```
 
 This creates a TOML file in `gov/adr/` with the decision context.
@@ -21,10 +21,14 @@ ADRs contain:
 
 ## Editing ADRs
 
-ADRs are TOML files — edit them directly or use govctl:
+ADRs are TOML files — edit them directly in your editor or use govctl to get/set fields:
 
 ```bash
-govctl edit ADR-0003
+# Get specific field
+govctl adr get ADR-0003 status
+
+# Set field value
+govctl adr set ADR-0003 status accepted
 ```
 
 ## Status Lifecycle
@@ -39,32 +43,32 @@ proposed → accepted → deprecated
 When consensus is reached:
 
 ```bash
-govctl accept ADR-0003
+govctl adr accept ADR-0003
 ```
 
 ### Deprecate
 
 When a decision is no longer relevant:
 
 ```bash
-govctl deprecate ADR-0003
+govctl adr deprecate ADR-0003
 ```
 
 ### Supersede
 
 When a new decision replaces an old one:
 
 ```bash
-govctl supersede ADR-0001 --by ADR-0005
+govctl adr supersede ADR-0001 --by ADR-0005
 ```
 
 This marks ADR-0001 as superseded and records ADR-0005 as its replacement.
 
 ## Listing ADRs
 
 ```bash
-govctl list adr
-govctl list adr --status accepted
+govctl adr list
+govctl adr list accepted    # Filter by status
 ```
 
 ## Why TOML?

docs/guide/getting-started.md

@@ -73,7 +73,7 @@ gov/
 ## Create Your First RFC
 
 ```bash
-govctl new rfc "Feature Title"
+govctl rfc new "Feature Title"
 ```
 
 This creates `gov/rfc/RFC-0000/rfc.json` with the RFC metadata.
@@ -83,13 +83,13 @@ This creates `gov/rfc/RFC-0000/rfc.json` with the RFC metadata.
 RFCs are composed of clauses — atomic units of specification:
 
 ```bash
-govctl new clause RFC-0000:C-SCOPE "Scope" -s "Specification" -k normative
+govctl clause new RFC-0000:C-SCOPE "Scope" -s "Specification" -k normative
 ```
 
 ## Edit Clause Content
 
 ```bash
-govctl edit RFC-0000:C-SCOPE --stdin <<'EOF'
+govctl clause edit RFC-0000:C-SCOPE --stdin <<'EOF'
 The feature MUST do X.
 The feature SHOULD do Y.
 EOF

docs/guide/rfcs.md

@@ -6,10 +6,10 @@ RFCs (Requests for Comments) are the normative specifications in govctl. They de
 
 ```bash
 # Auto-assign next available ID
-govctl new rfc "Feature Title"
+govctl rfc new "Feature Title"
 
 # Specify ID manually
-govctl new rfc "Feature Title" --id RFC-0010
+govctl rfc new "Feature Title" --id RFC-0010
 ```
 
 ## RFC Structure
@@ -24,7 +24,7 @@ An RFC consists of:
 ### Create a Clause
 
 ```bash
-govctl new clause RFC-0010:C-SCOPE "Scope" -s "Specification" -k normative
+govctl clause new RFC-0010:C-SCOPE "Scope" -s "Specification" -k normative
 ```
 
 Options:
@@ -36,13 +36,13 @@ Options:
 
 ```bash
 # From stdin
-govctl edit RFC-0010:C-SCOPE --stdin <<'EOF'
+govctl clause edit RFC-0010:C-SCOPE --stdin <<'EOF'
 The system MUST validate all inputs.
 The system SHOULD log validation failures.
 EOF
 
 # Open in editor
-govctl edit RFC-0010:C-SCOPE
+govctl clause edit RFC-0010:C-SCOPE
 ```
 
 ### Delete a Clause
@@ -60,13 +60,13 @@ govctl delete --clause RFC-0010:C-MISTAKE -f
 - The RFC status is `draft` (normative RFCs are immutable)
 - No other artifacts reference the clause
 
-For normative RFCs, use `govctl deprecate RFC-0010:C-OLD` instead.
+For normative RFCs, use `govctl clause deprecate RFC-0010:C-OLD` instead.
 
 ### List Clauses
 
 ```bash
-govctl list clause
-govctl list clause --rfc RFC-0010
+govctl clause list
+govctl clause list RFC-0010
 ```
 
 ## Status Lifecycle
@@ -82,7 +82,7 @@ draft → normative → deprecated
 When the spec is complete and approved:
 
 ```bash
-govctl finalize RFC-0010 normative
+govctl rfc finalize RFC-0010 normative
 ```
 
 This makes the RFC binding — implementation must conform to it.
@@ -92,7 +92,7 @@ This makes the RFC binding — implementation must conform to it.
 When an RFC is superseded or obsolete:
 
 ```bash
-govctl finalize RFC-0010 deprecated
+govctl rfc finalize RFC-0010 deprecated
 ```
 
 ## Phase Lifecycle
@@ -106,9 +106,9 @@ spec → impl → test → stable
 ### Advance Phase
 
 ```bash
-govctl advance RFC-0010 impl    # Ready for implementation
-govctl advance RFC-0010 test    # Implementation complete, ready for testing
-govctl advance RFC-0010 stable  # Tested, ready for production
+govctl rfc advance RFC-0010 impl    # Ready for implementation
+govctl rfc advance RFC-0010 test    # Implementation complete, ready for testing
+govctl rfc advance RFC-0010 stable  # Tested, ready for production
 ```
 
 Phase transitions are gated:
@@ -122,15 +122,15 @@ RFCs use semantic versioning:
 
 ```bash
 # Bump version with changelog entry
-govctl bump RFC-0010 --patch -m "Fix typo in clause C-SCOPE"
-govctl bump RFC-0010 --minor -m "Add new clause for edge case"
-govctl bump RFC-0010 --major -m "Breaking change to API contract"
+govctl rfc bump RFC-0010 --patch -m "Fix typo in clause C-SCOPE"
+govctl rfc bump RFC-0010 --minor -m "Add new clause for edge case"
+govctl rfc bump RFC-0010 --major -m "Breaking change to API contract"
 ```
 
 ## Listing RFCs
 
 ```bash
-govctl list rfc
-govctl list rfc --status normative
-govctl list rfc --phase impl
+govctl rfc list
+govctl rfc list normative    # Filter by status
+govctl rfc list impl         # Filter by phase
 ```

docs/guide/work-items.md

@@ -6,10 +6,10 @@ Work Items track units of work from inception to completion. They provide an aud
 
 ```bash
 # Create in queue (pending)
-govctl new work "Implement caching layer"
+govctl work new "Implement caching layer"
 
 # Create and activate immediately
-govctl new work --active "Urgent bug fix"
+govctl work new --active "Urgent bug fix"
 ```
 
 Work items are automatically assigned IDs like `WI-2026-01-17-001`.
@@ -35,26 +35,26 @@ queue → active → done
 
 ```bash
 # By ID
-govctl mv WI-2026-01-17-001 active
-govctl mv WI-2026-01-17-001 done
+govctl work move WI-2026-01-17-001 active
+govctl work move WI-2026-01-17-001 done
 
 # By filename (without path)
-govctl mv implement-caching.toml active
+govctl work move implement-caching.toml active
 ```
 
 ## Acceptance Criteria
 
 ### Add Criteria
 
 ```bash
-govctl add WI-2026-01-17-001 acceptance_criteria "Unit tests pass"
-govctl add WI-2026-01-17-001 acceptance_criteria "Documentation updated"
+govctl work add WI-2026-01-17-001 acceptance_criteria "Unit tests pass"
+govctl work add WI-2026-01-17-001 acceptance_criteria "Documentation updated"
 ```
 
 ### Mark Criteria Complete
 
 ```bash
-govctl tick WI-2026-01-17-001 acceptance_criteria "Unit tests" -s done
+govctl work tick WI-2026-01-17-001 acceptance_criteria "Unit tests" -s done
 ```
 
 The pattern matches case-insensitively by substring.
@@ -64,7 +64,7 @@ The pattern matches case-insensitively by substring.
 Add context or progress notes:
 
 ```bash
-govctl add WI-2026-01-17-001 notes "Discovered edge case in validation"
+govctl work add WI-2026-01-17-001 notes "Discovered edge case in validation"
 ```
 
 ## Removing Items
@@ -73,22 +73,22 @@ Remove items from array fields using flexible matching:
 
 ```bash
 # Substring match (default, case-insensitive)
-govctl remove WI-2026-01-17-001 notes "edge case"
+govctl work remove WI-2026-01-17-001 notes "edge case"
 
 # Exact match
-govctl remove WI-2026-01-17-001 notes "Discovered edge case in validation" --exact
+govctl work remove WI-2026-01-17-001 notes "Discovered edge case in validation" --exact
 
 # By index (0-based)
-govctl remove WI-2026-01-17-001 notes --at 0
+govctl work remove WI-2026-01-17-001 notes --at 0
 
 # Negative index (from end)
-govctl remove WI-2026-01-17-001 notes --at -1
+govctl work remove WI-2026-01-17-001 notes --at -1
 
 # Regex pattern
-govctl remove WI-2026-01-17-001 refs "RFC-.*" --regex
+govctl work remove WI-2026-01-17-001 refs "RFC-.*" --regex
 
 # Remove all matches
-govctl remove WI-2026-01-17-001 refs "obsolete" --all
+govctl work remove WI-2026-01-17-001 refs "obsolete" --all
 ```
 
 ## Deleting Work Items
@@ -109,16 +109,16 @@ govctl delete --work WI-2026-01-17-999 -f
 For work items that have been activated, use status transitions instead:
 
 ```bash
-govctl mv WI-2026-01-17-001 cancelled
+govctl work move WI-2026-01-17-001 cancelled
 ```
 
 ## Listing Work Items
 
 ```bash
-govctl list work
-govctl list work queue      # Pending items
-govctl list work active     # In progress
-govctl list work done       # Completed
+govctl work list
+govctl work list queue      # Pending items
+govctl work list active     # In progress
+govctl work list done       # Completed
 ```
 
 ## Why TOML?