create-quiver 0.15.2 → 0.15.3

package/README.md

@@ -175,6 +175,7 @@ Usá la guía que corresponda al estado de tu proyecto:
 | `npx --yes create-quiver@latest doctor` | Revisa si el contrato de Quiver está sano. |
 | `npx --yes create-quiver@latest doctor --json` | Devuelve el diagnóstico como JSON para automatizaciones. |
 | `npx --yes create-quiver@latest flow` | Indica el próximo paso seguro. |
+| `npx --yes create-quiver@latest dashboard` | Muestra estado consolidado de specs, slices, runs, approvals y agentes sin escribir archivos. |
 | `npx --yes create-quiver@latest ai prepare-context --dry-run` | Previsualiza contexto de onboarding para IA sin tocar código de producto. |
 | `npx --yes create-quiver@latest ai prepare-context --with-planner --dry-run` | Previsualiza una propuesta de contexto generada por el planner. |
 | `npx --yes create-quiver@latest ai models list` | Lista proveedores y modelos conocidos por Quiver para configurar agentes. |

package/README_FOR_AI.md

@@ -27,8 +27,10 @@ The v29 spec is implemented under `specs/quiver-v29-planner-prepare-context-cli-
 The v30 spec is implemented under `specs/quiver-v30-interactive-cli-ux-agent-selection/` and is release-ready pending package publication; it adds production-grade interactive CLI UX with visible IA progress, Quiver-branded output, configured Planner/Executor/Reviewer/Doctor selectors, real provider model-selection contracts, Doctor human/JSON parity, guided init/spec-create selectors, and cross-platform release readiness.
 The v31 spec is implemented and release-ready pending PR/package publication under `specs/quiver-v31-ai-model-catalog-agent-selection/`; slice-00 through slice-07 are completed. Implemented scope includes the local AI model catalog, alias normalization, guided provider/model selection for `ai agent set <role>`, `ai agent doctor`, `ai agent repair --dry-run`, shared live-command model preflight, clearer provider errors for invalid model ids, `ai models list`, aligned README/reference/generated-template guidance, and final smoke/package readiness.
 The v32 documentation spec is implemented under `specs/quiver-v32-npx-installation-guidance/`; it clarifies why `npx --yes create-quiver@latest` does not install Quiver into project `node_modules`, when to install `create-quiver` as a `devDependency`, and where users should look when troubleshooting that behavior.
+The v34 dashboard spec is implemented under `specs/quiver-v34-cli-dashboard-status/`; it adds the read-only top-level `dashboard` command, compact schema v1 JSON output, global vs visible progress, next-ready slice guidance, edge-case guardrails, `quiver:dashboard` generated scripts, docs, tests, smokes, and package-readiness evidence. It does not publish npm.
+The v35 dashboard/version UX spec is implemented under `specs/quiver-v35-compact-dashboard-version-ux/`; it keeps `dashboard` compact by default, adds `dashboard --details`, `dashboard --section <name>`, `dashboard --limit <n>`, and adds the Quiver-branded `version` command without changing top-level `--version` / `-V`.
 Guided AI workflow behavior is available: prepare, approvals, production-readiness plan review, spec worktrees, executor commits, execution waves, PR creation, spec close, and package safety.
-Generated projects also get `quiver:*` npm scripts that call the Node CLI directly; prefer those for repeatable project workflows, including `quiver:flow` for the read-only guided entrypoint, `quiver:plan` for sequential planning, `quiver:graph` for parallel-level inspection, `quiver:next` for the next ready slice, `quiver:evidence` for local command evidence, `quiver:spec:create` for real spec generation, `quiver:spec:validate` for full spec validation, and the AI family `quiver:ai:agent`, `quiver:ai:inspect`, `quiver:ai:export`, `quiver:ai:specs`, `quiver:ai:slices`, `quiver:ai:trace`, `quiver:ai:onboard`, `quiver:ai:prepare-context`, `quiver:ai:plan`, `quiver:ai:review-plan`, `quiver:ai:approve`, `quiver:ai:prompt-slice`, `quiver:ai:execute-slice`, `quiver:ai:execute-plan`, `quiver:ai:pr`, and `quiver:ai:doctor`. Use `quiver:graph --format mermaid` for PR-ready Markdown or `quiver:graph --format dot` for Graphviz source.
+Generated projects also get `quiver:*` npm scripts that call the Node CLI directly; prefer those for repeatable project workflows, including `quiver:version` for version metadata, `quiver:flow` for the read-only guided entrypoint, `quiver:dashboard` for consolidated read-only project/spec/slice status, `quiver:plan` for sequential planning, `quiver:graph` for parallel-level inspection, `quiver:next` for the next ready slice, `quiver:evidence` for local command evidence, `quiver:spec:create` for real spec generation, `quiver:spec:validate` for full spec validation, and the AI family `quiver:ai:agent`, `quiver:ai:inspect`, `quiver:ai:export`, `quiver:ai:specs`, `quiver:ai:slices`, `quiver:ai:trace`, `quiver:ai:onboard`, `quiver:ai:prepare-context`, `quiver:ai:plan`, `quiver:ai:review-plan`, `quiver:ai:approve`, `quiver:ai:prompt-slice`, `quiver:ai:execute-slice`, `quiver:ai:execute-plan`, `quiver:ai:pr`, and `quiver:ai:doctor`. Use `quiver:graph --format mermaid` for PR-ready Markdown or `quiver:graph --format dot` for Graphviz source.
 `quiver:ai:execute-plan` supports `--mode manual` for paste-ready executor prompts and `--mode delegated` for temporary worktrees on parallel-ready waves; unsafe waves fall back to sequential execution.
 Agent profiles live in `.quiver/agents/profiles.json`; they store role, provider, technical `model`, human `displayName`, context label, profile id, and default profile only. Do not store API keys, tokens, or credentials there.
 `model` is the technical id passed to the provider CLI, for example `gpt-5.5`. `displayName` is the human label shown in Quiver output, for example `GPT 5.5`.
@@ -53,7 +55,7 @@ The raw analyzer output is internal machinery at `.quiver/scans/PROJECT_SCAN.jso
 `npx create-quiver ai agent set <role> --provider <provider> --model <model-id> --dry-run` must preview `.quiver/agents/profiles.json` changes without writing. In TTY mode, `npx create-quiver ai agent set <role>` can guide provider/model selection; in CI/no-TTY, require explicit `--provider` and `--model`. Use dry-run before saving planner/executor/reviewer/doctor profiles.
 GitHub PR diagnostics must stay cross-platform: auth failures should point to likely account, scope, and SSH alias issues; path examples with spaces must be copy-safe for macOS/Linux, Windows PowerShell, Git Bash, and WSL.
 CLI UX standard lives in `docs/CLI_UX_GUIDE.md`. Supported Quiver colors are `#86C8F2`, `#6BADEB`, `#7F9EE8`, `#9B82E6`, and `#D56AB0`; output must respect `--no-color`, `NO_COLOR`, CI, and no-TTY environments.
