create-quiver 0.15.1 → 0.15.3

package/specs/quiver-v33-approval-ux-and-planner-progress/slices/slice-06-workflow-surface-integration/slice.json

@@ -0,0 +1,87 @@
+{
+  "slice_id": "slice-06-workflow-surface-integration",
+  "ticket": "QUIVER-33-06",
+  "type": "feature",
+  "title": "Workflow surface integration",
+  "objective": "Use shared approval candidates across status, approval, flow, resume, and spec-create surfaces.",
+  "description": "Integrates the shared decision model into `ai approvals`, `flow`, `ai status`, `ai resume`, and `spec create --interactive` so every surface recommends the same safe next step.",
+  "git": {
+    "branch_type": "feature",
+    "base_branch": "main",
+    "branch_slug": "v33-workflow-surface-integration",
+    "branch_name": "feature/QUIVER-33-06-v33-workflow-surface-integration"
+  },
+  "files": [
+    "src/create-quiver/commands/ai.js",
+    "src/create-quiver/commands/flow.js",
+    "src/create-quiver/commands/spec.js",
+    "src/create-quiver/lib/ai/run-state.js",
+    "src/create-quiver/lib/approvals.js",
+    "tests/commands/ai-run-state.test.js",
+    "tests/commands/flow.test.js",
+    "tests/commands/spec-create.test.js"
+  ],
+  "expected_read_paths": [
+    "src/create-quiver/commands/ai.js",
+    "src/create-quiver/commands/flow.js",
+    "src/create-quiver/commands/spec.js",
+    "src/create-quiver/lib/ai/run-state.js",
+    "src/create-quiver/lib/approvals.js",
+    "tests/commands/ai-run-state.test.js",
+    "tests/commands/flow.test.js",
+    "tests/commands/spec-create.test.js",
+    "SPEC.md"
+  ],
+  "allowed_write_paths": [
+    "src/create-quiver/commands/ai.js",
+    "src/create-quiver/commands/flow.js",
+    "src/create-quiver/commands/spec.js",
+    "src/create-quiver/lib/ai/run-state.js",
+    "src/create-quiver/lib/approvals.js",
+    "tests/commands/ai-run-state.test.js",
+    "tests/commands/flow.test.js",
+    "tests/commands/spec-create.test.js",
+    "specs/quiver-v33-approval-ux-and-planner-progress/**"
+  ],
+  "depends_on": [
+    "slice-01-approval-candidates-model",
+    "slice-02-approve-interactive-selection",
+    "slice-03-technical-plan-review-decision-data"
+  ],
+  "parallel_safe": "no",
+  "parallel_safe_reason": "This slice touches multiple workflow surfaces and should land after core approval behavior is stable.",
+  "must": [
+    "Update `ai approvals` to use shared approval candidate data.",
+    "Update `flow` recommendations to avoid conflicting approval guidance.",
+    "Update `ai status` and `ai resume` next safe commands where approval selection applies.",
+    "Update `spec create --interactive` to show reviewed and approved technical-plan input using shared data.",
+    "Keep read-only/machine-readable surfaces free of prompts.",
+    "Avoid duplicating decision logic in each command."
+  ],
+  "not_included": [
+    "Changing execution-plan logic.",
+    "Changing spec artifact generation semantics.",
+    "Adding new lifecycle phases unless unavoidable."
+  ],
+  "acceptance": [
+    "`ai approvals` shows the same recommended approval version as `ai approve`.",
+    "`flow` recommends approval commands consistent with candidate state.",
+    "`ai status` and `ai resume` do not contradict `ai approvals`.",
+    "`spec create --interactive` identifies the reviewed and approved technical plan clearly.",
+    "JSON and read-only commands remain prompt-free.",
+    "Tests cover drift-prone states."
+  ],
+  "tests": [
+    "node --test tests/commands/ai-run-state.test.js tests/commands/flow.test.js tests/commands/spec-create.test.js tests/commands/ai-review-plan.test.js",
+    "git diff --check"
+  ],
+  "validation_hints": [
+    "Prefer one shared formatting/data helper over duplicated command-specific state checks.",
+    "Keep command output stable enough for existing tests unless the visible contract intentionally changes."
+  ],
+  "estimated_hours": 8,
+  "status": "completed",
+  "blocked_reason": null,
+  "actual_hours": 8,
+  "completed_at": "2026-05-28"
+}

package/specs/quiver-v33-approval-ux-and-planner-progress/slices/slice-07-docs-tests-release-readiness/CLOSURE_BRIEF.md

@@ -0,0 +1,21 @@
+# CLOSURE_BRIEF - slice-07 Docs, tests, and release readiness
+
+## Summary
+
+Completed docs, template alignment, full test validation, smokes, package readiness, evidence, status metadata, and PR body updates for v33.
+
+## Validation
+
+- [x] Docs are aligned.
+- [x] Full tests pass.
+- [x] Smokes pass.
+- [x] Evidence and PR body are updated.
+
+## Pending
+
+- None.
+
+## Remaining Risks
+
+- None critical.
+- This slice does not claim npm publication.

package/specs/quiver-v33-approval-ux-and-planner-progress/slices/slice-07-docs-tests-release-readiness/EXECUTION_BRIEF.md

