create-quiver 0.15.1 → 0.15.2

package/specs/quiver-v33-approval-ux-and-planner-progress/slices/slice-00-approval-ux-foundation/CLOSURE_BRIEF.md

@@ -0,0 +1,30 @@
+# CLOSURE_BRIEF - slice-00 Approval UX foundation
+
+## Summary
+
+Created the v33 planning package for approval UX, planner progress, shared approval decision guidance, and revise input guardrails.
+
+## Validation Against Acceptance Criteria
+
+- [x] Spec folder created.
+- [x] Every slice has `slice.json`, `EXECUTION_BRIEF.md`, and `CLOSURE_BRIEF.md`.
+- [x] Product code was not modified.
+- [x] JSON validation captured.
+- [x] Spec validation captured.
+- [x] `git diff --check` captured.
+
+## Relevant Changes
+
+- New folder: `specs/quiver-v33-approval-ux-and-planner-progress/`.
+
+## Pending
+
+- None.
+
+## Remaining Risks
+
+- The repository still lacks `docs/INDEX.md`; this spec used the documented Quiver sources available in the repo.
+
+## Future Recommendations
+
+Keep future approval-gate changes covered by focused selector, no-TTY, review-state, and workflow-surface tests.

package/specs/quiver-v33-approval-ux-and-planner-progress/slices/slice-00-approval-ux-foundation/EXECUTION_BRIEF.md

@@ -0,0 +1,56 @@
+# EXECUTION_BRIEF - slice-00 Approval UX foundation
+
+## Context
+
+The user approved a revised production-reviewed plan for approval UX, planner progress, revise input guardrails, and shared approval decision guidance.
+
+## Objective
+
+Create the v33 planning package under `specs/quiver-v33-approval-ux-and-planner-progress/` without implementing product code.
+
+## Scope
+
+- `specs/quiver-v33-approval-ux-and-planner-progress/SPEC.md`
+- `specs/quiver-v33-approval-ux-and-planner-progress/STATUS.md`
+- `specs/quiver-v33-approval-ux-and-planner-progress/EVIDENCE_REPORT.md`
+- `specs/quiver-v33-approval-ux-and-planner-progress/EXECUTION_PLAN.md`
+- `specs/quiver-v33-approval-ux-and-planner-progress/pr.md`
+- all slice folders and handoff briefs
+
+## Acceptance Criteria
+
+- Spec package exists.
+- Every slice has `slice.json`, `EXECUTION_BRIEF.md`, and `CLOSURE_BRIEF.md`.
+- `slice-00` records the approved acceptance criteria and revised technical plan.
+- JSON files parse.
+- Spec validation passes.
+- No product code is modified.
+
+## Technical Plan Summary
+
+Use recent Quiver specs as the local contract and keep slice-00 documentation-only.
+
+## Suggested Steps
+
+1. Create the spec folder.
+2. Create top-level spec artifacts.
+3. Create slice folders and JSON contracts.
+4. Create execution and closure briefs for every slice.
+5. Validate JSON and spec structure.
+
+## Restrictions
+
+- Do not edit `src/`.
+- Do not edit tests.
+- Do not claim implementation is complete.
+
+## Risks
+
+- Missing `docs/INDEX.md` remains a documentation debt outside this slice.
+
+## Completion Checklist
+
+- [x] Spec artifacts created.
+- [x] Slice contracts created.
+- [x] Handoff briefs created.
+- [x] Validation commands run.

package/specs/quiver-v33-approval-ux-and-planner-progress/slices/slice-00-approval-ux-foundation/slice.json