-UX flags are intentionally limited: `ai prepare-context`, `ai plan`, and `spec create` support `--with-planner`, `--interactive`, and `--review`; `ai pr` supports `--interactive` and `--review` but rejects `--with-planner`; read-only commands such as `flow`, `next`, `graph`, `ai inspect`, `ai export`, `ai specs list`, `ai slices list`, and `ai trace report` reject these UX flags. `--json` must reject `--interactive` and `--review` before writing human output.
+UX flags are intentionally limited: `ai prepare-context`, `ai plan`, and `spec create` support `--with-planner`, `--interactive`, and `--review`; `ai pr` supports `--interactive` and `--review` but rejects `--with-planner`; read-only commands such as `flow`, `dashboard`, `version`, `next`, `graph`, `ai inspect`, `ai export`, `ai specs list`, `ai slices list`, and `ai trace report` reject these UX flags. `dashboard` may use read-only inspection flags `--details`, `--section`, and `--limit`; `--json` must reject human-only dashboard flags plus `--interactive` and `--review` before writing human output.
 The universal router for generated projects is `AGENTS.md`; read it before `docs/AI_CONTEXT.md` and `docs/AI_ONBOARDING_PROMPT.md`.
 Generated projects also get `docs/DECISIONS.md`; use it for durable choices that should not be re-litigated.
 If a generated project has been analyzed, the exact agent handoff prompt is `docs/AI_ONBOARDING_PROMPT.md`.
