create-quiver 0.15.2 → 0.15.4

package/specs/quiver-v35-compact-dashboard-version-ux/SPEC.md

@@ -0,0 +1,147 @@
+# Quiver v35 - Compact Dashboard and Version UX
+
+**Date:** 2026-05-28
+**Status:** Planned
+**Source:** User-approved requirement, acceptance criteria, technical plan, and three production-readiness reviews for improving Quiver CLI UX without adding Ink/fullscreen TUI.
+
+Slice numbering resets here. This spec intentionally starts at `slice-00`.
+
+## Problem
+
+`npx create-quiver dashboard` currently renders a long vertical report. When projects have many specs, slices, warnings, agents, runs, or approvals, the user must scroll and section headings disappear, making it hard to understand project state at a glance.
+
+Quiver also has a plain semver `--version` contract, but no human-friendly version surface with Quiver identity comparable to the Angular CLI style shown by the user.
+
+## Objective
+
+Improve Quiver CLI human UX with:
+
+- a compact, summary-first `dashboard` default that answers "what is happening and what should I do next?";
+- explicit detail and section views for deeper inspection;
+- a Quiver-branded human `version` command with a color-aware ASCII banner;
+- stable machine-readable output for automation;
+- no Ink, fullscreen TUI, providers, prompts, spinners, writes, or workflow side effects.
+
+## Scope
+
+### Included
+
+- Improve `npx create-quiver dashboard` human default output.
+- Add dashboard human-only flags:
+  - `--details`
+  - `--section <name>`
+  - `--limit <n>`
+- Preserve existing `dashboard --json` contract by default.
+- Add JSON-safe errors for rejected `dashboard --json` combinations.
+- Add `npx create-quiver version`.
+- Add `npx create-quiver version --json`.
+- Preserve `npx create-quiver --version` and `-V` as semver-only output.
+- Support the `quiver` binary alias for the new command.
+- Update help, references, CLI UX docs, generated guidance, tests, smokes, and package validation.
+- Record the `docs/INDEX.md` documentation debt and package-publication decision.
+
+### Excluded
+
+- Ink/fullscreen TUI.
+- Browser UI or local server.
+- Interactive navigation.
+- Prompt-driven dashboard flows.
+- Writing project state from `dashboard` or `version`.
+- Running npm, git, provider CLIs, or shell probes from `version`.
+- Publishing to npm.
+
+## Approved Acceptance Criteria
+
+### Dashboard compact default
+
+1. `npx create-quiver dashboard` prints a compact summary-first human report.
+2. The default report prioritizes state, blockers, warnings, next safe command, progress, and summary counts.
+3. The default report does not print complete repeated lists in projects with many specs, slices, warnings, agents, approvals, or runs.
+4. In a large fixture, the default report is `<= 28` non-empty lines after ANSI is stripped.
+5. The next safe command must remain in the compact view and must not be pushed below long lists.
+6. Empty/no-spec projects still show useful state, warnings, and the next planning command without repeated empty sections.
+
+### Dashboard detail and section views
+
+7. `dashboard --details` renders the full report for human inspection.
+8. `dashboard --section <name>` renders only the requested supported section.
+9. Supported sections are `overview`, `specs`, `slices`, `blockers`, `warnings`, `agents`, `approvals`, `runs`, `active-slice`, and `next-steps`.
+10. Unsupported sections fail with an actionable error that lists valid values.
+11. `dashboard --limit <n>` accepts integers from `1` to `100`.
+12. `dashboard --limit <n>` without `--section` applies to all compact repeated lists.
+13. `dashboard --limit 0`, negative values, decimals, text, or missing values fail with actionable guidance.
+14. Truncated lists show how many entries are hidden and the exact command to inspect them, for example `+ 12 more. Run: npx create-quiver dashboard --section slices`.
+15. Long descriptive text is truncated with `...` to protect horizontal readability.
+16. Critical next-step commands should not be truncated; if too long, show a shorter inspection command in compact output and leave exact detail in `--details`.
+
+### Dashboard JSON and flag safety
+
+17. `dashboard --json` remains parseable JSON with no colors, prompts, spinners, or human prose.
+18. `dashboard --json` keeps the existing schema shape by default.
+19. `dashboard --json --section specs`, `dashboard --json --details`, and equivalent human-only combinations are rejected with JSON in stdout, empty stderr, and non-zero exit code.
+20. `dashboard --details --section specs` is rejected rather than relying on implicit precedence.
+21. New dashboard flags are command-scoped: using them outside `dashboard` fails with clear guidance.
+22. `dashboard` remains read-only and does not write files, start slices, open worktrees, run providers, or prompt.
+23. `dashboard` collects state once and renders from the in-memory report; section rendering must not introduce a second state collection path.
+
+### Version command
+
+24. `npx create-quiver version` prints a human-readable Quiver version report.
+25. The human report includes an ASCII `Quiver` banner that uses the approved Quiver palette when color is available: `#86C8F2`, `#6BADEB`, `#7F9EE8`, `#9B82E6`, `#D56AB0`.
+26. The banner and human report remain readable without color and fit within `<= 80` columns.
+27. Color is disabled for `--no-color`, `NO_COLOR`, `FORCE_COLOR=0`, CI, no-TTY, and dumb terminals.
+28. `version` works outside initialized Quiver projects; project metadata is best-effort and uses `Project: none` when unavailable.
+29. `version` does not execute external processes such as `npm --version`, `git`, or provider CLIs.
+30. `version --json` emits parseable JSON with `version_schema_version: 1`, `cli.version`, `runtime.node`, `runtime.platform`, `runtime.arch`, `package_manager`, and `project`.
+31. `version --json` emits no banner, ANSI, or human prose.
+32. `npx create-quiver --version`, `npx create-quiver -V`, `quiver --version`, and `quiver -V` continue to print only the package semver.
+33. `quiver version` behaves like `create-quiver version`.
+
+### Documentation, packaging, and validation
+
+34. Help output documents the new command and dashboard flags.
+35. `docs/reference/commands.md`, `docs/CLI_UX_GUIDE.md`, and `README_FOR_AI.md` are updated if their public contracts change.
+36. If a real root `docs/INDEX.md` is added to this repository, package contents and `.npmignore` are reviewed so npm output is intentional.
+37. Tests cover compact dashboard, details, section rendering, limit validation, rejected flag combinations, JSON cleanliness, no-color/CI/no-TTY, version human output, version JSON, semver-only `--version`, and alias behavior.
+38. Smokes validate the package tarball installed into a temporary project and execute both `create-quiver` and `quiver` binaries.
+39. Final validation includes `node --test`, `git diff --check`, `npx create-quiver spec validate specs/quiver-v35-compact-dashboard-version-ux`, `npm run package:quiver`, and relevant smoke suites.
+
+## Approved Technical Plan
+
+1. Create the spec package and document the `docs/INDEX.md` debt without implementing product code.
+2. Add dashboard parsing and contract validation for `--details`, `--section`, and `--limit`.
+3. Keep human-only dashboard validations JSON-safe when `--json` is present.
+4. Build compact dashboard formatting on top of the existing report, not by creating a second state source.
+5. Add detail and section renderers after the flag contract is stable.
+6. Add a new `version` command that reuses Quiver theme helpers and best-effort local metadata only.
+7. Preserve semver-only top-level `--version` and `-V`.
+8. Update docs, generated guidance, and CLI help after command behavior stabilizes.
+9. Add focused tests first, then full tests and package-installed smokes.
+
+## Slice Roadmap
+
+| Slice | Title | Status | Dependencies |
+|---|---|---|---|
+| slice-00 | Foundation and doc router decision | completed | none |
+| slice-01 | Dashboard CLI contract | ready | slice-00 |
+| slice-02 | Dashboard compact renderer | planned | slice-01 |
+| slice-03 | Dashboard details and sections | planned | slice-01, slice-02 |
+| slice-04 | Version command and banner | planned | slice-01 |
+| slice-05 | Docs, help, and generated guidance | planned | slice-02, slice-03, slice-04 |
+| slice-06 | Tests, smokes, and release readiness | planned | slice-02, slice-03, slice-04, slice-05 |
+| slice-07 | Package and cross-platform smoke | planned | slice-05, slice-06 |
+
+## Risks and Guardrails
+
+- `--version` is automation-sensitive and must stay semver-only.
+- `--version` is also used as an AI approval flag; the new rich output must use `version`, not overload `--version`.
+- Parser-level errors currently produce human stderr, so JSON-safe dashboard combination errors need deliberate routing.
+- Terminal width, CI, no-TTY, and Windows behavior must be tested rather than assumed.
+- Adding a real `docs/INDEX.md` to this repo could change npm package contents.
+- The implementation must not introduce Ink or fullscreen TUI before there is evidence the compact renderer is insufficient.
+
+## Assumptions
+
+- This repository's canonical spec location is `specs/quiver-vNN-*`, not the generic `docs/specs` path from reusable skills.
+- The current dashboard report contract from v34 remains the source of truth for dashboard data.
+- `docs/INDEX.md` is missing in this checkout while `docs/INDEX.md.template` exists; this is documented debt, not a blocker for this spec package.

