create-quiver 0.15.2 → 0.15.4

package/specs/quiver-v44-provider-live-output-tui-lite/EVIDENCE_REPORT.md

@@ -0,0 +1,18 @@
+# Evidence Report - Quiver v44 Provider Live Output TUI-lite
+
+## slice-00-tui-lite-contract-foundation
+
+- Created this spec package and slice handoffs.
+- Runtime implementation intentionally not started.
+- `node -e "const fs=require('fs'); for (const f of fs.globSync('specs/quiver-v44-provider-live-output-tui-lite/slices/*/slice.json')) JSON.parse(fs.readFileSync(f,'utf8')); console.log('slice json ok')"`: Pass.
+- `node bin/create-quiver.js spec validate specs/quiver-v44-provider-live-output-tui-lite --strict`: Pass.
+- `git diff --check`: Pass.
+
+## Pending Evidence
+
+- `node --test tests/lib/ai-providers.test.js tests/lib/cli-ux.test.js`
+- `node --test tests/commands/ai-prepare-context-planner.test.js tests/commands/ai-plan.test.js tests/commands/ai-review-plan.test.js`
+- `node --test tests/**/*.test.js`
+- `npm run smoke:create-quiver`
+- `npm run package:quiver`
+- `node bin/create-quiver.js spec validate specs/quiver-v44-provider-live-output-tui-lite --strict`

package/specs/quiver-v44-provider-live-output-tui-lite/EXECUTION_PLAN.md

@@ -0,0 +1,31 @@
+# Execution Plan - Quiver v44 Provider Live Output TUI-lite
+
+## Execution Rules
+
+- Do not stream provider output unless `--verbose` is explicitly passed.
+- Keep non-verbose behavior unchanged.
+- Keep `--json`, CI, no-TTY, `--dry-run`, and `--print-prompt` clean.
+- Redact and truncate provider output before any human display.
+- Preserve provider result shape and downstream parsing.
+- Avoid full-screen TUI dependencies.
+
+## Suggested Order
+
+1. `slice-00-tui-lite-contract-foundation`
+2. `slice-01-provider-stream-hooks`
+3. `slice-02-live-output-renderer`
+4. `slice-03-prepare-context-integration`
+5. `slice-04-planner-command-audit-adoption`
+6. `slice-05-docs-tests-readiness`
+
+## Final Validation
+
+```bash
+node --test tests/lib/ai-providers.test.js tests/lib/cli-ux.test.js
+node --test tests/commands/ai-prepare-context-planner.test.js tests/commands/ai-plan.test.js tests/commands/ai-review-plan.test.js
+node --test tests/**/*.test.js
+npm run smoke:create-quiver
+npm run package:quiver
+git diff --check
+node bin/create-quiver.js spec validate specs/quiver-v44-provider-live-output-tui-lite --strict
+```

package/specs/quiver-v44-provider-live-output-tui-lite/SPEC.md

