create-quiver 0.13.0 → 0.14.1

package/docs/workflows/full-ai-spec-to-pr.md

@@ -0,0 +1,311 @@
+# Flujo completo de IA: de requerimiento a PR
+
+Esta guía cubre el flujo completo de Quiver desde un requerimiento hasta un pull request abierto.
+
+Ejecutá los comandos desde la raíz del proyecto.
+
+## 1. Confirmar estado del proyecto
+
+```bash
+git status -sb
+npx --yes create-quiver@latest flow
+npx --yes create-quiver@latest doctor
+```
+
+Qué hace:
+
+- revisa el estado local de Git;
+- le pide a Quiver el próximo paso seguro;
+- valida el contrato del proyecto.
+
+## 2. Crear un archivo de requerimiento
+
+```bash
+mkdir -p requirements
+$EDITOR requirements/mi-requerimiento.md
+```
+
+Qué hace:
+
+- crea una entrada durable para el planner;
+- evita perder el requerimiento en el historial del chat.
+
+## 3. Crear una ejecución de IA
+
+```bash
+npx --yes create-quiver@latest ai run create --input requirements/mi-requerimiento.md
+npx --yes create-quiver@latest ai status
+```
+
+Qué hace:
+
+- crea estado persistente en `.quiver/runs/`;
+- muestra la fase actual y el próximo comando seguro.
+
+## 4. Generar criterios de aceptación
+
+```bash
+npx --yes create-quiver@latest ai plan --phase acceptance --input requirements/mi-requerimiento.md --dry-run
+npx --yes create-quiver@latest ai plan --phase acceptance --input requirements/mi-requerimiento.md
+```
+
+Si querés revisar y confirmar el borrador antes de guardarlo:
+
+```bash
+npx --yes create-quiver@latest ai plan --phase acceptance --input requirements/mi-requerimiento.md --review --interactive
+```
+
+Qué hace:
+
+- previsualiza la invocación al proveedor;
+- le pide al planner un borrador de criterios de aceptación.
+
+Revisar borradores:
+
+```bash
+npx --yes create-quiver@latest ai approvals
+```
+
+Aprobar una versión:
+
+```bash
+npx --yes create-quiver@latest ai approve --phase acceptance --version <n>
+```
+
+Qué hace:
+
+- guarda los criterios aprobados como entrada para el plan técnico.
+
+## 5. Iterar criterios cuando haga falta
+
+```bash
+npx --yes create-quiver@latest ai revise --phase acceptance --input feedback.md --dry-run
+npx --yes create-quiver@latest ai revise --phase acceptance --input feedback.md
+```
+
+Qué hace:
+
+- crea un nuevo borrador sin aprobarlo automáticamente;
+- mantiene explícita la compuerta de aprobación humana.
+
+## 6. Generar el plan técnico
+
+```bash
+npx --yes create-quiver@latest ai plan --phase technical-plan --dry-run
+npx --yes create-quiver@latest ai plan --phase technical-plan
+```
+
+Si querés editar el borrador antes de guardarlo:
+
+```bash
+npx --yes create-quiver@latest ai plan --phase technical-plan --review --interactive
+```
+
+Qué hace:
+
+- genera un plan técnico desde los criterios aprobados;
+- exige información estructurada de slices para poder crear specs después.
+
+## 7. Revisar el plan técnico
+
+```bash
+npx --yes create-quiver@latest ai review-plan --dry-run
+npx --yes create-quiver@latest ai review-plan
+```
+
+Qué hace:
+
+- revisa el plan como si fuera a implementarse y probarse en producción;
+- guarda metadata de revisión con recomendación `approve`, `approve-with-risk` o `revise`;
+- bloquea la aprobación cuando hay fixes requeridos.
+
+Aprobar un plan revisado:
+
+```bash
+npx --yes create-quiver@latest ai approve --phase technical-plan --version <n>
+```
+
+## 8. Crear el paquete de spec
+
+```bash
+npx --yes create-quiver@latest spec create --dry-run
+npx --yes create-quiver@latest spec create
+```
+
+Si querés revisar el paquete antes de escribirlo:
+
+```bash
+npx --yes create-quiver@latest spec create --review --interactive
+```
+
+Qué hace:
+
+- crea `SPEC.md`;
+- crea el `slice-00` obligatorio;
+- crea slices de implementación;
+- crea `EXECUTION_BRIEF.md` y `CLOSURE_BRIEF.md`;
+- crea el plan de ejecución y `pr.md`.
+
+Validarlo:
+
+```bash
+npx --yes create-quiver@latest spec validate specs/<spec-slug> --strict
+```
+
+## 9. Crear o reutilizar el worktree de la spec
+
+```bash
+npx --yes create-quiver@latest spec start specs/<spec-slug> --dry-run
+npx --yes create-quiver@latest spec start specs/<spec-slug>
+```
+
+Qué hace:
+
+- prepara la rama y el worktree dedicados a esta spec;
+- mantiene una spec aislada de otros trabajos.
+
+## 10. Inspeccionar el orden de slices
+
+```bash
+npx --yes create-quiver@latest plan --spec <spec-slug>
+npx --yes create-quiver@latest graph --spec <spec-slug>
+npx --yes create-quiver@latest next --all-ready --spec <spec-slug>
+```
+
+Qué hace:
+
+- muestra el orden de ejecución;
+- muestra dependencias;
+- lista slices listos para ejecutar.
+
+## 11. Ejecutar slices manualmente
+
+Generá un prompt para un agente ejecutor de menor costo:
+
+```bash
+npx --yes create-quiver@latest ai prompt-slice --slice specs/<spec-slug>/slices/<slice-id>/slice.json --dry-run
+```
+
+Qué hace:
+
+- imprime el contexto mínimo que necesita el ejecutor;
+- evita enviar la spec completa salvo que sea necesario.
+
+## 12. Ejecutar un slice con Quiver
+
+```bash
+npx --yes create-quiver@latest ai execute-slice --slice specs/<spec-slug>/slices/<slice-id>/slice.json --commit --dry-run
+npx --yes create-quiver@latest ai execute-slice --slice specs/<spec-slug>/slices/<slice-id>/slice.json --commit
+```
+
+Qué hace:
+
+- ejecuta el slice con el ejecutor configurado;
+- valida rama y worktree;
+- valida archivos modificados contra el alcance del slice;
+- corre comandos de validación declarados;
+- actualiza cierre, evidencia, estado y `slice.json`;
+- crea un commit para el slice.
+
+## 13. Ejecutar slices por olas
+
+Modo manual:
+
+```bash
+npx --yes create-quiver@latest ai execute-plan --dry-run --commit --mode manual
+```
+
+Qué hace:
+
+- imprime prompts de slices en orden de ejecución;
+- no llama proveedores.
+
+Modo delegado:
+
+```bash
+npx --yes create-quiver@latest ai execute-plan --dry-run --commit --mode delegated
+npx --yes create-quiver@latest ai execute-plan --execute --commit --mode delegated
+```
+
+Qué hace:
+
+- previsualiza o ejecuta slices delegados;
+- usa worktrees temporales para slices paralelizables;
+- vuelve a ejecución secuencial cuando el alcance no es seguro.
+
+## 14. Validar antes del PR
+
+```bash
+npx --yes create-quiver@latest spec validate specs/<spec-slug> --strict
+npx --yes create-quiver@latest next --all-ready --spec <spec-slug>
+git diff --check
+```
+
+Qué hace:
+
+- confirma que el paquete de spec esté completo;
+- confirma que no queden slices listos sin ejecutar;
+- revisa whitespace.
+
+También corré validaciones propias del proyecto:
+
+```bash
+npm test
+npm run build
+npm run lint
+```
+
+Usá solo los scripts que existan en el proyecto.
+
+## 15. Previsualizar creación del PR
+
+```bash
+npx --yes create-quiver@latest ai pr \
+  --review \
+  --dry-run \
+  --input specs/<spec-slug>/pr.md \
+  --ssh-host-alias github-personal \
+  --identity-file ~/.ssh/github-personal
+```
+
+Qué hace:
+
+- valida `gh`;
+- valida autenticación de GitHub;
+- valida alias SSH y archivo de identidad;
+- verifica que exista el cuerpo del PR;
+- no crea el PR.
+
+Adaptá `--identity-file` a la ruta real de tu máquina, por ejemplo `~/ssh/github-personal`, `~/.ssh/github-personal` o una ruta de Windows.
+
+## 16. Crear el pull request
+
+```bash
+npx --yes create-quiver@latest ai pr \
+  --create \
+  --interactive \
+  --input specs/<spec-slug>/pr.md \
+  --ssh-host-alias github-personal \
+  --identity-file ~/.ssh/github-personal
+```
+
+Qué hace:
+
+- abre el PR usando `gh`;
+- usa el cuerpo generado en `pr.md`;
+- bloquea la creación si todavía quedan slices abiertos.
+
+## 17. Después del merge
+
+```bash
+npx --yes create-quiver@latest spec close specs/<spec-slug> --dry-run
+npx --yes create-quiver@latest spec close specs/<spec-slug>
+git switch main
+git pull --ff-only origin main
+```
+
+Qué hace:
+
+- previsualiza y luego cierra el worktree de la spec;
+- vuelve al checkout principal;
+- trae localmente el resultado mergeado.