package/specs/quiver-v35-compact-dashboard-version-ux/STATUS.md

@@ -0,0 +1,33 @@
+# Status - Quiver v35 Compact Dashboard and Version UX
+
+**Overall status:** Completed
+**Created:** 2026-05-28
+**Completed:** 2026-05-28
+**Current slice:** none
+
+## Summary
+
+This spec improves Quiver's human CLI UX by making `dashboard` compact and actionable by default, adding explicit detail/section inspection modes, and adding a Quiver-branded `version` command while preserving automation-safe JSON and semver-only version contracts.
+
+Implementation, docs, tests, package smoke, and cross-platform smoke are complete. No npm publication is included in this spec.
+
+## Slice Status
+
+| Slice | Status | Notes |
+|---|---|---|
+| slice-00-foundation-and-doc-router | Completed | Spec package, execution plan, PR body, evidence skeleton, and slice briefs created. |
+| slice-01-dashboard-cli-contract | Completed | Dashboard flags, validations, and JSON-safe error behavior implemented. |
+| slice-02-dashboard-compact-renderer | Completed | Default dashboard is compact, summary-first, and line-budgeted. |
+| slice-03-dashboard-details-sections | Completed | `--details` and section-specific human renderers implemented. |
+| slice-04-version-command | Completed | Branded human `version` and parseable `version --json` implemented. |
+| slice-05-docs-help-generated-guidance | Completed | Help, docs, generated guidance, and package-content decision updated. |
+| slice-06-tests-smokes-release-readiness | Completed | Focused tests, full validation, package smoke, and evidence completed. |
+| slice-07-package-and-cross-platform-smoke | Completed | Installed tarball, binary alias, package contents, and cross-platform behavior validated. |
+
+## Current Blockers
+
+- None.
+
+## Next Step
+
+Ready for human review and PR/package publication decision. No critical blockers remain.

