create-quiver 0.15.2 → 0.15.4

package/docs/WORKFLOW.md.es.template

@@ -0,0 +1,29 @@
+# Workflow
+
+**Fecha:** {{FECHA}}
+
+Este documento define el workflow canonico de implementacion del proyecto.
+
+## Reglas centrales
+
+- No implementar sin slice.
+- Un slice equivale a un commit.
+- Un spec equivale a un PR.
+- El spec define el plan; el slice define la ejecucion.
+- Ningun slice debe ejecutarse hasta estar listo.
+- La salida JSON y los artefactos machine-readable no se traducen.
+
+## Planificacion
+
+1. Ejecuta `npx create-quiver flow` si no sabes el siguiente paso seguro.
+2. Redacta criterios de aceptacion.
+3. Redacta y revisa el plan tecnico.
+4. Crea el spec con `npx create-quiver spec create`.
+5. Ejecuta slices de a uno, manteniendo scope y evidencia.
+
+## Validacion
+
+```bash
+npx create-quiver spec validate specs/<spec> --strict
+git diff --check
+```

package/docs/WORKFLOW.md.template

@@ -32,7 +32,7 @@ Use maps, metadata, diffs, and summaries first. Open full files only when the sm
 
 ## Planning
 
-1. Run `npx create-quiver flow` when the next safe command is unclear.
+1. Run `npx create-quiver flow` when the next safe command is unclear, or `npx create-quiver dashboard` when you need consolidated read-only project/spec/slice state.
 2. Triage the request.
 3. Save reusable planner/executor provider choices with `ai agent set` when the team has preferred local AI CLIs.
 4. Use `ai plan --phase acceptance` to draft criteria, then save the approved version with `ai approve --phase acceptance` in TTY or `--version <n>` in CI/no-TTY.
@@ -49,7 +49,7 @@ Use maps, metadata, diffs, and summaries first. Open full files only when the sm
 ## Execution
 
 1. Create or reuse the spec worktree with `npx create-quiver spec start specs/<spec-slug>` or `npm run quiver:spec:start -- specs/<spec-slug>`. Use `--dry-run` first when you want to inspect the planned branch/path without changing Git state.
-2. Inspect lifecycle state with `npx create-quiver ai inspect`, or export it with `npx create-quiver ai export --format json` for dashboards/agents and `--format markdown` for PRs/docs.
+2. Inspect lifecycle state with `npx create-quiver dashboard`, `npx create-quiver ai inspect`, or export it with `npx create-quiver ai export --format json` for dashboards/agents and `--format markdown` for PRs/docs.
 3. If active-slice state looks stale or conflicting, run `npx create-quiver ai active-slice reconcile --dry-run` before assigning more execution work.
 4. Inspect manual prompts with `npx create-quiver ai execute-plan --dry-run --commit --mode manual` or delegated waves with `npm run quiver:ai:execute-plan -- --dry-run --commit --mode delegated`.
 5. Print a minimal manual executor prompt with `npx create-quiver ai prompt-slice --slice <slice.json> --dry-run` when assigning the slice to another agent. For commands pasted into another AI agent, prefer `npx --yes create-quiver@<version> ai prompt-slice --slice <slice.json> --dry-run`.

package/docs/ai/LESSONS.md.es.template

@@ -0,0 +1,24 @@
+# Lecciones aprendidas
+
+**Ultima actualizacion:** {{FECHA}}
+
+## [Titulo de la leccion]
+
+### Contexto
+
+[Que paso]
+
+### Que funciono
+
+- [Item 1]
+- [Item 2]
+
+### Que no funciono
+
+- [Item 1]
+- [Item 2]
+
+### Proxima vez
+
+- [Regla 1]
+- [Regla 2]

package/docs/getting-started/installation.md

@@ -71,10 +71,29 @@ Qué cambia:
 |---|---|
 | Probar Quiver rápidamente | `npx --yes create-quiver@latest` |
 | Inicializar un proyecto nuevo | `npx --yes create-quiver@latest init --name "Mi Proyecto"` |
+| Inicializar docs en espanol | `npx --yes create-quiver@latest --lang es init --name "Mi Proyecto"` |
 | Usar siempre la última versión publicada | `npx --yes create-quiver@latest` |
 | Fijar una versión para el equipo | `npm install --save-dev create-quiver` |
 | Evitar dependencia local de workflow | Usar `npx` |
 
