create-quiver 0.12.1 → 0.14.0

package/specs/quiver-v28-pixel-quiver-feedback-reconciliation/slices/slice-03-active-slice-reconciliation-and-ai-inspect/CLOSURE_BRIEF.md

@@ -0,0 +1,34 @@
+# CLOSURE BRIEF - slice-03: Active slice reconciliation and AI inspect
+
+## Summary
+
+Implemented active-slice reconciliation and spec-aware `ai inspect` recovery for the v28 Pixel Quiver feedback loop.
+
+## Validation
+
+Passed:
+
+- `node --test tests/commands/ai-export.test.js tests/commands/cli-contract.test.js`
+- `node --test tests/lib/project-state-resolver.test.js tests/lib/ai-export-state.test.js`
+
+## Relevant Changes
+
+- Added `collectActiveSliceState` in `src/create-quiver/lib/project-state-resolver.js` to read `docs/ai/ACTIVE_SLICE.md` and `ACTIVE_SLICES.md`.
+- Added reconciliation decisions: `preserve`, `close`, `replace`, and `blocked`.
+- Added `npx create-quiver ai active-slice status|reconcile`; `reconcile` is dry-run-first and currently refuses live writes.
+- Updated lifecycle export and inspect output to include active-slice state, blockers, dashboard data, and spec-aware next steps.
+- Added regression tests for conflicting active sources, missing active doc replacement, completed active slice closure, stale spec-create guidance, and CLI dry-run output.
+
+## Pending Work
+
+No pending work for this slice.
+
+## Remaining Risks
+
+- `ai active-slice reconcile` intentionally does not write changes yet. Future write mode should be implemented only with explicit safe file operations and backup behavior.
+- Active-slice Markdown parsing supports the current generated formats; unusual custom tables may still require manual correction.
+
+## Future Recommendations
+
+- Consider adding a future write-capable `ai active-slice reconcile --apply` only after the dry-run report is stable across real dogfooding projects.
+- Consider exposing active-slice state in any future dashboard/export consumer as a first-class readiness signal.

package/specs/quiver-v28-pixel-quiver-feedback-reconciliation/slices/slice-03-active-slice-reconciliation-and-ai-inspect/EXECUTION_BRIEF.md

@@ -0,0 +1,52 @@
+# EXECUTION BRIEF - slice-03: Active slice reconciliation and AI inspect
+
+## Context
+
+Pixel Quiver showed that active slice state can live in more than one file and that `ai inspect` can continue suggesting `spec create` after a spec exists by fallback.
+
+## Objective
+
+Make active-slice state inspectable, safely reconcilable, and reflected in AI inspection guidance.
+
+## Scope
+
+- Project state resolver.
+- AI inspect/export state.
+- Active slice status/reconciliation command surface if needed.
+- Tests and fixtures for conflicting active state.
+
+## Acceptance Criteria
+
+- All active-slice sources are detected.
+- Dry-run reconciliation is safe and explicit.
+- `ai inspect` does not recommend stale `spec create` when an existing spec should be validated or executed.
+- No worktrees or branches are deleted automatically.
+
+## Technical Plan Summary
+
+Extend the resolver to read active-slice sources, expose reconciliation states, and update AI inspect guidance.
+
+## Suggested Execution Steps
+
+1. Add fixtures for active-state conflicts.
+2. Extend resolver tests.
+3. Update inspect/export behavior.
+4. Add command/help updates if a new command surface is introduced.
+5. Validate no-write dry-run behavior.
+
+## Restrictions
+
+- Do not implement repair-plan logic.
+- Do not modify worktree lifecycle logic except for reading/reporting.
+
+## Risks
+
+- Existing generated projects may have partial active-slice files.
+
+## Completion Checklist
+
+- [ ] Resolver tests pass.
+- [ ] Inspect/export tests pass.
+- [ ] Dry-run behavior verified.
+- [ ] Docs/evidence updated.
+

package/specs/quiver-v28-pixel-quiver-feedback-reconciliation/slices/slice-03-active-slice-reconciliation-and-ai-inspect/slice.json

