create-quiver 0.10.0 → 0.12.1

package/specs/quiver-v22-guided-ai-workflow/slices/slice-06-executor-commit-recovery/slice.json

@@ -0,0 +1,57 @@
+{
+  "slice_id": "slice-06-executor-commit-recovery",
+  "ticket": "QUIVER-22-06",
+  "type": "feature",
+  "title": "Executor validation, recovery, and commit per slice",
+  "objective": "Let executor agents modify approved slice scope and create one commit after validation passes.",
+  "description": "Extend slice execution with recoverable failure reporting, retry/abort guidance, optional commit automation, and strict one-slice-one-commit behavior.",
+  "git": {
+    "branch_type": "feature",
+    "base_branch": "main",
+    "branch_slug": "executor-commit-recovery",
+    "branch_name": "feature/QUIVER-22-06-executor-commit-recovery"
+  },
+  "files": [
+    "src/create-quiver/commands/ai.js",
+    "src/create-quiver/lib/ai/executor.js",
+    "src/create-quiver/lib/scope.js",
+    "src/create-quiver/lib/git.js",
+    "src/create-quiver/lib/slice-runner.js",
+    "tests/commands/ai-execute-slice.test.js",
+    "tests/lib/ai-executor.test.js",
+    "tests/lib/scope.test.js"
+  ],
+  "depends_on": [
+    "slice-05-spec-worktree-lifecycle"
+  ],
+  "parallel_safe": "after_dependencies",
+  "parallel_safe_reason": "Can run in parallel with PR creation only if file scopes remain separate.",
+  "must": [
+    "Keep executor context limited to approved slice data.",
+    "Require a clean worktree before execution unless explicitly overridden by existing safe options.",
+    "Validate changed files against slice scope after execution.",
+    "Run declared validation commands or report why they were skipped.",
+    "Create exactly one commit when validation passes and commit automation is enabled.",
+    "Write or print a recovery report when execution fails."
+  ],
+  "not_included": [
+    "Parallel execution waves.",
+    "PR creation.",
+    "Post-merge cleanup."
+  ],
+  "acceptance": [
+    "Executor refuses to run with dirty worktree by default.",
+    "Executor reports provider failure without hiding local changes.",
+    "Scope violations block commit automation.",
+    "Validation failures block commit automation.",
+    "Successful execution with commit enabled creates one slice commit.",
+    "Retry and abort guidance is shown after failures."
+  ],
+  "tests": [
+    "node --test tests/commands/ai-execute-slice.test.js tests/lib/ai-executor.test.js tests/lib/scope.test.js",
+    "git diff --check"
+  ],
+  "estimated_hours": 8,
+  "status": "completed",
+  "blocked_reason": null
+}

package/specs/quiver-v22-guided-ai-workflow/slices/slice-07-execution-waves-delegation/CLOSURE_BRIEF.md

@@ -0,0 +1,32 @@
+# CLOSURE BRIEF - slice-07: Execution waves and safe delegation
+
+## Resumen de lo realizado
+
+Se agrego `ai execute-plan` para imprimir o ejecutar olas de slices. El plan detecta conflictos por archivos, scope desconocido y fuerza fallback secuencial cuando no es seguro paralelizar.
+
+## Validacion contra criterios de aceptacion
+
+- [x] Olas respetan dependencias.
+- [x] Paralelo bloqueado ante conflictos.
+- [x] Dry-run no ejecuta providers.
+- [x] Tests ejecutados.
+
+## Cambios relevantes
+
+- `execution-plan` ahora incluye `execution_groups`, `fallback_reason` y `unknown_scope_slices`.
+- `parallel_ready` solo queda activo si hay mas de un slice, todos declaran files y no hay overlap.
+- `ai execute-plan --dry-run --commit` imprime comandos de executor por slice.
+- `ai execute-plan --execute --commit` ejecuta slices usando el executor validado y corta ante el primer fallo.
+- La ejecucion real exige `--commit` para preservar un commit por slice.
+
+## Pendientes
+
+Sin pendientes criticos para esta slice.
+
+## Riesgos remanentes
+
+La ejecucion paralela real queda representada como grupos `parallel-ready`; la ejecucion local integrada corre de forma controlada para no mezclar agentes en el mismo worktree.
+
+## Recomendaciones futuras
+
+Si se agrega paralelismo real automatico, debe crear worktrees separados por slice antes de llamar providers en paralelo.

