create-quiver 0.14.1 → 0.15.0

package/specs/quiver-v30-interactive-cli-ux-agent-selection/slices/slice-05-executor-pr-progress-flows/slice.json

@@ -0,0 +1,85 @@
+{
+  "slice_id": "slice-05-executor-pr-progress-flows",
+  "ticket": "QUIVER-30-05",
+  "type": "feature",
+  "title": "Executor, execution-plan, and PR progress flows",
+  "objective": "Apply the UX runtime, selectors, and progress contract to executor-oriented, execution-plan, and PR commands.",
+  "description": "Adds visible progress and selector-safe execution to ai execute-slice, ai execute-plan, ai prompt-slice where useful, and ai pr.",
+  "git": {
+    "branch_type": "feature",
+    "base_branch": "main",
+    "branch_slug": "v30-executor-pr-progress-flows",
+    "branch_name": "feature/QUIVER-30-05-v30-executor-pr-progress-flows"
+  },
+  "files": [
+    "src/create-quiver/commands/ai.js",
+    "src/create-quiver/lib/ai/executor.js",
+    "src/create-quiver/lib/ai/execution-plan.js",
+    "src/create-quiver/lib/ai/github.js",
+    "src/create-quiver/lib/cli/**",
+    "tests/commands/ai-execute-*.test.js",
+    "tests/commands/ai-pr.test.js",
+    "specs/quiver-v30-interactive-cli-ux-agent-selection/**"
+  ],
+  "expected_read_paths": [
+    "src/create-quiver/commands/ai.js",
+    "src/create-quiver/lib/ai/executor.js",
+    "src/create-quiver/lib/ai/execution-plan.js",
+    "src/create-quiver/lib/ai/github.js",
+    "src/create-quiver/lib/slice-graph.js",
+    "docs/GITFLOW_PR_GUIDE.md"
+  ],
+  "allowed_write_paths": [
+    "src/create-quiver/commands/ai.js",
+    "src/create-quiver/lib/ai/executor.js",
+    "src/create-quiver/lib/ai/execution-plan.js",
+    "src/create-quiver/lib/ai/github.js",
+    "src/create-quiver/lib/cli/**",
+    "tests/commands/ai-execute-*.test.js",
+    "tests/commands/ai-pr.test.js",
+    "docs/CLI_UX_GUIDE.md",
+    "docs/reference/commands.md",
+    "README_FOR_AI.md",
+    "specs/quiver-v30-interactive-cli-ux-agent-selection/**"
+  ],
+  "depends_on": [
+    "slice-01-cli-ux-runtime-progress-engine",
+    "slice-02-agent-profile-selection-selectors",
+    "slice-03-provider-model-selection-contract"
+  ],
+  "parallel_safe": "after_dependencies",
+  "parallel_safe_reason": "Can run after shared contracts, but may conflict with slice-04 in commands/ai.js.",
+  "must": [
+    "Use Executor display names for slice execution headings.",
+    "Add real stages for reading handoff, validating scope, preparing prompt, executing agent, validating diff, running checks, and committing when requested.",
+    "Add selector support for spec, slice, executor, execution strategy, and PR input when interactive.",
+    "Add real progress for ai pr preflight and PR creation.",
+    "Keep ai prompt-slice copyable and avoid unnecessary spinners.",
+    "Keep one-slice/one-commit behavior unchanged."
+  ],
+  "not_included": [
+    "Planner progress flows.",
+    "Doctor output.",
+    "Changing GitHub authentication semantics."
+  ],
+  "acceptance": [
+    "Executor commands show selected Executor display name.",
+    "Spec and slice selectors use unique internal values and respect dependencies.",
+    "Blocked slices are not silently selected as ready.",
+    "ai pr shows validation and creation progress without hiding gh errors.",
+    "Machine output remains clean."
+  ],
+  "tests": [
+    "node --test tests/commands/ai-execute-slice.test.js tests/commands/ai-execute-plan.test.js tests/commands/ai-pr.test.js",
+    "git diff --check"
+  ],
+  "validation_hints": [
+    "Use dry-run/manual modes for tests that should not execute provider CLIs.",
+    "Do not stream noisy provider output unless --verbose is introduced and tested."
+  ],
+  "estimated_hours": 12,
+  "status": "completed",
+  "blocked_reason": null,
+  "actual_hours": 7,
+  "completed_at": "2026-05-27"
+}