@@ -0,0 +1,82 @@
+{
+  "slice_id": "slice-03-active-slice-reconciliation-and-ai-inspect",
+  "ticket": "QUIVER-28-03",
+  "type": "feature",
+  "title": "Active slice reconciliation and AI inspect",
+  "objective": "Reconcile active slice state across multiple sources and make `ai inspect` recover from manual or fallback spec creation.",
+  "description": "Adds a safe, dry-run-first path for active-slice state and updates inspect guidance when specs already exist even if lifecycle state still points to spec creation.",
+  "git": {
+    "branch_type": "feature",
+    "base_branch": "main",
+    "branch_slug": "v28-active-slice-reconciliation-ai-inspect",
+    "branch_name": "feature/QUIVER-28-03-v28-active-slice-reconciliation-ai-inspect"
+  },
+  "files": [
+    "src/create-quiver/commands/ai.js",
+    "src/create-quiver/index.js",
+    "src/create-quiver/lib/project-state-resolver.js",
+    "src/create-quiver/lib/lifecycle.js",
+    "src/create-quiver/lib/statuses.js",
+    "src/create-quiver/lib/ai/export-state.js",
+    "tests/commands/ai-export.test.js",
+    "tests/commands/cli-contract.test.js",
+    "tests/lib/project-state-resolver.test.js",
+    "tests/lib/ai-export-state.test.js",
+    "specs/quiver-v28-pixel-quiver-feedback-reconciliation/**"
+  ],
+  "expected_read_paths": [
+    "src/create-quiver/lib/project-state-resolver.js",
+    "src/create-quiver/lib/lifecycle.js",
+    "src/create-quiver/commands/ai.js",
+    "tests/lib/project-state-resolver.test.js",
+    "tests/commands/ai-export.test.js"
+  ],
+  "allowed_write_paths": [
+    "src/create-quiver/commands/ai.js",
+    "src/create-quiver/index.js",
+    "src/create-quiver/lib/project-state-resolver.js",
+    "src/create-quiver/lib/lifecycle.js",
+    "src/create-quiver/lib/statuses.js",
+    "src/create-quiver/lib/ai/export-state.js",
+    "tests/commands/ai-export.test.js",
+    "tests/commands/cli-contract.test.js",
+    "tests/lib/project-state-resolver.test.js",
+    "tests/lib/ai-export-state.test.js",
+    "specs/quiver-v28-pixel-quiver-feedback-reconciliation/**"
+  ],
+  "depends_on": [
+    "slice-00-reconciliation-and-evidence-freeze",
+    "slice-01-ai-run-state-approvals-and-clean-output"
+  ],
+  "parallel_safe": "after_dependencies",
+  "parallel_safe_reason": "Can run after the run/approval model is clarified.",
+  "must": [
+    "Detect active slice state in docs/ai/ACTIVE_SLICE.md and ACTIVE_SLICES.md.",
+    "Return safe states: preserve, close, replace, blocked.",
+    "Keep reconciliation dry-run-first.",
+    "Update ai inspect next steps when specs exist by fallback/manual creation."
+  ],
+  "not_included": [
+    "Spec-create structured plan contract.",
+    "Worktree filesystem validation.",
+    "Deleting branches or worktrees automatically."
+  ],
+  "acceptance": [
+    "Active-slice state is reported from every supported source.",
+    "Reconciliation dry-run lists planned file changes and risks.",
+    "No state is changed without explicit write mode.",
+    "ai inspect suggests spec validate/next/prompt-slice when a spec already exists."
+  ],
+  "tests": [
+    "node --test tests/commands/ai-export.test.js tests/commands/cli-contract.test.js",
+    "node --test tests/lib/project-state-resolver.test.js tests/lib/ai-export-state.test.js"
+  ],
+  "validation_hints": [
+    "Use fixtures for conflicting active slice files.",
+    "Do not delete real worktrees in tests."
+  ],
+  "estimated_hours": 10,
+  "actual_hours": 10,
+  "status": "completed",
+  "completed_at": "2026-05-25T22:02:27Z"
+}

package/specs/quiver-v28-pixel-quiver-feedback-reconciliation/slices/slice-04-spec-validation-scope-and-worktree-reliability/CLOSURE_BRIEF.md

