create-quiver 0.9.1 → 0.12.0

package/specs/quiver-v21-ai-first-layout/slices/slice-05-empty-specs-layout-doctor/EXECUTION_BRIEF.md

@@ -0,0 +1,60 @@
+# EXECUTION BRIEF - slice-05: Empty specs and layout doctor
+
+**Spec:** quiver-v21-ai-first-layout
+**Slice:** slice-05-empty-specs-layout-doctor
+**Tipo:** feature
+
+## Contexto
+
+Default init ya no debe crear specs falsas. Por eso los comandos que recorren slices deben aceptar que todavia no haya specs.
+
+## Objetivo
+
+Hacer que comandos de planificacion y doctor soporten layout nuevo, legacy e hibrido sin falsos errores.
+
+## Alcance
+
+- `plan`
+- `graph`
+- `next`
+- `doctor`
+- Deteccion de layout.
+- Tests de no-spec repos.
+
+## Criterios de aceptacion
+
+- `plan`, `graph`, `next` y `doctor` no fallan por ausencia de specs.
+- Doctor detecta layout nuevo, legacy, hibrido e incompleto.
+- Doctor reporta recomendaciones accionables.
+- Proyectos con specs existentes siguen funcionando.
+
+## Plan tecnico resumido
+
+Separar "no specs yet" de errores reales. Agregar detector de layout en doctor y actualizar formatters para comunicar estados vacios.
+
+## Pasos sugeridos de ejecucion
+
+1. Agregar fixtures sin specs.
+2. Ajustar colectores de slices para estado vacio.
+3. Ajustar salidas human/json.
+4. Agregar detector de layout.
+5. Agregar tests de legacy/hibrido.
+
+## Restricciones
+
+- No migrar archivos.
+- No ocultar errores reales de JSON invalido.
+- No cambiar formato JSON existente salvo campos compatibles.
+
+## Riesgos
+
+- Convertir errores reales en estados vacios.
+- Romper automatizaciones que esperan exit code no cero.
+- Mensajes ambiguos para usuarios nuevos.
+
+## Checklist de finalizacion
+
+- [ ] No-spec tests pasan.
+- [ ] Layout doctor testeado.
+- [ ] Proyectos con specs siguen pasando.
+- [ ] Salidas JSON siguen parseables.

package/specs/quiver-v21-ai-first-layout/slices/slice-05-empty-specs-layout-doctor/slice.json

@@ -0,0 +1,65 @@
+{
+  "slice_id": "slice-05-empty-specs-layout-doctor",
+  "ticket": "QUIVER-21-05",
+  "type": "feature",
+  "title": "Support empty specs state and layout doctor",
+  "objective": "Make plan, graph, next, and doctor treat projects without specs as valid while doctor reports new, legacy, and hybrid layouts.",
+  "description": "Default init no longer creates placeholder specs, so orchestration commands must handle an empty specs directory or no specs directory cleanly.",
+  "git": {
+    "branch_type": "feature",
+    "base_branch": "main",
+    "branch_slug": "empty-specs-layout-doctor",
+    "branch_name": "feature/QUIVER-21-05-empty-specs-layout-doctor"
+  },
+  "files": [
+    "src/create-quiver/commands/plan.js",
+    "src/create-quiver/commands/graph.js",
+    "src/create-quiver/commands/next.js",
+    "src/create-quiver/lib/slice-graph.js",
+    "src/create-quiver/lib/doctor.js",
+    "src/create-quiver/index.js",
+    "tests/commands/doctor.test.js",
+    "tests/commands/plan.test.js",
+    "tests/commands/graph.test.js",
+    "tests/commands/next.test.js",
+    "tests/lib/doctor.test.js",
+    "specs/quiver-v21-ai-first-layout/STATUS.md",
+    "specs/quiver-v21-ai-first-layout/EVIDENCE_REPORT.md",
+    "specs/quiver-v21-ai-first-layout/slices/slice-05-empty-specs-layout-doctor/CLOSURE_BRIEF.md",
+    "specs/quiver-v21-ai-first-layout/slices/slice-05-empty-specs-layout-doctor/slice.json"
+  ],
+  "depends_on": [
+    "slice-03-generation-profiles-visible-contract",
+    "slice-04-analyze-scan-relocation"
+  ],
+  "parallel_safe": "after_dependencies",
+  "parallel_safe_reason": "Requires the new default no-spec behavior and scan path compatibility.",
+  "must": [
+    "Make `plan` return a clear valid empty state when no specs exist.",
+    "Make `graph` return a clear valid empty state when no specs exist.",
+    "Make `next` return a clear valid empty state when no specs exist.",
+    "Make `doctor` detect layout type: new, legacy, hybrid, or incomplete.",
+    "Doctor must not treat missing specs as an error immediately after default init.",
+    "Doctor should surface actionable recommendations for legacy files."
+  ],
+  "not_included": [
+    "Migrating legacy files.",
+    "Changing spec generation.",
+    "Documentation copy beyond command output strings."
+  ],
+  "acceptance": [
+    "No-spec projects do not fail `plan`, `graph`, `next`, or `doctor` unexpectedly.",
+    "Doctor reports layout state with clear language.",
+    "Legacy paths are warnings or recommendations, not hard failures.",
+    "Existing behavior for projects with specs remains intact."
+  ],
+  "tests": [
+    "node --test tests/commands/doctor.test.js tests/lib/doctor.test.js tests/commands/plan.test.js tests/commands/graph.test.js tests/commands/next.test.js",
+    "node --test tests/**/*.test.js",
+    "git diff --check"
+  ],
+  "estimated_hours": 6,
+  "actual_hours": 5,
+  "status": "completed",
+  "blocked_reason": null
+}