@@ -0,0 +1,55 @@
+# EXECUTION_BRIEF - slice-07 Docs, tests, and release readiness
+
+## Context
+
+This slice closes the spec after implementation slices land. It synchronizes documentation, evidence, and PR readiness.
+
+## Objective
+
+Update docs and evidence, run validation, and prepare the PR for review without claiming package publication.
+
+## Scope
+
+- `docs/CLI_UX_GUIDE.md`
+- `docs/reference/commands.md`
+- `README_FOR_AI.md`
+- generated docs templates if affected
+- changelog/roadmap if local release process requires it
+- spec evidence and closure docs
+
+## Acceptance Criteria
+
+- Public and AI-facing docs match implemented behavior.
+- Generated templates match command guidance.
+- Focused and full tests pass or blockers are explicit.
+- Smoke/package readiness evidence is recorded.
+- Spec status and PR body are updated.
+
+## Technical Plan Summary
+
+Close documentation after behavior is real. Run focused tests first, then full suite and smokes.
+
+## Suggested Steps
+
+1. Update docs and templates.
+2. Run focused command tests.
+3. Run full tests and smokes.
+4. Update evidence and status.
+5. Update PR body.
+
+## Restrictions
+
+- Do not claim npm publication.
+- Do not introduce new behavior beyond documentation/test closure.
+
+## Risks
+
+- Full smokes can be slow or environment-sensitive; record exact blockers if any fail.
+
+## Completion Checklist
+
+- [ ] Docs updated.
+- [ ] Focused tests run.
+- [ ] Full tests/smokes run or blockers recorded.
+- [ ] Evidence report updated.
+- [ ] PR body ready.

package/specs/quiver-v33-approval-ux-and-planner-progress/slices/slice-07-docs-tests-release-readiness/slice.json

@@ -0,0 +1,97 @@
+{
+  "slice_id": "slice-07-docs-tests-release-readiness",
+  "ticket": "QUIVER-33-07",
+  "type": "docs",
+  "title": "Docs, tests, and release readiness",
+  "objective": "Close documentation, regression coverage, smoke validation, and release readiness for v33.",
+  "description": "Updates public and AI-facing docs after implementation, runs full tests and smokes, records evidence, and prepares the PR for review.",
+  "git": {
+    "branch_type": "feature",
+    "base_branch": "main",
+    "branch_slug": "v33-docs-tests-release-readiness",
+    "branch_name": "feature/QUIVER-33-07-v33-docs-tests-release-readiness"
+  },
+  "files": [
+    "README_FOR_AI.md",
+    "docs/CLI_UX_GUIDE.md",
+    "docs/reference/commands.md",
+    "docs/COMMANDS.md.template",
+    "docs/AI_ONBOARDING_PROMPT.md.template",
+    "CHANGELOG.md",
+    "ROADMAP.md",
+    "specs/quiver-v33-approval-ux-and-planner-progress/**"
+  ],
+  "expected_read_paths": [
+    "README_FOR_AI.md",
+    "README.md",
+    "docs/CLI_UX_GUIDE.md",
+    "docs/reference/commands.md",
+    "docs/COMMANDS.md.template",
+    "docs/AI_ONBOARDING_PROMPT.md.template",
+    "CHANGELOG.md",
+    "ROADMAP.md",
+    "SPEC.md",
+    "EVIDENCE_REPORT.md"
+  ],
+  "allowed_write_paths": [
+    "README_FOR_AI.md",
+    "README.md",
+    "docs/CLI_UX_GUIDE.md",
+    "docs/reference/commands.md",
+    "docs/COMMANDS.md.template",
+    "docs/AI_ONBOARDING_PROMPT.md.template",
+    "CHANGELOG.md",
+    "ROADMAP.md",
+    "specs/quiver-v33-approval-ux-and-planner-progress/**"
+  ],
+  "depends_on": [
+    "slice-02-approve-interactive-selection",
+    "slice-03-technical-plan-review-decision-data",
+    "slice-04-revise-input-guardrails",
+    "slice-05-provider-progress-alignment",
+    "slice-06-workflow-surface-integration"
+  ],
+  "parallel_safe": "no",
+  "parallel_safe_reason": "Final docs, tests, smoke evidence, and release readiness must close after all implementation slices.",
+  "must": [
+    "Update CLI UX and command reference docs for approval selectors, revise guardrails, and progress behavior.",
+    "Update README_FOR_AI source-of-truth notes.",
+    "Update generated templates if command guidance changes.",
+    "Run focused tests and full test suite.",
+    "Run smoke commands and package readiness checks where feasible.",
+    "Update STATUS.md, EVIDENCE_REPORT.md, CLOSURE_BRIEF.md files, and pr.md with final evidence.",
+    "Avoid claiming package publication until it actually happens."
+  ],
+  "not_included": [
+    "New product behavior beyond closing docs/tests.",
+    "Actual npm publication.",
+    "Post-merge cleanup."
+  ],
+  "acceptance": [
+    "Docs describe TTY approval selection and no-TTY explicit version behavior.",
+    "Docs describe planner progress behavior without implying prompts are mandatory.",
+    "Generated templates remain aligned.",
+    "Focused tests for every changed command pass.",
+    "Full test suite passes or documented blockers are explicit.",
+    "Smoke/package readiness evidence is recorded.",
+    "Spec status and PR body are updated."
+  ],
+  "tests": [
+    "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-v33-approval-ux-and-planner-progress"
+  ],
+  "validation_hints": [
+    "If package smoke is too slow or blocked, record the exact blocker and run the maximal focused test subset.",
+    "Do not claim npm release or latest package availability."
+  ],
+  "estimated_hours": 6,
+  "status": "completed",
+  "blocked_reason": null,
+  "actual_hours": 6,
+  "completed_at": "2026-05-28"
+}

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.