@@ -0,0 +1,32 @@
+# CLOSURE BRIEF - slice-04: Spec validation, scope, and worktree reliability
+
+## Summary
+
+Completed the validation and worktree reliability hardening for v28. `spec validate` now catches missing execution git metadata, `spec status` reports expected but unregistered worktree paths as stale, `spec start --dry-run` gives actionable dirty-checkout recovery, and scope matching has regression coverage for exact paths plus supported globs.
+
+## Validation
+
+Passed:
+
+- `node --test tests/commands/spec-validate.test.js tests/commands/spec-worktree.test.js`
+- `node --test tests/lib/check-slice.test.js tests/lib/scope.test.js tests/lib/paths.test.js`
+
+## Relevant Changes
+
+- `src/create-quiver/commands/spec.js` validates required `git.*` execution metadata in every slice.
+- `src/create-quiver/lib/spec-worktrees.js` detects unregistered expected worktree directories and improves dirty-checkout recovery output.
+- `tests/commands/spec-validate.test.js` covers missing execution git metadata.
+- `tests/commands/spec-worktree.test.js` covers unregistered expected worktree paths and actionable dirty checkout output.
+- `tests/lib/scope.test.js` covers exact path plus supported glob write scopes.
+
+## Pending Work
+
+None for this slice.
+
+## Remaining Risks
+
+- Tightened validation may surface older specs that do not declare execution git metadata. This is intentional for local execution readiness and is covered by v28 release-readiness follow-up.
+
+## Future Recommendations
+
+- Consider adding a dedicated migration/check command for older specs if users report friction after release.

package/specs/quiver-v28-pixel-quiver-feedback-reconciliation/slices/slice-04-spec-validation-scope-and-worktree-reliability/EXECUTION_BRIEF.md

@@ -0,0 +1,55 @@
+# EXECUTION BRIEF - slice-04: Spec validation, scope, and worktree reliability
+
+## Context
+
+Pixel Quiver showed false confidence: `spec validate` could pass while `check-slice` failed, and `spec status` could report a missing worktree as healthy.
+
+## Objective
+
+Make validation and worktree diagnostics match the real execution preconditions.
+
+## Scope
+
+- `spec validate`
+- `check-slice`
+- `check-scope`
+- `spec status`
+- `spec start --dry-run`
+- related tests
+
+## Acceptance Criteria
+
+- Slice metadata problems are caught at spec validation time.
+- Missing/stale worktrees are reported accurately.
+- Dirty checkout failures include files and safe options.
+- Scope matching is covered by regression tests.
+
+## Technical Plan Summary
+
+Align spec-level and slice-level validators, harden worktree checks against filesystem and Git state, and improve dirty checkout diagnostics.
+
+## Suggested Execution Steps
+
+1. Add failing tests for each observed false-ready case.
+2. Update validation helpers.
+3. Update worktree status/start diagnostics.
+4. Add scope matching tests.
+5. Run focused tests and full relevant command tests.
+
+## Restrictions
+
+- Do not mutate dirty worktrees.
+- Do not add destructive cleanup.
+- Do not change AI lifecycle behavior here.
+
+## Risks
+
+- Stricter validation can affect old specs; use warnings or `--strict` where needed.
+
+## Completion Checklist
+
+- [ ] Spec validation tests pass.
+- [ ] Worktree tests pass.
+- [ ] Scope tests pass.
+- [ ] Backward compatibility behavior documented.
+

package/specs/quiver-v28-pixel-quiver-feedback-reconciliation/slices/slice-04-spec-validation-scope-and-worktree-reliability/slice.json