@@ -90,12 +92,12 @@ Prefer maps, metadata, diffs, and summaries over full file reads when they are e
 - The normal workflow runs from the project root without `--dir`; use `--dir` only when targeting another directory explicitly.
 - The cross-platform contract targets native macOS, Linux, and Windows users through the Node CLI (`npx create-quiver ...`) and generated `quiver:*` npm scripts. Bash wrappers are legacy or optional compatibility, not the primary path. Keep root README examples clear about adapting SSH identity paths on Windows PowerShell, Git Bash, WSL, macOS, and Linux.
 - The support contract lives in `docs/SUPPORT_MATRIX.md` and `docs/TROUBLESHOOTING.md`.
-- Generated project npm scripts should prefer `quiver:*` names such as `quiver:analyze`, `quiver:flow`, `quiver:plan`, `quiver:graph`, `quiver:next`, `quiver:doctor`, `quiver:evidence`, `quiver:ai:agent`, `quiver:ai:inspect`, `quiver:ai:export`, `quiver:ai:specs`, `quiver:ai:slices`, `quiver:ai:trace`, `quiver:ai:prepare-context`, `quiver:ai:plan`, `quiver:ai:review-plan`, `quiver:ai:approve`, `quiver:ai:prompt-slice`, `quiver:ai:execute-slice`, `quiver:ai:execute-plan`, `quiver:spec:create`, `quiver:spec:start`, `quiver:spec:status`, `quiver:spec:validate`, `quiver:spec:close`, `quiver:start-slice`, `quiver:check-slice`, and `quiver:check-pr`.
+- Generated project npm scripts should prefer `quiver:*` names such as `quiver:version`, `quiver:analyze`, `quiver:flow`, `quiver:dashboard`, `quiver:plan`, `quiver:graph`, `quiver:next`, `quiver:doctor`, `quiver:evidence`, `quiver:ai:agent`, `quiver:ai:inspect`, `quiver:ai:export`, `quiver:ai:specs`, `quiver:ai:slices`, `quiver:ai:trace`, `quiver:ai:prepare-context`, `quiver:ai:plan`, `quiver:ai:review-plan`, `quiver:ai:approve`, `quiver:ai:prompt-slice`, `quiver:ai:execute-slice`, `quiver:ai:execute-plan`, `quiver:spec:create`, `quiver:spec:start`, `quiver:spec:status`, `quiver:spec:validate`, `quiver:spec:close`, `quiver:start-slice`, `quiver:check-slice`, and `quiver:check-pr`.
 - Optional demos are created with `npx create-quiver demo create spec-viewer`; do not add demo output to the package or default init flow.
 - `quiver:graph` defaults to the tree view; choose `--format mermaid` or `--format dot` when you need exportable graph artifacts.
 - `quiver:next` prints the next ready slice and can auto-start it behind a confirmation prompt.
 - `quiver:next --all-ready` prints the whole ready level when you want to inspect every actionable slice at once.
-- Use `--include-completed` with `plan`, `graph`, or `next` only for audit/demo history; default output remains pending/actionable work.
+- Use `--include-completed` with `dashboard`, `plan`, `graph`, or `next` only for audit/demo history; default output remains pending/actionable work.
 
 ## Initialization Flow
 

package/docs/CLI_UX_GUIDE.md

@@ -59,7 +59,7 @@ Reglas:
 | `ai agent repair` | no | no | no | Por ahora solo `--dry-run`; muestra before/after sin escribir. |
 | `ai models list` | no | no | no | Lista el catalogo local conocido por Quiver; no valida acceso de cuenta. |
 | `doctor` | no | no | no | Renderiza `Quiver Doctor`, `Checks` y `Suggested fixes`; `--json` usa el mismo modelo de hallazgos. |
-| `flow`, `next`, `graph` | no | no | no | Lectura/inspeccion; no deben exponer flags decorativas. |
+| `flow`, `dashboard`, `next`, `graph`, `version` | no | no | no | Lectura/inspeccion; `dashboard` puede acotarse con `--details`, `--section` y `--limit`, pero no acepta flags decorativas. |
 | `ai inspect`, `ai export`, `ai specs list`, `ai slices list`, `ai trace report` | no | no | no | Superficies read-only o machine-readable. |
 
 ## Flujo recomendado para contexto de IA

package/docs/COMMANDS.md.template

@@ -13,13 +13,19 @@ This document is the canonical command reference for the orchestration roadmap.
 | `npx create-quiver init --interactive` | Guides project mode, methodology `wdd-sdd`, init profile, and agent-profile next steps without running providers | macOS, Linux, Windows | next | `npx create-quiver init --interactive` |
 | `npx create-quiver --name "<project>"` | Compatibility alias for the recommended init flow | macOS, Linux, Windows | current | `npx create-quiver --name "{{PROJECT_NAME}}"` |
 | `npx create-quiver --version` | Prints the installed CLI version | macOS, Linux, Windows | current | `npx create-quiver --version` |