package/docs/workflows/legacy-quiver-project.md

@@ -0,0 +1,102 @@
+# Flujo para proyecto con Quiver anterior
+
+Usá este flujo cuando el proyecto ya tiene archivos de Quiver creados por una versión anterior.
+
+## 1. Entrar al proyecto
+
+```bash
+cd /ruta/al/proyecto
+git status -sb
+```
+
+Qué hace:
+
+- revisa la rama actual y los cambios pendientes.
+
+## 2. Ejecutar doctor
+
+```bash
+npx --yes create-quiver@latest doctor
+```
+
+Qué hace:
+
+- detecta si el proyecto está inicializado, incompleto, legacy, híbrido o sano.
+
+## 3. Previsualizar migración
+
+```bash
+npx --yes create-quiver@latest migrate --dry-run
+```
+
+Qué hace:
+
+- muestra qué actualizaría Quiver;
+- evita escribir archivos.
+
+## 4. Aplicar migración
+
+```bash
+npx --yes create-quiver@latest migrate
+```
+
+Qué hace:
+
+- actualiza documentación y estado interno de Quiver;
+- preserva archivos existentes del proyecto;
+- mantiene la migración lo más aditiva posible.
+
+Usá esta variante si no querés instalar dependencias:
+
+```bash
+npx --yes create-quiver@latest migrate --skip-install
+```
+
+## 5. Reconstruir contexto del proyecto
+
+```bash
+npx --yes create-quiver@latest analyze
+npx --yes create-quiver@latest doctor
+```
+
+Qué hace:
+
+- refresca `docs/PROJECT_MAP.md`;
+- confirma que la estructura migrada esté sana.
+
+## 6. Preparar contexto para IA
+
+```bash
+npx --yes create-quiver@latest ai prepare-context --dry-run
+npx --yes create-quiver@latest ai prepare-context
+```
+
+Modo asistido por planner, útil cuando el contexto anterior quedó desactualizado:
+
+```bash
+npx --yes create-quiver@latest ai prepare-context --with-planner --dry-run
+npx --yes create-quiver@latest ai prepare-context --with-planner --review --interactive
+```
+
+Qué hace:
+
+- actualiza contexto de onboarding de forma segura;
+- reporta supuestos y contradicciones.
+
+## 7. Commit de migración
+
+```bash
+git status -sb
+git add AGENTS.md docs .quiver .gitignore package.json package-lock.json
+git commit -m "docs: migrate quiver workflow"
+```
+
+Qué hace:
+
+- crea una base estable antes de empezar specs nuevas.
+
+Ajustá los paths según lo que haya informado la migración.
+
+Siguiente paso:
+
+- [Ejecutar el flujo completo de spec a PR con IA](./full-ai-spec-to-pr.md)