package/specs/quiver-v22-guided-ai-workflow/slices/slice-07-execution-waves-delegation/EXECUTION_BRIEF.md

@@ -0,0 +1,58 @@
+# EXECUTION BRIEF - slice-07: Execution waves and safe delegation
+
+**Spec:** quiver-v22-guided-ai-workflow
+**Slice:** slice-07-execution-waves-delegation
+**Tipo:** feature
+
+## Contexto
+
+El usuario quiere que Quiver indique que slices van secuenciales y cuales pueden ir en paralelo con agentes ejecutores baratos.
+
+## Objetivo
+
+Agregar ejecucion por olas con fallback seguro a secuencial.
+
+## Alcance
+
+- Planificar olas desde dependencias.
+- Validar conflictos por archivos.
+- Imprimir comandos en dry-run.
+- Ejecutar olas cuando este habilitado.
+- Respetar un commit por slice.
+
+## Criterios de aceptacion
+
+- `slice-00` siempre va primero.
+- Paralelo solo se permite sin conflictos.
+- Scope desconocido cae a secuencial.
+- Una falla corta la ola requerida.
+- Dry-run no llama providers.
+
+## Plan tecnico resumido
+
+Extender `execution-plan` y agregar un comando de execute-plan que use el executor ya validado. Mantener primero modo print-only/dry-run.
+
+## Pasos sugeridos de ejecucion
+
+1. Revisar `execution-plan.js` y `slice-graph.js`.
+2. Agregar deteccion de conflicto por files.
+3. Agregar comando dry-run.
+4. Integrar ejecucion real con flags explicitos.
+5. Agregar tests de waves y conflictos.
+
+## Restricciones
+
+- No asumir que paralelo es seguro sin files declarados.
+- No abrir PR.
+
+## Riesgos
+
+- Ejecutar dos agentes que toquen la misma zona.
+- Dejar un wave a medio completar sin reporte claro.
+
+## Checklist de finalizacion
+
+- [ ] Olas generadas.
+- [ ] Conflictos detectados.
+- [ ] Dry-run print-only listo.
+- [ ] Tests pasan.

package/specs/quiver-v22-guided-ai-workflow/slices/slice-07-execution-waves-delegation/slice.json

@@ -0,0 +1,55 @@
+{
+  "slice_id": "slice-07-execution-waves-delegation",
+  "ticket": "QUIVER-22-07",
+  "type": "feature",
+  "title": "Execution waves and safe delegation",
+  "objective": "Execute or print execution waves that respect dependencies, slice-00, and file-scope conflicts.",
+  "description": "Turn the existing execution plan into a guided flow that can run sequential waves and safely identify parallel-ready slices for cheaper executor agents.",
+  "git": {
+    "branch_type": "feature",
+    "base_branch": "main",
+    "branch_slug": "execution-waves-delegation",
+    "branch_name": "feature/QUIVER-22-07-execution-waves-delegation"
+  },
+  "files": [
+    "src/create-quiver/commands/ai.js",
+    "src/create-quiver/lib/ai/execution-plan.js",
+    "src/create-quiver/lib/ai/executor.js",
+    "src/create-quiver/lib/slice-graph.js",
+    "src/create-quiver/lib/slice-runner.js",
+    "tests/lib/ai-execution-plan.test.js",
+    "tests/commands/ai-execute-plan.test.js"
+  ],
+  "depends_on": [
+    "slice-06-executor-commit-recovery"
+  ],
+  "parallel_safe": "no",
+  "parallel_safe_reason": "This slice coordinates multi-slice execution and should not be developed alongside executor changes.",
+  "must": [
+    "Always put slice-00 before all implementation slices.",
+    "Group ready slices into waves.",
+    "Detect file-scope conflicts before suggesting parallel execution.",
+    "Fall back to sequential execution when scope is unknown or conflicting.",
+    "Support a dry-run or print-only mode before real execution.",
+    "Keep one commit per slice when execution is enabled."
+  ],
+  "not_included": [
+    "Provider account billing controls.",
+    "Fully autonomous merge.",
+    "PR creation."
+  ],
+  "acceptance": [
+    "Execution plan shows waves with sequential and parallel groups.",
+    "Unknown or overlapping file scopes force sequential mode.",
+    "Dry-run prints commands and does not call providers.",
+    "Real execution stops the wave on failed required slice.",
+    "Successful slices keep one commit per slice."
+  ],
+  "tests": [
+    "node --test tests/lib/ai-execution-plan.test.js tests/commands/ai-execute-plan.test.js",
+    "git diff --check"
+  ],
+  "estimated_hours": 9,
+  "status": "completed",
+  "blocked_reason": null
+}