+## Idioma del proyecto
+
+Quiver puede generar documentacion humana inicial en `en` o `es`.
+
+Para una ejecucion puntual:
+
+```bash
+npx --yes create-quiver@latest --lang es init --name "Mi Proyecto"
+```
+
+Para guardar el idioma del proyecto y no repetir flags:
+
+```bash
+npx --yes create-quiver@latest config language set es
+```
+
+El idioma configurado afecta la salida humana y los docs humanos generados. No traduce JSON, JSONL, `package.json`, `slice.json`, comandos, flags, rutas, providers, modelos ni otros artefactos machine-readable.
+
 ## Qué no hace Quiver
 
 Quiver no se instala globalmente por defecto, no modifica credenciales de npm y no agrega una dependencia runtime a tu app salvo que lo pidas explícitamente con npm.

package/docs/reference/commands.md

@@ -26,15 +26,73 @@ Más detalle: [Instalación y uso con npx](../getting-started/installation.md).
 | Comando | Para qué sirve |
 |---|---|
 | `npx --yes create-quiver@latest --version` | Muestra la versión del CLI. |
+| `npx --yes create-quiver@latest version` | Muestra un reporte de versión con banner Quiver, runtime, package manager y proyecto detectado. |
+| `npx --yes create-quiver@latest version --json` | Emite el reporte de versión como JSON parseable para automatización. |
 | `npx --yes create-quiver@latest --help` | Muestra los comandos soportados. |
+| `npx --yes create-quiver@latest config language show` | Muestra el idioma efectivo y su fuente de configuración. |
+| `npx --yes create-quiver@latest config language show --json` | Emite el idioma efectivo como JSON estable. |
+| `npx --yes create-quiver@latest config language set es` | Guarda `es` como idioma del proyecto en `.quiver/config.json`. |
+| `npx --yes create-quiver@latest config language set en --global` | Guarda `en` como idioma global en `~/.quiver/config.json`. |
 | `npx --yes create-quiver@latest init --name "Proyecto"` | Inicializa Quiver en un proyecto. |
-| `npx --yes create-quiver@latest init --interactive` | Abre una guía interactiva para elegir modo de proyecto, metodología `wdd-sdd`, perfil inicial y próximos pasos de agentes. |
+| `npx --yes create-quiver@latest init --interactive` | Abre una guía interactiva para elegir idioma del proyecto, modo de proyecto, metodología `wdd-sdd`, perfil inicial y próximos pasos de agentes. |
 | `npx --yes create-quiver@latest migrate --dry-run` | Previsualiza migración de un proyecto Quiver anterior. |
 | `npx --yes create-quiver@latest migrate` | Aplica la migración. |
 | `npx --yes create-quiver@latest analyze` | Genera mapa del proyecto y datos de escaneo. |
 | `npx --yes create-quiver@latest doctor` | Valida la salud de Quiver. |
 | `npx --yes create-quiver@latest doctor --json` | Emite el mismo diagnóstico de Doctor como JSON parseable para automatización. |
 | `npx --yes create-quiver@latest flow` | Muestra el próximo paso seguro. |