package/specs/quiver-v35-compact-dashboard-version-ux/pr.md

@@ -0,0 +1,106 @@
+# PR: Quiver v35 Compact Dashboard and Version UX
+
+## Title
+
+Quiver v35 Compact Dashboard and Version UX
+
+## Summary
+
+- Makes `dashboard` compact, summary-first, and actionable by default.
+- Adds `dashboard --details`, `dashboard --section <name>`, and `dashboard --limit <n>` for focused inspection.
+- Adds branded `version` and parseable `version --json`.
+- Preserves semver-only top-level `--version` / `-V` and stable `dashboard --json` automation behavior.
+- Extends docs, generated guidance, tests, package smoke, installed tarball smoke, and spec evidence.
+
+## Scope
+
+- CLI parser/routing for dashboard human-only flags.
+- Dashboard human renderers and JSON-safe option validation.
+- Version report collection and Quiver ASCII banner rendering.
+- Generated `quiver:version` script and command documentation.
+- Release-readiness evidence for local tests, package build, smoke scripts, and cross-platform smoke.
+
+## Files
+
+- `src/create-quiver/index.js`
+- `src/create-quiver/commands/dashboard.js`
+- `src/create-quiver/lib/dashboard.js`
+- `src/create-quiver/lib/version.js`
+- `src/create-quiver/lib/init-docs.js`
+- `src/create-quiver/lib/init-layout.js`
+- `docs/reference/commands.md`
+- `docs/CLI_UX_GUIDE.md`
+- `README_FOR_AI.md`
+- `scripts/ci/smoke-create-quiver.sh`
+- `scripts/ci/smoke-cross-platform.js`
+- `tests/commands/dashboard.test.js`
+- `tests/commands/cli-contract.test.js`
+- `tests/lib/dashboard.test.js`
+- `tests/lib/version.test.js`
+- `specs/quiver-v35-compact-dashboard-version-ux/**`
+
+## How to Test (DETAILED - REQUIRED)
+
+### Required Environment
+
+- Node.js and npm available.
+- `gh` installed for PR preflight/creation.
+- SSH access configured for `github-personal` with identity file `~/ssh/github-personal`.
+
+### Worktree Access
+
+- Branch: `feature/QUIVER-35-compact-dashboard-version-ux`
+- Base used for this PR: `main`, because the remote currently exposes `main` as default and does not expose `origin/develop`.
+- Spec package: `specs/quiver-v35-compact-dashboard-version-ux/`
+
+### Run the Project
+
+```bash
+node bin/create-quiver.js dashboard
+node bin/create-quiver.js dashboard --section slices --limit 10
+node bin/create-quiver.js dashboard --json
+node bin/create-quiver.js version --no-color
+node bin/create-quiver.js version --json
+```
+
+### Use Cases
+
+- Human user can inspect project/spec/slice state without scrolling through every section by default.
+- Human user can opt into full dashboard detail with `--details`.
+- Human user can inspect one dashboard area with `--section <name>`.
+- Automation can keep using `dashboard --json` without ANSI/prose contamination.
+- Automation can keep using top-level `--version` / `-V` as semver-only output.
+- Humans and automation can use `version` / `version --json` for richer metadata.
+
+### Technical Verification
+
+```bash
+node --test tests/**/*.test.js
+git diff --check
+npx create-quiver spec validate specs/quiver-v35-compact-dashboard-version-ux --strict
+npm run package:quiver
+npm run smoke:create-quiver
+node scripts/ci/smoke-cross-platform.js
+```
+
+## Evidence
+
+- `node --test tests/**/*.test.js` passed: 523 tests.
+- `git diff --check` passed.
+- `npx create-quiver spec validate specs/quiver-v35-compact-dashboard-version-ux --strict` passed.
+- `npm run package:quiver` passed and produced `create-quiver-0.15.2.tgz`.
+- `npm run smoke:create-quiver` passed.
+- `node scripts/ci/smoke-cross-platform.js` passed.
+- Detailed evidence is recorded in `specs/quiver-v35-compact-dashboard-version-ux/EVIDENCE_REPORT.md`.
+
+## Rollback
+
+- Revert this PR.
+- If already packaged locally, remove the generated tarball `create-quiver-0.15.2.tgz`.
+- Existing `--version` consumers remain protected because top-level semver behavior is covered by tests and smoke.
+
+## Risks / Notes
+
+- No npm publication is included.
+- Root `docs/INDEX.md` was not added; this repo currently has `docs/INDEX.md.template`, while generated projects still receive `docs/INDEX.md`.
+- Native Windows was not run in this turn; cross-platform smoke includes Windows path/npm guards and passed locally on macOS.

