create-quiver 0.15.2 → 0.15.3

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.

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

@@ -0,0 +1,99 @@
+## Title
+
+Quiver v34: CLI dashboard status
+
+## Summary
+
+- Adds a read-only `dashboard` command for consolidated Quiver project state.
+- Shows specs, slices, global progress, visible progress, next ready work, blockers, warnings, approvals, agents, active-slice state, runs, evidence counts, and next safe commands.
+- Keeps the dashboard CLI-first and script-safe: no Ink, no prompts, no provider execution, no writes.
+- Adds compact `dashboard --json` output with a stable schema.
+- Adds docs, generated scripts, tests, smokes, and release-readiness evidence.
+
+## Scope
+
+- Dashboard report contract.
+- Human and JSON dashboard output.
+- Top-level CLI command routing and help.
+- Edge-case handling for missing specs, invalid graphs, legacy/incomplete layouts, no-spec states, no-color, CI/no-TTY, and evidence/log redaction.
+- Docs, generated templates, package scripts, tests, and evidence.
+
+## Files
+
+- `README.md`
+- `README_FOR_AI.md`
+- `docs/CLI_UX_GUIDE.md`
+- `docs/reference/commands.md`
+- `src/create-quiver/commands/dashboard.js`
+- `src/create-quiver/index.js`
+- `src/create-quiver/lib/dashboard.js`
+- `src/create-quiver/lib/init-docs.js`
+- `tests/commands/dashboard.test.js`
+- `tests/commands/cli-contract.test.js`
+- `tests/commands/ux-flags.test.js`
+- `tests/lib/dashboard.test.js`
+- `tests/lib/init-docs.test.js`
+- `tests/lib/init-layout.test.js`
+- `specs/quiver-v34-cli-dashboard-status/**`
+
+## How to Test (DETAILED - REQUIRED)
+
+### Required Environment
+
+- Node.js and npm.
+- No provider credentials are required.
+- No GitHub credentials are required.
+
+### Worktree Access
+
+- One dedicated branch/worktree for `quiver-v34-cli-dashboard-status`.
+- One commit per slice.
+
+### Use Cases
+
+- Run `npx create-quiver dashboard` in a project with specs and slices.
+- Run `npx create-quiver dashboard --json` and parse stdout as JSON.
+- Run `npx create-quiver dashboard --spec <slug>` for an existing spec.
+- Run `npx create-quiver dashboard --spec missing-spec` and verify actionable failure.
+- Run `npx create-quiver dashboard --include-completed` and verify completed slices are visible while global progress remains correct.
+- Run in legacy/incomplete/no-spec/no-slice fixtures and verify useful output without crashes.
+- Run with no-color/CI/no-TTY conditions and verify no prompts, spinners, or color-only semantics.
+
+### Technical Verification
+
+- `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`
+
+## Evidence
+
+- `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.
+- `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.
+- `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.
+- `git diff --check` passed.
+- `node bin/create-quiver.js spec validate specs/quiver-v34-cli-dashboard-status` passed.
+
+## Rollback
+
+Revert slice commits in reverse order. The dashboard is additive and read-only, so rollback should not affect existing workflow commands if done by slice.
+
+## Risks / Notes
+
+- Dashboard progress must distinguish global progress from visible filtered progress.
+- `dashboard --json` must stay compact and must not duplicate the full `ai export` contract.
+- Graph errors must not break the entire dashboard.
+- Evidence/log content must not be printed.
+- This PR does not publish npm.

package/specs/quiver-v34-cli-dashboard-status/slices/slice-00-dashboard-foundation/CLOSURE_BRIEF.md

@@ -0,0 +1,19 @@
+# CLOSURE_BRIEF - slice-00 Dashboard foundation
+
+## Summary
+
+Created the v34 spec package for the CLI dashboard status feature. This foundation is documentation-only and does not implement product behavior.
+
+## Validation
+
+- [x] Slice JSON parse command passed for 6 slice files.
+- [x] `node bin/create-quiver.js spec validate specs/quiver-v34-cli-dashboard-status` passed.
+- [x] `git diff --check` passed.
+
+## Pending
+
+- Execute `slice-01-dashboard-report-contract`.
+
+## Remaining Risks
+
+- None critical for the foundation package.

package/specs/quiver-v34-cli-dashboard-status/slices/slice-00-dashboard-foundation/EXECUTION_BRIEF.md

@@ -0,0 +1,49 @@
+# EXECUTION_BRIEF - slice-00 Dashboard foundation
+
+## Context
+
+The user approved a read-only CLI dashboard initiative after acceptance criteria and production-plan review. The repository already has lifecycle export state and CLI UX rules, so this foundation slice only creates the durable spec package.
+
+## Objective
+
+Create the v34 spec package for `quiver dashboard` without changing product code.
+
+## Scope
+
+- `specs/quiver-v34-cli-dashboard-status/**`
+
+## Acceptance Criteria
+
+- `SPEC.md`, `STATUS.md`, `EVIDENCE_REPORT.md`, `EXECUTION_PLAN.md`, and `pr.md` exist.
+- Every slice has `slice.json`, `EXECUTION_BRIEF.md`, and `CLOSURE_BRIEF.md`.
+- The approved acceptance criteria and reviewed technical plan are captured.
+- No product code is modified.
+
+## Technical Plan Summary
+
+Create a complete spec package following the existing `specs/quiver-vNN-*` pattern. Mark this foundation slice completed and leave implementation slices ready/planned.
+
+## Suggested Steps
+
+1. Create the spec directory and top-level documents.
+2. Create all slice directories and handoffs.
+3. Validate every `slice.json`.
+4. Validate the spec package.
+5. Record evidence.
+
+## Restrictions
+
+- Do not implement the dashboard.
+- Do not update root README or command docs in this slice.
+- Do not claim npm publication.
+
+## Risks
+
+- Missing handoffs would block future executor agents.
+
+## Completion Checklist
+
+- [ ] Spec package created.
+- [ ] Slice handoffs created.
+- [ ] Slice JSON files parse.
+- [ ] Spec validation passes.

package/specs/quiver-v34-cli-dashboard-status/slices/slice-00-dashboard-foundation/slice.json

@@ -0,0 +1,68 @@
+{
+  "slice_id": "slice-00-dashboard-foundation",
+  "ticket": "QUIVER-34-00",
+  "type": "docs",
+  "title": "Dashboard foundation",
+  "objective": "Create the v34 spec package for the read-only CLI dashboard status feature.",
+  "description": "Publishes the approved spec, execution plan, PR body, status, evidence report, slice definitions, and handoffs without changing product code.",
+  "git": {
+    "branch_type": "feature",
+    "base_branch": "main",
+    "branch_slug": "v34-dashboard-foundation",
+    "branch_name": "feature/QUIVER-34-00-v34-dashboard-foundation"
+  },
+  "files": [
+    "specs/quiver-v34-cli-dashboard-status/**"
+  ],
+  "expected_read_paths": [
+    "README_FOR_AI.md",
+    "ROADMAP.md",
+    "BACKLOG.md",
+    "docs/CLI_UX_GUIDE.md",
+    "docs/reference/commands.md",
+    "docs/workflows/full-ai-spec-to-pr.md",
+    "specs/quiver-v23-guided-flow-productization/**",
+    "specs/quiver-v29-planner-prepare-context-cli-ux/**",
+    "specs/quiver-v30-interactive-cli-ux-agent-selection/**",
+    "specs/quiver-v33-approval-ux-and-planner-progress/**"
+  ],
+  "allowed_write_paths": [
+    "specs/quiver-v34-cli-dashboard-status/**"
+  ],
+  "depends_on": [],
+  "parallel_safe": "no",
+  "parallel_safe_reason": "slice-00 is the foundation barrier for the spec.",
+  "must": [
+    "Create SPEC.md, STATUS.md, EVIDENCE_REPORT.md, EXECUTION_PLAN.md, and pr.md.",
+    "Create slice.json, EXECUTION_BRIEF.md, and CLOSURE_BRIEF.md for every slice.",
+    "Capture approved acceptance criteria, review findings, and technical plan.",
+    "Avoid product code changes."
+  ],
+  "not_included": [
+    "Implementing the dashboard command.",
+    "Changing CLI routing.",
+    "Updating public docs outside this spec package.",
+    "Publishing a package."
+  ],
+  "acceptance": [
+    "Spec folder exists under specs/quiver-v34-cli-dashboard-status.",
+    "Every slice has slice.json, EXECUTION_BRIEF.md, and CLOSURE_BRIEF.md.",
+    "Every slice.json parses successfully.",
+    "Spec validation passes.",
+    "No product code is modified."
+  ],
+  "tests": [
+    "git diff --check",
+    "find specs/quiver-v34-cli-dashboard-status -name \"slice.json\" -print -exec node -e \"JSON.parse(require('fs').readFileSync(process.argv[1], 'utf8'))\" {} \\;",
+    "node bin/create-quiver.js spec validate specs/quiver-v34-cli-dashboard-status"
+  ],
+  "validation_hints": [
+    "Keep this slice documentation-only.",
+    "Do not claim implementation or package publication."
+  ],
+  "estimated_hours": 2,
+  "status": "completed",
+  "blocked_reason": null,
+  "actual_hours": 2,
+  "completed_at": "2026-05-28"
+}

package/specs/quiver-v34-cli-dashboard-status/slices/slice-01-dashboard-report-contract/CLOSURE_BRIEF.md

@@ -0,0 +1,19 @@
+# CLOSURE_BRIEF - slice-01 Dashboard report contract
+
+## Summary
+
+Implemented the compact dashboard report contract in `src/create-quiver/lib/dashboard.js`. The report exposes schema version 1, global vs visible progress, filtered specs/slices, next-ready work, blockers, warnings, agents, approvals, active-slice reconciliation, run summaries, evidence counts, and next safe commands without leaking raw evidence values.
+
+## Validation
+
+- [x] `node --test tests/lib/dashboard.test.js`
+- [x] `node --test tests/lib/ai-export-state.test.js tests/commands/ai-export.test.js` covered by full `node --test`.
+- [x] `git diff --check`
+
+## Pending
+
+- None for this slice.
+
+## Remaining Risks
+
+- None critical.

package/specs/quiver-v34-cli-dashboard-status/slices/slice-01-dashboard-report-contract/EXECUTION_BRIEF.md

@@ -0,0 +1,53 @@
+# EXECUTION_BRIEF - slice-01 Dashboard report contract
+
+## Context
+
+`ai export --format json` already exposes lifecycle state and a `dashboard` subobject, but the new public dashboard needs a compact purpose-built contract. It must not become a second source of truth.
+
+## Objective
+
+Create the dashboard report model that future command rendering can consume.
+
+## Scope
+
+- `src/create-quiver/lib/dashboard.js`
+- compatible helper extraction in `src/create-quiver/lib/ai/export-state.js` if needed
+- focused model tests
+
+## Acceptance Criteria
+
+- Report includes `dashboard_schema_version: 1`.
+- Report includes `summary`, `global_progress`, `visible_progress`, `next_ready`, `specs`, `slices`, `agents`, `approvals`, `active_slice`, `blockers`, `warnings`, and `next_steps`.
+- Global progress includes completed slices even when visible work hides them.
+- Visible progress respects `--spec` and `--include-completed`.
+- Evidence and run details are summarized without raw logs or evidence values.
+- Missing data is represented with stable nulls/empty arrays rather than crashes.
+
+## Technical Plan Summary
+
+Build pure dashboard helpers on top of existing lifecycle export and project-state resolver data. Keep CLI routing and formatting out of this slice.
+
+## Suggested Steps
+
+1. Define the compact report shape.
+2. Add report construction from existing export state.
+3. Add global vs visible progress calculation.
+4. Add safe evidence/run summaries.
+5. Add next-ready derivation where graph data allows it.
+6. Add model tests for default, include-completed, spec filter, missing data, and evidence safety.
+
+## Restrictions
+
+- Do not add top-level command routing.
+- Do not add prompts, spinners, writes, providers, or shell-outs.
+- Do not return the full lifecycle export as dashboard JSON.
+
+## Risks
+
+- Progress can be misleading if global and visible counts are collapsed into one number.
+
+## Completion Checklist
+
+- [ ] Report contract implemented.
+- [ ] Focused tests added.
+- [ ] Existing `ai export` tests still pass.

package/specs/quiver-v34-cli-dashboard-status/slices/slice-01-dashboard-report-contract/slice.json

@@ -0,0 +1,78 @@
+{
+  "slice_id": "slice-01-dashboard-report-contract",
+  "ticket": "QUIVER-34-01",
+  "type": "feature",
+  "title": "Dashboard report contract",
+  "objective": "Create a compact read-only dashboard report contract from existing Quiver lifecycle state.",
+  "description": "Adds the dashboard data model that separates global progress from visible progress, exposes next-ready work, and summarizes state without duplicating lifecycle export or leaking evidence/log content.",
+  "git": {
+    "branch_type": "feature",
+    "base_branch": "main",
+    "branch_slug": "v34-dashboard-report-contract",
+    "branch_name": "feature/QUIVER-34-01-v34-dashboard-report-contract"
+  },
+  "files": [
+    "src/create-quiver/lib/dashboard.js",
+    "src/create-quiver/lib/ai/export-state.js",
+    "tests/lib/dashboard.test.js",
+    "tests/lib/ai-export-state.test.js"
+  ],
+  "expected_read_paths": [
+    "src/create-quiver/lib/ai/export-state.js",
+    "src/create-quiver/lib/project-state-resolver.js",
+    "src/create-quiver/commands/plan.js",
+    "src/create-quiver/commands/next.js",
+    "tests/commands/ai-export.test.js",
+    "tests/lib/ai-export-state.test.js",
+    "specs/quiver-v34-cli-dashboard-status/SPEC.md"
+  ],
+  "allowed_write_paths": [
+    "src/create-quiver/lib/dashboard.js",
+    "src/create-quiver/lib/ai/export-state.js",
+    "tests/lib/dashboard.test.js",
+    "tests/lib/ai-export-state.test.js",
+    "specs/quiver-v34-cli-dashboard-status/**"
+  ],
+  "depends_on": [
+    "slice-00-dashboard-foundation"
+  ],
+  "parallel_safe": "no",
+  "parallel_safe_reason": "The report contract is the dependency for command rendering and edge-case hardening.",
+  "must": [
+    "Use existing lifecycle/export state as the source of truth.",
+    "Define dashboard_schema_version 1.",
+    "Return a compact report, not the full ai export payload.",
+    "Calculate global_progress from all slices.",
+    "Calculate visible_progress from filters such as --spec and --include-completed.",
+    "Summarize evidence and runs without raw log or evidence content.",
+    "Expose next_ready when graph state allows it.",
+    "Preserve existing ai export behavior unless a backwards-compatible helper extraction is needed."
+  ],
+  "not_included": [
+    "Top-level CLI routing.",
+    "Human formatting.",
+    "Generated docs or package scripts.",
+    "Interactive behavior."
+  ],
+  "acceptance": [
+    "Dashboard report includes dashboard_schema_version, summary, global_progress, visible_progress, next_ready, specs, slices, agents, approvals, active_slice, blockers, warnings, and next_steps.",
+    "Completed slices are counted in global_progress even when hidden from visible slices.",
+    "Visible progress changes with --include-completed and --spec filters.",
+    "Evidence/log content is not included in the compact report.",
+    "Report construction does not shell out to the CLI."
+  ],
+  "tests": [
+    "node --test tests/lib/dashboard.test.js",
+    "node --test tests/lib/ai-export-state.test.js tests/commands/ai-export.test.js",
+    "git diff --check"
+  ],
+  "validation_hints": [
+    "Prefer pure functions for report construction.",
+    "Keep the report easy to snapshot and stable for future consumers."
+  ],
+  "estimated_hours": 5,
+  "status": "completed",
+  "blocked_reason": null,
+  "actual_hours": 5,
+  "completed_at": "2026-05-28"
+}

package/specs/quiver-v34-cli-dashboard-status/slices/slice-02-dashboard-command-rendering/CLOSURE_BRIEF.md

@@ -0,0 +1,19 @@
+# CLOSURE_BRIEF - slice-02 Dashboard command and rendering
+
+## Summary
+
+Added the top-level `dashboard` command, CLI router integration, help/example coverage, human output, JSON output, and UX flag guardrail coverage. The command is read-only, uses no prompts/spinners, and keeps JSON stdout parseable.
+
+## Validation
+
+- [x] `node --test tests/commands/dashboard.test.js`
+- [x] `node --test tests/commands/cli-contract.test.js tests/commands/ux-flags.test.js`
+- [x] `git diff --check`
+
+## Pending
+
+- None for this slice.
+
+## Remaining Risks
+
+- None critical.

package/specs/quiver-v34-cli-dashboard-status/slices/slice-02-dashboard-command-rendering/EXECUTION_BRIEF.md

@@ -0,0 +1,53 @@
+# EXECUTION_BRIEF - slice-02 Dashboard command and rendering
+
+## Context
+
+The report contract exists from slice-01. This slice makes it available through the CLI.
+
+## Objective
+
+Add `npx create-quiver dashboard` with human and JSON output.
+
+## Scope
+
+- `src/create-quiver/commands/dashboard.js`
+- `src/create-quiver/index.js`
+- focused command tests
+
+## Acceptance Criteria
+
+- `dashboard` is a supported top-level command.
+- `dashboard --json` emits parseable compact JSON.
+- Human output shows project, progress, next ready slice, blockers, approvals, agents, active slice, and next steps where available.
+- `--spec`, `--include-completed`, and `--no-color` are passed to the report/formatting layer.
+- `--interactive`, `--review`, and `--with-planner` are rejected.
+- Help output documents the command.
+
+## Technical Plan Summary
+
+Add a command wrapper that calls the dashboard report helpers and formats either compact JSON or human output. Integrate the command into the central parser/router/help.
+
+## Suggested Steps
+
+1. Add `commands/dashboard.js`.
+2. Add `dashboard` to supported modes.
+3. Add usage/help/example entries.
+4. Wire options into `runDashboard`.
+5. Add command tests for human output, JSON, filters, no-color, and unsupported UX flags.
+
+## Restrictions
+
+- Do not perform writes.
+- Do not start slices.
+- Do not prompt.
+- Do not use Ink.
+
+## Risks
+
+- Central CLI router changes can regress help or unsupported-command behavior.
+
+## Completion Checklist
+
+- [ ] Command implemented.
+- [ ] Help updated.
+- [ ] Command tests pass.