+| `npx --yes create-quiver@latest dashboard` | Muestra un resumen compacto read-only del proyecto, specs, slices, runs, approvals y agentes. |
+| `npx --yes create-quiver@latest dashboard --details` | Muestra el reporte humano completo cuando se necesita auditoría sin perder el resumen por defecto. |
+| `npx --yes create-quiver@latest dashboard --section <name>` | Muestra una sección humana puntual como `specs`, `slices`, `blockers`, `warnings`, `agents`, `approvals`, `runs`, `active-slice` o `next-steps`. |
+| `npx --yes create-quiver@latest dashboard --limit <n>` | Ajusta el límite de listas del dashboard compacto entre 1 y 100. |
+
+## Idioma del CLI
+
+Quiver resuelve el idioma de salida humana en este orden:
+
+1. `--lang en|es`
+2. variable de entorno `QUIVER_LANG`
+3. `.quiver/config.json`
+4. `~/.quiver/config.json`
+5. locale del entorno
+6. `en`
+
+Ejemplos:
+
+```bash
+npx --yes create-quiver@latest --lang es dashboard
+QUIVER_LANG=es npx --yes create-quiver@latest flow
+npx --yes create-quiver@latest config language set es
+npx --yes create-quiver@latest config language set en --global
+```
+
+`--json` conserva claves y estructura machine-readable en ingles tecnico; no traduce campos, codigos, comandos, flags, rutas, ids, providers ni modelos.
+
+## Nota de release i18n
+
+La superficie documentada del CLI soporta salida humana en `en` y `es` para comandos de inicializacion, configuracion, lectura de estado, dashboard, workflow de specs/slices, comandos IA, gates y PR. El idioma configurado al ejecutar `config language set es|en` se reutiliza en ejecuciones posteriores sin repetir flags; `--lang` y `QUIVER_LANG` siguen disponibles como overrides puntuales.
+
+La garantia de compatibilidad aplica a la salida humana. JSON/JSONL, nombres de campos, codigos, comandos, flags, rutas, ids, providers, modelos y snippets copiables se mantienen estables para automatizacion.
+
+## Idioma de docs generados
+
+El idioma configurado tambien aplica a documentacion humana generada por Quiver, como los docs creados por `init`.
+
+Ejemplos:
+
+```bash
+npx --yes create-quiver@latest --lang es init --name "Proyecto"
+npx --yes create-quiver@latest config language set es
+npx --yes create-quiver@latest init --name "Proyecto"
+```
+
+Reglas:
+
+- `--lang en|es` puede usarse como override para una ejecucion.
+- `.quiver/config.json` se usa como idioma por defecto del proyecto cuando no se pasa `--lang`.
+- Templates humanos Markdown pueden tener variantes localizadas, por ejemplo `docs/INDEX.md.es.template`.
+- Si falta una variante localizada, Quiver hace fallback explicito al template base en `en`.
+- Artefactos machine-readable como `package.template.json`, `slice.json`, JSON/JSONL, ids, comandos, flags, rutas, providers y modelos no se traducen.
 
 ## Planificación con IA
 
@@ -80,6 +138,8 @@ Más detalle: [Instalación y uso con npx](../getting-started/installation.md).
 | `npx --yes create-quiver@latest spec validate specs/<spec> --strict` | Valida el paquete de spec. |
 | `npx --yes create-quiver@latest spec start specs/<spec>` | Crea o reutiliza el worktree de una spec. |
 | `npx --yes create-quiver@latest plan --spec <spec>` | Muestra el orden de ejecución de slices. |
+| `npx --yes create-quiver@latest dashboard --spec <spec>` | Muestra estado consolidado read-only para una spec sin ocultar el progreso global. |
+| `npx --yes create-quiver@latest dashboard --section slices --spec <spec>` | Inspecciona solo slices de la spec seleccionada. |
 | `npx --yes create-quiver@latest graph --spec <spec>` | Muestra dependencias entre slices. |
 | `npx --yes create-quiver@latest next --all-ready --spec <spec>` | Lista slices listos para ejecutar. |
 | `npx --yes create-quiver@latest ai prompt-slice --slice <slice.json> --dry-run` | Imprime un prompt mínimo para el ejecutor. |
@@ -107,6 +167,12 @@ Más detalle: [Instalación y uso con npx](../getting-started/installation.md).
 | `--review` | Abre o prepara revisión humana antes de escrituras persistentes. |
 | `--methodology wdd-sdd` | Declara la metodología soportada por comandos interactivos o automatizados. |
 | `--no-color` | Desactiva colores ANSI en salida humana. |
+| `--json` | Emite salida machine-readable en comandos que lo soportan, incluyendo `dashboard` y `version`. |
+| `--lang en\|es` | Sobrescribe el idioma efectivo de la salida humana para una ejecución. |
+| `--global` | En `config language set`, escribe la configuración global de usuario en `~/.quiver/config.json`. |
+| `--details` | Expande el dashboard humano completo; no combina con `--json` ni `--section`. |
+| `--section <name>` | Muestra una sección humana del dashboard; no combina con `--json` ni `--details`. |
+| `--limit <n>` | Limita listas del dashboard compacto entre 1 y 100; no combina con `--json`. |
 | `--provider codex\|claude\|gemini` | Selecciona CLI local de proveedor. |
 | `--model <model-id>` | Selecciona el identificador técnico del modelo para `ai agent set` o ejecución de proveedor. Quiver normaliza alias conocidos, pero no garantiza acceso en la cuenta del proveedor. |
 | `--commit` | Permite que Quiver commitee trabajo validado del slice. |