package/specs/quiver-v30-interactive-cli-ux-agent-selection/slices/slice-06-doctor-visual-json-contract/CLOSURE_BRIEF.md

@@ -0,0 +1,35 @@
+# CLOSURE_BRIEF - slice-06 Doctor visual and JSON contract
+
+## Summary
+
+Implemented the Doctor visual/JSON contract with one diagnostics model that drives both human and machine output.
+
+## Validation Against Acceptance Criteria
+
+- [x] Human doctor output validated.
+- [x] JSON output validated.
+- [x] Finding parity validated.
+- [x] Exit codes validated.
+- [x] Smoke fixtures validated.
+
+## Relevant Changes
+
+- Added a shared Doctor command report with stable `schema_version`, status, exit code, checks, suggested fixes, warnings, and errors.
+- Added human output with `Quiver Doctor`, `Checks`, and `Suggested fixes`.
+- Added `doctor --json` output that remains parseable and uses the same findings as the human renderer.
+- Preserved `doctor --fix --dry-run` behavior and kept `doctor --fix --json` machine-clean.
+- Added tests for human hierarchy, JSON parsing, finding parity, and deterministic blocking exit code.
+- Documented the Doctor output contract in the CLI UX guide, command reference, and source-of-truth AI guide.
+
+## Pending
+
+- Final docs and package readiness are handled by slice-08.
+
+## Remaining Risks
+
+- The Doctor report schema is intentionally minimal. Future consumers should rely on `schema_version`, `checks`, `suggested_fixes`, `warnings`, `errors`, and `exit_code` rather than terminal formatting.
+- Existing host-environment warnings, such as `gh auth`, still depend on the local machine and can appear in warning checks.
+
+## Future Recommendations
+
+Consider a future `doctor --fix --interactive` flow only after this diagnostic contract is stable.

package/specs/quiver-v30-interactive-cli-ux-agent-selection/slices/slice-06-doctor-visual-json-contract/EXECUTION_BRIEF.md

@@ -0,0 +1,55 @@
+# EXECUTION_BRIEF - slice-06 Doctor visual and JSON contract
+
+## Context
+
+The user explicitly wants output shaped like `Quiver Doctor` with checks and suggested fixes. Doctor must remain useful for scripts.
+
+## Objective
+
+Give `doctor` a clear human format and a stable JSON contract with matching diagnostics.
+
+## Scope
+
+- Human doctor output.
+- JSON doctor output.
+- Exit-code semantics.
+- Doctor fixtures and smoke tests.
+- Docs for doctor output.
+
+## Acceptance Criteria
+
+- Human output includes `Quiver Doctor`, `Checks`, and `Suggested fixes`.
+- `doctor --json` remains parseable and stable.
+- Human and JSON findings match.
+- Exit codes are deterministic.
+- Smoke doctor fixtures pass.
+
+## Plan tecnico resumido
+
+Separate diagnostic data from renderers. Use the same findings model for human and JSON output.
+
+## Suggested Steps
+
+1. Identify current doctor findings data.
+2. Add human renderer using shared UX runtime.
+3. Add or stabilize JSON schema.
+4. Add fixture tests for representative states.
+5. Update docs.
+
+## Restrictions
+
+- Do not add automatic repair behavior.
+- Do not invoke IA provider in doctor by default.
+- Do not make colors required to understand severity.
+
+## Risks
+
+- Existing fixture snapshots may be brittle.
+- JSON schema changes can break downstream automation.
+
+## Completion Checklist
+
+- [ ] Human doctor output validated.
+- [ ] JSON schema validated.
+- [ ] Fixture smoke passes.
+- [ ] Docs updated.