@@ -0,0 +1,65 @@
+{
+  "slice_id": "slice-00-approval-ux-foundation",
+  "ticket": "QUIVER-33-00",
+  "type": "docs",
+  "title": "Approval UX foundation",
+  "objective": "Create the v33 spec package for approval UX, planner progress, and shared decision guidance.",
+  "description": "Publishes the approved spec, execution plan, PR body, status, evidence report, slice definitions, and handoffs without changing product code.",
+  "git": {
+    "branch_type": "feature",
+    "base_branch": "main",
+    "branch_slug": "v33-approval-ux-foundation",
+    "branch_name": "feature/QUIVER-33-00-v33-approval-ux-foundation"
+  },
+  "files": [
+    "specs/quiver-v33-approval-ux-and-planner-progress/**"
+  ],
+  "expected_read_paths": [
+    "README_FOR_AI.md",
+    "docs/CLI_UX_GUIDE.md",
+    "docs/reference/commands.md",
+    "docs/workflows/full-ai-spec-to-pr.md",
+    "specs/quiver-v29-planner-prepare-context-cli-ux/**",
+    "specs/quiver-v30-interactive-cli-ux-agent-selection/**",
+    "specs/quiver-v31-ai-model-catalog-agent-selection/**"
+  ],
+  "allowed_write_paths": [
+    "specs/quiver-v33-approval-ux-and-planner-progress/**"
+  ],
+  "depends_on": [],
+  "parallel_safe": "no",
+  "parallel_safe_reason": "slice-00 is the foundation barrier for the spec.",
+  "must": [
+    "Create SPEC.md, STATUS.md, EVIDENCE_REPORT.md, EXECUTION_PLAN.md, and pr.md.",
+    "Create slice.json, EXECUTION_BRIEF.md, and CLOSURE_BRIEF.md for every slice.",
+    "Capture approved acceptance criteria and production review fixes.",
+    "Avoid product code changes."
+  ],
+  "not_included": [
+    "Implementing approval selectors.",
+    "Changing command behavior.",
+    "Updating public docs outside this spec package.",
+    "Publishing a package."
+  ],
+  "acceptance": [
+    "Spec folder exists under specs/quiver-v33-approval-ux-and-planner-progress.",
+    "Every slice has slice.json, EXECUTION_BRIEF.md, and CLOSURE_BRIEF.md.",
+    "Every slice.json parses successfully.",
+    "Spec validation passes.",
+    "No product code is modified."
+  ],
+  "tests": [
+    "git diff --check",
+    "find specs/quiver-v33-approval-ux-and-planner-progress -name \"slice.json\" -print -exec node -e \"JSON.parse(require('fs').readFileSync(process.argv[1], 'utf8'))\" {} \\;",
+    "node bin/create-quiver.js spec validate specs/quiver-v33-approval-ux-and-planner-progress"
+  ],
+  "validation_hints": [
+    "Keep this slice documentation-only.",
+    "Do not claim implementation or package publication."
+  ],
+  "estimated_hours": 2,
+  "status": "completed",
+  "blocked_reason": null,
+  "actual_hours": 2,
+  "completed_at": "2026-05-28"
+}

package/specs/quiver-v33-approval-ux-and-planner-progress/slices/slice-01-approval-candidates-model/CLOSURE_BRIEF.md

@@ -0,0 +1,19 @@
+# CLOSURE_BRIEF - slice-01 Shared approval candidates model
+
+## Summary
+
+Completed shared approval-candidate construction for acceptance and technical-plan phases. Candidates include current/latest flags, approvability, next command, redacted/truncated previews, and technical-plan review decision data.
+
+## Validation
+
+- [x] Candidate model tests pass.
+- [x] Existing approval and plan-review tests pass.
+- [x] No provider execution added.
+
+## Pending
+
+- None.
+
+## Remaining Risks
+
+- None critical; downstream surfaces consume the model in slice-06.

package/specs/quiver-v33-approval-ux-and-planner-progress/slices/slice-01-approval-candidates-model/EXECUTION_BRIEF.md