package/specs/quiver-v22-guided-ai-workflow/slices/slice-08-pr-create-gh-ssh/CLOSURE_BRIEF.md

@@ -0,0 +1,32 @@
+# CLOSURE BRIEF - slice-08: PR creation with gh and SSH guidance
+
+## Resumen de lo realizado
+
+Se extendio `ai pr` para validar setup, leer `pr.md`, mostrar el plan de `gh pr create` en dry-run y crear el PR solo cuando el usuario pasa `--create`.
+
+## Validacion contra criterios de aceptacion
+
+- [x] Dry-run no crea PR.
+- [x] PR se crea con `gh` en setup valido.
+- [x] Faltantes bloquean.
+- [x] Tests ejecutados.
+
+## Cambios relevantes
+
+- `ai pr --dry-run` imprime comando planificado y no ejecuta `gh pr create`.
+- `ai pr --create --input specs/<spec-slug>/pr.md` ejecuta `gh pr create` con argumentos seguros.
+- El cuerpo del PR se toma de `pr.md`; si hay multiples `pr.md`, se exige `--input`.
+- Se mantiene la validacion de gh, auth, remote, branch, worktree limpio, guia GitFlow, alias SSH e identity file.
+- Tests mockean `gh` y cubren dry-run, create, faltantes y fallos de `gh pr create`.
+
+## Pendientes
+
+Sin pendientes criticos para esta slice.
+
+## Riesgos remanentes
+
+La deteccion automatica de `pr.md` requiere que haya uno solo; si hay varios specs en el repo, el usuario debe pasar `--input`.
+
+## Recomendaciones futuras
+
+Mantener el merge fuera de `ai pr`; el merge queda como decision humana.

package/specs/quiver-v22-guided-ai-workflow/slices/slice-08-pr-create-gh-ssh/EXECUTION_BRIEF.md

@@ -0,0 +1,58 @@
+# EXECUTION BRIEF - slice-08: PR creation with gh and SSH guidance
+
+**Spec:** quiver-v22-guided-ai-workflow
+**Slice:** slice-08-pr-create-gh-ssh
+**Tipo:** feature
+
+## Contexto
+
+`ai pr` hoy valida preflight, pero el flujo final necesita crear el PR con `gh` usando `pr.md`.
+
+## Objetivo
+
+Agregar creacion de PR segura, con dry-run y guia clara para gh/SSH.
+
+## Alcance
+
+- Leer `pr.md`.
+- Validar setup.
+- Construir y ejecutar `gh pr create`.
+- Mantener dry-run.
+- No mergear PRs.
+
+## Criterios de aceptacion
+
+- Dry-run no crea PR.
+- Faltantes bloquean con mensaje claro.
+- Setup valido crea PR usando `pr.md`.
+- Tests mockean `gh`.
+
+## Plan tecnico resumido
+
+Extender preflight existente y agregar una capa de creacion que use argumentos seguros, cuerpo desde archivo y confirmacion explicita.
+
+## Pasos sugeridos de ejecucion
+
+1. Revisar `ai/github.js` y `ai-pr.test.js`.
+2. Definir flags de create.
+3. Leer y validar `pr.md`.
+4. Construir llamada segura a `gh`.
+5. Agregar tests de dry-run y success mockeado.
+
+## Restricciones
+
+- No instalar `gh`.
+- No modificar SSH config.
+- No mergear.
+
+## Riesgos
+
+- Crear PR contra base incorrecta.
+- Confundir alias SSH con identity file.
+
+## Checklist de finalizacion
+
+- [ ] Dry-run listo.
+- [ ] Create listo con mocks.
+- [ ] Faltantes bloquean.
+- [ ] Tests pasan.