package/specs/quiver-v35-compact-dashboard-version-ux/slices/slice-00-foundation-and-doc-router/CLOSURE_BRIEF.md

@@ -0,0 +1,19 @@
+# CLOSURE_BRIEF - slice-00 Foundation and doc router decision
+
+## Summary
+
+Created the v35 spec package for compact dashboard and version UX, including the top-level spec, status, execution plan, evidence skeleton, PR body, and all per-slice handoffs.
+
+## Validation
+
+- [x] JSON parse validation for slice files.
+- [x] `node bin/create-quiver.js spec validate specs/quiver-v35-compact-dashboard-version-ux`
+- [x] `git diff --check`
+
+## Pending
+
+- None for this slice.
+
+## Remaining Risks
+
+- `docs/INDEX.md` is still missing in the repository root and remains documented debt for a future implementation slice.

package/specs/quiver-v35-compact-dashboard-version-ux/slices/slice-00-foundation-and-doc-router/EXECUTION_BRIEF.md

@@ -0,0 +1,38 @@
+# EXECUTION_BRIEF - slice-00 Foundation and doc router decision
+
+## Objective
+
+Create the v35 spec package for compact dashboard and version UX without product-code implementation.
+
+## Context
+
+The user approved acceptance criteria and a hardened technical plan. The repository's expected `docs/INDEX.md` is missing in this checkout, but `docs/INDEX.md.template` exists. The repo's real spec convention is `specs/quiver-vNN-*`.
+
+## Scope
+
+- `specs/quiver-v35-compact-dashboard-version-ux/SPEC.md`
+- `STATUS.md`
+- `EXECUTION_PLAN.md`
+- `EVIDENCE_REPORT.md`
+- `pr.md`
+- all slice directories and handoff files
+
+## Acceptance Criteria
+
+- Spec package exists under `specs/quiver-v35-compact-dashboard-version-ux`.
+- Each slice has `slice.json`, `EXECUTION_BRIEF.md`, and `CLOSURE_BRIEF.md`.
+- `STATUS.md` marks this slice completed and the next implementation slice ready.
+- No product code is modified.
+- Validation is attempted and any blocker is documented.
+
+## Restrictions
+
+- Do not create dashboard or version implementation.
+- Do not create or modify root `docs/INDEX.md` in this slice.
+- Do not publish npm.
+
+## Completion Checklist
+
+- [x] Spec package created.
+- [x] Slice handoffs created.
+- [x] JSON and spec validation run.