@@ -0,0 +1,51 @@
+# EXECUTION_BRIEF - slice-01 Shared approval candidates model
+
+## Context
+
+Approval guidance is currently split across approval persistence, plan-review metadata, `ai approve`, `ai approvals`, `flow`, and run-state formatting.
+
+## Objective
+
+Create a shared read-only candidate model that every later approval UX surface can consume.
+
+## Scope
+
+- `src/create-quiver/lib/approvals.js`
+- `src/create-quiver/lib/ai/plan-review.js`
+- focused tests
+
+## Acceptance Criteria
+
+- Candidate data includes phase, version, path, source, current/latest state, review recommendation, blocking state, risks, and next command.
+- Only the latest draft is marked recommended/approvable.
+- Technical-plan candidates include plan-review state.
+- Candidate summaries are bounded and safe.
+- Existing approval metadata remains backward compatible.
+
+## Technical Plan Summary
+
+Add pure helper functions around existing metadata readers. Keep formatting and interactivity out of this slice except for minimal candidate summary helpers if needed.
+
+## Suggested Steps
+
+1. Model candidate shape.
+2. Build acceptance candidates from approval metadata.
+3. Build technical-plan candidates with plan-review context.
+4. Add unit tests for missing, draft, stale, approved, approve-with-risk, and revise states.
+5. Export only stable helpers needed by later slices.
+
+## Restrictions
+
+- Do not add prompts.
+- Do not change approval persistence format unless tests prove compatibility.
+- Do not relax review blocking.
+
+## Risks
+
+- A poorly scoped helper can become another duplicated formatter instead of a source of truth.
+
+## Completion Checklist
+
+- [ ] Shared candidate helpers implemented.
+- [ ] Candidate tests added.
+- [ ] Existing approval tests still pass.

package/specs/quiver-v33-approval-ux-and-planner-progress/slices/slice-01-approval-candidates-model/slice.json

@@ -0,0 +1,74 @@
+{
+  "slice_id": "slice-01-approval-candidates-model",
+  "ticket": "QUIVER-33-01",
+  "type": "feature",
+  "title": "Shared approval candidates model",
+  "objective": "Create a single approval-candidate model for acceptance, technical-plan, and plan-review decision data.",
+  "description": "Adds reusable read-only candidate construction so approval commands and workflow surfaces share the same current draft, version, review state, recommendation, and next-command guidance.",
+  "git": {
+    "branch_type": "feature",
+    "base_branch": "main",
+    "branch_slug": "v33-approval-candidates-model",
+    "branch_name": "feature/QUIVER-33-01-v33-approval-candidates-model"
+  },
+  "files": [
+    "src/create-quiver/lib/approvals.js",
+    "src/create-quiver/lib/ai/plan-review.js",
+    "tests/lib/approvals.test.js",
+    "tests/commands/ai-review-plan.test.js"
+  ],
+  "expected_read_paths": [
+    "src/create-quiver/lib/approvals.js",
+    "src/create-quiver/lib/ai/plan-review.js",
+    "src/create-quiver/commands/ai.js",
+    "tests/lib/approvals.test.js",
+    "tests/commands/ai-review-plan.test.js",
+    "SPEC.md"
+  ],
+  "allowed_write_paths": [
+    "src/create-quiver/lib/approvals.js",
+    "src/create-quiver/lib/ai/plan-review.js",
+    "tests/lib/approvals.test.js",
+    "tests/commands/ai-review-plan.test.js",
+    "specs/quiver-v33-approval-ux-and-planner-progress/**"
+  ],
+  "depends_on": [
+    "slice-00-approval-ux-foundation"
+  ],
+  "parallel_safe": "no",
+  "parallel_safe_reason": "This model is a dependency for later command and workflow surfaces.",
+  "must": [
+    "Expose candidate data without changing existing persisted approval metadata unless required.",
+    "Include phase, version, path, created_at, source_file, latest/current flags, status, recommendation, blocking state, recommended action, and next command.",
+    "Represent older drafts as history but mark them non-current and not recommended.",
+    "Expose technical-plan plan-review state using the existing plan-review semantics.",
+    "Use redacted/truncated summary helpers for any preview text.",
+    "Keep JSON/no-TTY consumers clean."
+  ],
+  "not_included": [
+    "Interactive prompts.",
+    "Changing approval execution behavior.",
+    "Changing plan-review blocking rules."
+  ],
+  "acceptance": [
+    "Acceptance candidates include the latest draft and draft history.",
+    "Technical-plan candidates include plan-review state and recommendation.",
+    "Older drafts are visible as history but not marked approvable.",
+    "A revise recommendation is represented as blocking.",
+    "Approve-with-risk is represented as approvable with risks.",
+    "Candidate summaries do not print unbounded draft contents."
+  ],
+  "tests": [
+    "node --test tests/lib/approvals.test.js tests/commands/ai-review-plan.test.js",
+    "git diff --check"
+  ],
+  "validation_hints": [
+    "Prefer pure functions that can be reused by commands without I/O side effects.",
+    "Do not call providers in this slice."
+  ],
+  "estimated_hours": 6,
+  "status": "completed",
+  "blocked_reason": null,
+  "actual_hours": 6,
+  "completed_at": "2026-05-28"
+}