@@ -124,7 +190,7 @@ Más detalle: [Instalación y uso con npx](../getting-started/installation.md).
 | `spec create` | sí | sí | sí |
 | `ai pr` | no | sí | sí |
 | `ai approve` | no | no | no |
-| `flow`, `next`, `graph` | no | no | no |
+| `flow`, `dashboard`, `next`, `graph`, `version` | no | no | no |
 | `ai inspect`, `ai export`, `ai specs list`, `ai slices list`, `ai trace report` | no | no | no |
 
 `--json` no se puede combinar con `--interactive` ni `--review`, porque la salida debe mantenerse legible por máquinas. El estándar completo vive en [docs/CLI_UX_GUIDE.md](../CLI_UX_GUIDE.md).

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-quiver",
-  "version": "0.15.2",
+  "version": "0.15.4",
   "private": false,
   "description": "Quiver CLI for scaffolding projects from the packaged template",
   "license": "MIT",
@@ -14,8 +14,10 @@
     "start:slice": "bash tools/scripts/start-slice.sh",
     "cleanup:slice": "bash tools/scripts/cleanup-slice.sh",
     "migrate": "bash tools/scripts/migrate-project.sh",
+    "quiver:version": "npx create-quiver version",
     "quiver:analyze": "npx create-quiver analyze",
     "quiver:flow": "npx create-quiver flow",
+    "quiver:dashboard": "npx create-quiver dashboard",
     "quiver:prepare": "npx create-quiver prepare",
     "quiver:plan": "node bin/create-quiver.js plan",
     "quiver:graph": "node bin/create-quiver.js graph",

package/specs/quiver-v34-cli-dashboard-status/EVIDENCE_REPORT.md