@@ -0,0 +1,118 @@
+# Quiver v44 - Provider Live Output TUI-lite
+
+**Date:** 2026-05-29
+**Status:** Planned
+**Source:** User-approved acceptance criteria and technical plan for elegant provider output visibility.
+
+## Problem
+
+Provider-backed commands currently show clean progress spinners, but long-running executions can feel opaque. During dogfooding, `ai prepare-context --with-planner --review --interactive` remained on `Ejecutando agente` for several minutes while the underlying provider process was still active. The user could not see whether the model was producing useful output, blocked, waiting, or failing.
+
+Showing raw provider output by default would conflict with Quiver's automation and privacy contracts. The improvement needs a controlled, opt-in, visually polished human mode.
+
+## Objective
+
+Add a safe and elegant TUI-lite live output experience for provider-backed commands, starting with:
+
+```bash
+npx create-quiver ai prepare-context --with-planner --review --interactive --verbose
+```
+
+The experience must improve observability and diagnostics without breaking JSON output, CI/no-TTY usage, provider result parsing, docs-only validation, or existing non-verbose behavior.
+
+## Scope
+
+### Included
+
+- Introduce `--verbose` as the opt-in flag for provider live output.
+- Add safe provider stream hooks without changing default provider result behavior.
+- Add a reusable TUI-lite renderer using Quiver's existing CLI theme, colors, and TTY rules.
+- Integrate the renderer into `ai prepare-context --with-planner`.
+- Audit and adopt the renderer where appropriate for:
+  - `ai plan --phase acceptance`
+  - `ai plan --phase technical-plan`
+  - `ai revise --phase acceptance`
+  - `ai revise --phase technical-plan`
+  - `ai review-plan`
+  - `ai repair-plan`
+- Preserve redaction, truncation, JSON cleanliness, no-color fallback, no-TTY behavior, CI behavior, and review/interactive gates.
+- Update public docs and AI guidance for the visible contract.
+- Add focused tests and final validation evidence.
+
+### Excluded
+
+- Full-screen TUI framework.
+- Keyboard navigation, scrollback panes, persistent terminal state, or curses/Ink-style application mode.
+- Showing provider output by default.
+- Streaming hidden chain-of-thought or bypassing provider output policies.
+- Storing provider credentials, tokens, or raw unredacted logs.
+- Changing WDD + SDD semantics or approval gates.
+- Product feature implementation outside CLI provider-output UX.
+
+## Approved Acceptance Criteria
+
+1. Given a user in a human TTY, when `ai prepare-context --with-planner --review --interactive --verbose` executes a provider, Quiver shows a TUI-lite view with clear sections for agent, progress, provider/model, duration, provider output, and next step.
+2. Given the same command without `--verbose`, Quiver preserves current clean loader behavior and does not show detailed model output.
+3. Provider output is displayed inside a controlled visual panel, redacted and truncated before printing.
+4. Output respects `--no-color`, `NO_COLOR`, `TERM=dumb`, CI, and no-TTY, with a simple fallback and no incompatible ANSI.
+5. `--json` remains incompatible with human TUI output and is not contaminated by loaders, colors, prompts, or provider text.
+6. If the provider emits no visible output for a reasonable interval, Quiver shows an actionable heartbeat with provider, model, elapsed time, and waiting state.
+7. If the provider fails, Quiver shows an actionable error and, when available, relevant redacted provider output.
+8. TUI-lite output does not alter parsing of the provider result or docs-only validation in `prepare-context`.
+9. The implementation audits the listed planner/reviewer commands and either adopts the renderer or records a concrete reason and follow-up.
+10. The renderer is shared or structured for reuse instead of being hardcoded only inside `prepare-context`.
+11. Documentation updates cover `docs/CLI_UX_GUIDE.md`, `docs/reference/commands.md`, and `README_FOR_AI.md` when the visible agent contract changes.
+12. Tests cover TTY verbose, TTY non-verbose, no-TTY/CI, no-color, JSON cleanliness, provider success, provider failure, redaction/truncation, and `--review --interactive` compatibility.
+13. The feature does not introduce a heavyweight TUI dependency or behavior that blocks automation.
+14. The visual style follows `docs/CLI_UX_GUIDE.md` and Quiver's existing CLI theme.
+
+## Approved Technical Plan
+
+1. Add parser and option plumbing for `--verbose`, scoped to provider-backed commands and rejected or ignored safely where unsupported.
+2. Extend provider execution internals with optional stream/status callbacks while preserving accumulated stdout/stderr and final result shape.
+3. Create a reusable TUI-lite provider renderer under the CLI library layer.
+4. Wire renderer activation through TTY-aware UX mode checks: human TTY + `--verbose` + live provider execution only.
+5. Integrate the renderer into `runPrepareContextWithPlanner`.
+6. Audit and adopt the same pattern for planner/reviewer commands using shared provider progress paths.
+7. Keep provider output redacted/truncated before display and never persist new unredacted logs.
+8. Update docs and AI guidance after behavior is implemented.
+9. Add focused unit/command tests and final full-suite/package validation.
+
+## Slice Roadmap
+
+| Slice | Title | Status | Dependencies |
+|---|---|---|---|
+| slice-00 | TUI-lite contract foundation | completed | none |
+| slice-01 | Provider stream hooks | planned | slice-00 |
+| slice-02 | Live output renderer | planned | slice-01 |
+| slice-03 | Prepare-context integration | planned | slice-02 |
+| slice-04 | Planner command audit and adoption | planned | slice-03 |
+| slice-05 | Docs, tests, and readiness | planned | slice-04 |
+
+## Validation Strategy
+
+```bash
+node --test tests/lib/ai-providers.test.js tests/lib/cli-ux.test.js
+node --test tests/commands/ai-prepare-context-planner.test.js tests/commands/ai-plan.test.js tests/commands/ai-review-plan.test.js
+node --test tests/**/*.test.js
+npm run smoke:create-quiver
+npm run package:quiver
+git diff --check
+node bin/create-quiver.js spec validate specs/quiver-v44-provider-live-output-tui-lite --strict
+```
+
+## Risks
+
+- Streaming output can leak sensitive values if redaction is bypassed.
+- Spinner and live output can conflict visually if both render at once.
+- JSON/no-TTY/CI output can regress if verbose gates are not centralized.
+- Provider CLIs may buffer output differently, so heartbeat diagnostics are needed.
+- Renderer snapshots can become brittle if tests assert transient spinner frames.
+
+## Resolved Decisions
+
+- Use `--verbose` instead of enabling output by default.
+- Implement TUI-lite append-only output, not a full-screen TUI.
+- Preserve the current provider result contract.
+- Reuse existing Quiver colors and UX mode detection.
+- Treat clean automation output as higher priority than visual richness.