package/specs/quiver-v33-approval-ux-and-planner-progress/slices/slice-02-approve-interactive-selection/CLOSURE_BRIEF.md

@@ -0,0 +1,20 @@
+# CLOSURE_BRIEF - slice-02 Interactive approval selection
+
+## Summary
+
+Completed TTY approval selection for acceptance and technical-plan when `--version` is omitted, while preserving explicit version approval for scripts and CI.
+
+## Validation
+
+- [x] Acceptance selector test passes.
+- [x] Technical-plan selector test passes.
+- [x] No-TTY/CI failure test passes.
+- [x] Explicit version regression test passes.
+
+## Pending
+
+- None.
+
+## Remaining Risks
+
+- None critical; slice-06 integrates shared guidance into the remaining surfaces.

package/specs/quiver-v33-approval-ux-and-planner-progress/slices/slice-02-approve-interactive-selection/EXECUTION_BRIEF.md

@@ -0,0 +1,53 @@
+# EXECUTION_BRIEF - slice-02 Interactive approval selection
+
+## Context
+
+Users currently need to run `ai approvals`, inspect versions manually, then pass `--version <n>`. The requested UX should behave like `ai agent set`: guide users in TTY and stay explicit in automation.
+
+## Objective
+
+Add TTY approval selection for `ai approve` when `--version` is omitted.
+
+## Scope
+
+- `src/create-quiver/commands/ai.js`
+- selector helpers if needed
+- approval tests
+
+## Acceptance Criteria
+
+- TTY acceptance approval without `--version` shows candidates.
+- TTY technical-plan approval without `--version` shows review-aware candidates.
+- No-TTY/CI requires `--version`.
+- Explicit `--version` behavior remains stable.
+- Cancellation writes no files.
+- Blocked candidates cannot be approved.
+
+## Technical Plan Summary
+
+Resolve candidates from slice-01, use `selectOption` for prompt-capable environments, and pass the selected version into the existing approval path.
+
+## Suggested Steps
+
+1. Add approval selection resolver.
+2. Wire resolver into `runApprove`.
+3. Add no-TTY guardrail message.
+4. Add tests for acceptance and technical-plan.
+5. Verify explicit version path remains unchanged.
+
+## Restrictions
+
+- Do not add `--review` support.
+- Do not weaken technical-plan validation.
+- Do not prompt in CI/no-TTY/JSON.
+
+## Risks
+
+- Prompt availability detection must match existing `ai agent set` behavior closely enough to avoid CI hangs.
+
+## Completion Checklist
+
+- [ ] TTY selector implemented.
+- [ ] No-TTY guardrail tested.
+- [ ] Cancellation tested.
+- [ ] Explicit `--version` tested.

package/specs/quiver-v33-approval-ux-and-planner-progress/slices/slice-02-approve-interactive-selection/slice.json