package/specs/quiver-v21-ai-first-layout/slices/slice-06-legacy-migration-optional-assets/CLOSURE_BRIEF.md

@@ -0,0 +1,31 @@
+# CLOSURE BRIEF - slice-06: Legacy migration and optional assets
+
+## Resumen de lo realizado
+
+Se implemento la transicion no destructiva para migracion y se habilitaron los assets opcionales explicitos.
+
+## Validacion contra criterios de aceptacion
+
+- [x] Migracion no destructiva.
+- [x] Legacy scripts opcionales.
+- [x] Templates exportados bajo `.quiver/`.
+- [x] Full mode validado.
+
+## Cambios relevantes
+
+- `migrate` ahora reporta layout legado detectado y preservado, incluyendo `docs-template/`, `tools/scripts/` y `docs/PROJECT_SCAN.json`.
+- `init --legacy-scripts` crea wrappers Bash y scripts npm compatibles.
+- `init --include-templates` exporta templates a `.quiver/templates/`.
+- `init --full` sigue habilitando el layout amplio de compatibilidad.
+
+## Pendientes
+
+Ninguno para este slice.
+
+## Riesgos remanentes
+
+- La salida de migracion sigue siendo conservadora: detecta y reporta, pero no limpia automaticamente el layout viejo.
+
+## Recomendaciones futuras
+
+- Mantener las smokes de migracion y perfiles opcionales en slices posteriores para evitar regresiones.

package/specs/quiver-v21-ai-first-layout/slices/slice-06-legacy-migration-optional-assets/EXECUTION_BRIEF.md