@@ -0,0 +1,119 @@
+# Evidence Report - Quiver v34 CLI Dashboard Status
+
+## Summary
+
+This report records implementation and validation evidence for the v34 CLI dashboard slices.
+
+## slice-00 - Dashboard foundation
+
+### Completed
+
+- Created v34 spec package with `SPEC.md`, `STATUS.md`, `EXECUTION_PLAN.md`, `EVIDENCE_REPORT.md`, and `pr.md`.
+- Created 6 slice folders with `slice.json`, `EXECUTION_BRIEF.md`, and `CLOSURE_BRIEF.md`.
+- Captured approved acceptance criteria, production review fixes, revised technical plan, slice roadmap, and validation strategy.
+
+### Validation
+
+- `find specs/quiver-v34-cli-dashboard-status -name 'slice.json' -print -exec node -e "JSON.parse(require('fs').readFileSync(process.argv[1], 'utf8')); console.log('ok', process.argv[1])" {} \;` passed for 6 slice files.
+- `node bin/create-quiver.js spec validate specs/quiver-v34-cli-dashboard-status` passed and reported 6 slices.
+- `git diff --check` passed.
+
+### Risks Observed During Planning
+
+- `docs/INDEX.md` is still missing in this repository; onboarding used `docs/INDEX.md.template` plus repo-specific Quiver docs as the documented fallback.
+- A parked backlog entry exists for a local web console, but this spec is intentionally CLI-only and read-only.
+- `ROADMAP.md` lists `create-quiver status dashboard` as polish debt; this spec chooses `dashboard` to avoid ambiguity with `ai status`.
+
+## slice-01 - Dashboard report contract
+
+### Completed
+
+- Added `src/create-quiver/lib/dashboard.js`.
+- Defined `dashboard_schema_version: 1`.
+- Added compact report fields for summary, global progress, visible progress, specs, slices, next-ready work, blockers, warnings, agents, approvals, active-slice state, runs, evidence counts, graph state, and next safe commands.
+- Preserved evidence/log secrecy by exposing counts and slice refs only.
+- Added graph-cycle tolerance by fixing `allowGraphErrors` handling in `project-state-resolver`.
+
+### Validation
+
+- `node --test tests/lib/dashboard.test.js` passed.
+- Full `node --test` passed and covered `tests/lib/ai-export-state.test.js` plus existing AI export behavior.
+- `git diff --check` passed.
+
+## slice-02 - Dashboard command and rendering
+
+### Completed
+
+- Added `src/create-quiver/commands/dashboard.js`.
+- Added top-level `dashboard` routing, help grouping, usage, examples, and exports.
+- Added human dashboard output and clean JSON mode.
+- Added `dashboard` to the UX flag matrix as a read-only command.
+- Added CLI tests for human output, JSON output, `--spec`, `--include-completed`, missing spec JSON failure, and graph-error output.
+
+### Validation
+
+- `node --test tests/commands/dashboard.test.js` passed.
+- `node --test tests/commands/cli-contract.test.js tests/commands/ux-flags.test.js` passed.
+- `git diff --check` passed.
+
+## slice-03 - Dashboard edge cases and guardrails
+
+### Completed
+
+- Explicit missing `--spec` returns an actionable error; JSON mode returns parseable schema v1 error output and non-zero exit.
+- Zero-slice specs produce a useful dashboard with `NO_VISIBLE_SLICES`.
+- Graph cycles produce warnings/blockers without crashing dashboard output.
+- Legacy/incomplete layout warnings are surfaced from existing layout diagnostics.
+- Evidence summaries expose only counts and slice refs.
+
+### Validation
+
+- `node --test tests/lib/dashboard.test.js tests/commands/dashboard.test.js` passed.
+- Full `node --test` passed.
+- `node bin/create-quiver.js dashboard --json --spec quiver-v34-cli-dashboard-status` passed against this repository.
+- `git diff --check` passed.
+
+## slice-04 - Docs, templates, and scripts
+
+### Completed
+
+- Updated `README.md`, `README_FOR_AI.md`, `docs/CLI_UX_GUIDE.md`, and `docs/reference/commands.md`.
+- Updated generated command/workflow templates for `dashboard`.
+- Added root and generated `quiver:dashboard` scripts.
+- Updated init docs and generated script tests.
+
+### Validation
+
+- `node --test tests/lib/init-docs.test.js tests/lib/init-layout.test.js` passed.
+- `node --test tests/commands/cli-contract.test.js` passed.
+- Full `node --test` passed.
+- `git diff --check` passed.
+
+## slice-05 - Tests, smokes, and release readiness
+
+### Completed
+
+- Ran focused dashboard, CLI contract, UX flag, generated docs/script tests.
+- Ran full test suite.
+- Ran required smokes and package smoke.
+- Updated slice closure briefs, `STATUS.md`, this evidence report, slice metadata, and `pr.md`.
+
+### Validation
+
+- `node --test tests/lib/dashboard.test.js tests/commands/dashboard.test.js tests/commands/cli-contract.test.js tests/commands/ux-flags.test.js tests/lib/init-layout.test.js tests/lib/init-docs.test.js` passed: 45 tests.
+- `node --test` passed: 511 tests.
+- `npm run smoke:create-quiver` passed.
+- `npm run smoke:doctor-fixtures` passed: 13 states.
+- `npm run smoke:guided-workflow` passed, including package smoke.
+- `npm run package:quiver` passed: `create-quiver-0.15.2.tgz`.
+- `node bin/create-quiver.js dashboard --json --spec quiver-v34-cli-dashboard-status` passed.
+- `find specs/quiver-v34-cli-dashboard-status -name 'slice.json' -print -exec node -e "JSON.parse(require('fs').readFileSync(process.argv[1], 'utf8')); console.log('ok', process.argv[1])" {} \;` passed for 6 slice files.
+- `git diff --check` passed.
+- `node bin/create-quiver.js spec validate specs/quiver-v34-cli-dashboard-status` passed.
+
+## Final Notes
+
+- No provider credentials were required.
+- No GitHub credentials were required.
+- No npm publication was performed.
+- The repository still reports a legacy-layout warning in dashboard output; this is pre-existing project state and not caused by v34.

package/specs/quiver-v34-cli-dashboard-status/EXECUTION_PLAN.md