@@ -0,0 +1,79 @@
+{
+  "slice_id": "slice-02-approve-interactive-selection",
+  "ticket": "QUIVER-33-02",
+  "type": "feature",
+  "title": "Interactive approval selection",
+  "objective": "Let `ai approve --phase acceptance|technical-plan` guide TTY users when `--version` is omitted while preserving explicit non-interactive behavior.",
+  "description": "Adds a selector patterned after `ai agent set`, recommends the current latest draft, blocks unsafe approvals, and keeps CI/no-TTY requiring `--version <n>`.",
+  "git": {
+    "branch_type": "feature",
+    "base_branch": "main",
+    "branch_slug": "v33-approve-interactive-selection",
+    "branch_name": "feature/QUIVER-33-02-v33-approve-interactive-selection"
+  },
+  "files": [
+    "src/create-quiver/commands/ai.js",
+    "src/create-quiver/lib/cli/selectors.js",
+    "src/create-quiver/lib/approvals.js",
+    "tests/commands/ai-review-plan.test.js",
+    "tests/commands/ai-plan.test.js",
+    "tests/lib/cli-selectors.test.js"
+  ],
+  "expected_read_paths": [
+    "src/create-quiver/commands/ai.js",
+    "src/create-quiver/lib/approvals.js",
+    "src/create-quiver/lib/cli/selectors.js",
+    "tests/commands/ai-review-plan.test.js",
+    "tests/commands/ai-plan.test.js",
+    "SPEC.md"
+  ],
+  "allowed_write_paths": [
+    "src/create-quiver/commands/ai.js",
+    "src/create-quiver/lib/cli/selectors.js",
+    "src/create-quiver/lib/approvals.js",
+    "tests/commands/ai-review-plan.test.js",
+    "tests/commands/ai-plan.test.js",
+    "tests/lib/cli-selectors.test.js",
+    "specs/quiver-v33-approval-ux-and-planner-progress/**"
+  ],
+  "depends_on": [
+    "slice-01-approval-candidates-model"
+  ],
+  "parallel_safe": "no",
+  "parallel_safe_reason": "This slice changes approval command behavior and should land before downstream consumers rely on it.",
+  "must": [
+    "Open a selector only when `--version` is omitted and prompts are available.",
+    "Require explicit `--version <n>` in CI/no-TTY.",
+    "Keep explicit `--version <n>` behavior backward compatible.",
+    "Recommend the current/latest approvable draft.",
+    "Show concise useful decision information for each candidate.",
+    "Allow cancellation without writes.",
+    "Do not approve older or blocked drafts silently."
+  ],
+  "not_included": [
+    "Changing plan-review result derivation.",
+    "Changing spec generation.",
+    "Adding editor review to approve."
+  ],
+  "acceptance": [
+    "`ai approve --phase acceptance` in TTY without `--version` shows a selector.",
+    "`ai approve --phase technical-plan` in TTY without `--version` shows a selector with review context.",
+    "No-TTY/CI without `--version` fails actionably.",
+    "`--version 1` still approves through the existing path when valid.",
+    "Canceling the selector writes no approval.",
+    "Older draft versions cannot be approved through the selector."
+  ],
+  "tests": [
+    "node --test tests/commands/ai-plan.test.js tests/commands/ai-review-plan.test.js tests/lib/cli-selectors.test.js",
+    "git diff --check"
+  ],
+  "validation_hints": [
+    "Use injected selector helpers in tests; do not require a real terminal.",
+    "Test no-TTY and CI explicitly."
+  ],
+  "estimated_hours": 8,
+  "status": "completed",
+  "blocked_reason": null,
+  "actual_hours": 8,
+  "completed_at": "2026-05-28"
+}

package/specs/quiver-v33-approval-ux-and-planner-progress/slices/slice-03-technical-plan-review-decision-data/CLOSURE_BRIEF.md

@@ -0,0 +1,19 @@
+# CLOSURE_BRIEF - slice-03 Technical-plan review decision data
+
+## Summary
+
+Completed technical-plan candidate enrichment so approval decisions reflect review status, approval recommendation, blocking state, required fixes, optional hardening, risks, and next command.
+
+## Validation
+
+- [x] Plan-review state tests pass.
+- [x] Revise blocking test passes.
+- [x] Approve-with-risk test passes.
+
+## Pending
+
+- None.
+
+## Remaining Risks
+
+- None critical; workflow surfaces are integrated in slice-06.

