create-quiver 0.13.0 → 0.14.1

package/specs/quiver-v28-pixel-quiver-feedback-reconciliation/EVIDENCE_REPORT.md

@@ -0,0 +1,200 @@
+# Evidence Report - Quiver v28 Pixel Quiver Feedback Reconciliation
+
+## slice-00-reconciliation-and-evidence-freeze
+
+Completed on 2026-05-25.
+
+### Source Evidence Frozen
+
+The following Pixel Quiver files were treated as evidence inputs only. They were not copied into fixtures.
+
+| Source | SHA-256 | Modified |
+|---|---|---|
+| `/Users/fabrijk/Documents/Work/Proyectos Personales/nika/Pixel Quiver/QUIVER_PROBLEMS.md` | `516d8928af437fc3d20cacfe50fb78752954eb59b6dace6860cdda820aa6701d` | 2026-05-25 03:29:24 -03 |
+| `/Users/fabrijk/Documents/Work/Proyectos Personales/nika/Pixel Quiver/QUIVER_IMPROVEMENT_SUGGESTIONS.md` | `43c4bfbef68fc8343b7f905f299c53716b55abcace415c9ce1088aa53ac12949` | 2026-05-25 03:29:39 -03 |
+| `/Users/fabrijk/Documents/Work/Proyectos Personales/nika/Pixel Quiver/QUIVER_FRAMEWORK_IMPROVEMENTS.md` | `7a4eb66a996fc44cce80df4907a948fbef3e780a5f8fc856a6bdc2b0bd1f1ea3` | 2026-05-25 03:29:53 -03 |
+
+Detected IDs:
+
+- `QP-001` to `QP-028`
+- `QIS-001` to `QIS-031`
+- Narrative framework-improvement sections without stable IDs
+
+### Repository Evidence Inspected
+
+- `README_FOR_AI.md`
+- `ROADMAP.md`
+- `BACKLOG.md`
+- `CHANGELOG.md`
+- `specs/quiver-v27-reliability-ai-workflow-hardening/COVERAGE_MATRIX.md`
+- `specs/quiver-v27-reliability-ai-workflow-hardening/STATUS.md`
+- `specs/quiver-v27-reliability-ai-workflow-hardening/EVIDENCE_REPORT.md`
+- `src/create-quiver/commands/spec.js`
+- `src/create-quiver/commands/ai.js`
+- `src/create-quiver/lib/ai/run-state.js`
+- `src/create-quiver/lib/ai/export-state.js`
+- `src/create-quiver/lib/ai/plan-review.js`
+- `src/create-quiver/lib/approvals.js`
+- `src/create-quiver/lib/spec-worktrees.js`
+- `src/create-quiver/lib/lifecycle.js`
+- Focused tests under `tests/commands/*` and `tests/lib/*`
+
+### Reconciliation Outcome
+
+- v27 is documented as complete and covers many earlier findings (`QP-001` to `QP-019`, `QIS-001` to `QIS-022`), but several later Pixel Quiver findings expose gaps that v27 either did not intend to solve or only partially solved.
+- Confirmed no product-code change is required for `slice-00`.
+- The final execution mapping is now captured in `COVERAGE_MATRIX.md`.
+- `slice-01` and `slice-04` are the only implementation slices ready immediately after `slice-00`.
+
+## Final Release-Readiness Evidence
+
+`slice-06` completed the pending final checks for source compatibility, generated docs, smoke coverage, and package contents.
+
+## Validation Evidence for slice-00
+
+Passed:
+
+- `git diff --check`
+- JSON parse validation for all v28 `slice.json` files
+- `node bin/create-quiver.js spec validate specs/quiver-v28-pixel-quiver-feedback-reconciliation`
+- `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-00-reconciliation-and-evidence-freeze/slice.json`
+- `node bin/create-quiver.js next --all-ready --spec quiver-v28-pixel-quiver-feedback-reconciliation`
+- `node bin/create-quiver.js plan --spec quiver-v28-pixel-quiver-feedback-reconciliation --json`
+
+Ready slices reported after `slice-00`:
+
+- `slice-01-ai-run-state-approvals-and-clean-output`
+- `slice-04-spec-validation-scope-and-worktree-reliability`
+
+## slice-01-ai-run-state-approvals-and-clean-output
+
+Completed on 2026-05-25.
+
+### Implementation Evidence
+
+- Updated `src/create-quiver/commands/ai.js` so successful provider-backed planner commands print clean extracted output instead of raw stdout/stderr.
+- Preserved raw provider artifact persistence and redaction for `ai plan` and `ai review-plan`.
+- Updated `ai approvals` output to separate run-scoped approvals, active run, global planner approvals, and run relation.
+- Added `ai run close --run <id>` to close/archive stale runs without deleting `.quiver/runs/<id>` evidence.
+- Updated `src/create-quiver/lib/ai/run-state.js` so `ai status` reports the number of open runs and lists other open runs with next safe commands.
+
+### Validation Evidence
+
+Passed:
+
+- `node --test tests/commands/ai-run-state.test.js tests/commands/ai-plan.test.js tests/commands/ai-export.test.js tests/commands/cli-contract.test.js`
+- `node --test tests/lib/ai-run-state.test.js tests/lib/approvals.test.js tests/lib/ai-export-state.test.js`
+
+## slice-04-spec-validation-scope-and-worktree-reliability
+
+Completed on 2026-05-25.
+
+### Implementation Evidence
+
+- Updated `src/create-quiver/commands/spec.js` so `spec validate` rejects slices missing execution git metadata required by local slice execution: `git.branch_type`, `git.base_branch`, `git.branch_slug`, and `git.branch_name`.
+- Updated `src/create-quiver/lib/spec-worktrees.js` so `spec status` reports expected worktree paths that exist on disk but are not registered in `git worktree list` as missing/stale.
+- Updated dirty checkout failures in `spec start --dry-run` to list blocking dirty files and safe recovery options without modifying state.
+- Added regression coverage for exact path plus supported glob scope matching.
+
+### Validation Evidence
+
+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`
+
+## slice-02-structured-technical-plan-contract-and-repair-flow
+
+Completed on 2026-05-25.
+
+### Implementation Evidence
+
+- Updated `src/create-quiver/commands/ai.js` so technical-plan prompts require a fenced structured JSON contract with `spec.slices[]`.
+- Added approval-time validation for `ai approve --phase technical-plan` so invalid drafts fail before `approved.md` is written.
+- Added `ai repair-plan` to repair legacy approved technical plans missing `spec.slices[]` into a new provider-backed draft without mutating the approved artifact.
+- Added shared `validateTechnicalPlanSpecContract` in `src/create-quiver/lib/ai/spec-generator.js`.
+- Updated CLI help and dispatch so `ai repair-plan --dry-run` and `--print-prompt` are first-class commands.
+
+### Validation Evidence
+
+Passed:
+
+- `node --test tests/commands/ai-plan.test.js tests/commands/ai-plan-spec-phase.test.js tests/commands/spec-create.test.js`
+- `node --test tests/commands/ai-review-plan.test.js tests/commands/flow.test.js tests/commands/cli-contract.test.js`
+- `node --test tests/lib/ai-spec-generator.test.js tests/lib/approvals.test.js`
+
+## slice-03-active-slice-reconciliation-and-ai-inspect
+
+Completed on 2026-05-25.
+
+### Implementation Evidence
+
+- Added resolver-backed active-slice source collection for `docs/ai/ACTIVE_SLICE.md` and `ACTIVE_SLICES.md`.
+- Added canonical reconciliation decisions: `preserve`, `close`, `replace`, and `blocked`.
+- Added `ai active-slice status|reconcile` with dry-run-first behavior; live reconcile currently refuses writes.
+- Updated `ai inspect`/lifecycle export so existing specs take precedence over stale `spec create --dry-run` lifecycle guidance.
+- Added active-slice state to lifecycle export summary, dashboard data, blockers, and human inspect output.
+- Hardened `ACTIVE_SLICES.md` table parsing so Markdown separator rows are ignored.
+
+### Validation Evidence
+
+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`
+
+## slice-05-review-plan-closure-and-agent-dx
+
+Completed on 2026-05-25.
+
+### Implementation Evidence
+
+- Added structured `review_result` metadata to saved plan reviews with `approve`, `approve-with-risk`, and `revise` recommendations.
+- Updated the review prompt to require a fenced JSON review contract.
+- Updated `ai approve --phase technical-plan` to block reviews with required fixes or `revise` recommendation.
+- Updated `ai approvals`/plan-review summary to include approval recommendation, blocking status, required fixes, optional hardening, and next command.
+- Updated executor context-pack guidance to avoid full-spec context unless explicitly required.
+- Added shell-specific GitHub CLI install and SSH alias setup guidance for macOS, Linux, Windows PowerShell, Git Bash, and WSL.
+- Added agent-facing non-interactive `npx --yes create-quiver@<version>` examples to help and docs.
+
+### Validation Evidence
+
+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`
+
+## slice-06-backward-compatibility-docs-and-release-readiness
+
+Completed on 2026-05-25.
+
+### Implementation Evidence
+
+- Updated `CHANGELOG.md` with unreleased v28 additions, changes, and fixes without claiming npm publication.
+- Updated `ROADMAP.md` so v28 is visible as an unreleased reconciliation/release-readiness milestone.
+- Updated `README.md`, `docs/WORKFLOW.md.template`, and `docs/TROUBLESHOOTING.md.template` to match implemented review-plan, active-slice, and pinned agent-command behavior.
+- Expanded `slice-06` scope to include `.npmignore` after package dry-run evidence showed a local requirements PDF would otherwise be included in the npm tarball.
+- Updated `.npmignore` to exclude local `*.pdf` files from published packages.
+
+### Validation Evidence
+
+Passed:
+
+- `node --test tests/**/*.test.js` (`376` tests passed)
+- `npm run smoke:doctor-fixtures` (`13` doctor fixture states passed)
+- `npm run smoke:guided-workflow`
+- `npm run smoke:create-quiver`
+- `npm run package:quiver`
+- `npm pack --dry-run --json` with a follow-up assertion that no `.pdf` files are included (`543` files)
+- `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`
+
+### Release Notes
+
+- npm publication was not performed.
+- PR creation was not performed.
+- `package.json` version remains `0.13.0`.
+- Pre-fix package evidence showed `Quiver_Spec_Viewer_requisitos.pdf` would be packed. The file was left in the working tree and excluded through `.npmignore`.

package/specs/quiver-v28-pixel-quiver-feedback-reconciliation/EXECUTION_PLAN.md

@@ -0,0 +1,60 @@
+# Execution Plan - Quiver v28 Pixel Quiver Feedback Reconciliation
+
+## Execution Order
+
+```mermaid
+flowchart TD
+    S00[slice-00: Reconciliation and evidence freeze]
+    S01[slice-01: AI run state, approvals, and clean output]
+    S02[slice-02: Structured technical plan contract and repair flow]
+    S03[slice-03: Active slice reconciliation and AI inspect]
+    S04[slice-04: Spec validation, scope, and worktree reliability]
+    S05[slice-05: Review-plan closure and agent DX]
+    S06[slice-06: Backward compatibility, docs, and release readiness]
+
+    S00 --> S01
+    S00 --> S04
+    S01 --> S02
+    S01 --> S03
+    S01 --> S05
+    S02 --> S06
+    S03 --> S06
+    S04 --> S06
+    S05 --> S06
+```
+
+## Waves
+
+### Wave 0 - Sequential
+
+1. `slice-00-reconciliation-and-evidence-freeze`
+
+This slice must run first. It decides what is already resolved, what is pending, and what must not be reimplemented.
+
+### Wave 1 - Parallel after slice-00
+
+- `slice-01-ai-run-state-approvals-and-clean-output`
+- `slice-04-spec-validation-scope-and-worktree-reliability`
+
+These can run in parallel because their primary write scopes are different.
+
+### Wave 2 - Parallel after slice-01
+
+- `slice-02-structured-technical-plan-contract-and-repair-flow`
+- `slice-03-active-slice-reconciliation-and-ai-inspect`
+- `slice-05-review-plan-closure-and-agent-dx`
+
+These depend on the run/approval model being clarified.
+
+### Wave 3 - Sequential close
+
+1. `slice-06-backward-compatibility-docs-and-release-readiness`
+
+This slice must run last because it validates compatibility, docs, package smoke, and final coverage.
+
+## Parallel Safety Notes
+
+- Do not run slices in parallel if `slice-00` finds that their write scopes overlap more than currently expected.
+- `slice-02` and `slice-05` may both touch planning prompts; if `slice-00` identifies overlap, run `slice-02` before `slice-05`.
+- `slice-06` is never parallel-safe.
+

package/specs/quiver-v28-pixel-quiver-feedback-reconciliation/SPEC.md

@@ -0,0 +1,132 @@
+# Quiver v28 - Pixel Quiver Feedback Reconciliation
+
+**Date:** 2026-05-25
+**Status:** Completed
+**Source:** Pixel Quiver dogfooding follow-up after `create-quiver@0.13.0`
+
+Slice numbering resets here. This spec intentionally starts at `slice-00`.
+
+## Problem
+
+Pixel Quiver produced a second set of framework feedback after Quiver v27 shipped in `create-quiver@0.13.0`. The repository source of truth says v27 already covered `QP-001` to `QP-019` and `QIS-001` to `QIS-022`, but the Pixel Quiver files still list several of those items as open and add later issues around `spec create`, repair flows, active-slice reconciliation, worktrees, and `ai inspect`.
+
+The risk is implementing duplicate fixes or missing regressions. Quiver needs a reconciliation-first spec that verifies what v27 truly covers, then fixes only the remaining, partial, regressed, or newly observed gaps.
+
+## Objective
+
+Reconcile Pixel Quiver feedback against the current Quiver implementation, then harden the unresolved workflow gaps across AI runs, approvals, structured technical plans, active-slice state, spec validation, worktrees, plan reviews, agent DX, documentation, and release readiness.
+
+## Evidence Sources
+
+Primary input files:
+
+- `/Users/fabrijk/Documents/Work/Proyectos Personales/nika/Pixel Quiver/QUIVER_PROBLEMS.md`
+- `/Users/fabrijk/Documents/Work/Proyectos Personales/nika/Pixel Quiver/QUIVER_IMPROVEMENT_SUGGESTIONS.md`
+- `/Users/fabrijk/Documents/Work/Proyectos Personales/nika/Pixel Quiver/QUIVER_FRAMEWORK_IMPROVEMENTS.md`
+
+Repository source-of-truth files:
+
+- `README_FOR_AI.md`
+- `ROADMAP.md`
+- `BACKLOG.md`
+- `specs/quiver-v27-reliability-ai-workflow-hardening/**`
+
+## Core Decisions
+
+- Do not reimplement v27 behavior blindly.
+- `slice-00` must freeze and reconcile evidence before implementation slices start.
+- Each finding must end as `verified-resolved`, `fixed`, `documented-risk`, `duplicate`, or `out-of-scope-with-reason`.
+- No npm publication or PR creation is included in this spec.
+- Changes must remain backward compatible by default unless a stricter mode is explicitly documented.
+- `--dry-run` behavior must remain read-only.
+- Machine-readable output must be valid without stripping human logs.
+
+## Scope
+
+### Included
+
+- Reconciliation matrix for all supplied Pixel Quiver `QP-*`, `QIS-*`, and framework improvement sections.
+- AI run lifecycle and approval clarity.
+- Clean AI command output and raw provider log persistence.
+- Structured `spec.slices[]` contract for technical plans.
+- Safe repair path for approved technical plans with missing structure.
+- Active-slice multi-source reconciliation.
+- `ai inspect` behavior after manual/fallback spec creation.
+- `spec validate`, `check-slice`, `spec status`, `spec start`, scope, and worktree reliability.
+- Structured `ai review-plan` closure metadata.
+- Agent command DX using `npx --yes create-quiver@<version>`.
+- Cross-platform help, docs, fixtures, tests, smoke coverage, and release readiness.
+
+### Excluded
+
+- Pixel Quiver application changes.
+- Building a web dashboard inside Quiver core.
+- Publishing npm.
+- Opening a PR.
+- Removing legacy compatibility without migration.
+- Storing provider credentials.
+
+## Acceptance Criteria
+
+1. Given v27 claims coverage for earlier findings, when `slice-00` completes, then every supplied finding is classified with evidence as resolved, partial, pending, regression, duplicate, or out of scope.
+2. Given a finding is already resolved by v27, when the final matrix is produced, then it is not reimplemented unless a regression test proves it still fails.
+3. Given a finding is pending or partial, when implementation starts, then it is mapped to exactly one primary slice and at least one validation artifact.
+4. Given an AI run is active, when another run is created or inspected, then Quiver avoids mixing scopes and shows the next safe action.
+5. Given approvals exist across multiple runs, when `ai approvals` runs, then active, historical, stale, orphaned, and run-specific approvals are distinguishable.
+6. Given `ai onboard`, `ai plan`, or provider-backed commands run, when output is shown, then useful human output is separated from raw logs and redacted raw artifacts are persisted separately.
+7. Given a technical plan is generated, when it is approved or used by `spec create`, then it contains a parseable structured `spec.slices[]` contract or fails before writing files.
+8. Given an approved plan lacks required structure, when the user requests repair, then Quiver can create a derived draft without mutating the approved artifact and requires review plus approval.
+9. Given active slice state exists in multiple files, when reconciliation runs, then Quiver reports all sources and supports safe dry-run decisions: preserve, close, replace, or block.
+10. Given a spec was created manually or by fallback, when `ai inspect` runs, then it reconciles existing specs and suggests `spec validate`, `next`, or `ai prompt-slice` instead of stale `spec create`.
+11. Given `spec validate` runs, when slices are structurally invalid for execution, then the command detects the relevant `check-slice --local` failures or reports them as strict warnings.
+12. Given a spec worktree path is missing, stale, dirty, or not listed by Git, when `spec status` runs, then the command reports the real state and recovery guidance.
+13. Given `spec start --dry-run` finds a dirty checkout, when it fails, then it lists blocking files and safe options without modifying state.
+14. Given `ai review-plan` runs, when it finishes, then it emits structured metadata for blocking status, approval recommendation, required fixes, optional hardening, and next command.
+15. Given generated examples target agents, when commands are printed, then non-interactive versioned examples use `npx --yes create-quiver@<version>`.
+16. Given docs are updated, when the spec closes, then `README_FOR_AI.md`, `README.md`, `CHANGELOG.md`, and `ROADMAP.md` do not contradict the implemented state.
+17. Given final validation runs, when release readiness is checked, then source tests and package/tarball smoke evidence are recorded.
+
+## Technical Plan
+
+1. Freeze evidence and create the reconciliation matrix before implementation.
+2. Add focused fixtures for unresolved or regressed cases.
+3. Harden AI run state and approvals before touching spec generation.
+4. Enforce the structured technical-plan contract and repair path.
+5. Add active-slice reconciliation and stale `ai inspect` recovery.
+6. Align validation gates and worktree reporting.
+7. Add plan-review closure metadata and agent-friendly command examples.
+8. Close with compatibility tests, documentation sync, smoke coverage, and release evidence.
+
+## Slice Roadmap
+
+| Slice | Title | Status | Dependencies |
+|---|---|---|---|
+| slice-00 | Reconciliation and evidence freeze | completed | none |
+| slice-01 | AI run state, approvals, and clean output | completed | slice-00 |
+| slice-02 | Structured technical plan contract and repair flow | completed | slice-00, slice-01 |
+| slice-03 | Active slice reconciliation and AI inspect | completed | slice-00, slice-01 |
+| slice-04 | Spec validation, scope, and worktree reliability | completed | slice-00 |
+| slice-05 | Review-plan closure and agent DX | completed | slice-00, slice-01 |
+| slice-06 | Backward compatibility, docs, and release readiness | completed | slice-01, slice-02, slice-03, slice-04, slice-05 |
+
+## Validation Strategy
+
+- `node --test tests/**/*.test.js`
+- `npm run smoke:doctor-fixtures`
+- `npm run smoke:guided-workflow`
+- `npm run smoke:create-quiver`
+- `npm run package:quiver`
+- package/tarball smoke from a temporary directory
+- `git diff --check`
+- JSON parse validation for all `slice.json`
+- `npx create-quiver spec validate specs/quiver-v28-pixel-quiver-feedback-reconciliation`
+- `npx create-quiver check-handoff` for each execution and closure brief
+
+## Risks
+
+- Some findings may already be fixed by v27 and only stale in Pixel Quiver docs.
+- Tightening validation can break older project specs if strict behavior is not gated.
+- AI lifecycle changes can affect existing `.quiver/runs` and `.quiver/approvals` state.
+- Worktree changes can affect users with in-flight branches.
+- Real dogfooding evidence contains absolute local paths and must not be copied into fixtures without sanitization.
+- Local non-package files can accidentally enter npm tarballs unless ignored; v28 added `*.pdf` to `.npmignore` after package dry-run evidence.

package/specs/quiver-v28-pixel-quiver-feedback-reconciliation/STATUS.md

@@ -0,0 +1,36 @@
+# Status - Quiver v28 Pixel Quiver Feedback Reconciliation
+
+## Overall Status
+
+- Phase: Final validation complete
+- Progress: 100%
+- Current recommended slice: none
+- Source evidence: Pixel Quiver feedback files after `create-quiver@0.13.0`
+
+## Slices
+
+| Slice | Title | Status | Progress | Dependencies |
+|---|---|---|---:|---|
+| slice-00 | Reconciliation and evidence freeze | completed | 100% | none |
+| slice-01 | AI run state, approvals, and clean output | completed | 100% | slice-00 |
+| slice-02 | Structured technical plan contract and repair flow | completed | 100% | slice-00, slice-01 |
+| slice-03 | Active slice reconciliation and AI inspect | completed | 100% | slice-00, slice-01 |
+| slice-04 | Spec validation, scope, and worktree reliability | completed | 100% | slice-00 |
+| slice-05 | Review-plan closure and agent DX | completed | 100% | slice-00, slice-01 |
+| slice-06 | Backward compatibility, docs, and release readiness | completed | 100% | slice-01, slice-02, slice-03, slice-04, slice-05 |
+
+## Blockers
+
+- None.
+
+## Known Production Concerns
+
+- v27 already covers part of the Pixel Quiver feedback; remaining slices must not duplicate verified-resolved work.
+- Pixel Quiver evidence contains absolute local paths and must remain evidence only unless sanitized into fixtures.
+- Backward compatibility for existing `.quiver/runs`, `.quiver/approvals`, active-slice docs, and worktree state is mandatory.
+- Tightening validation must avoid breaking older specs by default; strict behavior should be explicit when needed.
+- A local PDF in the repo root was detected by `npm pack --dry-run`; `.npmignore` now excludes `*.pdf` to avoid accidental package publication.
+
+## Next Step
+
+Prepare the PR/release decision outside this spec. npm publication and PR creation were intentionally not performed here.

package/specs/quiver-v28-pixel-quiver-feedback-reconciliation/pr.md

@@ -0,0 +1,128 @@
+# Quiver v28 - Pixel Quiver Feedback Reconciliation
+
+## Title
+
+Quiver v28 - Pixel Quiver Feedback Reconciliation
+
+## Summary
+
+- Reconciles Pixel Quiver dogfooding findings against the current Quiver implementation.
+- Fixes unresolved AI lifecycle, approvals, spec creation, active-slice, validation, worktree, plan-review, and agent-DX gaps.
+- Adds regression coverage, documentation updates, smoke evidence, and package-readiness checks.
+- Keeps v28 changes in `Unreleased`; no npm publication is claimed by this PR.
+
+## Scope
+
+- `slice-00`: evidence freeze and reconciliation matrix.
+- `slice-01`: AI run state, approvals, and clean output.
+- `slice-02`: structured technical-plan contract and repair flow.
+- `slice-03`: active-slice reconciliation and `ai inspect` recovery.
+- `slice-04`: spec validation, scope, and worktree reliability.
+- `slice-05`: review-plan closure and agent DX.
+- `slice-06`: docs, compatibility checks, smoke tests, and release readiness.
+
+## Files
+
+- `src/create-quiver/commands/ai.js`
+- `src/create-quiver/commands/spec.js`
+- `src/create-quiver/index.js`
+- `src/create-quiver/lib/ai/**`
+- `src/create-quiver/lib/project-state-resolver.js`
+- `src/create-quiver/lib/spec-worktrees.js`
+- `tests/commands/**`
+- `tests/lib/**`
+- `README.md`
+- `README_FOR_AI.md`
+- `CHANGELOG.md`
+- `ROADMAP.md`
+- `docs/*.template`
+- `.npmignore`
+- `specs/quiver-v28-pixel-quiver-feedback-reconciliation/**`
+
+## How to Test (DETAILED - REQUIRED)
+
+### Required Environment
+
+- Node.js and npm available locally.
+- Git repository checkout with access to the Quiver remote.
+- `gh` is required only for PR operations, not for source validation.
+
+### Worktree Access
+
+Run from the repository root:
+
+```bash
+cd /Users/fabrijk/Documents/Work/Proyectos\ Personales/nika/frameworks/quiver
+```
+
+### Run the Project
+
+This PR changes the `create-quiver` CLI. Use direct Node execution or npm scripts from the repo root:
+
+```bash
+node bin/create-quiver.js --help
+node bin/create-quiver.js ai --help
+```
+
+### Use Cases
+
+Validate the main updated workflows:
+
+```bash
+node bin/create-quiver.js spec validate specs/quiver-v28-pixel-quiver-feedback-reconciliation --strict
+node bin/create-quiver.js next --all-ready --spec quiver-v28-pixel-quiver-feedback-reconciliation
+```
+
+Expected result:
+
+- Spec validation passes.
+- `next --all-ready` reports no ready slices after v28 closure.
+
+### Technical Verification
+
+Run:
+
+```bash
+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
+git diff --check
+```
+
+Expected result:
+
+- All tests pass.
+- Smoke commands pass.
+- Package smoke passes.
+- `npm pack --dry-run --json` does not include local PDF files.
+- `git diff --check` returns no whitespace errors.
+
+## Evidence
+
+Recorded in `specs/quiver-v28-pixel-quiver-feedback-reconciliation/EVIDENCE_REPORT.md`.
+
+Latest validation evidence:
+
+- `node --test tests/**/*.test.js` passed with `376` tests.
+- `npm run smoke:doctor-fixtures` passed with `13` fixture states.
+- `npm run smoke:guided-workflow` passed.
+- `npm run smoke:create-quiver` passed.
+- `npm run package:quiver` passed.
+- `npm pack --dry-run --json` passed with no `.pdf` files in the package.
+- `git diff --check` passed.
+- `node bin/create-quiver.js spec validate specs/quiver-v28-pixel-quiver-feedback-reconciliation --strict` passed.
+- `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` passed.
+
+## Rollback
+
+Revert this PR. No migration, npm publication, external service change, or credential storage change is included.
+
+## Risks / Notes
+
+- v28 tightens validation and approval gates. Backward compatibility was preserved by keeping stricter behavior behind explicit validation and review paths where possible.
+- Existing local `.quiver/` state may expose more precise stale-run or active-slice diagnostics after this change.
+- `.npmignore` now excludes `*.pdf` because package dry-run showed a local requirements PDF would otherwise be included in the npm tarball.
+- npm publication is intentionally out of scope for this PR.

package/specs/quiver-v28-pixel-quiver-feedback-reconciliation/slices/slice-00-reconciliation-and-evidence-freeze/CLOSURE_BRIEF.md

@@ -0,0 +1,44 @@
+# CLOSURE BRIEF - slice-00: Reconciliation and evidence freeze
+
+## Summary
+
+Completed the mandatory reconciliation slice for Quiver v28. The Pixel Quiver feedback files were frozen with hashes/timestamps, all supplied `QP-*`, `QIS-*`, and narrative framework-improvement sections were classified, and the execution mapping for remaining slices was updated.
+
+## Validation
+
+Passed:
+
+- `git diff --check`
+- JSON parse validation for v28 `slice.json` files
+- `node bin/create-quiver.js spec validate specs/quiver-v28-pixel-quiver-feedback-reconciliation`
+- `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-00-reconciliation-and-evidence-freeze/slice.json`
+- `node bin/create-quiver.js next --all-ready --spec quiver-v28-pixel-quiver-feedback-reconciliation`
+- `node bin/create-quiver.js plan --spec quiver-v28-pixel-quiver-feedback-reconciliation --json`
+
+## Relevant Changes
+
+- Replaced the initial planning matrix in `COVERAGE_MATRIX.md` with evidence-backed classifications.
+- Updated `EVIDENCE_REPORT.md` with frozen source hashes, timestamps, inspected evidence, and remaining validation requirements.
+- Updated `STATUS.md` and `SPEC.md` so `slice-00` is completed and Wave 1 slices are ready.
+- Marked `slice-01` and `slice-04` as ready in their `slice.json` files.
+- Expanded `slice-05` scope to own GitHub auth/alias recovery copy, compact executor handoff guidance, and agent-safe command examples.
+
+## Pending Work
+
+- `slice-01`: AI run state, approvals, and clean output.
+- `slice-04`: spec validation, scope, and worktree reliability.
+- `slice-02`, `slice-03`, and `slice-05` remain blocked until `slice-01` completes.
+- `slice-06` remains the final documentation, compatibility, and release-readiness pass.
+
+## Remaining Risks
+
+- Some v27-covered findings may still need regression tests if implementation slices touch nearby behavior.
+- Pixel Quiver evidence contains absolute local paths and must not be copied into fixtures without sanitization.
+- Framework ideas such as graph conflict summaries and browser-based visual validation are documented as future work, not v28 blockers.
+
+## Future Recommendations
+
+- Keep all implementation slices anchored to `COVERAGE_MATRIX.md`.
+- Do not start `slice-02`, `slice-03`, or `slice-05` until `slice-01` clarifies run and approval state.
+- If a later slice finds that a `verified-resolved` item still fails in code, update the matrix before implementing the fix.

package/specs/quiver-v28-pixel-quiver-feedback-reconciliation/slices/slice-00-reconciliation-and-evidence-freeze/EXECUTION_BRIEF.md

@@ -0,0 +1,56 @@
+# EXECUTION BRIEF - slice-00: Reconciliation and evidence freeze
+
+## Context
+
+Pixel Quiver produced a follow-up set of Quiver framework findings after `create-quiver@0.13.0`. `README_FOR_AI.md` says v27 already covered part of that set, so this slice must verify reality before code changes.
+
+## Objective
+
+Freeze the input evidence and produce the final reconciliation matrix for v28.
+
+## Scope
+
+- `specs/quiver-v28-pixel-quiver-feedback-reconciliation/**`
+- `README_FOR_AI.md`
+- `ROADMAP.md`
+- `CHANGELOG.md`
+
+## Acceptance Criteria
+
+- Every finding from the supplied files is classified with evidence.
+- Pending or partial findings map to one implementation slice.
+- Already-resolved findings are not scheduled for duplicate work.
+- No product code changes are made.
+
+## Technical Plan Summary
+
+Read the supplied Pixel Quiver files, compare them with v27 docs/code/tests, update the coverage matrix, and finalize the slice plan.
+
+## Suggested Execution Steps
+
+1. Record evidence source paths, timestamps, and hashes where practical.
+2. Compare each finding against v27 docs, source, and tests.
+3. Update `COVERAGE_MATRIX.md`.
+4. Update `STATUS.md`, `EVIDENCE_REPORT.md`, and `CLOSURE_BRIEF.md`.
+5. Validate JSON and spec structure.
+
+## Restrictions
+
+- Do not modify product code.
+- Do not publish npm.
+- Do not open a PR.
+- Do not mark a finding resolved without evidence.
+
+## Risks
+
+- Reimplementing v27 behavior would create noise and possible regressions.
+- Pixel Quiver files may be stale relative to the current Quiver source.
+
+## Completion Checklist
+
+- [ ] Evidence freeze complete.
+- [ ] Matrix final statuses assigned.
+- [ ] Implementation slices adjusted if needed.
+- [ ] JSON validation passed.
+- [ ] Spec validation passed.
+