@@ -0,0 +1,62 @@
+# EXECUTION BRIEF - slice-06: Legacy migration and optional assets
+
+**Spec:** quiver-v21-ai-first-layout
+**Slice:** slice-06-legacy-migration-optional-assets
+**Tipo:** feature
+
+## Contexto
+
+Cambiar el default no alcanza: proyectos existentes pueden tener layout viejo y algunos usuarios siguen necesitando scripts o templates visibles.
+
+## Objetivo
+
+Agregar transicion no destructiva y flags explicitos para assets opcionales.
+
+## Alcance
+
+- `migrate` legacy detection.
+- `--legacy-scripts`.
+- `--include-templates`.
+- `--full` broad optional assets.
+- Smokes de migracion y perfiles opcionales.
+
+## Criterios de aceptacion
+
+- `migrate` no borra ni mueve archivos legacy.
+- Layout legacy se detecta y reporta.
+- `--legacy-scripts` crea wrappers y scripts validos.
+- `--include-templates` exporta a `.quiver/templates/`.
+- `--full` mantiene assets amplios de forma explicita.
+
+## Plan tecnico resumido
+
+Extender perfiles y migracion para distinguir cleanup sugerido de acciones destructivas. Mantener compatibilidad por lectura y generar opcionales solo cuando el usuario lo pide.
+
+## Pasos sugeridos de ejecucion
+
+1. Agregar deteccion legacy en migrate.
+2. Implementar generacion legacy scripts bajo flag.
+3. Implementar export de templates bajo `.quiver/templates/`.
+4. Definir set full.
+5. Actualizar package scripts segun flags.
+6. Agregar smokes de migracion.
+
+## Restricciones
+
+- No borrar archivos legacy.
+- No crear root `docs-template/` en layout nuevo.
+- No mezclar scripts legacy en default.
+
+## Riesgos
+
+- Flags combinados generen scripts inconsistentes.
+- Migracion demasiado silenciosa.
+- Full mode arrastre demasiada deuda sin documentar.
+
+## Checklist de finalizacion
+
+- [ ] Migrate preserva legacy.
+- [ ] Legacy scripts validos.
+- [ ] Include templates validado.
+- [ ] Full mode validado.
+- [ ] Recomendaciones de migracion claras.

package/specs/quiver-v21-ai-first-layout/slices/slice-06-legacy-migration-optional-assets/slice.json

@@ -0,0 +1,66 @@
+{
+  "slice_id": "slice-06-legacy-migration-optional-assets",
+  "ticket": "QUIVER-21-06",
+  "type": "feature",
+  "title": "Add legacy migration and optional assets",
+  "objective": "Make migration non-destructive for legacy layouts and implement explicit optional generation for legacy scripts and templates.",
+  "description": "This slice handles transition behavior so existing projects can keep working while new projects stay clean by default.",
+  "git": {
+    "branch_type": "feature",
+    "base_branch": "main",
+    "branch_slug": "legacy-migration-optional-assets",
+    "branch_name": "feature/QUIVER-21-06-legacy-migration-optional-assets"
+  },
+  "files": [
+    "src/create-quiver/index.js",
+    "src/create-quiver/lib/init-docs.js",
+    "src/create-quiver/lib/init-layout.js",
+    "src/create-quiver/lib/state.js",
+    "scripts/migrate-project.sh",
+    "scripts/ci/smoke-create-quiver.sh",
+    "scripts/ci/smoke-cross-platform.js",
+    "tests/commands/init-profiles.test.js",
+    "specs/quiver-v21-ai-first-layout/STATUS.md",
+    "specs/quiver-v21-ai-first-layout/EVIDENCE_REPORT.md",
+    "specs/quiver-v21-ai-first-layout/slices/slice-06-legacy-migration-optional-assets/CLOSURE_BRIEF.md",
+    "specs/quiver-v21-ai-first-layout/slices/slice-06-legacy-migration-optional-assets/slice.json"
+  ],
+  "depends_on": [
+    "slice-03-generation-profiles-visible-contract",
+    "slice-04-analyze-scan-relocation"
+  ],
+  "parallel_safe": "after_dependencies",
+  "parallel_safe_reason": "Can run after generation profiles and scan relocation are stable.",
+  "must": [
+    "`migrate` must not delete or move legacy files without explicit user action.",
+    "`migrate` must detect legacy root `docs-template/`, `tools/scripts/`, and `docs/PROJECT_SCAN.json`.",
+    "`--legacy-scripts` must create Bash wrappers and matching package scripts.",
+    "`--include-templates` must export templates under `.quiver/templates/`.",
+    "`--full` must keep broad optional docs and OSS/community files as explicit behavior.",
+    "Migration output must explain recommended next steps for legacy-to-AI-first cleanup."
+  ],
+  "not_included": [
+    "Automatic destructive cleanup of legacy files.",
+    "Publishing package release.",
+    "Long-form documentation rewrite."
+  ],
+  "acceptance": [
+    "Legacy project migration preserves existing files.",
+    "Legacy layout is detected and reported.",
+    "`--legacy-scripts` creates wrappers and scripts that point to real files.",
+    "`--include-templates` creates `.quiver/templates/` and no root `docs-template/`.",
+    "`--full` covers optional broad assets intentionally."
+  ],
+  "tests": [
+    "node --test tests/commands/init-profiles.test.js tests/lib/init-docs.test.js",
+    "node --test tests/**/*.test.js",
+    "bash scripts/ci/smoke-init-docs.sh",
+    "bash scripts/ci/smoke-create-quiver.sh",
+    "node scripts/ci/smoke-cross-platform.js",
+    "git diff --check"
+  ],
+  "estimated_hours": 7,
+  "actual_hours": 6,
+  "status": "completed",
+  "blocked_reason": null
+}