package/specs/quiver-v33-approval-ux-and-planner-progress/slices/slice-03-technical-plan-review-decision-data/EXECUTION_BRIEF.md

@@ -0,0 +1,50 @@
+# EXECUTION_BRIEF - slice-03 Technical-plan review decision data
+
+## Context
+
+Technical-plan approval already has safety checks, but users need visible decision data before approving.
+
+## Objective
+
+Surface plan-review state and recommendation consistently during technical-plan approval.
+
+## Scope
+
+- `src/create-quiver/lib/ai/plan-review.js`
+- approval candidate helpers
+- `runApprove` selector output if needed
+- focused plan-review tests
+
+## Acceptance Criteria
+
+- Missing, stale, unapproved, approve, approve-with-risk, and revise states are distinguishable.
+- Revise blocks approval.
+- Approve-with-risk remains approvable and visible.
+- Required fixes, optional hardening, risks, and next command are shown where relevant.
+- Existing technical-plan approval validation remains intact.
+
+## Technical Plan Summary
+
+Extend the shared candidate data with normalized review-decision fields and consume them in the approval selector.
+
+## Suggested Steps
+
+1. Normalize review decision state.
+2. Add candidate annotations for technical-plan.
+3. Update selector rendering or approval summaries.
+4. Add tests for all review states.
+
+## Restrictions
+
+- Do not modify provider prompts.
+- Do not change review-result schema unless needed for backward compatibility.
+
+## Risks
+
+- Displaying unapproved vs reviewed states incorrectly can lead users to approve the wrong artifact.
+
+## Completion Checklist
+
+- [ ] Review states normalized.
+- [ ] Blocking behavior preserved.
+- [ ] Tests cover all review states.

package/specs/quiver-v33-approval-ux-and-planner-progress/slices/slice-03-technical-plan-review-decision-data/slice.json

@@ -0,0 +1,75 @@
+{
+  "slice_id": "slice-03-technical-plan-review-decision-data",
+  "ticket": "QUIVER-33-03",
+  "type": "feature",
+  "title": "Technical-plan review decision data",
+  "objective": "Make technical-plan approval decisions visibly reflect plan-review state and recommendation.",
+  "description": "Ensures approval selection and command output distinguish missing, stale, unapproved, approve, approve-with-risk, and revise review states without weakening existing gates.",
+  "git": {
+    "branch_type": "feature",
+    "base_branch": "main",
+    "branch_slug": "v33-technical-plan-review-decision-data",
+    "branch_name": "feature/QUIVER-33-03-v33-technical-plan-review-decision-data"
+  },
+  "files": [
+    "src/create-quiver/lib/ai/plan-review.js",
+    "src/create-quiver/lib/approvals.js",
+    "src/create-quiver/commands/ai.js",
+    "tests/commands/ai-review-plan.test.js",
+    "tests/lib/approvals.test.js"
+  ],
+  "expected_read_paths": [
+    "src/create-quiver/lib/ai/plan-review.js",
+    "src/create-quiver/lib/approvals.js",
+    "src/create-quiver/commands/ai.js",
+    "tests/commands/ai-review-plan.test.js",
+    "SPEC.md"
+  ],
+  "allowed_write_paths": [
+    "src/create-quiver/lib/ai/plan-review.js",
+    "src/create-quiver/lib/approvals.js",
+    "src/create-quiver/commands/ai.js",
+    "tests/commands/ai-review-plan.test.js",
+    "tests/lib/approvals.test.js",
+    "specs/quiver-v33-approval-ux-and-planner-progress/**"
+  ],
+  "depends_on": [
+    "slice-01-approval-candidates-model",
+    "slice-02-approve-interactive-selection"
+  ],
+  "parallel_safe": "yes",
+  "parallel_safe_reason": "Can proceed after approval selection if command-file conflicts are coordinated.",
+  "must": [
+    "Represent plan-review statuses missing, stale, unapproved, reviewed approve, reviewed approve-with-risk, and reviewed revise.",
+    "Block approval when recommendation is revise.",
+    "Allow approve-with-risk with visible risk context.",
+    "Show required fixes count and next command when blocked.",
+    "Preserve existing explicit technical-plan approval validation."
+  ],
+  "not_included": [
+    "Changing how reviewers generate review metadata.",
+    "Changing structured review schema unless required for display.",
+    "Relaxing stale review checks."
+  ],
+  "acceptance": [
+    "Technical-plan selector shows missing review as not ready.",
+    "Stale review blocks or redirects to review-plan.",
+    "Unapproved review guides to approve with the reviewed version when valid.",
+    "Approve-with-risk exposes optional hardening and risks.",
+    "Revise recommendation blocks approval.",
+    "Explicit version approval still enforces the same blocking rules."
+  ],
+  "tests": [
+    "node --test tests/commands/ai-review-plan.test.js tests/lib/approvals.test.js",
+    "git diff --check"
+  ],
+  "validation_hints": [
+    "Reuse existing `reviewBlocksApproval` semantics.",
+    "Add tests around every plan-review status."
+  ],
+  "estimated_hours": 6,
+  "status": "completed",
+  "blocked_reason": null,
+  "actual_hours": 6,
+  "completed_at": "2026-05-28"
+}