@@ -0,0 +1,77 @@
+# Execution Plan - Quiver v34 CLI Dashboard Status
+
+## Execution Order
+
+```mermaid
+flowchart TD
+    S00[slice-00: Dashboard foundation]
+    S01[slice-01: Dashboard report contract]
+    S02[slice-02: Dashboard command and rendering]
+    S03[slice-03: Edge cases and guardrails]
+    S04[slice-04: Docs, templates, and scripts]
+    S05[slice-05: Tests, smokes, and release readiness]
+
+    S00 --> S01
+    S01 --> S02
+    S01 --> S03
+    S02 --> S03
+    S02 --> S04
+    S03 --> S04
+    S03 --> S05
+    S04 --> S05
+```
+
+## Waves
+
+### Wave 0 - Foundation
+
+1. `slice-00-dashboard-foundation`
+
+This slice publishes the approved spec package and does not change product code.
+
+### Wave 1 - Report Contract
+
+1. `slice-01-dashboard-report-contract`
+
+Build the dashboard data contract before adding a public command.
+
+### Wave 2 - Public Command
+
+1. `slice-02-dashboard-command-rendering`
+
+Expose the report through `npx create-quiver dashboard` with human and JSON output.
+
+### Wave 3 - Hardening
+
+1. `slice-03-dashboard-edge-cases-and-guardrails`
+
+Harden missing specs, graph failures, layout states, no-spec projects, blockers, no-color/CI/no-TTY, and sensitive summaries after the command path exists.
+
+### Wave 4 - Docs
+
+1. `slice-04-docs-templates-and-scripts`
+
+Document the command and generated `quiver:dashboard` script after the command contract stabilizes.
+
+### Wave 5 - Close
+
+1. `slice-05-tests-smokes-release-readiness`
+
+Run full validation, update evidence, close slice metadata, and prepare the PR body.
+
+## Parallel Safety Notes
+
+- Do not implement `slice-02` before `slice-01`; the command must consume a stable report contract.
+- `slice-03` should follow `slice-02` so guardrails can test both model and command behavior.
+- `slice-04` should wait until command flags and output shape are stable.
+- `slice-05` is never parallel-safe because it closes docs, evidence, smokes, and readiness state.
+- Keep JSON cleanliness validated at every implementation slice, not only at final release readiness.
+
+## Recommended Commit Order
+
+1. `docs: add v34 cli dashboard spec`
+2. `feat: add dashboard report contract`
+3. `feat: add dashboard command rendering`
+4. `fix: harden dashboard edge cases`
+5. `docs: document dashboard command`
+6. `test: close dashboard release readiness`

package/specs/quiver-v34-cli-dashboard-status/SPEC.md