@@ -0,0 +1,85 @@
+{
+  "slice_id": "slice-04-spec-validation-scope-and-worktree-reliability",
+  "ticket": "QUIVER-28-04",
+  "type": "feature",
+  "title": "Spec validation, scope, and worktree reliability",
+  "objective": "Align spec validation with slice execution preconditions and make worktree/scope diagnostics reflect the real filesystem and Git state.",
+  "description": "Hardens `spec validate`, `check-slice`, `check-scope`, `spec status`, and `spec start` so users do not get false readiness signals.",
+  "git": {
+    "branch_type": "feature",
+    "base_branch": "main",
+    "branch_slug": "v28-spec-validation-scope-worktree-reliability",
+    "branch_name": "feature/QUIVER-28-04-v28-spec-validation-scope-worktree-reliability"
+  },
+  "files": [
+    "src/create-quiver/commands/spec.js",
+    "src/create-quiver/lib/readiness.js",
+    "src/create-quiver/lib/scope.js",
+    "src/create-quiver/lib/slice.js",
+    "src/create-quiver/lib/spec-worktrees.js",
+    "src/create-quiver/lib/git.js",
+    "tests/commands/spec-validate.test.js",
+    "tests/commands/spec-worktree.test.js",
+    "tests/lib/check-slice.test.js",
+    "tests/lib/scope.test.js",
+    "tests/lib/paths.test.js",
+    "specs/quiver-v28-pixel-quiver-feedback-reconciliation/**"
+  ],
+  "expected_read_paths": [
+    "src/create-quiver/commands/spec.js",
+    "src/create-quiver/lib/readiness.js",
+    "src/create-quiver/lib/scope.js",
+    "src/create-quiver/lib/spec-worktrees.js",
+    "tests/commands/spec-*.test.js",
+    "tests/lib/check-slice.test.js",
+    "tests/lib/scope.test.js"
+  ],
+  "allowed_write_paths": [
+    "src/create-quiver/commands/spec.js",
+    "src/create-quiver/lib/readiness.js",
+    "src/create-quiver/lib/scope.js",
+    "src/create-quiver/lib/slice.js",
+    "src/create-quiver/lib/spec-worktrees.js",
+    "src/create-quiver/lib/git.js",
+    "tests/commands/spec-validate.test.js",
+    "tests/commands/spec-worktree.test.js",
+    "tests/lib/check-slice.test.js",
+    "tests/lib/scope.test.js",
+    "tests/lib/paths.test.js",
+    "specs/quiver-v28-pixel-quiver-feedback-reconciliation/**"
+  ],
+  "depends_on": [
+    "slice-00-reconciliation-and-evidence-freeze"
+  ],
+  "parallel_safe": "after_dependencies",
+  "parallel_safe_reason": "Can run after slice-00 if it does not alter AI run state files.",
+  "must": [
+    "Make spec validate catch local slice execution metadata problems.",
+    "Make spec status verify filesystem and git worktree list.",
+    "Make spec start dirty-check failures actionable.",
+    "Verify scope matching behavior and support expected globs if slice-00 confirms the gap."
+  ],
+  "not_included": [
+    "AI approval lifecycle changes.",
+    "Plan repair flow.",
+    "Deleting worktrees automatically."
+  ],
+  "acceptance": [
+    "spec validate catches slice metadata required by check-slice --local or reports strict warnings.",
+    "spec status reports missing/stale worktrees accurately.",
+    "spec start --dry-run lists dirty checkout blockers and safe options.",
+    "check-scope behavior is covered by tests for exact paths and supported globs."
+  ],
+  "tests": [
+    "node --test tests/commands/spec-validate.test.js tests/commands/spec-worktree.test.js",
+    "node --test tests/lib/check-slice.test.js tests/lib/scope.test.js tests/lib/paths.test.js"
+  ],
+  "validation_hints": [
+    "Use temp repos/worktrees in tests.",
+    "Keep default behavior backward compatible unless --strict is used."
+  ],
+  "estimated_hours": 9,
+  "actual_hours": 9,
+  "status": "completed",
+  "completed_at": "2026-05-25T15:38:16Z"
+}

package/specs/quiver-v28-pixel-quiver-feedback-reconciliation/slices/slice-05-review-plan-closure-and-agent-dx/CLOSURE_BRIEF.md