package/specs/quiver-v22-guided-ai-workflow/slices/slice-08-pr-create-gh-ssh/slice.json

@@ -0,0 +1,53 @@
+{
+  "slice_id": "slice-08-pr-create-gh-ssh",
+  "ticket": "QUIVER-22-08",
+  "type": "feature",
+  "title": "PR creation with gh and SSH guidance",
+  "objective": "Create GitHub PRs from generated pr.md after validating gh, auth, branch, worktree, remote, and SSH inputs.",
+  "description": "Upgrade GitHub PR preflight into PR creation while keeping dry-run, explicit confirmation, and cross-platform setup guidance.",
+  "git": {
+    "branch_type": "feature",
+    "base_branch": "main",
+    "branch_slug": "pr-create-gh-ssh",
+    "branch_name": "feature/QUIVER-22-08-pr-create-gh-ssh"
+  },
+  "files": [
+    "src/create-quiver/commands/ai.js",
+    "src/create-quiver/lib/ai/github.js",
+    "src/create-quiver/lib/pr-create.js",
+    "tests/commands/ai-pr.test.js",
+    "tests/lib/ai-github.test.js"
+  ],
+  "depends_on": [
+    "slice-05-spec-worktree-lifecycle"
+  ],
+  "parallel_safe": "conditional",
+  "parallel_safe_reason": "Conceptually independent after spec worktree lifecycle, but it currently overlaps command-router files with executor and execution-wave slices. Run sequentially unless file ownership is split first.",
+  "must": [
+    "Read the generated pr.md body.",
+    "Validate gh is installed and authenticated.",
+    "Validate remote, branch, worktree, clean state, SSH alias, and identity file.",
+    "Support dry-run without creating a PR.",
+    "Create a PR with gh only after checks pass and user intent is explicit.",
+    "Keep PR merge out of scope."
+  ],
+  "not_included": [
+    "Merging PRs.",
+    "Post-merge cleanup.",
+    "Installing gh automatically."
+  ],
+  "acceptance": [
+    "Dry-run prints the gh command plan and creates no PR.",
+    "Missing gh/auth/identity/GitFlow guide/remote/dirty worktree blocks creation with clear guidance.",
+    "Valid setup creates a PR using pr.md.",
+    "The command never merges the PR.",
+    "Tests mock gh and do not require real GitHub auth."
+  ],
+  "tests": [
+    "node --test tests/commands/ai-pr.test.js tests/lib/ai-github.test.js",
+    "git diff --check"
+  ],
+  "estimated_hours": 7,
+  "status": "completed",
+  "blocked_reason": null
+}

package/specs/quiver-v22-guided-ai-workflow/slices/slice-09-post-merge-cleanup-release-safety/CLOSURE_BRIEF.md

@@ -0,0 +1,33 @@
+# CLOSURE BRIEF - slice-09: Post-merge cleanup and release safety
+
+## Resumen de lo realizado
+
+Se agrego cierre seguro de worktrees por spec con `spec close` y un gate de package safety para bloquear archivos locales sensibles antes del release.
+
+## Validacion contra criterios de aceptacion
+
+- [x] Cleanup bloquea PR no mergeado.
+- [x] Cleanup bloquea worktree sucio.
+- [x] Main local se actualiza.
+- [x] Package safety cubierto.
+
+## Cambios relevantes
+
+- Nuevo comando `npx create-quiver spec close <spec-dir>`.
+- `spec close` bloquea worktrees sucios y ramas de spec no mergeadas, salvo descarte explicito.
+- `spec close --dry-run` muestra la limpieza planeada sin remover worktrees.
+- `spec close` remueve el worktree mergeado y hace `git pull --ff-only` cuando hay remote base.
+- Nuevo modulo `package-safety` para validar paths del tarball.
+- `scripts/package-quiver.sh` ejecuta package safety sobre el contenido real de `npm pack`.
+
+## Pendientes
+
+Sin pendientes criticos para esta slice.
+
+## Riesgos remanentes
+
+Package safety valida nombres/rutas dentro del tarball; no inspecciona secretos embebidos dentro de archivos aparentemente seguros.
+
+## Recomendaciones futuras
+
+Mantener cleanup destructivo separado de PR merge. Si se agrega borrado de ramas remotas, debe quedar detras de un flag explicito distinto.