package/specs/quiver-v30-interactive-cli-ux-agent-selection/slices/slice-06-doctor-visual-json-contract/slice.json

@@ -0,0 +1,81 @@
+{
+  "slice_id": "slice-06-doctor-visual-json-contract",
+  "ticket": "QUIVER-30-06",
+  "type": "feature",
+  "title": "Doctor visual and JSON contract",
+  "objective": "Make doctor output visually clear for humans while preserving stable JSON diagnostics for automation.",
+  "description": "Applies the Quiver Doctor output structure with checks, warnings, errors, suggested fixes, exit-code semantics, and JSON parity.",
+  "git": {
+    "branch_type": "feature",
+    "base_branch": "main",
+    "branch_slug": "v30-doctor-visual-json-contract",
+    "branch_name": "feature/QUIVER-30-06-v30-doctor-visual-json-contract"
+  },
+  "files": [
+    "src/create-quiver/lib/doctor.js",
+    "src/create-quiver/index.js",
+    "src/create-quiver/lib/cli/**",
+    "tests/commands/doctor.test.js",
+    "tests/fixtures/doctor/**",
+    "scripts/ci/smoke-doctor-fixtures.js",
+    "specs/quiver-v30-interactive-cli-ux-agent-selection/**"
+  ],
+  "expected_read_paths": [
+    "src/create-quiver/lib/doctor.js",
+    "src/create-quiver/index.js",
+    "scripts/ci/smoke-doctor-fixtures.js",
+    "tests/fixtures/doctor/**",
+    "docs/CLI_UX_GUIDE.md"
+  ],
+  "allowed_write_paths": [
+    "src/create-quiver/lib/doctor.js",
+    "src/create-quiver/index.js",
+    "src/create-quiver/lib/cli/**",
+    "tests/commands/doctor.test.js",
+    "tests/fixtures/doctor/**",
+    "scripts/ci/smoke-doctor-fixtures.js",
+    "docs/CLI_UX_GUIDE.md",
+    "docs/reference/commands.md",
+    "README.md",
+    "README_FOR_AI.md",
+    "specs/quiver-v30-interactive-cli-ux-agent-selection/**"
+  ],
+  "depends_on": [
+    "slice-01-cli-ux-runtime-progress-engine"
+  ],
+  "parallel_safe": "after_dependencies",
+  "parallel_safe_reason": "Doctor can adopt the shared runtime independently after slice-01.",
+  "must": [
+    "Render human doctor output with a `Quiver Doctor` heading, `Checks`, and `Suggested fixes` sections.",
+    "Preserve a stable JSON schema for doctor diagnostics.",
+    "Ensure human and JSON modes report the same underlying findings.",
+    "Keep exit codes consistent for ok, warning, blocking error, and internal CLI error.",
+    "Add tests for missing docs, missing briefs, warnings, and fix suggestions."
+  ],
+  "not_included": [
+    "Adding automatic repairs.",
+    "Running Doctor IA provider by default.",
+    "Changing project initialization."
+  ],
+  "acceptance": [
+    "Human doctor output matches the approved hierarchy.",
+    "doctor --json emits parseable stable JSON.",
+    "Human and JSON outputs have parity for findings.",
+    "Exit codes remain deterministic.",
+    "Smoke doctor fixtures pass."
+  ],
+  "tests": [
+    "node --test tests/commands/doctor.test.js",
+    "npm run smoke:doctor-fixtures",
+    "git diff --check"
+  ],
+  "validation_hints": [
+    "Do not make doctor visual-only; automation compatibility is part of the slice.",
+    "Fixture expected output should avoid brittle spinner frames."
+  ],
+  "estimated_hours": 8,
+  "status": "completed",
+  "blocked_reason": null,
+  "actual_hours": 5,
+  "completed_at": "2026-05-27"
+}