@@ -0,0 +1,35 @@
+# CLOSURE BRIEF - slice-05: Review-plan closure and agent DX
+
+## Summary
+
+Implemented structured plan-review closure metadata and agent-facing DX hardening for review, executor handoff context, command examples, and GitHub PR preflight guidance.
+
+## Validation
+
+Passed:
+
+- `node --test tests/commands/ai-review-plan.test.js tests/commands/cli-contract.test.js`
+- `node --test tests/lib/ai-context-packs.test.js tests/lib/ai-github.test.js`
+
+## Relevant Changes
+
+- `ai review-plan` now asks for and persists structured review metadata with `approve`, `approve-with-risk`, or `revise`.
+- `ai approve --phase technical-plan` now refuses approval when the saved review has required fixes or a `revise` recommendation.
+- Plan-review summaries include approval recommendation, blocking status, required fixes, optional hardening, and next command.
+- Executor context-pack guidance now keeps agents on compact slice context by default.
+- GitHub CLI and SSH alias guidance now covers macOS, Linux, Windows PowerShell, Git Bash, and WSL.
+- Help and docs now include `npx --yes create-quiver@<version>` examples for commands pasted into agents.
+
+## Pending Work
+
+No pending work for this slice. `slice-06` is now ready for final compatibility, docs, smoke, and release-readiness validation.
+
+## Remaining Risks
+
+- Existing historical plan reviews without structured metadata are treated heuristically for backward compatibility.
+- Provider output can still be malformed; the prompt now asks for JSON, but fallback classification remains intentionally conservative.
+
+## Future Recommendations
+
+- Consider a future explicit `--json` mode for `ai review-plan` summaries if dashboard consumers need stable stdout.
+- Consider adding an apply/fix loop around plan-review required fixes after more dogfooding evidence.

package/specs/quiver-v28-pixel-quiver-feedback-reconciliation/slices/slice-05-review-plan-closure-and-agent-dx/EXECUTION_BRIEF.md

@@ -0,0 +1,59 @@
+# EXECUTION BRIEF - slice-05: Review-plan closure and agent DX
+
+## Context
+
+Pixel Quiver showed long review/revise loops without a formal signal for when a plan is approvable, approvable with risks, or blocked.
+The reconciliation pass also mapped agent-facing command safety, compact executor handoff guidance, and GitHub auth/SSH alias recovery copy to this slice.
+
+## Objective
+
+Make plan reviews actionable and make generated agent commands reproducible and non-interactive.
+
+## Scope
+
+- `ai review-plan` output and metadata.
+- Review prompt/contract.
+- Agent-facing command examples.
+- GitHub auth and SSH alias diagnostic copy used by agent-driven PR flows.
+- Compact executor handoff guidance/context packaging.
+- Tests for review recommendations.
+
+## Acceptance Criteria
+
+- Review output includes structured blocking status and approval recommendation.
+- Required fixes and optional hardening are separated.
+- A recommended next command is available.
+- Docs/help examples prefer `npx --yes create-quiver@<version>` where appropriate.
+- GitHub auth and alias diagnostics provide actionable recovery across macOS, Linux, Windows, Git Bash, WSL, and PowerShell where applicable.
+- Executor handoff guidance stays compact and does not require passing the full spec when the slice brief is enough.
+
+## Technical Plan Summary
+
+Extend plan review persistence/output with structured metadata, then update prompt/help/docs, GitHub diagnostic copy, and context-pack guidance for safer agent execution.
+
+## Suggested Execution Steps
+
+1. Add fixtures for review classifications.
+2. Update review-plan parsing/persistence.
+3. Update CLI output and docs.
+4. Improve GitHub auth/alias recovery messaging where gaps are confirmed.
+5. Add tests for recommended next command and agent-facing recovery copy.
+6. Validate help output snapshots if applicable.
+
+## Restrictions
+
+- Do not weaken approval gates.
+- Do not implement repair-plan here.
+- Do not store provider, GitHub, or SSH secrets.
+
+## Risks
+
+- Provider text can be inconsistent; metadata generation must be resilient and testable.
+
+## Completion Checklist
+
+- [ ] Review-plan tests pass.
+- [ ] GitHub diagnostic tests pass if messaging changes.
+- [ ] CLI help/docs updated.
+- [ ] Agent command examples verified.
+- [ ] Closure evidence updated.

package/specs/quiver-v28-pixel-quiver-feedback-reconciliation/slices/slice-05-review-plan-closure-and-agent-dx/slice.json