+| `npx create-quiver version` | Prints the Quiver-branded version report with CLI, runtime, package manager, and detected project metadata | macOS, Linux, Windows | next | `npx create-quiver version --no-color` |
+| `quiver:version` | Runs the Quiver-branded version report through the generated npm script | macOS, Linux, Windows | next | `npm run quiver:version -- --json` |
 | `npx create-quiver --help` | Lists all public commands with descriptions, key options, and recommended examples | macOS, Linux, Windows | current | `npx create-quiver --help` |
 | `npx create-quiver help` | Readable alias for the complete CLI help | macOS, Linux, Windows | current | `npx create-quiver help` |
 | `quiver --help` | Shows the same help when Quiver is installed locally as a project dependency | macOS, Linux, Windows | current | `quiver --help` |
 | `npx create-quiver flow` | Shows the read-only guided flow entrypoint, context source/freshness, package-manager-aware script guidance, and next safe command | macOS, Linux, Windows | v0.11 | `npx create-quiver flow` |
+| `npx create-quiver dashboard` | Shows a compact read-only summary of project, spec, slice, run, approval, and agent status | macOS, Linux, Windows | next | `npx create-quiver dashboard --spec <spec>` |
+| `npx create-quiver dashboard --details` | Shows the full human dashboard report for audit/debug sessions | macOS, Linux, Windows | next | `npx create-quiver dashboard --details` |
+| `npx create-quiver dashboard --section <name>` | Shows one human dashboard section such as `specs`, `slices`, `blockers`, `warnings`, `agents`, `approvals`, `runs`, `active-slice`, or `next-steps` | macOS, Linux, Windows | next | `npx create-quiver dashboard --section slices --limit 10` |
 | `npx create-quiver analyze --dry-run` | Previews scan, project-map, and AI context writes without creating files | macOS, Linux, Windows | v0.13 | `npx create-quiver analyze --dry-run` |
 | `quiver:analyze` | Writes raw analyzer data to `.quiver/scans/PROJECT_SCAN.json`, the visible project map to `docs/PROJECT_MAP.md`, and refreshed AI context | macOS, Linux, Windows | v0.8 | `npm run quiver:analyze` |
 | `quiver:flow` | Runs the guided flow entrypoint through the generated npm script | macOS, Linux, Windows | v0.11 | `npm run quiver:flow` |
+| `quiver:dashboard` | Runs the consolidated read-only dashboard through the generated npm script | macOS, Linux, Windows | next | `npm run quiver:dashboard -- --json` |
 | `quiver:prepare` | Runs guided setup diagnostics and context preparation | macOS, Linux, Windows | v0.10 | `npm run quiver:prepare -- --dry-run --provider codex` |
 | `quiver:doctor` | Validates the Quiver contract and reports layout or migration guidance | macOS, Linux, Windows | v0.8 | `npm run quiver:doctor` |
 | `quiver:doctor -- --json` | Emits the Doctor checks and suggested fixes as stable machine-readable JSON | macOS, Linux, Windows | next | `npm run quiver:doctor -- --json` |
@@ -95,12 +101,15 @@ This document is the canonical command reference for the orchestration roadmap.
 | `--output <file>` | `evidence run` | Write the evidence Markdown file to an explicit path instead of `.quiver/evidence/` |
 | `--max-output <n>` | `evidence run` | Limit captured stdout and stderr characters per section |
 | `--dir <target>` | `demo create spec-viewer` | Select the demo target directory; default is `./quiver-spec-viewer` |
-| `--json` | `plan`, `graph`, `next` | Emit machine-readable JSON |
+| `--json` | `dashboard`, `version`, `plan`, `graph`, `next` | Emit machine-readable JSON |
+| `--details` | `dashboard` | Show the full human dashboard report instead of the compact default; incompatible with `--json` and `--section` |
+| `--section <name>` | `dashboard` | Show one human dashboard section; incompatible with `--json` and `--details` |
+| `--limit <n>` | `dashboard` | Limit compact dashboard lists between 1 and 100; incompatible with `--json` |
 | `--all-ready` | `next` | List all ready slices instead of just the next one |
 | `--only-ready` | `plan` | Show only slices with no pending dependencies |