package/specs/quiver-v30-interactive-cli-ux-agent-selection/slices/slice-07-interactive-init-spec-create/CLOSURE_BRIEF.md

@@ -0,0 +1,34 @@
+# CLOSURE_BRIEF - slice-07 Interactive init and spec create flows
+
+## Summary
+
+Implemented guided interactive flows for init and spec creation while keeping default automation unchanged.
+
+## Validation Against Acceptance Criteria
+
+- [x] `init --interactive` validated.
+- [x] non-interactive init compatibility validated.
+- [x] `spec create --interactive` validated.
+- [x] no-TTY/CI/JSON fallback validated.
+
+## Relevant Changes
+
+- Added `init --interactive` guided choices for project mode, methodology, init profile, and optional agent-profile next steps.
+- Enforced the only supported methodology, `wdd-sdd`, through `--methodology` and interactive selectors.
+- Added summaries before persistent writes in interactive init/spec-create flows.
+- Added `spec create --interactive` selectors for methodology, approved technical-plan input, and direct-vs-review write mode.
+- Added no-TTY guardrails so interactive commands fail with explicit flag guidance instead of blocking automation.
+- Documented the interactive flow and methodology flag in CLI docs and source-of-truth guide.
+
+## Pending
+
+- Full docs and release-readiness evidence are handled by slice-08.
+
+## Remaining Risks
+
+- The project-mode selector currently maps "solo validar estructura" to Doctor. That is useful and non-destructive, but it still requires the target to have Quiver initialization evidence.
+- `spec create --interactive` presents the currently resolved approved technical plan input; additional historical input selection can be added later if multiple approved inputs become a supported contract.
+
+## Future Recommendations
+
+Keep the interactive question count small and add more prompts only when real dogfooding shows repeated confusion.

package/specs/quiver-v30-interactive-cli-ux-agent-selection/slices/slice-07-interactive-init-spec-create/EXECUTION_BRIEF.md

@@ -0,0 +1,55 @@
+# EXECUTION_BRIEF - slice-07 Interactive init and spec create flows
+
+## Context
+
+The user wants guided selectors for onboarding-style flows, methodology, and spec decisions, but Quiver must stay script-safe.
+
+## Objective
+
+Add useful interactive flows to `init` and `spec create` without changing default automation behavior.
+
+## Scope
+
+- `init --interactive`
+- `spec create --interactive`
+- methodology selector with `WDD + SDD`
+- write summary before action
+- equivalent non-interactive flags and docs
+
+## Acceptance Criteria
+
+- `init --interactive` is guided.
+- `init` without `--interactive` is unchanged.
+- `spec create --interactive` lets the human review choices before writes.
+- No prompt opens in CI/no-TTY/JSON.
+- The methodology selector does not invent unsupported options.
+
+## Plan tecnico resumido
+
+Use the selector infrastructure from slice-02 and keep interactive prompts as explicit opt-in convenience wrappers around existing command contracts.
+
+## Suggested Steps
+
+1. Identify init/spec-create decision points.
+2. Add selectors behind `--interactive`.
+3. Add summary-before-write behavior.
+4. Add no-TTY/CI fallback errors or defaults.
+5. Add tests with injected prompt answers.
+
+## Restrictions
+
+- Do not run providers from init.
+- Do not add unsupported methodology choices.
+- Do not make prompts default behavior.
+
+## Risks
+
+- Interactive init can become too long if too many questions are added.
+- Spec create must not re-open already approved plan gates incorrectly.
+
+## Completion Checklist
+
+- [ ] Interactive init tested.
+- [ ] Non-interactive init compatibility tested.
+- [ ] Interactive spec create tested.
+- [ ] Methodology selector documented.

package/specs/quiver-v30-interactive-cli-ux-agent-selection/slices/slice-07-interactive-init-spec-create/slice.json