package/specs/quiver-v44-provider-live-output-tui-lite/STATUS.md

@@ -0,0 +1,25 @@
+# Status - Quiver v44 Provider Live Output TUI-lite
+
+**Overall status:** Planned
+**Created:** 2026-05-29
+**Completed:** Not completed
+**Current slice:** slice-01-provider-stream-hooks
+
+## Summary
+
+This spec adds an opt-in TUI-lite live output mode for provider-backed commands, starting with planner-assisted `ai prepare-context`.
+
+## Slice Status
+
+| Slice | Status | Notes |
+|---|---|---|
+| slice-00-tui-lite-contract-foundation | Completed | Spec package and handoffs created. |
+| slice-01-provider-stream-hooks | Planned | Add safe provider callbacks without changing default result behavior. |
+| slice-02-live-output-renderer | Planned | Add reusable TUI-lite renderer with redaction/truncation/fallbacks. |
+| slice-03-prepare-context-integration | Planned | Integrate verbose renderer into `ai prepare-context --with-planner`. |
+| slice-04-planner-command-audit-adoption | Planned | Audit/adopt for planner and review-plan commands. |
+| slice-05-docs-tests-readiness | Planned | Final docs, tests, smokes, and evidence. |
+
+## Current Blockers
+
+- None. Runtime implementation has not started.

package/specs/quiver-v44-provider-live-output-tui-lite/pr.md