package/specs/quiver-v35-compact-dashboard-version-ux/slices/slice-00-foundation-and-doc-router/slice.json

@@ -0,0 +1,64 @@
+{
+  "slice_id": "slice-00-foundation-and-doc-router",
+  "ticket": "QUIVER-35-00",
+  "type": "documentation",
+  "title": "Foundation and doc router decision",
+  "objective": "Create the approved v35 spec package and record the docs/INDEX.md router decision without changing product code.",
+  "description": "Publishes the spec, execution plan, status, PR body, evidence skeleton, and per-slice handoffs for compact dashboard and version UX work.",
+  "git": {
+    "branch_type": "feature",
+    "base_branch": "main",
+    "branch_slug": "v35-foundation-doc-router",
+    "branch_name": "feature/QUIVER-35-00-v35-foundation-doc-router"
+  },
+  "files": [
+    "specs/quiver-v35-compact-dashboard-version-ux/**"
+  ],
+  "expected_read_paths": [
+    "README_FOR_AI.md",
+    "docs/CLI_UX_GUIDE.md",
+    "docs/reference/commands.md",
+    "docs/INDEX.md.template",
+    "specs/quiver-v34-cli-dashboard-status/SPEC.md",
+    "specs/quiver-v34-cli-dashboard-status/EXECUTION_PLAN.md"
+  ],
+  "allowed_write_paths": [
+    "specs/quiver-v35-compact-dashboard-version-ux/**"
+  ],
+  "depends_on": [],
+  "parallel_safe": "never",
+  "parallel_safe_reason": "This slice establishes the spec package and execution order for all later slices.",
+  "must": [
+    "Create SPEC.md, STATUS.md, EXECUTION_PLAN.md, EVIDENCE_REPORT.md, and pr.md.",
+    "Create every slice directory with slice.json, EXECUTION_BRIEF.md, and CLOSURE_BRIEF.md.",
+    "Record that docs/INDEX.md is missing in this checkout while docs/INDEX.md.template exists.",
+    "Do not implement product code."
+  ],
+  "not_included": [
+    "Dashboard parser changes.",
+    "Version command implementation.",
+    "Docs/INDEX.md creation outside the spec package.",
+    "Tests or smokes."
+  ],
+  "acceptance": [
+    "Spec package exists under specs/quiver-v35-compact-dashboard-version-ux.",
+    "Each slice has slice.json, EXECUTION_BRIEF.md, and CLOSURE_BRIEF.md.",
+    "STATUS.md marks slice-00 completed and slice-01 ready.",
+    "No product code is modified by this slice.",
+    "Spec validation is attempted and any blocker is documented."
+  ],
+  "tests": [
+    "node -e \"const fs=require('fs'); for (const f of process.argv.slice(1)) JSON.parse(fs.readFileSync(f,'utf8'))\" specs/quiver-v35-compact-dashboard-version-ux/slices/*/slice.json",
+    "npx create-quiver spec validate specs/quiver-v35-compact-dashboard-version-ux",
+    "git diff --check"
+  ],
+  "validation_hints": [
+    "Use the repo's existing specs/quiver-vNN-* format rather than the generic docs/specs skill format.",
+    "Keep handoff content concise enough for executor agents."
+  ],
+  "estimated_hours": 2,
+  "status": "completed",
+  "blocked_reason": null,
+  "actual_hours": 2,
+  "completed_at": "2026-05-28"
+}

package/specs/quiver-v35-compact-dashboard-version-ux/slices/slice-01-dashboard-cli-contract/CLOSURE_BRIEF.md