@@ -0,0 +1,94 @@
+{
+  "slice_id": "slice-05-review-plan-closure-and-agent-dx",
+  "ticket": "QUIVER-28-05",
+  "type": "feature",
+  "title": "Review-plan closure and agent DX",
+  "objective": "Add structured review-plan closure metadata and make generated commands safer for AI agents.",
+  "description": "Reduces review/revise loops by making review results machine-readable and improves agent command examples with non-interactive, versioned npx usage.",
+  "git": {
+    "branch_type": "feature",
+    "base_branch": "main",
+    "branch_slug": "v28-review-plan-closure-agent-dx",
+    "branch_name": "feature/QUIVER-28-05-v28-review-plan-closure-agent-dx"
+  },
+  "files": [
+    "src/create-quiver/commands/ai.js",
+    "src/create-quiver/index.js",
+    "src/create-quiver/lib/ai/plan-review.js",
+    "src/create-quiver/lib/ai/prompts.js",
+    "src/create-quiver/lib/ai/context-packs.js",
+    "src/create-quiver/lib/ai/github.js",
+    "README.md",
+    "README_FOR_AI.md",
+    "docs/COMMANDS.md.template",
+    "tests/commands/ai-review-plan.test.js",
+    "tests/commands/cli-contract.test.js",
+    "tests/lib/ai-context-packs.test.js",
+    "tests/lib/ai-github.test.js",
+    "specs/quiver-v28-pixel-quiver-feedback-reconciliation/**"
+  ],
+  "expected_read_paths": [
+    "src/create-quiver/lib/ai/plan-review.js",
+    "src/create-quiver/lib/ai/prompts.js",
+    "src/create-quiver/index.js",
+    "README.md",
+    "README_FOR_AI.md",
+    "docs/COMMANDS.md.template",
+    "tests/commands/ai-review-plan.test.js"
+  ],
+  "allowed_write_paths": [
+    "src/create-quiver/commands/ai.js",
+    "src/create-quiver/index.js",
+    "src/create-quiver/lib/ai/plan-review.js",
+    "src/create-quiver/lib/ai/prompts.js",
+    "src/create-quiver/lib/ai/context-packs.js",
+    "src/create-quiver/lib/ai/github.js",
+    "README.md",
+    "README_FOR_AI.md",
+    "docs/COMMANDS.md.template",
+    "tests/commands/ai-review-plan.test.js",
+    "tests/commands/cli-contract.test.js",
+    "tests/lib/ai-context-packs.test.js",
+    "tests/lib/ai-github.test.js",
+    "specs/quiver-v28-pixel-quiver-feedback-reconciliation/**"
+  ],
+  "depends_on": [
+    "slice-00-reconciliation-and-evidence-freeze",
+    "slice-01-ai-run-state-approvals-and-clean-output"
+  ],
+  "parallel_safe": "after_dependencies",
+  "parallel_safe_reason": "Can run after clean AI state is clarified; may need sequencing with slice-02 if prompt files overlap.",
+  "must": [
+    "Emit review metadata with blocking status and recommendation.",
+    "Separate required fixes from optional hardening.",
+    "Include recommended next command.",
+    "Update agent-facing examples to prefer npx --yes create-quiver@<version>.",
+    "Improve GitHub auth and SSH alias recovery guidance for agent-driven PR flows.",
+    "Document or generate compact executor handoff context without requiring the full spec."
+  ],
+  "not_included": [
+    "Spec create repair flow.",
+    "Active-slice reconciliation.",
+    "Provider credential management."
+  ],
+  "acceptance": [
+    "ai review-plan outputs structured metadata for approval decisions.",
+    "Review loops can be stopped based on blocking/optional classification.",
+    "Generated docs/help include non-interactive versioned examples for agents.",
+    "GitHub auth and alias diagnostics include actionable recovery for macOS, Linux, Windows, Git Bash, WSL, and PowerShell where applicable.",
+    "Executor-facing handoff guidance stays compact and avoids requiring full-spec context.",
+    "Tests cover approve, approve-with-risk, and revise recommendations."
+  ],
+  "tests": [
+    "node --test tests/commands/ai-review-plan.test.js tests/commands/cli-contract.test.js",
+    "node --test tests/lib/ai-context-packs.test.js tests/lib/ai-github.test.js"
+  ],
+  "validation_hints": [
+    "Keep human-readable review output useful.",
+    "Ensure --json output stays machine-parseable if present."
+  ],
+  "estimated_hours": 8,
+  "actual_hours": 8,
+  "status": "completed",
+  "completed_at": "2026-05-25T22:14:57Z"
+}

package/specs/quiver-v28-pixel-quiver-feedback-reconciliation/slices/slice-06-backward-compatibility-docs-and-release-readiness/CLOSURE_BRIEF.md