package/specs/quiver-v33-approval-ux-and-planner-progress/slices/slice-04-revise-input-guardrails/CLOSURE_BRIEF.md

@@ -0,0 +1,19 @@
+# CLOSURE_BRIEF - slice-04 Revise input guardrails
+
+## Summary
+
+Completed revise input guardrails for missing `--input` values, nonexistent feedback files, and accidental extra positional arguments before any provider execution.
+
+## Validation
+
+- [x] Missing input tests pass.
+- [x] Nonexistent file tests pass.
+- [x] Valid revise regression tests pass.
+
+## Pending
+
+- None.
+
+## Remaining Risks
+
+- None critical; broader CLI contract coverage passed in the full suite.

package/specs/quiver-v33-approval-ux-and-planner-progress/slices/slice-04-revise-input-guardrails/EXECUTION_BRIEF.md

@@ -0,0 +1,51 @@
+# EXECUTION_BRIEF - slice-04 Revise input guardrails
+
+## Context
+
+The requirement explicitly called out incomplete `ai revise --phase technical-plan --input` usage and an accidental trailing `s`. Production review expanded the scope to acceptance revise as well.
+
+## Objective
+
+Make invalid `ai revise --input` usage fail clearly before provider execution for both planner phases.
+
+## Scope
+
+- CLI argument parsing if needed.
+- `runRevise` / `runPlan` input validation.
+- focused command tests.
+
+## Acceptance Criteria
+
+- Missing `--input` value is detected for acceptance and technical-plan.
+- Nonexistent feedback files fail before provider execution.
+- Accidental extra arguments are reported or rejected clearly.
+- No-TTY/CI never prompts.
+- Valid revise commands remain unchanged.
+
+## Technical Plan Summary
+
+Add explicit guardrails at the parser/command boundary, then test command-level behavior with provider execution disabled or asserted absent.
+
+## Suggested Steps
+
+1. Inspect parse behavior for `--input` without value.
+2. Add a consistent actionable error.
+3. Add nonexistent-file regression coverage.
+4. Add accidental extra-arg coverage if parser supports it.
+5. Confirm valid revise flows still pass.
+
+## Restrictions
+
+- Do not run a provider when input is invalid.
+- Do not auto-create feedback files.
+
+## Risks
+
+- Parser changes can affect other commands that use `--input`.
+
+## Completion Checklist
+
+- [ ] Missing input covered for both phases.
+- [ ] Nonexistent input covered.
+- [ ] Extra argument behavior covered.
+- [ ] Valid revise flow still passes.