@@ -0,0 +1,19 @@
+# CLOSURE_BRIEF - slice-01 Dashboard CLI contract
+
+## Summary
+
+Implemented dashboard-scoped parsing and validation for `--details`, `--section <name>`, and `--limit <n>`. JSON mode now rejects human-only dashboard flags with parseable JSON stdout and no human stderr, and non-dashboard commands fail clearly for dashboard-only flags.
+
+## Validation
+
+- [x] `node --test tests/commands/dashboard.test.js`
+- [x] `node --test tests/commands/cli-contract.test.js`
+- [x] `git diff --check`
+
+## Pending
+
+- None.
+
+## Remaining Risks
+
+- Low. JSON-safe error behavior is covered by command tests and installed-package smoke.

package/specs/quiver-v35-compact-dashboard-version-ux/slices/slice-01-dashboard-cli-contract/EXECUTION_BRIEF.md

@@ -0,0 +1,49 @@
+# EXECUTION_BRIEF - slice-01 Dashboard CLI contract
+
+## Context
+
+`dashboard --json` already has tests asserting parseable stdout and empty stderr on dashboard errors. New human-only dashboard flags must not break that automation contract.
+
+## Objective
+
+Add the dashboard flag contract for `--details`, `--section <name>`, and `--limit <n>`.
+
+## Scope
+
+- CLI parsing/routing for dashboard flags
+- dashboard option validation
+- focused CLI tests
+
+## Acceptance Criteria
+
+- `dashboard --details` is accepted for human output.
+- `dashboard --section specs` is accepted for human output.
+- `dashboard --limit 5` is accepted.
+- `dashboard --details --section specs` fails actionably.
+- `dashboard --json --section specs` fails with JSON stdout, empty stderr, and non-zero exit.
+- `dashboard --json` remains compatible when no human-only flags are passed.
+- New flags fail clearly outside `dashboard`.
+
+## Technical Plan Summary
+
+Add parser support for the flags, then validate dashboard-specific combinations in a location that can still return JSON errors when `--json` is present.
+
+## Suggested Steps
+
+1. Add parse support for `--details`, `--section`, and `--limit`.
+2. Scope the flags to dashboard.
+3. Validate `--limit` as integer `1..100`.
+4. Add JSON-safe dashboard combination errors.
+5. Add CLI tests for valid and invalid combinations.
+
+## Restrictions
+
+- Do not change dashboard default rendering yet.
+- Do not add the version command.
+- Do not alter `dashboard --json` schema by default.
+
+## Completion Checklist
+
+- [ ] Parser updated.
+- [ ] Dashboard option validation added.
+- [ ] Focused CLI tests pass.

package/specs/quiver-v35-compact-dashboard-version-ux/slices/slice-01-dashboard-cli-contract/slice.json