package/docs/workflows/new-project.md

@@ -0,0 +1,76 @@
+# Flujo para proyecto nuevo
+
+Usá este flujo cuando el repositorio todavía no existe o la carpeta está vacía.
+
+## 1. Crear la carpeta del proyecto
+
+```bash
+mkdir mi-proyecto
+cd mi-proyecto
+git init
+```
+
+Qué hace:
+
+- crea una carpeta para el proyecto;
+- inicializa Git para que Quiver pueda razonar sobre cambios y worktrees.
+
+## 2. Inicializar Quiver
+
+```bash
+npx --yes create-quiver@latest init --name "Mi Proyecto"
+```
+
+Qué hace:
+
+- crea el contrato visible de Quiver;
+- crea el estado interno en `.quiver/`;
+- agrega scripts `quiver:*` cuando existe o se crea `package.json`.
+
+## 3. Revisar el próximo paso
+
+```bash
+npx --yes create-quiver@latest flow
+```
+
+Qué hace:
+
+- muestra el estado actual del workflow;
+- recomienda el próximo comando seguro.
+
+## 4. Analizar y validar
+
+```bash
+npx --yes create-quiver@latest analyze
+npx --yes create-quiver@latest doctor
+```
+
+Qué hace:
+
+- crea o actualiza `docs/PROJECT_MAP.md`;
+- refresca el contexto para IA;
+- valida que el contrato de Quiver esté sano.
+
+## 5. Preparar contexto para IA
+
+```bash
+npx --yes create-quiver@latest ai prepare-context --dry-run
+npx --yes create-quiver@latest ai prepare-context
+```
+
+Modo asistido por planner, si querés que una IA proponga el contexto:
+
+```bash
+npx --yes create-quiver@latest ai prepare-context --with-planner --dry-run
+npx --yes create-quiver@latest ai prepare-context --with-planner --review --interactive
+```
+
+Qué hace:
+
+- previsualiza cambios documentales de onboarding;
+- escribe la documentación de contexto después de revisar;
+- evita cambios en código de producto.
+
+Siguiente paso:
+
+- [Ejecutar el flujo completo de spec a PR con IA](./full-ai-spec-to-pr.md)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-quiver",
-  "version": "0.13.0",
+  "version": "0.14.1",
   "private": false,
   "description": "Quiver CLI for scaffolding projects from the packaged template",
   "license": "MIT",