package/specs/quiver-v22-guided-ai-workflow/slices/slice-09-post-merge-cleanup-release-safety/EXECUTION_BRIEF.md

@@ -0,0 +1,59 @@
+# EXECUTION BRIEF - slice-09: Post-merge cleanup and release safety
+
+**Spec:** quiver-v22-guided-ai-workflow
+**Slice:** slice-09-post-merge-cleanup-release-safety
+**Tipo:** feature
+
+## Contexto
+
+Despues del merge, el usuario quiere cerrar el worktree y actualizar el checkout principal. Ademas, la publicacion npm debe bloquear archivos locales sensibles.
+
+## Objetivo
+
+Agregar cierre seguro de spec y guardas de packaging/release.
+
+## Alcance
+
+- Cleanup post-merge.
+- Validacion de PR mergeado.
+- Proteccion ante worktree sucio.
+- Pull del checkout principal.
+- Guardas para `npm pack`/release.
+
+## Criterios de aceptacion
+
+- No se limpia si el PR no esta mergeado.
+- No se limpia worktree sucio por default.
+- El cierre exitoso elimina worktree y actualiza main.
+- Packaging falla si entran archivos sensibles.
+
+## Plan tecnico resumido
+
+Extender lifecycle a nivel spec y agregar un chequeo de paquete que inspeccione el resultado de `npm pack --dry-run` o equivalente antes de publicar.
+
+## Pasos sugeridos de ejecucion
+
+1. Revisar cleanup actual y supuestos de base branch.
+2. Definir cierre de spec.
+3. Agregar validaciones de merge/dirty.
+4. Agregar package safety.
+5. Cubrir tests y smoke.
+
+## Restricciones
+
+- No mergear PR.
+- No publicar npm.
+- No descartar cambios sin flag explicito.
+
+## Riesgos
+
+- Borrar trabajo local no mergeado.
+- Fallar en repos con base branch distinta.
+- Falsos positivos en package safety.
+
+## Checklist de finalizacion
+
+- [ ] Cleanup seguro listo.
+- [ ] Main/develop sin hardcode incorrecto.
+- [ ] Package safety listo.
+- [ ] Tests pasan.

package/specs/quiver-v22-guided-ai-workflow/slices/slice-09-post-merge-cleanup-release-safety/slice.json

@@ -0,0 +1,59 @@
+{
+  "slice_id": "slice-09-post-merge-cleanup-release-safety",
+  "ticket": "QUIVER-22-09",
+  "type": "feature",
+  "title": "Post-merge cleanup and release safety",
+  "objective": "Safely close merged spec worktrees and prevent local AI/tool state from entering npm packages.",
+  "description": "Add post-merge lifecycle checks and release/package safety guards for secrets, env files, npm credentials, and local AI tool directories.",
+  "git": {
+    "branch_type": "feature",
+    "base_branch": "main",
+    "branch_slug": "post-merge-cleanup-release-safety",
+    "branch_name": "feature/QUIVER-22-09-post-merge-cleanup-release-safety"
+  },
+  "files": [
+    "src/create-quiver/index.js",
+    "src/create-quiver/lib/lifecycle.js",
+    "src/create-quiver/lib/git.js",
+    "src/create-quiver/lib/spec-worktrees.js",
+    "src/create-quiver/lib/package-safety.js",
+    "scripts/release-quiver.sh",
+    ".npmignore",
+    "tests/commands/spec-close.test.js",
+    "tests/lib/package-safety.test.js"
+  ],
+  "depends_on": [
+    "slice-07-execution-waves-delegation",
+    "slice-08-pr-create-gh-ssh"
+  ],
+  "parallel_safe": "no",
+  "parallel_safe_reason": "Cleanup and release safety must integrate final workflow state and PR behavior.",
+  "must": [
+    "Refuse normal cleanup before PR merge is confirmed.",
+    "Refuse cleanup when the worktree is dirty unless explicit discard behavior is used.",
+    "Remove the spec worktree after safe confirmation.",
+    "Pull merged changes into the main local checkout.",
+    "Fail package/release safety if local settings, env files, npm credentials, or AI tool local state would enter the tarball.",
+    "Keep destructive operations explicit and recoverable."
+  ],
+  "not_included": [
+    "Merging PRs.",
+    "Deleting remote branches without explicit existing workflow support.",
+    "Publishing a new npm version."
+  ],
+  "acceptance": [
+    "Unmerged PR blocks normal spec cleanup.",
+    "Dirty worktree blocks normal spec cleanup.",
+    "Merged clean spec can be closed and main checkout can be pulled.",
+    "Release/package safety fails when unsafe local files would be packaged.",
+    "Release/package safety passes when unsafe paths are ignored or absent."
+  ],
+  "tests": [
+    "node --test tests/commands/spec-close.test.js tests/lib/package-safety.test.js",
+    "npm pack --dry-run",
+    "git diff --check"
+  ],
+  "estimated_hours": 8,
+  "status": "completed",
+  "blocked_reason": null
+}