package/specs/quiver-v21-ai-first-layout/slices/slice-07-docs-guidance-alignment/CLOSURE_BRIEF.md

@@ -0,0 +1,33 @@
+# CLOSURE BRIEF - slice-07: Documentation and guidance alignment
+
+## Resumen de lo realizado
+
+Se alineo la documentacion humana, la guia para agentes y las plantillas generadas con el layout AI-first actual. El flujo default ahora queda documentado como contrato visible chico con maquinaria interna en `.quiver/`, mientras `docs-template/`, `tools/scripts/` y los specs placeholder quedan marcados como compatibilidad u opciones explicitas.
+
+## Validacion contra criterios de aceptacion
+
+- [x] Visible vs interno documentado.
+- [x] Legacy marcado como compatibilidad.
+- [x] Specs reales documentadas en fase spec.
+- [x] Paths de scan/map correctos.
+
+## Cambios relevantes
+
+- `README.md` prioriza `init --name`, `.quiver/`, `docs/PROJECT_MAP.md` y el flujo planner/executor.
+- `README_FOR_AI.md` dejo de presentar `docs-template/` como onboarding normal.
+- `docs/AI_ONBOARDING_PROMPT.md.template`, `docs/WORKFLOW.md.template` y `docs/STANDARD.md.template` apuntan al mapa visible y al scan crudo en `.quiver/scans/PROJECT_SCAN.json`.
+- `docs/COMMANDS.md.template` documenta init, profiles y analyzer output.
+- `src/create-quiver/lib/init-docs.js` y `scripts/init-docs.sh` ajustan README generado y dejan el script Bash como compatibilidad legacy.
+- Los smokes esperan la ruta nueva del scan en el onboarding prompt generado.
+
+## Pendientes
+
+Ninguno para este slice.
+
+## Riesgos remanentes
+
+El script Bash `scripts/init-docs.sh` sigue siendo una ruta legacy amplia y conserva referencias internas a `docs-template/`, `tools/scripts/` y `slice-template` porque ese es su proposito de compatibilidad.
+
+## Recomendaciones futuras
+
+Completar `slice-08` con la validacion final de smokes, release readiness y consistencia del paquete antes de publicar.

package/specs/quiver-v21-ai-first-layout/slices/slice-07-docs-guidance-alignment/EXECUTION_BRIEF.md