@@ -0,0 +1,85 @@
+{
+  "slice_id": "slice-07-interactive-init-spec-create",
+  "ticket": "QUIVER-30-07",
+  "type": "feature",
+  "title": "Interactive init and spec create flows",
+  "objective": "Add guided interactive selection to init and spec create without making prompts mandatory or breaking automation.",
+  "description": "Applies the selector contract to project onboarding and spec package creation, including methodology, profile defaults, approved plan selection, and review mode.",
+  "git": {
+    "branch_type": "feature",
+    "base_branch": "main",
+    "branch_slug": "v30-interactive-init-spec-create",
+    "branch_name": "feature/QUIVER-30-07-v30-interactive-init-spec-create"
+  },
+  "files": [
+    "src/create-quiver/index.js",
+    "src/create-quiver/commands/spec.js",
+    "src/create-quiver/lib/init-layout.js",
+    "src/create-quiver/lib/init-docs.js",
+    "src/create-quiver/lib/cli/**",
+    "tests/commands/init-*.test.js",
+    "tests/commands/spec-*.test.js",
+    "specs/quiver-v30-interactive-cli-ux-agent-selection/**"
+  ],
+  "expected_read_paths": [
+    "src/create-quiver/index.js",
+    "src/create-quiver/commands/spec.js",
+    "src/create-quiver/lib/init-layout.js",
+    "src/create-quiver/lib/init-docs.js",
+    "tests/commands/init-profiles.test.js",
+    "tests/commands/spec-create.test.js"
+  ],
+  "allowed_write_paths": [
+    "src/create-quiver/index.js",
+    "src/create-quiver/commands/spec.js",
+    "src/create-quiver/lib/init-layout.js",
+    "src/create-quiver/lib/init-docs.js",
+    "src/create-quiver/lib/cli/**",
+    "tests/commands/init-*.test.js",
+    "tests/commands/spec-*.test.js",
+    "docs/CLI_UX_GUIDE.md",
+    "docs/reference/commands.md",
+    "README.md",
+    "README_FOR_AI.md",
+    "specs/quiver-v30-interactive-cli-ux-agent-selection/**"
+  ],
+  "depends_on": [
+    "slice-01-cli-ux-runtime-progress-engine",
+    "slice-02-agent-profile-selection-selectors"
+  ],
+  "parallel_safe": "after_dependencies",
+  "parallel_safe_reason": "Init/spec-create interaction can be implemented after UX and selector contracts are available.",
+  "must": [
+    "Add `init --interactive` prompts for project mode, methodology, and optional default agent profile guidance.",
+    "Show only real methodology option: WDD + SDD.",
+    "Keep init non-interactive behavior unchanged without --interactive.",
+    "Add `spec create --interactive` selectors for approved inputs and review choices where appropriate.",
+    "Show summary before writes in interactive mode.",
+    "Provide equivalent flags for automation."
+  ],
+  "not_included": [
+    "Adding unsupported methodologies.",
+    "Changing default init output shape beyond documented options.",
+    "Running provider CLIs from init."
+  ],
+  "acceptance": [
+    "init --interactive is guided and safe.",
+    "init without --interactive remains script-compatible.",
+    "spec create --interactive shows reviewable choices before writes.",
+    "No prompt opens in CI/no-TTY/JSON.",
+    "Methodology selector lists WDD + SDD only."
+  ],
+  "tests": [
+    "node --test tests/commands/init-profiles.test.js tests/commands/spec-create.test.js",
+    "git diff --check"
+  ],
+  "validation_hints": [
+    "Inject prompt responses in tests.",
+    "Do not prompt for values that existing flags already provide unless --interactive is explicit."
+  ],
+  "estimated_hours": 8,
+  "status": "completed",
+  "blocked_reason": null,
+  "actual_hours": 6,
+  "completed_at": "2026-05-27"
+}