@@ -49,5 +49,9 @@
     "smoke:tiered-pack": "bash scripts/ci/smoke-tiered-pack.sh",
     "smoke:guided-workflow": "bash scripts/ci/smoke-guided-workflow.sh",
     "release:quiver": "bash scripts/release-quiver.sh"
+  },
+  "dependencies": {
+    "@clack/prompts": "^1.4.0",
+    "zod": "^4.4.3"
   }
 }

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

@@ -0,0 +1,117 @@
+# Coverage Matrix - Quiver v28 Pixel Quiver Feedback Reconciliation
+
+`slice-00` completed the evidence freeze on 2026-05-25. This matrix replaces the initial planning hypothesis and is the execution contract for the remaining slices.
+
+Status meanings used during this spec:
+
+- `verified-resolved`: current repo evidence shows enough code, test, or doc coverage; no v28 implementation should repeat it.
+- `partial`: current repo covers part of the issue, but Pixel Quiver evidence still exposes a gap or missing regression guard.
+- `pending`: no sufficient current coverage was found; implement in the mapped v28 slice.
+- `duplicate`: tracked through another finding.
+- `documented-risk`: not fixed in this slice; must remain visible until closure.
+- `out-of-scope-with-reason`: intentionally excluded from v28 with a reason.
+
+## Frozen Inputs
+
+| Source | Unique IDs | SHA-256 | Modified |
+|---|---:|---|---|
+| Pixel Quiver `QUIVER_PROBLEMS.md` | `QP-001` to `QP-028` | `516d8928af437fc3d20cacfe50fb78752954eb59b6dace6860cdda820aa6701d` | 2026-05-25 03:29:24 -03 |
+| Pixel Quiver `QUIVER_IMPROVEMENT_SUGGESTIONS.md` | `QIS-001` to `QIS-031` | `43c4bfbef68fc8343b7f905f299c53716b55abcace415c9ce1088aa53ac12949` | 2026-05-25 03:29:39 -03 |
+| Pixel Quiver `QUIVER_FRAMEWORK_IMPROVEMENTS.md` | narrative sections only | `7a4eb66a996fc44cce80df4907a948fbef3e780a5f8fc856a6bdc2b0bd1f1ea3` | 2026-05-25 03:29:53 -03 |
+
+## Problem Coverage
+
+| Finding | Status | Primary slice | Evidence | Required action |
+|---|---|---|---|---|
+| QP-001 | verified-resolved | slice-00 | v27 matrix maps flow freshness to slice-07; `tests/commands/flow.test.js`; `src/create-quiver/commands/flow.js`. | Do not reimplement. |
+| QP-002 | fixed | slice-05 | v27 path handling remains, and help/docs now include non-interactive `npx --yes create-quiver@<version>` examples for agents. | Completed in slice-05. |
+| QP-003 | fixed | slice-03 | `collectLifecycleExport` now includes active-slice state, uses shared resolver data, and `ai inspect` next steps reconcile existing specs before suggesting stale creation. Covered by `tests/lib/ai-export-state.test.js` and `tests/commands/ai-export.test.js`. | Completed in slice-03. |
+| QP-004 | fixed | slice-05 | GitHub install/auth/alias guidance now includes account/scope/alias diagnosis plus macOS, Linux, Windows PowerShell, Git Bash, and WSL recovery copy. Covered by `tests/lib/ai-github.test.js`. | Completed in slice-05. |
+| QP-005 | verified-resolved | slice-00 | v27 matrix maps React/Vite analyzer detection to slice-07; `tests/commands/analyze.test.js`; `tests/fixtures/validation-errors/matrix.json`. | Do not reimplement unless a new failing fixture appears. |
+| QP-006 | verified-resolved | slice-00 | v27 matrix maps evidence-backed `prepare-context` to slice-07; `README_FOR_AI.md`; `docs/PROJECT_MAP.md` contract in templates. | Do not reimplement. |
+| QP-007 | verified-resolved | slice-00 | v27 matrix maps agent docs gaps to slice-07/slice-08; generated templates include current docs instead of missing `docs/ai/QUICK.md` style paths. | Do not reimplement. |
+| QP-008 | verified-resolved | slice-00 | v27 status is 100%; v27 evidence says source-of-truth docs were synchronized; `README_FOR_AI.md` documents v27 coverage. | Do not reimplement. |
+| QP-009 | verified-resolved | slice-00 | `src/create-quiver/lib/ai/artifacts.js`; `tests/commands/ai-plan.test.js`; v27 slice-04 closure covers revise compaction. | Do not reimplement. |
+| QP-010 | fixed | slice-01 | `src/create-quiver/commands/ai.js`; `tests/commands/ai-plan.test.js` covers clean console output without prompt echo/stderr logs while raw artifacts remain persisted. | Completed in slice-01. |
+| QP-011 | fixed | slice-02 | `ai plan --phase technical-plan` prompts for the required `spec.slices[]` contract; `ai approve --phase technical-plan` blocks invalid drafts before writing approved artifacts; `spec create` still fails before writes for legacy invalid approvals. | Completed in slice-02. |
+| QP-012 | verified-resolved | slice-00 | `tests/lib/ai-spec-generator.test.js` covers fail-before-writing and no build remnants. | Do not reimplement. |
+| QP-013 | fixed | slice-01 | `ai status` reports multiple open runs; `ai run close --run <id>` archives stale runs without deleting evidence; covered by `tests/commands/ai-run-state.test.js`. | Completed in slice-01. |
+| QP-014 | fixed | slice-01 | Provider-backed `ai onboard`, `ai plan`, and `ai review-plan` print clean output on success; raw output is only printed on provider failure. Covered by focused `ai plan` test. | Completed in slice-01. |
+| QP-015 | fixed | slice-01 | `ai approvals` now separates run-scoped approvals, active run, global planner approvals, and run relation (`active`, `historical`, `orphaned`, `none`). | Completed in slice-01. |
+| QP-016 | fixed | slice-03 | Added active-source detection for `docs/ai/ACTIVE_SLICE.md` and `ACTIVE_SLICES.md`, conflict detection, and `ai active-slice reconcile --dry-run`. Covered by resolver and CLI tests. | Completed in slice-03. |
+| QP-017 | fixed | slice-05 | `ai review-plan` now stores structured `review_result` metadata with approval recommendation, blocking status, required fixes, optional hardening, risks, and next command. | Completed in slice-05. |
+| QP-018 | fixed | slice-05 | Stale technical-plan review approval errors now recommend dry-run review followed by live review, and blocking review results surface the exact next command. | Completed in slice-05. |
+| QP-019 | fixed | slice-05 | Review closure now distinguishes `approve`, `approve-with-risk`, and `revise`, with required fixes blocking approval and optional hardening remaining non-blocking. | Completed in slice-05. |
+| QP-020 | fixed | slice-03 | `collectActiveSliceState` defines supported sources and canonical dry-run decisions: `preserve`, `close`, `replace`, and `blocked`. | Completed in slice-03. |
+| QP-021 | fixed | slice-05 | Review metadata separates `required_fixes` from `optional_hardening`, and approval checks block only revise/blocking results. | Completed in slice-05. |
+| QP-022 | fixed | slice-03 | Added `npx create-quiver ai active-slice status|reconcile`; `reconcile` is dry-run-first and refuses live writes. | Completed in slice-03. |
+| QP-023 | fixed | slice-02 | Technical-plan approval now validates that the selected draft can generate a spec package before approving it. | Completed in slice-02. |
+| QP-024 | fixed | slice-02 | Added `ai repair-plan` to create a provider-backed derived structured draft from a legacy approved invalid technical plan while preserving the original approved artifact. | Completed in slice-02. |
+| QP-025 | fixed | slice-04 | `spec validate` now rejects slices missing execution git metadata required by `check-slice --local`; covered by `tests/commands/spec-validate.test.js`. | Completed in slice-04. |
+| QP-026 | fixed | slice-04 | `spec status` now reports expected worktree paths that exist but are not registered in `git worktree list` as missing/stale; covered by `tests/commands/spec-worktree.test.js`. | Completed in slice-04. |
+| QP-027 | fixed | slice-04 | `spec start --dry-run` dirty checkout failures now list dirty files and safe recovery options; covered by `tests/commands/spec-worktree.test.js`. | Completed in slice-04. |
+| QP-028 | fixed | slice-03 | `ai inspect` detects existing specs when an active run still points at `spec create --dry-run` and now suggests `spec validate`, `next --all-ready`, and `ai prompt-slice`. | Completed in slice-03. |
+
+## Suggestion Coverage
+
+| Finding | Status | Primary slice | Evidence | Required action |
+|---|---|---|---|---|
+| QIS-001 | verified-resolved | slice-00 | v27 flow source/freshness coverage; `tests/commands/flow.test.js`. | Do not reimplement. |
+| QIS-002 | fixed | slice-05 | Agent examples now include `npx --yes create-quiver@<version>` and existing shell-safe copy remains covered. | Completed in slice-05. |
+| QIS-003 | fixed | slice-04 | `spec validate` now catches missing execution git metadata before users reach local slice execution. | Completed in slice-04. |
+| QIS-004 | verified-resolved | slice-00 | `src/create-quiver/lib/ai/export-state.js` exposes schema v2 dashboard data. | Do not reimplement unless schema gaps appear. |
+| QIS-005 | fixed | slice-05 | Executor context pack guidance now explicitly limits agents to `slice.json`, `EXECUTION_BRIEF`, `CLOSURE_BRIEF`, allowed files, acceptance criteria, and validation commands; docs include non-interactive prompt-slice examples. | Completed in slice-05. |
+| QIS-006 | fixed | slice-03 | `ai inspect`, `ai export`, active-slice status, spec listing, and slice listing share resolver-backed lifecycle export data. | Completed in slice-03. |
+| QIS-007 | verified-resolved | slice-00 | v27 analyzer coverage and fixtures. | Do not reimplement. |
+| QIS-008 | verified-resolved | slice-00 | v27 context evidence coverage and source-backed docs contract. | Do not reimplement. |
+| QIS-009 | fixed | slice-05 | GitHub preflight guidance now includes shell-specific `gh` installation and SSH alias setup/verification copy. | Completed in slice-05. |
+| QIS-010 | verified-resolved | slice-00 | v27 agent docs/template cleanup. | Do not reimplement. |
+| QIS-011 | verified-resolved | slice-00 | `tests/commands/ai-agent.test.js` covers `ai agent set --dry-run`. | Do not reimplement. |
+| QIS-012 | verified-resolved | slice-00 | v27 artifact compaction tests and `src/create-quiver/lib/ai/artifacts.js`. | Do not reimplement. |
+| QIS-013 | fixed | slice-01 | Clean/raw persistence remains, and console output no longer emits provider transcript/logs on successful planner commands. | Completed in slice-01. |
+| QIS-014 | fixed | slice-02 | Structured technical-plan output is now required in planner prompts and enforced before technical-plan approval/spec creation. | Completed in slice-02. |
+| QIS-015 | fixed | slice-02 | Existing generator regressions continue to cover slug/title normalization, collision refusal, multi-slice preservation, and structured markdown extraction while the shared contract validator was added. | Completed in slice-02. |
+| QIS-016 | fixed | slice-01 | `ai status` exposes other open runs and `ai run close --run <id>` provides a safe archive path. | Completed in slice-01. |
+| QIS-017 | fixed | slice-01 | Successful provider-backed planner commands print clean output only; raw logs remain stored/redacted. | Completed in slice-01. |
+| QIS-018 | fixed | slice-01 | `ai approvals` groups active/historical run-scoped approvals separately from global approval files. | Completed in slice-01. |
+| QIS-019 | fixed | slice-03 | Added `ai active-slice status|reconcile` with multi-source reporting and dry-run output. | Completed in slice-03. |
+| QIS-020 | fixed | slice-05 | `summarizePlanReview` now reports approval recommendation, blocking status, required fixes, optional hardening, and next command. | Completed in slice-05. |
+| QIS-021 | fixed | slice-05 | `meta.json` stores machine-readable `review_result` data for downstream agents and gates. | Completed in slice-05. |
+| QIS-022 | fixed | slice-03 | Added canonical multi-source active-slice reconciliation from active doc plus root board. | Completed in slice-03. |
+| QIS-023 | fixed | slice-05 | CLI help, README, README_FOR_AI, and generated command docs now include `npx --yes create-quiver@<version>` guidance for agent-pasted commands. | Completed in slice-05. |
+| QIS-024 | fixed | slice-05 | Review close threshold is now `approve`, `approve-with-risk`, or `revise`; `revise` and blocking required fixes prevent technical-plan approval. | Completed in slice-05. |
+| QIS-025 | fixed | slice-03 | `ai active-slice reconcile --dry-run` reports supported sources, detected sources, planned changes, risks, and no-write guarantee. | Completed in slice-03. |
+| QIS-026 | fixed | slice-02 | Missing `spec.slices[]` is now caught before approval and before spec creation. | Completed in slice-02. |
+| QIS-027 | fixed | slice-02 | `ai repair-plan` provides a traceable repair path for approved legacy plans missing structure. | Completed in slice-02. |
+| QIS-028 | fixed | slice-04 | `spec validate` enforces local execution metadata parity with focused regression coverage. | Completed in slice-04. |
+| QIS-029 | fixed | slice-04 | `spec status` detects unregistered expected worktree directories and reports them as stale. | Completed in slice-04. |
+| QIS-030 | fixed | slice-04 | Dirty checkout recovery now includes blocking files and safe options. | Completed in slice-04. |
+| QIS-031 | fixed | slice-03 | `collectNextSteps` now prefers existing-spec recovery commands over stale lifecycle `spec create` guidance. | Completed in slice-03. |
+
+## Framework Improvement Sections
+
+| Area from Pixel Quiver improvement file | Status | Primary slice | Evidence | Required action |
+|---|---|---|---|---|
+| Intent/spec selection before a spec exists | fixed | slice-03 | `ai inspect` now reconciles existing specs and ready slices before suggesting another spec creation path. | Completed in slice-03 without adding a separate intent system. |
+| Local vs latest Quiver version visibility | documented-risk | slice-06 | README now states the package remains `0.13.0` and v28 changes are unreleased until future publication; package smoke ran against the local package artifact without claiming npm publish. | Future work: consider `status --versions`. |
+| Standard names for improvement files | documented-risk | slice-06 | v28 preserved the three Pixel Quiver evidence files as explicit source inputs and frozen hashes in this matrix/evidence report. | Future work: document accepted feedback filenames and aliases. |
+| Graph conflicts summary | out-of-scope-with-reason | slice-06 | Useful but not required for the AI lifecycle failures in v28. | Record as future graph UX work. |
+| Visual validation command | out-of-scope-with-reason | slice-06 | Valuable for frontend projects, but would require browser tooling and a larger product decision. | Record as future visual evidence feature. |
+| Active run management | fixed | slice-01 | `ai status` surfaces multiple open runs; `ai run close --run <id>` closes stale runs while preserving `.quiver/runs/<id>`. | Completed in slice-01. |
+| Clean AI output | fixed | slice-01 | Successful provider-backed planner commands now print clean extracted output instead of raw stdout/stderr. | Completed in slice-01. |
+| Active slice reconciliation | fixed | slice-03 | Matches QP-016/QP-020/QIS-019/QIS-022/QIS-025; implemented through resolver state and `ai active-slice` CLI. | Completed in slice-03. |
+| Structured plan/spec create | fixed | slice-02 | Matches QP-011, QP-023, QP-024, QIS-014, QIS-015, QIS-026, and QIS-027; validated by approval, repair, spec-create, and generator tests. | Completed in slice-02. |
+| Worktree and validation hardening | fixed | slice-04 | Matches QP-025 to QP-027 and QIS-028 to QIS-030; validated by spec validation, worktree, check-slice, scope, and path tests. | Completed in slice-04. |
+| Review-plan closure | fixed | slice-05 | Matches QP-017/QP-019/QP-021 and QIS-020/QIS-021/QIS-024; implemented with structured review metadata and approval gating. | Completed in slice-05. |
+| Agent-safe `npx --yes create-quiver@<version>` examples | fixed | slice-05 | Matches QIS-023 and Pixel command log; help/docs now include non-interactive pinned examples for agents. | Completed in slice-05. |
+| GitHub auth/alias guidance | fixed | slice-05 | Matches QP-004/QIS-009; guidance and tests cover gh install/auth plus SSH alias setup across supported shells. | Completed in slice-05. |
+| Package contents safety | fixed | slice-06 | `npm pack --dry-run` first showed `Quiver_Spec_Viewer_requisitos.pdf` would be included. `.npmignore` now excludes `*.pdf`, and the follow-up JSON dry-run confirmed no PDF files in the package. | Completed in slice-06. |
+
+## Execution Decisions
+
+- `slice-01` and `slice-04` are completed after `slice-00`.
+- `slice-02`, `slice-03`, and `slice-04` are completed after `slice-01`.
+- `slice-05` is completed after `slice-01`; `slice-06` owns final compatibility, docs sync, smoke, and release readiness.
+- Graph conflict summaries and visual validation commands are kept as documented future work, not v28 blocking implementation.
+- No product code was modified by `slice-00`.
+- `slice-06` did not publish npm or open a PR; it only established source and package-readiness evidence.