@@ -0,0 +1,61 @@
+# EXECUTION BRIEF - slice-07: Documentation and guidance alignment
+
+**Spec:** quiver-v21-ai-first-layout
+**Slice:** slice-07-docs-guidance-alignment
+**Tipo:** docs
+
+## Contexto
+
+Despues de cambiar comportamiento, la documentacion debe dejar de presentar `docs-template/`, `tools/scripts/` y spec placeholder como default.
+
+## Objetivo
+
+Alinear README, README_FOR_AI, generated README y templates con el nuevo layout AI-first.
+
+## Alcance
+
+- Root README.
+- AI guide.
+- Generated README in Node and Bash paths.
+- Docs templates for commands, workflow, onboarding, support and troubleshooting.
+- Smoke assertions de docs.
+
+## Criterios de aceptacion
+
+- Toda la documentacion diferencia contrato visible de maquinaria interna.
+- `docs-template/` y `tools/scripts/` aparecen solo como legacy/opcionales.
+- Specs reales se documentan como salida de `ai plan --phase spec`.
+- Scan crudo y project map tienen paths correctos.
+
+## Plan tecnico resumido
+
+Actualizar docs despues de estabilizar comportamiento. Agregar asserts en smokes para evitar drift.
+
+## Pasos sugeridos de ejecucion
+
+1. Revisar textos actuales que nombren paths legacy.
+2. Actualizar README y README_FOR_AI.
+3. Actualizar generated README.
+4. Actualizar templates.
+5. Ajustar smokes de doc.
+6. Validar que no se prometan comandos inexistentes.
+
+## Restricciones
+
+- No cambiar codigo de comportamiento salvo generated README text.
+- No duplicar instrucciones largas.
+- No documentar flags no implementados.
+
+## Riesgos
+
+- Docs queden ahead del comportamiento.
+- README se vuelva demasiado largo.
+- Onboarding IA vuelva a abrir `.quiver/` innecesariamente.
+
+## Checklist de finalizacion
+
+- [ ] README actualizado.
+- [ ] README_FOR_AI actualizado.
+- [ ] Generated README actualizado.
+- [ ] Templates actualizados.
+- [ ] Smokes de docs pasan.

package/specs/quiver-v21-ai-first-layout/slices/slice-07-docs-guidance-alignment/slice.json

@@ -0,0 +1,67 @@
+{
+  "slice_id": "slice-07-docs-guidance-alignment",
+  "ticket": "QUIVER-21-07",
+  "type": "docs",
+  "title": "Align documentation with AI-first layout",
+  "objective": "Update human and AI-facing documentation so every source describes the same visible contract and internal `.quiver/` model.",
+  "description": "Behavior changes need docs alignment to avoid two competing truths about `docs-template/`, `tools/scripts/`, scans, and specs.",
+  "git": {
+    "branch_type": "docs",
+    "base_branch": "main",
+    "branch_slug": "docs-guidance-alignment",
+    "branch_name": "docs/QUIVER-21-07-docs-guidance-alignment"
+  },
+  "files": [
+    "README.md",
+    "README_FOR_AI.md",
+    "docs/AI_ONBOARDING_PROMPT.md.template",
+    "docs/COMMANDS.md.template",
+    "docs/WORKFLOW.md.template",
+    "docs/SUPPORT_MATRIX.md.template",
+    "docs/TROUBLESHOOTING.md.template",
+    "docs/GITFLOW_PR_GUIDE.md.template",
+    "src/create-quiver/lib/init-docs.js",
+    "scripts/init-docs.sh",
+    "scripts/ci/smoke-create-quiver.sh",
+    "scripts/ci/smoke-init-docs.sh",
+    "specs/quiver-v21-ai-first-layout/STATUS.md",
+    "specs/quiver-v21-ai-first-layout/EVIDENCE_REPORT.md",
+    "specs/quiver-v21-ai-first-layout/slices/slice-07-docs-guidance-alignment/CLOSURE_BRIEF.md",
+    "specs/quiver-v21-ai-first-layout/slices/slice-07-docs-guidance-alignment/slice.json"
+  ],
+  "depends_on": [
+    "slice-05-empty-specs-layout-doctor",
+    "slice-06-legacy-migration-optional-assets"
+  ],
+  "parallel_safe": "after_dependencies",
+  "parallel_safe_reason": "Docs must reflect final behavior from previous slices.",
+  "must": [
+    "Update root README to present AI-first layout and init profiles accurately.",
+    "Update README_FOR_AI so `docs-template/` is no longer the normal onboarding flow.",
+    "Update generated README content to explain visible contract vs internal `.quiver/` machinery.",
+    "Update commands/support/troubleshooting templates for new paths and flags.",
+    "Document that real specs are created by `ai plan --phase spec`, not default init.",
+    "Document legacy paths as compatibility, not recommended default."
+  ],
+  "not_included": [
+    "Changing behavior.",
+    "Release publication.",
+    "Large marketing rewrite unrelated to layout."
+  ],
+  "acceptance": [
+    "Docs agree that `.quiver/` is internal.",
+    "Docs agree that default init does not create `docs-template/`, `tools/scripts/`, or placeholder specs.",
+    "Generated README points agents to visible contract first.",
+    "Docs mention `.quiver/scans/PROJECT_SCAN.json` and visible `docs/PROJECT_MAP.md` correctly.",
+    "Legacy guidance is clearly marked as compatibility."
+  ],
+  "tests": [
+    "bash scripts/ci/smoke-init-docs.sh",
+    "npm run smoke:create-quiver",
+    "git diff --check"
+  ],
+  "estimated_hours": 5,
+  "actual_hours": 4,
+  "status": "completed",
+  "blocked_reason": null
+}