-| `--include-completed` | `plan`, `graph`, `next` | Include completed slices for audit/demo history without changing default pending-only behavior |
+| `--include-completed` | `dashboard`, `plan`, `graph`, `next` | Include completed slices for audit/demo history without changing default pending-only behavior |
 | `--local` | `check-slice` | Run structural validation without remote/base checks; use normal mode before PR readiness |
-| `--spec <slug>` | `plan`, `graph`, `spec create` | Restrict output to one spec or override the generated spec slug |
+| `--spec <slug>` | `dashboard`, `plan`, `graph`, `spec create` | Restrict output to one spec or override the generated spec slug |
 | `--format <tree\|mermaid\|dot\|json\|markdown>` | `graph`, `ai export` | Select graph or lifecycle export output format |
 | `--provider <codex\|claude\|gemini>` | `ai onboard`, `ai plan`, `ai revise`, `ai review-plan`, `ai execute-slice`, `ai execute-plan` | Select the local AI CLI adapter |
 | `--model <model-id>` | `ai agent set`, provider-backed AI commands | Store or pass the technical model id. Quiver normalizes known display aliases, but the catalog is known by Quiver and does not guarantee account availability |
@@ -146,6 +155,8 @@ This document is the canonical command reference for the orchestration roadmap.
 - `init --interactive` and `spec create --interactive` are human-only wrappers. They fail in no-TTY/CI/JSON and always keep `WDD + SDD` as the only methodology option.
 - Quiver human output uses the palette `#86C8F2`, `#6BADEB`, `#7F9EE8`, `#9B82E6`, and `#D56AB0`; respect `--no-color`, `NO_COLOR`, CI, and no-TTY environments.
 - `quiver:flow` reports the detected package manager and the matching generated project script, for example `npm run quiver:flow`, `pnpm run quiver:flow`, `yarn run quiver:flow`, or `bun run quiver:flow`.
+- `quiver:version` prints the Quiver-branded version report; `--json` emits schema version 1 for automation and the top-level `--version` / `-V` semver flags stay unchanged.
+- `quiver:dashboard` reports compact read-only project, spec, slice, run, approval, and agent status by default; use `--details` for the full human report, `--section <name>` for focused inspection, and `--json` for schema version 1 automation.
 - `npx create-quiver ai models list` shows the local catalog of provider/model ids known by Quiver. It does not prove account-level access in Codex, Claude, or Gemini.
 - Agent profiles separate `model` and `displayName`: `model` is the technical id passed to the provider CLI, while `displayName` is the human label used in selectors and reports.
 - `quiver:ai:agent -- set ... --dry-run` previews provider/model profile changes without writing `.quiver/agents/profiles.json`.

package/docs/INDEX.md