package/specs/quiver-v22-guided-ai-workflow/slices/slice-10-docs-smokes-release-readiness/CLOSURE_BRIEF.md

@@ -0,0 +1,34 @@
+# CLOSURE BRIEF - slice-10: Final docs, smokes, and release readiness
+
+## Resumen de lo realizado
+
+- Se actualizaron README, README_FOR_AI, CHANGELOG, ROADMAP, BACKLOG y templates generados para presentar el guided AI workflow como disponible.
+- Se alinearon los snippets de onboarding con aprobaciones persistidas, `spec start`, ejecución por olas, PR con `pr.md` y cierre de worktree.
+- Se agregó `smoke:guided-workflow` y se reforzaron los smokes existentes para el contrato real post-`analyze`, scripts nuevos y `slice-00` obligatorio.
+- `docs/AI_CONTEXT.md` refrescado por `analyze` conserva front matter para mantener el contrato token-efficient.
+- Se actualizaron STATUS, EVIDENCE_REPORT y el estado del slice.
+
+## Validacion contra criterios de aceptacion
+
+- [x] Docs finales listas.
+- [x] Smokes listas.
+- [x] STATUS/EVIDENCE actualizados.
+- [x] No se publico npm.
+
+## Cambios relevantes
+
+- Root docs y templates muestran `prepare`, `ai approve`, `ai execute-plan`, `ai pr --input`, `spec start/status/close` y commit opt-in.
+- Scripts de smoke cubren flujo guiado, creación/migración, package safety y fixtures con `slice-00`.
+- El package dry-run pasó usando cache temporal por permisos rotos en la cache global de npm.
+
+## Pendientes
+
+- Publicar una nueva version npm queda fuera de este slice y debe hacerse con el flujo de release.
+
+## Riesgos remanentes
+
+- La cache global `~/.npm` tiene archivos root-owned; `npm pack --dry-run` requiere cache temporal o corregir permisos localmente.
+
+## Recomendaciones futuras
+
+- Ejecutar `npm run release:quiver` o `bash scripts/release-quiver.sh ...` solo despues de revisar este PR y decidir el bump.

package/specs/quiver-v22-guided-ai-workflow/slices/slice-10-docs-smokes-release-readiness/EXECUTION_BRIEF.md