package/specs/quiver-v21-ai-first-layout/slices/slice-08-smokes-release-readiness/CLOSURE_BRIEF.md

@@ -0,0 +1,35 @@
+# CLOSURE BRIEF - slice-08: Smokes and release readiness
+
+## Resumen de lo realizado
+
+Se ejecuto la matriz final de validacion para v21 y se ajusto `smoke-tiered-pack` para que pruebe explicitamente el perfil `--full --skip-install` cuando necesita assets legacy como spec placeholder y wrappers. Tambien se actualizaron evidencia, status y cuerpo de PR.
+
+## Validacion contra criterios de aceptacion
+
+- [x] Suite Node pasa.
+- [x] Smokes pasan.
+- [x] Evidence actualizado.
+- [x] PR body listo.
+
+## Cambios relevantes
+
+- `scripts/ci/smoke-tiered-pack.sh` usa `init --full --skip-install` y espera la guia correcta de `doctor` para el estado AI-first sin specs.
+- `scripts/ci/smoke-cross-platform.js` usa `init` explicito para el smoke de perfiles.
+- `src/create-quiver/index.js` tiene fallback sin `npm` para empaquetar templates cuando `--skip-install` evita instalar dependencias.
+- Scripts legacy quedaron alineados con shellcheck y `check-slice` acepta `develop` local en modo sin origin.
+- `specs/quiver-v21-ai-first-layout/EVIDENCE_REPORT.md` registra la matriz final.
+- `specs/quiver-v21-ai-first-layout/STATUS.md` marca la spec como completada.
+- `specs/quiver-v21-ai-first-layout/pr.md` queda listo para copiar al PR.
+- `slice.json` queda marcado como completado.
+
+## Pendientes
+
+No quedan pendientes dentro de esta spec. No se publico npm ni se abrio PR.
+
+## Riesgos remanentes
+
+La matriz local valida macOS/shell actual y el smoke cross-platform simulado; la verificacion definitiva multi-OS queda en CI.
+
+## Recomendaciones futuras
+
+Abrir PR de la spec con el cuerpo preparado y correr la CI completa antes de publicar una nueva version npm.

package/specs/quiver-v21-ai-first-layout/slices/slice-08-smokes-release-readiness/EXECUTION_BRIEF.md

@@ -0,0 +1,66 @@
+# EXECUTION BRIEF - slice-08: Smokes and release readiness
+
+**Spec:** quiver-v21-ai-first-layout
+**Slice:** slice-08-smokes-release-readiness
+**Tipo:** chore
+
+## Contexto
+
+El cambio toca init, analyze, doctor, docs y compatibilidad legacy. El cierre debe probar todos los perfiles y estados criticos.
+
+## Objetivo
+
+Completar validaciones, evidencia y cuerpo de PR para la spec v21.
+
+## Alcance
+
+- Smokes de perfiles.
+- Smokes cross-platform.
+- Suite Node.
+- Evidence report.
+- PR body.
+- Fixes menores necesarios para que las validaciones pasen.
+
+## Criterios de aceptacion
+
+- Suite Node completa pasa.
+- Smokes principales pasan.
+- Evidencia real agregada.
+- PR body listo.
+- No queda drift documental conocido.
+
+## Plan tecnico resumido
+
+Ejecutar la matriz completa despues de todas las slices funcionales y documentales. Ajustar smokes o errores menores solo dentro del alcance de v21.
+
+## Pasos sugeridos de ejecucion
+
+1. Ejecutar suite Node.
+2. Ejecutar smoke create-quiver.
+3. Ejecutar smoke init-docs.
+4. Ejecutar smoke cross-platform.
+5. Revisar `git diff --check`.
+6. Actualizar evidence y PR body.
+7. Cerrar status.
+
+## Restricciones
+
+- No publicar npm.
+- No abrir PR sin pedido explicito.
+- No agregar nuevo alcance funcional.
+
+## Riesgos
+
+- Smokes lentos o dependientes de red.
+- Tests legacy que asumen layout viejo.
+- Fixes de ultimo minuto que expandan alcance.
+
+## Checklist de finalizacion
+
+- [ ] `node --test tests/**/*.test.js` pasa.
+- [ ] `npm run smoke:create-quiver` pasa.
+- [ ] `bash scripts/ci/smoke-init-docs.sh` pasa.
+- [ ] `node scripts/ci/smoke-cross-platform.js` pasa.
+- [ ] `git diff --check` pasa.
+- [ ] Evidence report actualizado.
+- [ ] PR body actualizado.