@@ -0,0 +1,80 @@
+{
+  "slice_id": "slice-01-dashboard-cli-contract",
+  "ticket": "QUIVER-35-01",
+  "type": "feature",
+  "title": "Dashboard CLI contract",
+  "objective": "Add the public CLI contract for dashboard details, section, and limit flags while preserving automation-safe JSON behavior.",
+  "description": "Defines parser, validation, and routing behavior for dashboard human-only flags before changing human rendering.",
+  "git": {
+    "branch_type": "feature",
+    "base_branch": "main",
+    "branch_slug": "v35-dashboard-cli-contract",
+    "branch_name": "feature/QUIVER-35-01-v35-dashboard-cli-contract"
+  },
+  "files": [
+    "src/create-quiver/index.js",
+    "src/create-quiver/commands/dashboard.js",
+    "src/create-quiver/lib/dashboard.js",
+    "tests/commands/dashboard.test.js",
+    "tests/commands/cli-contract.test.js"
+  ],
+  "expected_read_paths": [
+    "src/create-quiver/index.js",
+    "src/create-quiver/commands/dashboard.js",
+    "src/create-quiver/lib/dashboard.js",
+    "src/create-quiver/lib/cli/ux-flags.js",
+    "tests/commands/dashboard.test.js",
+    "tests/commands/cli-contract.test.js",
+    "specs/quiver-v35-compact-dashboard-version-ux/SPEC.md"
+  ],
+  "allowed_write_paths": [
+    "src/create-quiver/index.js",
+    "src/create-quiver/commands/dashboard.js",
+    "src/create-quiver/lib/dashboard.js",
+    "tests/commands/dashboard.test.js",
+    "tests/commands/cli-contract.test.js",
+    "specs/quiver-v35-compact-dashboard-version-ux/**"
+  ],
+  "depends_on": [
+    "slice-00-foundation-and-doc-router"
+  ],
+  "parallel_safe": "no",
+  "parallel_safe_reason": "The dashboard parser and validation contract controls all later dashboard rendering slices.",
+  "must": [
+    "Add dashboard-scoped parsing for --details, --section <name>, and --limit <n>.",
+    "Reject dashboard human-only flags with --json using JSON stdout, empty stderr, and non-zero exit code.",
+    "Reject --details combined with --section instead of using implicit precedence.",
+    "Validate --limit as an integer from 1 to 100.",
+    "Ensure new dashboard flags fail clearly outside the dashboard command.",
+    "Preserve existing dashboard --json schema by default."
+  ],
+  "not_included": [
+    "Compact dashboard rendering.",
+    "Version command.",
+    "Docs updates beyond test-facing help text required for the parser."
+  ],
+  "acceptance": [
+    "dashboard --details is accepted for human output.",
+    "dashboard --section specs is accepted for human output.",
+    "dashboard --limit 5 is accepted and passed to rendering options.",
+    "dashboard --details --section specs fails actionably.",
+    "dashboard --json --section specs fails with parseable JSON stdout and empty stderr.",
+    "dashboard --json without human-only flags remains compatible.",
+    "Non-dashboard use of --section, --details, or --limit fails clearly."
+  ],
+  "tests": [
+    "node --test tests/commands/dashboard.test.js",
+    "node --test tests/commands/cli-contract.test.js",
+    "git diff --check"
+  ],
+  "validation_hints": [
+    "Do not put JSON-sensitive combination validation only in the global parser if that would force human stderr.",
+    "Prefer a small dashboard option validator close to runDashboard."
+  ],
+  "estimated_hours": 4,
+  "status": "completed",
+  "started_at": "2026-05-28T17:00:00Z",
+  "completed_at": "2026-05-28T17:36:57Z",
+  "actual_hours": 2,
+  "blocked_reason": null
+}

package/specs/quiver-v35-compact-dashboard-version-ux/slices/slice-02-dashboard-compact-renderer/CLOSURE_BRIEF.md

@@ -0,0 +1,19 @@
+# CLOSURE_BRIEF - slice-02 Dashboard compact renderer
+
+## Summary
+
+Implemented the compact default dashboard renderer. The default view is summary-first, keeps the next safe command visible, caps repeated lists, includes truncation hints, and preserves the JSON report contract.
+
+## Validation
+
+- [x] `node --test tests/lib/dashboard.test.js`
+- [x] `node --test tests/commands/dashboard.test.js`
+- [x] `git diff --check`
+
+## Pending
+
+- None.
+
+## Remaining Risks
+
+- Low. Large fixture tests strip ANSI and enforce compact line budget plus truncation behavior.

package/specs/quiver-v35-compact-dashboard-version-ux/slices/slice-02-dashboard-compact-renderer/EXECUTION_BRIEF.md

@@ -0,0 +1,48 @@
+# EXECUTION_BRIEF - slice-02 Dashboard compact renderer
+
+## Context
+
+The current dashboard human output prints every section vertically. The user explicitly reported that this makes headings disappear when there is a lot of information.
+
+## Objective
+
+Make `npx create-quiver dashboard` compact and actionable by default.
+
+## Scope
+
+- Default human renderer only
+- List truncation helpers
+- Line-budget and no-spec tests
+
+## Acceptance Criteria
+
+- Default output is summary-first.
+- Large fixture output is `<= 28` non-empty lines after ANSI stripping.
+- Next safe command is visible in compact output.
+- No-spec output avoids repeated empty sections.
+- Truncated lists show `+ N more` and an inspection command.
+- `dashboard --json` remains unchanged.
+
+## Technical Plan Summary
+
+Build the compact view from the existing dashboard report. Keep details and section rendering for the next slice.
+
+## Suggested Steps
+
+1. Add compact formatting helper.
+2. Add ANSI-stripped line-count test helper.
+3. Create a large dashboard fixture.
+4. Add truncation and horizontal shortening.
+5. Preserve JSON tests.
+
+## Restrictions
+
+- Do not introduce Ink or fullscreen TUI.
+- Do not change report collection semantics.
+- Do not implement `--details` or `--section` rendering here.
+
+## Completion Checklist
+
+- [ ] Compact renderer implemented.
+- [ ] Large fixture line budget tested.
+- [ ] JSON compatibility tested.