package/specs/quiver-v30-interactive-cli-ux-agent-selection/slices/slice-08-tests-docs-cross-platform-release/CLOSURE_BRIEF.md

@@ -0,0 +1,34 @@
+# CLOSURE_BRIEF - slice-08 Tests, docs, cross-platform smokes, and release readiness
+
+## Summary
+
+Completed the v30 release-readiness pass: synchronized docs, updated generated command templates, recorded final evidence, validated the full suite and smoke commands, and verified package dry-run readiness without publishing to npm.
+
+## Validation Against Acceptance Criteria
+
+- [x] Full test suite passed.
+- [x] Smoke suites passed.
+- [x] Package smoke passed.
+- [x] npm pack dry-run passed.
+- [x] Docs synchronized.
+- [x] Evidence report completed.
+
+## Relevant Changes
+
+- Updated release-facing docs: `README.md`, `README_FOR_AI.md`, `ROADMAP.md`, `CHANGELOG.md`, and `docs/COMMANDS.md.template`.
+- Updated spec state: `STATUS.md`, `EVIDENCE_REPORT.md`, `pr.md`, and this slice closure metadata.
+- Confirmed that v30 is release-ready but not published.
+
+## Pending
+
+- Open PR if requested by the human.
+- Publish the npm package only after explicit release approval and npm authentication are confirmed.
+
+## Remaining Risks
+
+- Live provider smoke tests were not run against every external IA CLI because they depend on locally installed/authenticated providers.
+- Terminal rendering can vary by shell and OS, so final release notes should still mention that machine-readable modes remain the source of truth for scripts.
+
+## Future Recommendations
+
+Publish only after the human confirms release intent and npm authentication is ready.

package/specs/quiver-v30-interactive-cli-ux-agent-selection/slices/slice-08-tests-docs-cross-platform-release/EXECUTION_BRIEF.md

@@ -0,0 +1,59 @@
+# EXECUTION_BRIEF - slice-08 Tests, docs, cross-platform smokes, and release readiness
+
+## Context
+
+This slice closes v30. It must prove that the UX improvements work for humans without breaking automation or package publication.
+
+## Objective
+
+Validate the full v30 implementation and prepare release-ready evidence.
+
+## Scope
+
+- Full test suite.
+- Smoke suites.
+- Package smoke and `npm pack --dry-run`.
+- Docs, README, README_FOR_AI, ROADMAP, CHANGELOG.
+- Final evidence, status, and PR body updates.
+
+## Acceptance Criteria
+
+- Full tests pass.
+- Smoke suites pass.
+- Package/tarball checks pass.
+- Human vs machine output docs are accurate.
+- Cross-platform usage is documented.
+- Final evidence is recorded.
+
+## Plan tecnico resumido
+
+Treat this as release readiness: no new product behavior unless it fixes validation gaps from earlier slices.
+
+## Suggested Steps
+
+1. Audit all accepted criteria against implementation.
+2. Add missing tests or fixtures.
+3. Update docs and generated templates.
+4. Run full validations.
+5. Update evidence/status/pr body.
+6. Prepare package release notes.
+
+## Restrictions
+
+- Do not publish npm without explicit user request.
+- Do not expand scope beyond v30 acceptance criteria.
+- Do not leave failing validations unrecorded.
+
+## Risks
+
+- Cross-platform behavior can be hard to prove fully on one OS.
+- Package tarball may expose missing dependencies or unintended files.
+
+## Completion Checklist
+
+- [ ] Full tests pass.
+- [ ] Smoke suites pass.
+- [ ] Package smoke passes.
+- [ ] Docs updated.
+- [ ] Evidence report updated.
+- [ ] PR body ready.

package/specs/quiver-v30-interactive-cli-ux-agent-selection/slices/slice-08-tests-docs-cross-platform-release/slice.json