package/specs/quiver-v21-ai-first-layout/slices/slice-08-smokes-release-readiness/slice.json

@@ -0,0 +1,62 @@
+{
+  "slice_id": "slice-08-smokes-release-readiness",
+  "ticket": "QUIVER-21-08",
+  "type": "chore",
+  "title": "Finalize smokes and release readiness",
+  "objective": "Run and harden the full validation matrix for the AI-first layout before PR or release work.",
+  "description": "This slice closes cross-profile smoke coverage, evidence, and final consistency checks.",
+  "git": {
+    "branch_type": "chore",
+    "base_branch": "main",
+    "branch_slug": "smokes-release-readiness",
+    "branch_name": "chore/QUIVER-21-08-smokes-release-readiness"
+  },
+  "files": [
+    "scripts/ci/smoke-create-quiver.sh",
+    "scripts/ci/smoke-init-docs.sh",
+    "scripts/ci/smoke-cross-platform.js",
+    "tests/**/*.test.js",
+    "specs/quiver-v21-ai-first-layout/EVIDENCE_REPORT.md",
+    "specs/quiver-v21-ai-first-layout/STATUS.md",
+    "specs/quiver-v21-ai-first-layout/pr.md",
+    "specs/quiver-v21-ai-first-layout/slices/slice-08-smokes-release-readiness/CLOSURE_BRIEF.md",
+    "specs/quiver-v21-ai-first-layout/slices/slice-08-smokes-release-readiness/slice.json"
+  ],
+  "depends_on": [
+    "slice-07-docs-guidance-alignment"
+  ],
+  "parallel_safe": "after_dependencies",
+  "parallel_safe_reason": "Final validation depends on completed behavior and docs.",
+  "must": [
+    "Validate default, minimal, full, legacy-scripts, include-templates, and dry-run profiles.",
+    "Validate analyze scan relocation and visible project map.",
+    "Validate no-spec state for plan, graph, next, and doctor.",
+    "Validate legacy compatibility for scan, docs-template, and tools/scripts where applicable.",
+    "Update evidence report with real commands and outcomes.",
+    "Update PR body with summary, validation, and risks."
+  ],
+  "not_included": [
+    "Publishing to npm.",
+    "Opening the PR unless explicitly requested.",
+    "Changing product behavior beyond smoke fixes required for this spec."
+  ],
+  "acceptance": [
+    "Full Node test suite passes.",
+    "Create-quiver smoke passes.",
+    "Init-docs smoke passes.",
+    "Cross-platform smoke passes.",
+    "Evidence report is updated.",
+    "PR body is ready for review."
+  ],
+  "tests": [
+    "node --test tests/**/*.test.js",
+    "npm run smoke:create-quiver",
+    "bash scripts/ci/smoke-init-docs.sh",
+    "node scripts/ci/smoke-cross-platform.js",
+    "git diff --check"
+  ],
+  "estimated_hours": 4,
+  "actual_hours": 3,
+  "status": "completed",
+  "blocked_reason": null
+}