@@ -0,0 +1,40 @@
+# CLOSURE BRIEF - slice-06: Backward compatibility, docs, and release readiness
+
+## Summary
+
+Closed v28 with documentation synchronization, full source test evidence, smoke coverage, package/tarball readiness checks, and final spec status updates. A package dry-run exposed that a local root PDF would be included in npm output, so `.npmignore` was updated to exclude `*.pdf`.
+
+## Validation
+
+Passed:
+
+- `node --test tests/**/*.test.js`
+- `npm run smoke:doctor-fixtures`
+- `npm run smoke:guided-workflow`
+- `npm run smoke:create-quiver`
+- `npm run package:quiver`
+- `npm pack --dry-run --json` with a no-PDF assertion
+- `git diff --check`
+- `node bin/create-quiver.js spec validate specs/quiver-v28-pixel-quiver-feedback-reconciliation --strict`
+- `node bin/create-quiver.js check-slice --local specs/quiver-v28-pixel-quiver-feedback-reconciliation/slices/slice-06-backward-compatibility-docs-and-release-readiness/slice.json`
+- `node bin/create-quiver.js next --all-ready --spec quiver-v28-pixel-quiver-feedback-reconciliation`
+
+## Relevant Changes
+
+- Added unreleased v28 release notes to `CHANGELOG.md`.
+- Updated `ROADMAP.md`, `README.md`, `docs/WORKFLOW.md.template`, and `docs/TROUBLESHOOTING.md.template` to reflect implemented v28 behavior.
+- Added `*.pdf` to `.npmignore` after tarball validation showed the local Pixel Quiver requirements PDF would otherwise be included.
+- Completed `SPEC.md`, `STATUS.md`, `COVERAGE_MATRIX.md`, `EVIDENCE_REPORT.md`, and this closure brief for v28.
+
+## Pending Work
+
+No pending work for this slice. npm publication and PR creation remain intentionally out of scope.
+
+## Remaining Risks
+
+- `package.json` remains `0.13.0`; v28 changes are documented as unreleased until a future publication decision.
+- Future local artifacts with extensions other than `.pdf` could still require package ignore or package-safety rules.
+
+## Future Recommendations
+
+Consider a future Quiver command that reports package-version drift and package contents risk before publication.

package/specs/quiver-v28-pixel-quiver-feedback-reconciliation/slices/slice-06-backward-compatibility-docs-and-release-readiness/EXECUTION_BRIEF.md

@@ -0,0 +1,56 @@
+# EXECUTION BRIEF - slice-06: Backward compatibility, docs, and release readiness
+
+## Context
+
+After implementation slices, Quiver must prove the final behavior works with older generated project state and is accurately documented.
+
+## Objective
+
+Close v28 with compatibility tests, docs synchronization, smoke evidence, and final coverage status.
+
+## Scope
+
+- Source-of-truth docs.
+- Command templates and troubleshooting docs.
+- Smoke scripts/tests if needed.
+- Final spec status, evidence, and PR body.
+
+## Acceptance Criteria
+
+- Every finding has a final status and evidence.
+- Docs match implemented behavior.
+- Source tests and available smoke tests pass.
+- Package/tarball smoke evidence is recorded.
+- npm is not published and PR is not opened by this slice.
+
+## Technical Plan Summary
+
+Run full validation, update docs, complete final evidence, and prepare release readiness without performing release actions.
+
+## Suggested Execution Steps
+
+1. Read closure briefs from slices 01-05.
+2. Complete the final coverage matrix.
+3. Update README/README_FOR_AI/ROADMAP/CHANGELOG as needed.
+4. Run full tests and smoke tests.
+5. Run package/tarball smoke if available.
+6. Close final status/evidence.
+
+## Restrictions
+
+- Do not publish npm.
+- Do not open PR.
+- Do not change package version unless explicitly authorized.
+
+## Risks
+
+- Package smoke can reveal packaging issues not visible in source tests.
+
+## Completion Checklist
+
+- [ ] Full tests passed.
+- [ ] Smoke tests passed.
+- [ ] Package/tarball smoke passed or documented.
+- [ ] Docs synced.
+- [ ] Final matrix completed.
+