@@ -0,0 +1,95 @@
+{
+  "slice_id": "slice-08-tests-docs-cross-platform-release",
+  "ticket": "QUIVER-30-08",
+  "type": "release",
+  "title": "Tests, docs, cross-platform smokes, and release readiness",
+  "objective": "Close the v30 spec with comprehensive tests, documentation, cross-platform guidance, package readiness, and final evidence.",
+  "description": "Validates the complete UX/selector/model/progress contract across human and machine modes before publishing a package.",
+  "git": {
+    "branch_type": "feature",
+    "base_branch": "main",
+    "branch_slug": "v30-tests-docs-cross-platform-release",
+    "branch_name": "feature/QUIVER-30-08-v30-tests-docs-cross-platform-release"
+  },
+  "files": [
+    "README.md",
+    "README_FOR_AI.md",
+    "ROADMAP.md",
+    "CHANGELOG.md",
+    "docs/**",
+    "tests/**",
+    "scripts/ci/**",
+    "package.json",
+    "package-lock.json",
+    "specs/quiver-v30-interactive-cli-ux-agent-selection/**"
+  ],
+  "expected_read_paths": [
+    "SPEC.md",
+    "README_FOR_AI.md",
+    "docs/CLI_UX_GUIDE.md",
+    "docs/reference/commands.md",
+    "scripts/release-quiver.sh",
+    "scripts/package-quiver.sh",
+    "tests/**"
+  ],
+  "allowed_write_paths": [
+    "README.md",
+    "README_FOR_AI.md",
+    "ROADMAP.md",
+    "CHANGELOG.md",
+    "docs/**",
+    "tests/**",
+    "scripts/ci/**",
+    "package.json",
+    "package-lock.json",
+    "specs/quiver-v30-interactive-cli-ux-agent-selection/**"
+  ],
+  "depends_on": [
+    "slice-04-planner-ia-progress-flows",
+    "slice-05-executor-pr-progress-flows",
+    "slice-06-doctor-visual-json-contract",
+    "slice-07-interactive-init-spec-create"
+  ],
+  "parallel_safe": "no",
+  "parallel_safe_reason": "Final validation and docs depend on every previous slice.",
+  "must": [
+    "Add or update docs for the UX standard, agent selectors, model support, doctor output, and command examples.",
+    "Verify human output tests and machine output tests cover the accepted criteria.",
+    "Add cross-platform guidance for macOS, Linux, Windows PowerShell, Git Bash, and WSL where commands include paths or SSH examples.",
+    "Run full tests and smoke suites.",
+    "Run package safety and npm pack dry-run.",
+    "Update EVIDENCE_REPORT.md, STATUS.md, and pr.md with final evidence."
+  ],
+  "not_included": [
+    "Publishing npm without explicit release step.",
+    "Adding new product scope beyond approved slices.",
+    "Skipping failed tests to reach release."
+  ],
+  "acceptance": [
+    "Full test suite passes.",
+    "Smoke suites pass.",
+    "Package smoke and npm pack dry-run pass.",
+    "Docs clearly explain human vs machine output and selectors.",
+    "README and README_FOR_AI stay synchronized with implemented behavior.",
+    "Final evidence is recorded."
+  ],
+  "tests": [
+    "node --test tests/**/*.test.js",
+    "npm run smoke:create-quiver",
+    "npm run smoke:doctor-fixtures",
+    "npm run smoke:guided-workflow",
+    "npm run package:quiver",
+    "npm pack --dry-run",
+    "git diff --check",
+    "node bin/create-quiver.js spec validate specs/quiver-v30-interactive-cli-ux-agent-selection"
+  ],
+  "validation_hints": [
+    "Validate `npx create-quiver@file:<tarball>` behavior if package smoke supports it.",
+    "Document any manual live-provider smoke separately from automated tests."
+  ],
+  "estimated_hours": 8,
+  "status": "completed",
+  "blocked_reason": null,
+  "actual_hours": 5,
+  "completed_at": "2026-05-27"
+}