@@ -0,0 +1,58 @@
+# EXECUTION BRIEF - slice-10: Final docs, smokes, and release readiness
+
+**Spec:** quiver-v22-guided-ai-workflow
+**Slice:** slice-10-docs-smokes-release-readiness
+**Tipo:** docs-test
+
+## Contexto
+
+Cuando todas las piezas existen, hay que actualizar la documentacion publica, templates generados, smokes y evidencia.
+
+## Objetivo
+
+Cerrar la feature con docs completas, pruebas y readiness de release sin publicar.
+
+## Alcance
+
+- README y guia IA.
+- Templates/docs generados.
+- Smoke tests.
+- STATUS/EVIDENCE_REPORT.
+- Checklist de release.
+
+## Criterios de aceptacion
+
+- Docs muestran el flujo como disponible.
+- Smokes cubren happy path y fallas principales.
+- Evidencia actualizada.
+- No se publica npm.
+
+## Plan tecnico resumido
+
+Actualizar docs y templates despues de terminar comportamiento, luego ejecutar suite amplia y registrar evidencia.
+
+## Pasos sugeridos de ejecucion
+
+1. Revisar todos los comandos implementados.
+2. Actualizar README y README_FOR_AI.
+3. Actualizar generated docs/templates.
+4. Agregar smokes.
+5. Ejecutar tests.
+6. Actualizar STATUS/EVIDENCE_REPORT.
+
+## Restricciones
+
+- No publicar npm.
+- No abrir PR si no se pidio.
+
+## Riesgos
+
+- Documentar comandos con nombres distintos a los implementados.
+- Smokes demasiado dependientes de herramientas reales.
+
+## Checklist de finalizacion
+
+- [ ] Docs finales actualizadas.
+- [ ] Templates actualizados.
+- [ ] Smokes agregados.
+- [ ] Evidencia final registrada.

package/specs/quiver-v22-guided-ai-workflow/slices/slice-10-docs-smokes-release-readiness/slice.json

@@ -0,0 +1,60 @@
+{
+  "slice_id": "slice-10-docs-smokes-release-readiness",
+  "ticket": "QUIVER-22-10",
+  "type": "docs-test",
+  "title": "Final docs, smokes, and release readiness",
+  "objective": "Finish the guided workflow with updated user docs, generated templates, smoke coverage, and release readiness evidence.",
+  "description": "Update public docs and generated project templates, add end-to-end smoke coverage, and confirm the feature is ready for release without publishing.",
+  "git": {
+    "branch_type": "feature",
+    "base_branch": "main",
+    "branch_slug": "guided-workflow-release-readiness",
+    "branch_name": "feature/QUIVER-22-10-guided-workflow-release-readiness"
+  },
+  "files": [
+    "README.md",
+    "README_FOR_AI.md",
+    "CHANGELOG.md",
+    "src/create-quiver/lib/init-docs.js",
+    "src/create-quiver/lib/init-layout.js",
+    "tests/commands/*.test.js",
+    "scripts/ci/*.sh",
+    "specs/quiver-v22-guided-ai-workflow/STATUS.md",
+    "specs/quiver-v22-guided-ai-workflow/EVIDENCE_REPORT.md"
+  ],
+  "depends_on": [
+    "slice-09-post-merge-cleanup-release-safety"
+  ],
+  "parallel_safe": "no",
+  "parallel_safe_reason": "Final docs and smokes must run after all behavior slices are complete.",
+  "must": [
+    "Document the finished guided workflow in root docs.",
+    "Update generated project docs/templates where users see commands.",
+    "Add smoke coverage for the happy path and major failure paths.",
+    "Update STATUS and EVIDENCE_REPORT.",
+    "Run full relevant test suite.",
+    "Do not publish npm in this slice."
+  ],
+  "not_included": [
+    "Changing feature behavior after acceptance unless a blocking bug is found.",
+    "Publishing a release.",
+    "Merging PR."
+  ],
+  "acceptance": [
+    "README shows the guided AI workflow as available behavior.",
+    "Generated docs mention prepare, approvals, executor commits, PR creation, and cleanup.",
+    "Smoke tests cover dry-run preparation, approvals, execution waves, PR dry-run, cleanup dry-run, and package safety.",
+    "STATUS and EVIDENCE_REPORT reflect completed slices.",
+    "Release checklist is ready but no npm publish is performed."
+  ],
+  "tests": [
+    "node --test tests/**/*.test.js",
+    "npm run smoke:create-quiver",
+    "npm run smoke:tiered-pack",
+    "npm pack --dry-run",
+    "git diff --check"
+  ],
+  "estimated_hours": 6,
+  "status": "completed",
+  "blocked_reason": null
+}