@@ -0,0 +1,152 @@
+# Quiver v34 - CLI Dashboard Status
+
+**Date:** 2026-05-28
+**Status:** Planned
+**Source:** User-approved acceptance criteria and production review for a read-only CLI dashboard that visualizes Quiver project state.
+
+Slice numbering resets here. This spec intentionally starts at `slice-00`.
+
+## Problem
+
+Quiver exposes useful state through `flow`, `plan`, `next`, `ai export`, `ai specs list`, and `ai slices list`, but users still need to combine several commands to understand the whole project at a glance.
+
+The gap is especially visible when deciding what to do next:
+
+- spec and slice progress are spread across multiple surfaces;
+- blockers, warnings, migration guidance, approvals, agents, active-slice state, runs, and evidence are not shown together;
+- machine-readable export exists, but there is no compact human dashboard optimized for quick project status;
+- a future dashboard must avoid duplicating Quiver state or creating a second source of truth.
+
+## Objective
+
+Add a read-only CLI dashboard that shows the complete actionable state of a Quiver project without using Ink, a web console, providers, prompts, or writes.
+
+The dashboard should answer:
+
+- What is the current project state?
+- How many specs and slices exist?
+- What is complete, open, ready, or blocked?
+- What is the next ready slice?
+- What blockers, warnings, approvals, active-slice issues, agent gaps, runs, and evidence exist?
+- What safe commands should the user run next?
+
+## Scope
+
+### Included
+
+- New top-level command: `npx create-quiver dashboard`.
+- `dashboard --json` with a compact stable schema.
+- `dashboard --spec <slug>` filter.
+- `dashboard --include-completed`.
+- Human output that follows `docs/CLI_UX_GUIDE.md`.
+- Distinct global progress and visible progress.
+- Tolerant behavior for legacy, incomplete, uninitialized, no-spec, no-slice, and graph-error states.
+- No evidence/log content in human or compact JSON output.
+- Generated `quiver:dashboard` npm script.
+- Documentation, tests, smokes, and release-readiness evidence.
+
+### Excluded
+
+- Ink or fullscreen TUI.
+- Browser/web console.
+- Local server.
+- Interactive navigation.
+- Diff viewer.
+- Starting slices from the dashboard.
+- Creating specs, opening PRs, discarding changes, running providers, or writing project state.
+- Changing WDD + SDD semantics.
+
+## Approved Acceptance Criteria
+
+### Read-only dashboard behavior
+
+1. Given a project with Quiver, when the user runs `npx create-quiver dashboard`, then Quiver prints a consolidated read-only dashboard and does not modify files, run providers, open prompts, create worktrees, start slices, or create PRs.
+2. Given specs and slices exist, when the dashboard renders, then it shows spec count, slice count, completed slices, open slices, blocked slices, ready slices, and progress.
+3. Given completed slices are hidden from visible work by default, when the dashboard renders, then it still shows correct global progress across all slices and separately shows visible progress for the current filter.
+4. Given `--include-completed` is passed, then visible progress and visible slice sections include completed slices.
+5. Given `--spec <slug>` is passed, then visible dashboard sections are limited to that spec while global project context remains clear.
+6. Given `--spec <slug>` is passed for a missing spec, then the command fails with actionable guidance instead of silently showing an empty dashboard.
+
+### Next ready work and blockers
+
+7. Given at least one slice is ready, when the dashboard renders, then it shows the recommended next slice with spec slug, slice id, title, status, path, and start command.
+8. Given multiple slices are ready, then the dashboard shows the recommended first slice and indicates that more ready slices exist.
+9. Given blockers or warnings exist, then the dashboard shows their refs, reasons, and next commands where available.
+10. Given the slice graph is invalid, then the dashboard does not crash; it reports the graph issue and still renders the rest of the available state.
+
+### Workflow state
+
+11. Given planner approvals exist or are missing, then the dashboard shows `acceptance`, `technical-plan`, and `plan-review` status.
+12. Given agent profiles exist or are missing, then the dashboard shows planner, executor, reviewer, and doctor configuration without exposing credentials or secrets.
+13. Given active-slice state exists, then the dashboard shows active-slice sources, reconciliation decision, reason, and risks if any.
+14. Given runs or evidence exist, then the dashboard shows counts and refs only, not raw logs, command output, or evidence contents.
+
+### Output contracts
+
+15. Given `dashboard --json`, then stdout is parseable JSON with no colors, prompts, spinners, or human prose.
+16. Given `dashboard --json`, then the payload uses `dashboard_schema_version: 1` and includes `summary`, `global_progress`, `visible_progress`, `next_ready`, `specs`, `slices`, `agents`, `approvals`, `active_slice`, `blockers`, `warnings`, and `next_steps`.
+17. Given human output, then it follows the Quiver CLI UX standard: clear hierarchy, next safe commands, no color-only status, ASCII/no-color fallback, and no prompts.
+18. Given unsupported UX flags such as `--interactive`, `--review`, or `--with-planner` are passed, then Quiver rejects them through the existing UX flag guardrails.
+
+### Documentation and validation
+
+19. Given the command is public, then README, `README_FOR_AI.md`, command reference, CLI UX guide, generated templates, and package scripts are updated.
+20. Given implementation is complete, then tests cover human output, JSON cleanliness, `--spec`, missing spec, `--include-completed`, no specs, graph errors, legacy/incomplete layout, agent gaps, blockers, no-color, CI/no-TTY, and no evidence/log leakage.
+21. Given every slice is created, then each slice has `slice.json`, `EXECUTION_BRIEF.md`, and `CLOSURE_BRIEF.md`.
+
+## Approved Technical Plan
+
+1. Inventory the current state surfaces and tests before implementation.
+2. Add a dashboard report contract that consumes existing state from `collectLifecycleExport()` and related internal helpers without shelling out to the CLI.
+3. Calculate `global_progress` from all slices and `visible_progress` from filtered visible slices.
+4. Derive `next_ready` from graph/plan state when the graph is valid; degrade safely with a warning when graph state is invalid.
+5. Define a compact JSON schema with `dashboard_schema_version: 1`; do not return the full lifecycle export from `dashboard --json`.
+6. Add human formatting with existing Quiver UX/theme helpers and no prompt/spinner behavior.
+7. Add top-level `dashboard` routing, help text, examples, and UX-flag support matrix behavior.
+8. Add `quiver:dashboard` to generated project scripts and docs.
+9. Add focused tests for report construction, command output, JSON cleanliness, filters, missing specs, graph errors, legacy/no-spec states, no-color/CI/no-TTY, and secret-safe evidence summaries.
+10. Update docs, templates, smoke coverage, PR body, status, and evidence only after command contract is stable.
+
+## Slice Roadmap
+
+| Slice | Title | Status | Dependencies |
+|---|---|---|---|
+| slice-00 | Dashboard foundation | completed | none |
+| slice-01 | Dashboard report contract | ready | slice-00 |
+| slice-02 | Dashboard command and rendering | planned | slice-01 |
+| slice-03 | Dashboard edge cases and guardrails | planned | slice-01, slice-02 |
+| slice-04 | Docs, templates, and scripts | planned | slice-02, slice-03 |
+| slice-05 | Tests, smokes, and release readiness | planned | slice-03, slice-04 |
+
+## Validation Strategy
+
+- `node --test tests/lib/dashboard.test.js`
+- `node --test tests/commands/dashboard.test.js`
+- `node --test tests/commands/cli-contract.test.js tests/commands/ux-flags.test.js`
+- `node --test tests/lib/ai-export-state.test.js tests/commands/ai-export.test.js`
+- `node --test tests/lib/init-docs.test.js tests/lib/init-layout.test.js`
+- `node --test tests/**/*.test.js`
+- `npm run smoke:create-quiver`
+- `npm run smoke:doctor-fixtures`
+- `npm run smoke:guided-workflow`
+- `npm run package:quiver`
+- `git diff --check`
+- `node bin/create-quiver.js spec validate specs/quiver-v34-cli-dashboard-status`
+
+## Risks
+
+- Progress can be misleading if visible filters hide completed slices; global and visible progress must remain distinct.
+- A dashboard can become another source of truth if it rebuilds state independently; reuse existing resolver/export state.
+- Graph errors can break naive `next_ready` logic; the dashboard must degrade safely.
+- A missing `--spec` filter can hide typos if empty output is treated as success.
+- Evidence and runs can contain sensitive command output; the dashboard must summarize counts and refs only.
+- Human formatting can contaminate JSON if output paths are not tested separately.
+
+## Resolved Decisions
+
+- Use `dashboard`, not top-level `status`, to avoid ambiguity with `ai status`.
+- Do not use Ink for the MVP.
+- Do not add interactive behavior in this spec.
+- Do not add write actions from the dashboard.
+- `dashboard --json` has a compact schema, not the full `ai export` schema.
+- The command must be useful in legacy and incomplete layouts.