@@ -0,0 +1,92 @@
+## Title
+
+Document Quiver v44 provider live output TUI-lite spec
+
+## Summary
+
+- Adds the approved v44 spec package for opt-in provider live output TUI-lite.
+- Documents acceptance criteria, technical plan, execution order, risks, and PR scope.
+- Adds slice handoffs for provider stream hooks, renderer, prepare-context integration, planner-command adoption, and readiness.
+- Updates the docs index so the new spec is discoverable.
+
+## Scope
+
+Included:
+
+- `specs/quiver-v44-provider-live-output-tui-lite/**`
+- `docs/INDEX.md`
+
+Excluded:
+
+- Runtime implementation.
+- CLI parser changes.
+- Provider runner changes.
+- Tests beyond structural spec validation.
+
+## Files
+
+- `docs/INDEX.md`
+- `specs/quiver-v44-provider-live-output-tui-lite/SPEC.md`
+- `specs/quiver-v44-provider-live-output-tui-lite/STATUS.md`
+- `specs/quiver-v44-provider-live-output-tui-lite/EXECUTION_PLAN.md`
+- `specs/quiver-v44-provider-live-output-tui-lite/EVIDENCE_REPORT.md`
+- `specs/quiver-v44-provider-live-output-tui-lite/pr.md`
+- `specs/quiver-v44-provider-live-output-tui-lite/slices/**`
+
+## How to Test (DETAILED - REQUIRED)
+
+### Required Environment
+
+- Node.js available.
+- Repository dependencies installed.
+- Run commands from the repository root.
+
+### Worktree Access
+
+- Use the feature branch for `QUIVER-44-00`.
+- Do not mix runtime implementation changes into this documentation PR.
+
+### Run the Project
+
+No runtime server is required. This PR only adds spec documentation.
+
+### Use Cases
+
+1. Review the v44 spec and confirm it captures the approved `--verbose` TUI-lite provider output requirements.
+2. Review slice handoffs and confirm each future slice has `slice.json`, `EXECUTION_BRIEF.md`, and `CLOSURE_BRIEF.md`.
+3. Confirm `docs/INDEX.md` links to the v44 spec.
+
+### Technical Verification
+
+```bash
+node -e "const fs=require('fs'); for (const f of fs.globSync('specs/quiver-v44-provider-live-output-tui-lite/slices/*/slice.json')) JSON.parse(fs.readFileSync(f,'utf8')); console.log('slice json ok')"
+node bin/create-quiver.js spec validate specs/quiver-v44-provider-live-output-tui-lite --strict
+git diff --check
+```
+
+## Evidence
+
+```text
+slice json ok
+PASS: spec validation passed.
+git diff --check passed with no output.
+```
+
+## Rollback
+
+Revert the documentation commit. No runtime code, generated package output, or persisted Quiver state is changed.
+
+## Risks / Notes
+
+- This PR intentionally does not implement `--verbose` runtime behavior.
+- Follow-up implementation starts at `slice-01-provider-stream-hooks`.
+- The spec follows `docs/GITFLOW_PR_GUIDE.md`: documentation PR first, implementation slices after merge.
+- Repository remote currently exposes `origin/main` but not `origin/develop`; this PR targets `main`.
+node --test tests/lib/ai-providers.test.js tests/lib/cli-ux.test.js
+node --test tests/commands/ai-prepare-context-planner.test.js tests/commands/ai-plan.test.js tests/commands/ai-review-plan.test.js
+node --test tests/**/*.test.js
+npm run smoke:create-quiver
+npm run package:quiver
+git diff --check
+node bin/create-quiver.js spec validate specs/quiver-v44-provider-live-output-tui-lite --strict
+```

package/specs/quiver-v44-provider-live-output-tui-lite/slices/slice-00-tui-lite-contract-foundation/CLOSURE_BRIEF.md

@@ -0,0 +1,11 @@
+# CLOSURE_BRIEF - slice-00 TUI-lite contract foundation
+
+## Summary
+
+Spec package and slice handoffs created from approved acceptance criteria and technical plan. Runtime implementation intentionally not started.
+
+## Validation
+
+- [x] `node -e "const fs=require('fs'); for (const f of fs.globSync('specs/quiver-v44-provider-live-output-tui-lite/slices/*/slice.json')) JSON.parse(fs.readFileSync(f,'utf8')); console.log('slice json ok')"`
+- [x] `node bin/create-quiver.js spec validate specs/quiver-v44-provider-live-output-tui-lite --strict`
+- [x] `git diff --check`

package/specs/quiver-v44-provider-live-output-tui-lite/slices/slice-00-tui-lite-contract-foundation/EXECUTION_BRIEF.md

@@ -0,0 +1,23 @@
+# EXECUTION_BRIEF - slice-00 TUI-lite contract foundation
+
+## Context
+
+The user approved acceptance criteria and a technical plan for an opt-in TUI-lite provider output experience. This slice creates the documented contract only.
+
+## Objective
+
+Create the v44 spec package and handoffs without implementing runtime code.
+
+## Acceptance Criteria
+
+- Spec package exists under `specs/quiver-v44-provider-live-output-tui-lite`.
+- `SPEC.md`, `STATUS.md`, `EXECUTION_PLAN.md`, `EVIDENCE_REPORT.md`, and `pr.md` exist.
+- Every slice directory includes `slice.json`, `EXECUTION_BRIEF.md`, and `CLOSURE_BRIEF.md`.
+- Runtime implementation is explicitly marked as not started.
+- Source code implementation files are not modified.
+
+## Completion Checklist
+
+- [x] Spec package created.
+- [x] Slice handoffs created.
+- [x] Implementation deferred.

package/specs/quiver-v44-provider-live-output-tui-lite/slices/slice-00-tui-lite-contract-foundation/slice.json

@@ -0,0 +1,64 @@
+{
+  "slice_id": "slice-00-tui-lite-contract-foundation",
+  "ticket": "QUIVER-44-00",
+  "type": "documentation",
+  "title": "TUI-lite contract foundation",
+  "objective": "Create the approved spec package and implementation handoffs for provider live output TUI-lite.",
+  "description": "Documents the user-approved acceptance criteria, technical plan, execution order, risks, and slice handoffs before runtime implementation starts.",
+  "git": {
+    "branch_type": "feature",
+    "base_branch": "main",
+    "branch_slug": "v44-tui-lite-contract-foundation",
+    "branch_name": "feature/QUIVER-44-00-v44-tui-lite-contract-foundation"
+  },
+  "files": [
+    "specs/quiver-v44-provider-live-output-tui-lite/**",
+    "docs/INDEX.md"
+  ],
+  "expected_read_paths": [
+    "docs/INDEX.md",
+    "docs/CLI_UX_GUIDE.md",
+    "docs/reference/commands.md",
+    "README_FOR_AI.md",
+    "specs/quiver-v33-approval-ux-and-planner-progress/SPEC.md",
+    "specs/quiver-v30-interactive-cli-ux-agent-selection/slices/slice-05-executor-pr-progress-flows/slice.json"
+  ],
+  "allowed_write_paths": [
+    "specs/quiver-v44-provider-live-output-tui-lite/**",
+    "docs/INDEX.md"
+  ],
+  "depends_on": [],
+  "parallel_safe": "no",
+  "parallel_safe_reason": "Foundation defines the contract for all later v44 slices.",
+  "must": [
+    "Create SPEC, STATUS, EXECUTION_PLAN, EVIDENCE_REPORT, PR body, and all slice handoffs.",
+    "Capture approved acceptance criteria and technical plan.",
+    "Keep implementation code untouched.",
+    "Add the new spec to the documentation index for discoverability."
+  ],
+  "not_included": [
+    "Runtime implementation.",
+    "Provider stream hooks.",
+    "CLI parser changes.",
+    "Tests beyond structural validation."
+  ],
+  "acceptance": [
+    "Spec package exists under specs/quiver-v44-provider-live-output-tui-lite.",
+    "Every slice has slice.json, EXECUTION_BRIEF.md, and CLOSURE_BRIEF.md.",
+    "The package records that runtime implementation has not started.",
+    "No source code implementation files are modified by this slice."
+  ],
+  "tests": [
+    "node -e \"const fs=require('fs'); for (const f of fs.globSync('specs/quiver-v44-provider-live-output-tui-lite/slices/*/slice.json')) JSON.parse(fs.readFileSync(f,'utf8')); console.log('slice json ok')\"",
+    "git diff --check"
+  ],
+  "validation_hints": [
+    "Validate JSON parseability for every slice file.",
+    "Inspect git diff to confirm only docs/spec files changed for this slice."
+  ],
+  "estimated_hours": 1,
+  "status": "completed",
+  "blocked_reason": null,
+  "actual_hours": 1,
+  "completed_at": "2026-05-29"
+}

package/specs/quiver-v44-provider-live-output-tui-lite/slices/slice-01-provider-stream-hooks/CLOSURE_BRIEF.md

@@ -0,0 +1,10 @@
+# CLOSURE_BRIEF - slice-01 Provider stream hooks
+
+## Summary
+
+Pending implementation.
+
+## Validation
+
+- [ ] `node --test tests/lib/ai-providers.test.js`
+- [ ] `git diff --check`

package/specs/quiver-v44-provider-live-output-tui-lite/slices/slice-01-provider-stream-hooks/EXECUTION_BRIEF.md

@@ -0,0 +1,24 @@
+# EXECUTION_BRIEF - slice-01 Provider stream hooks
+
+## Context
+
+`runProvider` currently captures stdout/stderr and returns them after provider completion. TUI-lite needs optional live observation while preserving this contract.
+
+## Objective
+
+Add opt-in provider stream/status callbacks with no behavior change for existing callers.
+
+## Acceptance Criteria
+
+- Existing provider runner behavior remains unchanged when callbacks are absent.
+- Optional callbacks can observe stdout and stderr chunks.
+- Provider result shape and accumulated stdout/stderr remain stable.
+- Callback data is safe for display paths and does not bypass redaction.
+- Timeout, preflight, spawn error, missing provider CLI, and invalid model behavior remain intact.
+
+## Completion Checklist
+
+- [ ] Provider runner callbacks implemented.
+- [ ] Default behavior regression tests pass.
+- [ ] Callback behavior tests added.
+- [ ] No renderer or command UX behavior added in this slice.

package/specs/quiver-v44-provider-live-output-tui-lite/slices/slice-01-provider-stream-hooks/slice.json

@@ -0,0 +1,65 @@
+{
+  "slice_id": "slice-01-provider-stream-hooks",
+  "ticket": "QUIVER-44-01",
+  "type": "feature",
+  "title": "Provider stream hooks",
+  "objective": "Add optional provider output callbacks without changing default provider execution behavior.",
+  "description": "Extends provider runner internals so verbose TTY flows can observe stdout, stderr, and status while existing callers still receive the same accumulated provider result.",
+  "git": {
+    "branch_type": "feature",
+    "base_branch": "main",
+    "branch_slug": "v44-provider-stream-hooks",
+    "branch_name": "feature/QUIVER-44-01-v44-provider-stream-hooks"
+  },
+  "files": [
+    "src/create-quiver/lib/ai/providers.js",
+    "tests/lib/ai-providers.test.js"
+  ],
+  "expected_read_paths": [
+    "src/create-quiver/lib/ai/providers.js",
+    "src/create-quiver/lib/evidence.js",
+    "src/create-quiver/lib/ai/artifacts.js",
+    "tests/lib/ai-providers.test.js",
+    "docs/CLI_UX_GUIDE.md"
+  ],
+  "allowed_write_paths": [
+    "src/create-quiver/lib/ai/providers.js",
+    "tests/lib/ai-providers.test.js",
+    "specs/quiver-v44-provider-live-output-tui-lite/**"
+  ],
+  "depends_on": [
+    "slice-00-tui-lite-contract-foundation"
+  ],
+  "parallel_safe": "after_dependencies",
+  "parallel_safe_reason": "Provider hooks are foundational for renderer work and should land before command integration.",
+  "must": [
+    "Add optional callbacks for stdout, stderr, and provider status.",
+    "Preserve existing runProvider return shape and stdout/stderr accumulation.",
+    "Keep callbacks opt-in and safe when absent.",
+    "Redact chunks before they leave provider internals for human display paths.",
+    "Preserve timeout, preflight, prompt transport, and error behavior."
+  ],
+  "not_included": [
+    "TUI renderer implementation.",
+    "Command parser changes beyond what is strictly needed for provider tests.",
+    "Changing provider CLI invocation semantics."
+  ],
+  "acceptance": [
+    "Existing provider tests pass without callback options.",
+    "Callback tests receive stdout and stderr chunks in order.",
+    "Provider result still contains accumulated redacted stdout/stderr.",
+    "Provider failure and timeout paths still surface actionable errors.",
+    "No provider output is printed directly by this layer."
+  ],
+  "tests": [
+    "node --test tests/lib/ai-providers.test.js",
+    "git diff --check"
+  ],
+  "validation_hints": [
+    "Use fake spawn fixtures to avoid live provider CLIs.",
+    "Assert callbacks do not change final stdout/stderr."
+  ],
+  "estimated_hours": 4,
+  "status": "planned",
+  "blocked_reason": null
+}

package/specs/quiver-v44-provider-live-output-tui-lite/slices/slice-02-live-output-renderer/CLOSURE_BRIEF.md

@@ -0,0 +1,10 @@
+# CLOSURE_BRIEF - slice-02 Live output renderer
+
+## Summary
+
+Pending implementation.
+
+## Validation
+
+- [ ] `node --test tests/lib/cli-ux.test.js tests/lib/provider-live-output.test.js`
+- [ ] `git diff --check`

package/specs/quiver-v44-provider-live-output-tui-lite/slices/slice-02-live-output-renderer/EXECUTION_BRIEF.md

@@ -0,0 +1,24 @@
+# EXECUTION_BRIEF - slice-02 Live output renderer
+
+## Context
+
+Quiver already has shared UX helpers and a theme. The TUI-lite output should reuse that infrastructure instead of creating command-specific formatting.
+
+## Objective
+
+Create a reusable provider live output renderer with safe formatting, redaction, truncation, and fallbacks.
+
+## Acceptance Criteria
+
+- Human TTY verbose mode can render agent metadata, progress, provider output, elapsed time, and next step.
+- JSON/no-TTY/CI modes remain clean.
+- `--no-color`, `NO_COLOR`, `TERM=dumb`, and ASCII locales remain readable.
+- Provider output display is redacted and truncated.
+- Renderer does not require full-screen terminal control or new heavyweight dependencies.
+
+## Completion Checklist
+
+- [ ] Shared renderer added.
+- [ ] Theme/fallback behavior covered.
+- [ ] Redaction/truncation covered.
+- [ ] Renderer tests added.

package/specs/quiver-v44-provider-live-output-tui-lite/slices/slice-02-live-output-renderer/slice.json

@@ -0,0 +1,70 @@
+{
+  "slice_id": "slice-02-live-output-renderer",
+  "ticket": "QUIVER-44-02",
+  "type": "feature",
+  "title": "Live output renderer",
+  "objective": "Create a reusable TUI-lite provider output renderer for human TTY verbose mode.",
+  "description": "Adds a shared renderer that presents agent metadata, progress, provider output, elapsed time, heartbeat, and next steps using Quiver's theme and safe fallbacks.",
+  "git": {
+    "branch_type": "feature",
+    "base_branch": "main",
+    "branch_slug": "v44-live-output-renderer",
+    "branch_name": "feature/QUIVER-44-02-v44-live-output-renderer"
+  },
+  "files": [
+    "src/create-quiver/lib/cli/provider-live-output.js",
+    "src/create-quiver/lib/cli/ux.js",
+    "tests/lib/cli-ux.test.js",
+    "tests/lib/provider-live-output.test.js"
+  ],
+  "expected_read_paths": [
+    "src/create-quiver/lib/cli/ux.js",
+    "src/create-quiver/lib/cli/theme.js",
+    "src/create-quiver/lib/evidence.js",
+    "tests/lib/cli-ux.test.js",
+    "docs/CLI_UX_GUIDE.md"
+  ],
+  "allowed_write_paths": [
+    "src/create-quiver/lib/cli/provider-live-output.js",
+    "src/create-quiver/lib/cli/ux.js",
+    "tests/lib/cli-ux.test.js",
+    "tests/lib/provider-live-output.test.js",
+    "specs/quiver-v44-provider-live-output-tui-lite/**"
+  ],
+  "depends_on": [
+    "slice-01-provider-stream-hooks"
+  ],
+  "parallel_safe": "after_dependencies",
+  "parallel_safe_reason": "Renderer depends on callback contract but does not yet modify command execution.",
+  "must": [
+    "Render a TUI-lite append-only view for human TTY verbose mode.",
+    "Use Quiver theme symbols and colors.",
+    "Support no-color, dumb terminal, ASCII, and no-TTY fallbacks.",
+    "Redact and truncate displayed provider output.",
+    "Expose a heartbeat/status update API for long silent provider runs.",
+    "Avoid full-screen terminal control and heavyweight dependencies."
+  ],
+  "not_included": [
+    "Provider runner changes.",
+    "Command integration.",
+    "Full-screen TUI or keyboard navigation."
+  ],
+  "acceptance": [
+    "Renderer outputs sections for agent, progress, provider output, and next step.",
+    "Renderer suppresses decorative output in JSON/no-TTY/CI modes.",
+    "No-color and dumb terminal output remain readable.",
+    "Long output is truncated with an explicit marker.",
+    "Secret-like values are redacted before display."
+  ],
+  "tests": [
+    "node --test tests/lib/cli-ux.test.js tests/lib/provider-live-output.test.js",
+    "git diff --check"
+  ],
+  "validation_hints": [
+    "Use deterministic writer injection for snapshot-like assertions.",
+    "Avoid asserting transient spinner frames."
+  ],
+  "estimated_hours": 5,
+  "status": "planned",
+  "blocked_reason": null
+}

package/specs/quiver-v44-provider-live-output-tui-lite/slices/slice-03-prepare-context-integration/CLOSURE_BRIEF.md

@@ -0,0 +1,10 @@
+# CLOSURE_BRIEF - slice-03 Prepare-context integration
+
+## Summary
+
+Pending implementation.
+
+## Validation
+
+- [ ] `node --test tests/commands/ai-prepare-context-planner.test.js`
+- [ ] `git diff --check`

package/specs/quiver-v44-provider-live-output-tui-lite/slices/slice-03-prepare-context-integration/EXECUTION_BRIEF.md

@@ -0,0 +1,25 @@
+# EXECUTION_BRIEF - slice-03 Prepare-context integration
+
+## Context
+
+`ai prepare-context --with-planner` is the first target because it exposed the spinner-only opacity during dogfooding.
+
+## Objective
+
+Wire `--verbose` TUI-lite output into planner-assisted `ai prepare-context` without changing default behavior.
+
+## Acceptance Criteria
+
+- `--verbose` is parsed and passed to `runPrepareContextWithPlanner`.
+- Human TTY verbose mode shows the TUI-lite renderer.
+- Non-verbose mode keeps the existing progress checks and spinner.
+- Dry-run, print-prompt, JSON, CI, and no-TTY modes stay clean.
+- Review/interactive gates still run before docs writes.
+- Provider result parsing and docs-only validation remain unchanged.
+
+## Completion Checklist
+
+- [ ] Parser plumbing added.
+- [ ] Prepare-context integration added.
+- [ ] Success/failure tests added.
+- [ ] Automation-safe modes verified.