@@ -0,0 +1,87 @@
+# Quiver Documentation Index
+
+**Last updated:** 2026-05-28
+
+Use this file as the first documentation map before planning, implementing, reviewing, or opening PRs in this repository. Prefer the smallest set of linked documents that fits the task.
+
+## Start Here
+
+- **Public overview:** [`../README.md`](../README.md)
+- **AI guide:** [`../README_FOR_AI.md`](../README_FOR_AI.md)
+- **CLI UX standards:** [`./CLI_UX_GUIDE.md`](./CLI_UX_GUIDE.md)
+- **Command reference:** [`./reference/commands.md`](./reference/commands.md)
+- **Troubleshooting:** [`./TROUBLESHOOTING.md`](./TROUBLESHOOTING.md)
+- **Git and PR workflow:** [`./GITFLOW_PR_GUIDE.md`](./GITFLOW_PR_GUIDE.md)
+
+## Getting Started
+
+- **Install and npx behavior:** [`./getting-started/installation.md`](./getting-started/installation.md)
+- **macOS setup:** [`./getting-started/macos.md`](./getting-started/macos.md)
+- **Linux setup:** [`./getting-started/linux.md`](./getting-started/linux.md)
+- **Windows PowerShell setup:** [`./getting-started/windows-powershell.md`](./getting-started/windows-powershell.md)
+- **Windows Git Bash / WSL setup:** [`./getting-started/windows-git-bash-wsl.md`](./getting-started/windows-git-bash-wsl.md)
+
+## Workflows
+
+- **New project:** [`./workflows/new-project.md`](./workflows/new-project.md)
+- **Existing project:** [`./workflows/existing-project.md`](./workflows/existing-project.md)
+- **Legacy Quiver project:** [`./workflows/legacy-quiver-project.md`](./workflows/legacy-quiver-project.md)
+- **Full AI spec-to-PR flow:** [`./workflows/full-ai-spec-to-pr.md`](./workflows/full-ai-spec-to-pr.md)
+
+## AI Configuration
+
+- **AI principles:** [`./ai/PRINCIPLES.md`](./ai/PRINCIPLES.md)
+- **AI rules:** [`./ai/RULES.yaml`](./ai/RULES.yaml)
+
+## Specs
+
+Canonical specs live outside `docs/` in [`../specs/`](../specs/).
+
+Recent specs:
+
+- [`../specs/quiver-v36-ai-run-watch-portable/SPEC.md`](../specs/quiver-v36-ai-run-watch-portable/SPEC.md)
+- [`../specs/quiver-v35-compact-dashboard-version-ux/SPEC.md`](../specs/quiver-v35-compact-dashboard-version-ux/SPEC.md)
+- [`../specs/quiver-v34-cli-dashboard-status/SPEC.md`](../specs/quiver-v34-cli-dashboard-status/SPEC.md)
+
+For implementation work, read the target spec and the target slice's `slice.json`, `EXECUTION_BRIEF.md`, and `CLOSURE_BRIEF.md` only.
+
+## Templates
+
+These files are templates for generated projects or optional profiles. Do not treat them as concrete project state unless the task is about templates or init output:
+
+- [`./AI_CONTEXT.md.template`](./AI_CONTEXT.md.template)
+- [`./AI_ONBOARDING_PROMPT.md.template`](./AI_ONBOARDING_PROMPT.md.template)
+- [`./COMMANDS.md.template`](./COMMANDS.md.template)
+- [`./CONTEXTO.md.template`](./CONTEXTO.md.template)
+- [`./DECISIONS.md.template`](./DECISIONS.md.template)
+- [`./DOCUMENTATION_GUIDE.md.template`](./DOCUMENTATION_GUIDE.md.template)
+- [`./STATUS.md.template`](./STATUS.md.template)
+- [`./SUPPORT_MATRIX.md.template`](./SUPPORT_MATRIX.md.template)
+- [`./TESTING_GUIDE_FOR_AI.md.template`](./TESTING_GUIDE_FOR_AI.md.template)
+- [`./WORKFLOW.md.template`](./WORKFLOW.md.template)
+- [`./ai/LESSONS.md.template`](./ai/LESSONS.md.template)
+
+## Task Routing
+
+- **Documentation/index work:** read this index, then the affected docs only.
+- **CLI UX, output, dashboard, or version work:** read [`./CLI_UX_GUIDE.md`](./CLI_UX_GUIDE.md), [`./reference/commands.md`](./reference/commands.md), and the relevant spec.
+- **Spec or slice execution:** read the relevant [`../specs/`](../specs/) package, especially the target slice files.
+- **PR creation:** read [`./GITFLOW_PR_GUIDE.md`](./GITFLOW_PR_GUIDE.md) and the relevant `pr.md`.
+- **Troubleshooting or install issues:** read [`./TROUBLESHOOTING.md`](./TROUBLESHOOTING.md) and the matching getting-started guide.
+- **AI agent behavior:** read [`../README_FOR_AI.md`](../README_FOR_AI.md), [`./ai/PRINCIPLES.md`](./ai/PRINCIPLES.md), and [`./ai/RULES.yaml`](./ai/RULES.yaml).
+
+## Known Documentation Debt
+
+The following concrete docs are referenced by templates or generated-project guidance but do not currently exist as repository docs:
+
+- `docs/CONTEXTO.md`
+- `docs/WORKFLOW.md`
+- `docs/STATUS.md`
+- `docs/SUPPORT_MATRIX.md`
+- `docs/TESTING_GUIDE_FOR_AI.md`
+- `docs/AI_CONTEXT.md`
+- `docs/AI_ONBOARDING_PROMPT.md`
+- `docs/DECISIONS.md`
+- `docs/ai/LESSONS.md`
+
+Use the `.template` files only when the task is about generated project output or template maintenance.

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/reference/commands.md

@@ -26,6 +26,8 @@ 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 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. |
@@ -35,6 +37,10 @@ Más detalle: [Instalación y uso con npx](../getting-started/installation.md).
 | `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. |
 
 ## Planificación con IA
 
@@ -80,6 +86,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 +115,10 @@ 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`. |
+| `--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 +136,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.3",
   "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`