package/specs/quiver-v34-cli-dashboard-status/STATUS.md

@@ -0,0 +1,29 @@
+# Status - Quiver v34 CLI Dashboard Status
+
+**Overall status:** Completed
+**Created:** 2026-05-28
+**Completed:** 2026-05-28
+**Current slice:** All slices completed
+
+## Summary
+
+This spec added a read-only CLI dashboard for Quiver project state. The dashboard consolidates specs, slices, progress, blockers, warnings, approvals, agents, active-slice state, runs, evidence counts, and next safe commands without introducing Ink, prompts, providers, writes, or a second source of truth.
+
+## Slice Status
+
+| Slice | Status | Notes |
+|---|---|---|
+| slice-00-dashboard-foundation | Completed | Spec package, execution plan, PR body, evidence skeleton, and slice briefs created. |
+| slice-01-dashboard-report-contract | Completed | Added compact schema v1 report with global/visible progress, next-ready state, summaries, and evidence redaction. |
+| slice-02-dashboard-command-rendering | Completed | Added top-level command routing, help, human rendering, JSON output, and UX guardrails. |
+| slice-03-dashboard-edge-cases-and-guardrails | Completed | Hardened missing specs, zero-slice specs, graph cycles, JSON failure output, and evidence leakage. |
+| slice-04-docs-templates-and-scripts | Completed | Updated public docs, generated templates, init docs, package scripts, and generated script tests. |
+| slice-05-tests-smokes-release-readiness | Completed | Completed focused tests, full tests, smokes, package smoke, spec validation, and evidence closure. |
+
+## Current Blockers
+
+- None.
+
+## Next Step
+
+Open review/PR and package publication only after normal release approval. npm publication was not performed in this spec.