create-quiver 0.6.0 → 0.8.0

package/specs/quiver-v18-slice-orchestration/STATUS.md

@@ -0,0 +1,33 @@
+# Quiver v0.18 Spec Status
+
+**Spec:** quiver-v18-slice-orchestration
+**Last updated:** 2026-04-24
+
+Slice numbering is local to this spec. The first slice is `slice-01`.
+
+## Status
+
+| Slice | Title | Status | PR | Estimated hours | Actual hours |
+|-------|-------|--------|----|-----------------|--------------|
+| slice-01 | `quiver:plan` Command | Completed | https://github.com/FabriJuncal/quiver/pull/49 | 5 | 5 |
+| slice-02 | `quiver:graph` MVP Tree | Completed | https://github.com/FabriJuncal/quiver/pull/50 | 4 | 4 |
+| slice-03 | `quiver:graph` Extended Formats | Completed | https://github.com/FabriJuncal/quiver/pull/51 | 2 | 2 |
+| slice-04 | `quiver:next` Command | Completed | https://github.com/FabriJuncal/quiver/pull/52 | 3 | 4 |
+
+## Progress
+
+- Completed slices: 4 / 4
+- Estimated hours: 14
+- Actual hours: 15
+
+## Blockers
+
+| Slice | Blocker | Since | Action needed |
+|-------|---------|-------|---------------|
+| - | - | - | - |
+
+## Dependencies
+
+- All slices depend on `quiver-v17-orchestration-foundation/slice-02-slice-graph-library`
+- slice-03 depends on slice-02 (extends graph output with new formats)
+- slice-04 depends on slice-01 (reuses plan ordering for "next")

package/specs/quiver-v18-slice-orchestration/slices/slice-01-plan-command/slice.json

@@ -0,0 +1,79 @@
+{
+  "slice_id": "slice-01-plan-command",
+  "ticket": "QUIVER-01",
+  "type": "feat",
+  "title": "`quiver:plan` Command",
+  "objective": "Ship `npx create-quiver plan` and `quiver:plan` that print the sequential execution order of all pending slices, the critical path, and the total hours, with `--json` for tooling integration.",
+  "description": "The plan command answers \"what do I work on next, and in what order?\" across every spec in the repo. It reads all `slice.json` files, drops completed and skipped slices, builds the dependency graph using the v17 library, topologically sorts the remaining nodes, and prints the result. The command is read-only, deterministic, and cross-platform.",
+  "git": {
+    "branch_type": "feature",
+    "base_branch": "main",
+    "branch_slug": "plan-command",
+    "branch_name": "feature/QUIVER-01-plan-command"
+  },
+  "must": [
+    "Create `src/create-quiver/commands/plan.js` that wires up `readAllSlices`, `inferDependencies`, `buildGraph`, and `topoSort` from the v17 library",
+    "Implement critical path detection by walking the longest-hours chain in the DAG",
+    "Implement `--spec <slug>`, `--only-ready`, and `--json` flags",
+    "Register `plan` in `bin/create-quiver.js` and add `quiver:plan` to `package.json`",
+    "Print human output with ASCII by default, Unicode only when `process.env.LANG` includes `UTF-8` or `--unicode` is passed",
+    "Respect `NO_COLOR` and `!isTTY` when deciding whether to emit colors",
+    "Create `docs/examples/plan.md` with input and representative output",
+    "Add a `COMMANDS.md` row for plan",
+    "Update `README.md` npm scripts list and `README_FOR_AI.md` reading order if relevant",
+    "Add a `CHANGELOG.md` entry"
+  ],
+  "not_included": [
+    "Auto-starting slices (handled by `next --auto-start`)",
+    "Rendering a graph tree (handled in slice-02)",
+    "Status dashboards (handled in v19)"
+  ],
+  "acceptance": [
+    "`npx create-quiver plan` returns exit 0 and prints a non-empty plan in the Quiver repo",
+    "`npx create-quiver plan --json` produces valid JSON with `plan`, `critical_path`, and `total_hours` fields",
+    "`npx create-quiver plan --only-ready` returns only slices with no pending predecessors",
+    "`npx create-quiver plan --spec quiver-v14-tiered-context-pack` returns only that spec's slices",
+    "Introducing a cycle in a test fixture causes exit code 1 with a message naming the cycle",
+    "Running under `CI=true TERM=dumb NO_COLOR=1` produces ASCII output without color codes",
+    "`docs/examples/plan.md` exists with a real example block",
+    "`docs/COMMANDS.md` has a row naming `plan` with OS support listed"
+  ],
+  "files": [
+    "src/create-quiver/commands/plan.js",
+    "bin/create-quiver.js",
+    "package.json",
+    "docs/examples/plan.md",
+    "docs/COMMANDS.md",
+    "README.md",
+    "README_FOR_AI.md",
+    "CHANGELOG.md",
+    "tests/commands/plan.test.js",
+    "specs/quiver-v18-slice-orchestration/slices/slice-01-plan-command/slice.json"
+  ],
+  "tests": [
+    "node --test tests/commands/plan.test.js",
+    "node bin/create-quiver.js plan --json > /tmp/quiver-plan.json",
+    "node -e \"const p=require('/tmp/quiver-plan.json'); if(!Array.isArray(p.plan)||typeof p.total_hours!=='number') process.exit(1)\"",
+    "git diff --check"
+  ],
+  "documentation": [
+    "docs/examples/plan.md",
+    "docs/COMMANDS.md",
+    "README.md",
+    "README_FOR_AI.md",
+    "CHANGELOG.md"
+  ],
+  "dependencies": ["quiver-v17-orchestration-foundation/slice-02-slice-graph-library"],
+  "assumptions": [
+    "`readAllSlices` is fast enough to run on every invocation without caching",
+    "A single critical-path metric (longest hours chain) is sufficient for now",
+    "Humans reading the default output prefer ASCII over Unicode box-drawing by default"
+  ],
+  "estimated_hours": 5,
+  "actual_hours": 5,
+  "status": "completed",
+  "blocked_reason": null,
+  "ready_at": null,
+  "started_at": null,
+  "completed_at": null
+}

package/specs/quiver-v18-slice-orchestration/slices/slice-02-graph-mvp-tree/slice.json

@@ -0,0 +1,75 @@
+{
+  "slice_id": "slice-02-graph-mvp-tree",
+  "ticket": "QUIVER-02",
+  "type": "feat",
+  "title": "`quiver:graph` MVP Tree",
+  "objective": "Ship `npx create-quiver graph --format tree` and `quiver:graph` that print the dependency tree of pending slices, grouped by parallel level, with optional `--show-conflicts` and `--level <n>` flags.",
+  "description": "Given the library returns levels and conflict groups, this slice focuses on rendering a readable ASCII tree that makes parallel-safe lots obvious. Mermaid and DOT formats are deferred to slice-03; the MVP keeps the surface small. Conflict markers use `⚠` with UTF-8 locale and a plain `!` as fallback.",
+  "git": {
+    "branch_type": "feature",
+    "base_branch": "main",
+    "branch_slug": "graph-mvp-tree",
+    "branch_name": "feature/QUIVER-02-graph-mvp-tree"
+  },
+  "must": [
+    "Create `src/create-quiver/commands/graph.js` with a `--format tree` default",
+    "Render one section per topological level, with slices that can run in parallel listed together",
+    "Mark file conflicts between same-level slices with a conflict symbol and a brief list of shared paths when `--show-conflicts` is set",
+    "Implement `--level <n>` to focus on a single level",
+    "Implement `--json` to emit `{ levels: Slice[][], conflicts: ConflictGroup[] }`",
+    "Register `graph` in `bin/create-quiver.js` and add `quiver:graph` to `package.json`",
+    "Create `docs/examples/graph.md` with input and representative ASCII output",
+    "Add a `docs/COMMANDS.md` row and update `README.md` npm scripts list",
+    "Add a `CHANGELOG.md` entry"
+  ],
+  "not_included": [
+    "Mermaid and DOT formats (handled in slice-03)",
+    "Editing or starting any slice (read-only)",
+    "Rendering file contents; only slice IDs, titles, hours, and shared paths"
+  ],
+  "acceptance": [
+    "`npx create-quiver graph` prints a tree grouped by level with counts of parallel lots",
+    "`npx create-quiver graph --show-conflicts` marks slices that intersect on `files[]`",
+    "`npx create-quiver graph --level 0` prints only the first level",
+    "`npx create-quiver graph --json` produces valid JSON with `levels` and `conflicts` arrays",
+    "Output is ASCII by default; with `LANG=en_US.UTF-8` or `--unicode`, Unicode box-drawing is used",
+    "`docs/examples/graph.md` exists with a real example"
+  ],
+  "files": [
+    "src/create-quiver/commands/graph.js",
+    "src/create-quiver/lib/renderers/tree.js",
+    "bin/create-quiver.js",
+    "package.json",
+    "docs/examples/graph.md",
+    "docs/COMMANDS.md",
+    "README.md",
+    "CHANGELOG.md",
+    "tests/commands/graph.test.js",
+    "specs/quiver-v18-slice-orchestration/slices/slice-02-graph-mvp-tree/slice.json"
+  ],
+  "tests": [
+    "node --test tests/commands/graph.test.js",
+    "node bin/create-quiver.js graph --json > /tmp/quiver-graph.json",
+    "node -e \"const g=require('/tmp/quiver-graph.json'); if(!Array.isArray(g.levels)) process.exit(1)\"",
+    "git diff --check"
+  ],
+  "documentation": [
+    "docs/examples/graph.md",
+    "docs/COMMANDS.md",
+    "README.md",
+    "CHANGELOG.md"
+  ],
+  "dependencies": ["quiver-v17-orchestration-foundation/slice-02-slice-graph-library", "slice-01-plan-command"],
+  "assumptions": [
+    "Two slices on the same level that intersect on `files[]` are effectively serialized in practice; warning is enough, no hard block",
+    "ASCII tree is readable for repos with fewer than 50 pending slices; larger repos may justify paging later",
+    "Graphviz is not assumed to be installed"
+  ],
+  "estimated_hours": 4,
+  "actual_hours": 4,
+  "status": "completed",
+  "blocked_reason": null,
+  "ready_at": null,
+  "started_at": null,
+  "completed_at": null
+}

package/specs/quiver-v18-slice-orchestration/slices/slice-03-graph-extended-formats/slice.json

@@ -0,0 +1,70 @@
+{
+  "slice_id": "slice-03-graph-extended-formats",
+  "ticket": "QUIVER-03",
+  "type": "feat",
+  "title": "`quiver:graph` Extended Formats (Mermaid, DOT)",
+  "objective": "Extend `quiver:graph` with `--format mermaid` and `--format dot` so dependency graphs can be pasted into GitHub markdown (Mermaid) or rendered with Graphviz (DOT) for documentation and slide decks.",
+  "description": "Once the ASCII tree is working, adding machine-renderable formats is cheap: both are templated serializations of the same levels and conflicts data. Mermaid is the primary target for PR descriptions; DOT unlocks Graphviz pipelines and high-resolution exports. Neither format requires external binaries to be present; Graphviz is only needed by the end user if they want to render DOT.",
+  "git": {
+    "branch_type": "feature",
+    "base_branch": "main",
+    "branch_slug": "graph-extended-formats",
+    "branch_name": "feature/QUIVER-03-graph-extended-formats"
+  },
+  "must": [
+    "Add a Mermaid renderer at `src/create-quiver/lib/renderers/mermaid.js` producing a `flowchart TD` block",
+    "Add a DOT renderer at `src/create-quiver/lib/renderers/dot.js` producing valid `digraph` source",
+    "Wire both renderers to `quiver:graph --format mermaid` and `quiver:graph --format dot`",
+    "Update `docs/examples/graph.md` with sample Mermaid and DOT outputs and a note about GitHub's Mermaid support",
+    "Add a `docs/COMMANDS.md` note covering the new formats",
+    "Add a `CHANGELOG.md` entry"
+  ],
+  "not_included": [
+    "Auto-rendering DOT to PNG (Graphviz binary not assumed)",
+    "Interactive web visualizer",
+    "Per-spec subgraphs in Mermaid (flat layout is enough for now)"
+  ],
+  "acceptance": [
+    "`npx create-quiver graph --format mermaid` prints a valid `flowchart TD` block starting with ```` ```mermaid ```` fence",
+    "Pasting the output into a GitHub markdown preview renders the graph",
+    "`npx create-quiver graph --format dot` prints valid DOT source starting with `digraph`",
+    "`echo $(node bin/create-quiver.js graph --format dot) | dot -Tsvg` produces SVG when Graphviz is installed (test runs conditionally)",
+    "`docs/examples/graph.md` shows both formats"
+  ],
+  "files": [
+    "src/create-quiver/commands/graph.js",
+    "src/create-quiver/lib/renderers/mermaid.js",
+    "src/create-quiver/lib/renderers/dot.js",
+    "docs/examples/graph.md",
+    "docs/COMMANDS.md",
+    "CHANGELOG.md",
+    "tests/lib/renderers/mermaid.test.js",
+    "tests/lib/renderers/dot.test.js",
+    "specs/quiver-v18-slice-orchestration/slices/slice-03-graph-extended-formats/slice.json"
+  ],
+  "tests": [
+    "node --test tests/lib/renderers/mermaid.test.js",
+    "node --test tests/lib/renderers/dot.test.js",
+    "node bin/create-quiver.js graph --format mermaid | head -n 1 | grep -q mermaid",
+    "node bin/create-quiver.js graph --format dot | head -n 1 | grep -q digraph",
+    "git diff --check"
+  ],
+  "documentation": [
+    "docs/examples/graph.md",
+    "docs/COMMANDS.md",
+    "CHANGELOG.md"
+  ],
+  "dependencies": ["slice-02-graph-mvp-tree"],
+  "assumptions": [
+    "GitHub continues to render Mermaid in markdown",
+    "DOT identifiers sanitized from slice IDs are stable enough not to collide",
+    "Users who want PNG/SVG have Graphviz installed locally; Quiver does not bundle it"
+  ],
+  "estimated_hours": 2,
+  "actual_hours": 2,
+  "status": "completed",
+  "blocked_reason": null,
+  "ready_at": null,
+  "started_at": null,
+  "completed_at": "2026-04-24T00:00:00Z"
+}

package/specs/quiver-v18-slice-orchestration/slices/slice-04-next-command/slice.json

@@ -0,0 +1,73 @@
+{
+  "slice_id": "slice-04-next-command",
+  "ticket": "QUIVER-04",
+  "type": "feat",
+  "title": "`quiver:next` Command",
+  "objective": "Ship `npx create-quiver next` and `quiver:next` as the daily entry point that answers \"what do I work on right now?\" with an optional `--auto-start` shortcut behind an interactive confirmation.",
+  "description": "`quiver:next` prints the top-1 ready slice by default (the first node returned by `quiver:plan --only-ready`). With `--all-ready`, it lists the whole first level. With `--auto-start`, it prompts the user to confirm and then runs `start-slice` on the suggested slice; the prompt is mandatory on TTY and the command refuses to auto-start on a non-TTY to avoid surprises in CI.",
+  "git": {
+    "branch_type": "feature",
+    "base_branch": "main",
+    "branch_slug": "next-command",
+    "branch_name": "feature/QUIVER-04-next-command"
+  },
+  "must": [
+    "Create `src/create-quiver/commands/next.js` that reuses the plan ordering",
+    "Default output: print the top-1 slice plus the exact `start-slice` command to copy",
+    "Flag `--all-ready`: list every slice at the first unblocked level",
+    "Flag `--auto-start`: read a `y/N` prompt on TTY, run `start-slice` on `y`, refuse on non-TTY",
+    "Flag `--json`: emit `{ next: Slice | null, all_ready: Slice[] }`",
+    "Register `next` in `bin/create-quiver.js` and add `quiver:next` to `package.json`",
+    "Create `docs/examples/next.md` showing both read-only and `--auto-start` flows",
+    "Add a `docs/COMMANDS.md` row and update `README.md` npm scripts list",
+    "Add a `CHANGELOG.md` entry"
+  ],
+  "not_included": [
+    "Silent auto-start without confirmation",
+    "Auto-start on non-TTY environments",
+    "Automatic branch merging or PR creation after the slice is started"
+  ],
+  "acceptance": [
+    "`npx create-quiver next` prints a single slice and the exact `start-slice` command; running it twice returns the same slice",
+    "`npx create-quiver next --all-ready` prints every slice in level 0",
+    "`npx create-quiver next --auto-start` on a TTY prompts `Start slice X? [y/N]` and only proceeds on `y`",
+    "`npx create-quiver next --auto-start` on a non-TTY exits non-zero with a clear message and does not start anything",
+    "`--json` output is valid and parseable"
+  ],
+  "files": [
+    "src/create-quiver/commands/next.js",
+    "bin/create-quiver.js",
+    "package.json",
+    "docs/examples/next.md",
+    "docs/COMMANDS.md",
+    "README.md",
+    "CHANGELOG.md",
+    "tests/commands/next.test.js",
+    "specs/quiver-v18-slice-orchestration/slices/slice-04-next-command/slice.json"
+  ],
+  "tests": [
+    "node --test tests/commands/next.test.js",
+    "node bin/create-quiver.js next --json > /tmp/quiver-next.json",
+    "node -e \"const n=require('/tmp/quiver-next.json'); if(!('next' in n)) process.exit(1)\"",
+    "git diff --check"
+  ],
+  "documentation": [
+    "docs/examples/next.md",
+    "docs/COMMANDS.md",
+    "README.md",
+    "CHANGELOG.md"
+  ],
+  "dependencies": ["slice-01-plan-command"],
+  "assumptions": [
+    "Users accept that `next` is a suggestion and not a commitment",
+    "Interactive TTY prompts are acceptable in CLI tools for destructive actions",
+    "`start-slice` already handles worktree creation and is idempotent enough to tolerate re-runs"
+  ],
+  "estimated_hours": 3,
+  "actual_hours": 4,
+  "status": "completed",
+  "blocked_reason": null,
+  "ready_at": null,
+  "started_at": "2026-04-24T00:00:00Z",
+  "completed_at": "2026-04-24T00:00:00Z"
+}

package/specs/quiver-v18-stabilization/EVIDENCE_REPORT.md

@@ -0,0 +1,26 @@
+# Quiver v0.18 Stabilization — Evidence Report
+
+**Spec:** quiver-v18-stabilization
+**Date:** 2026-05-12
+**Status:** Completed
+
+## Summary
+
+3/3 slices completados. `quiver:plan` exit 0 en el propio repo, ROADMAP sin `(unreleased)`, drafts branch publicada en origin con SHA verificado.
+
+## Slice Evidence
+
+| Slice | Status | Evidence |
+|-------|--------|----------|
+| slice-01 | Completed | PR #54 merged 2026-05-12. `node --test tests/**/*.test.js` → 32/32 pass. `node bin/create-quiver.js plan` → exit 0, 8 slices, 40h. `plan --json` → valid JSON con `plan`, `critical_path`, `total_hours`. Commit: `11c821e`. |
+| slice-02 | Completed | PR #56 merged 2026-05-12. `grep 'unreleased' ROADMAP.md` → sin match. `grep 'v0.6 (shipped)' ROADMAP.md` → match. ~29 branches merged eliminados + 2 backups + 4 worktrees stale prunados. |
+| slice-03 | Completed | Push directo 2026-05-12. SHA local `13eab96e4d0a9e34ba1ea1add3b969603eda255c` = SHA remoto. Sin PR (rama de referencia, no candidata a merge). |
+
+## Final Evidence
+
+- `npx create-quiver plan` → exit 0, 8 slices, 40h. ✓
+- `npx create-quiver plan --json` → JSON válido con `plan`, `critical_path`, `total_hours`. ✓
+- `git branch | grep backup` → sin output. ✓
+- `ROADMAP.md` → `v0.6 (shipped)`, sin `(unreleased)`. ✓
+- `git ls-remote origin drafts/v19-v22-orchestration-followups` → `13eab96e4d0a9e34ba1ea1add3b969603eda255c`. ✓
+- `node --test tests/**/*.test.js` → 32/32 pass. ✓

package/specs/quiver-v18-stabilization/SPEC.md

@@ -0,0 +1,62 @@
+# Quiver v0.18 Stabilization
+
+**Date:** 2026-05-12
+**Status:** Ready
+
+Slice numbering resets here: this spec starts at `slice-01` and does not continue any previous spec's numbering.
+
+## Objective
+
+Close the three loose ends left after v18 merged: fix a crash in `slice-graph.js` that blocks the v18 validation checkpoint, clean up stale local branches and an unclosed ROADMAP entry, and publish the parked draft specs to origin once the checkpoint passes.
+
+## Context
+
+v17 and v18 shipped all planned slices and closed their PRs. During the post-merge smoke test, `npx create-quiver plan` was found to crash on the Quiver repo itself with `SliceGraphError: Missing dependency reference(s)`. The root cause is a one-line normalization bug in `slice-graph.js`: slices with the legacy `"dependencies"` field using bare spec names (e.g. `"quiver-v01"`) get expanded to an invalid ref that the graph validator then rejects. The fix is minimal and non-breaking.
+
+The remaining two slices are housekeeping: one commit to close the `v0.6 (unreleased)` entry in ROADMAP and delete stale local branches; one `git push` to publish the parked v19–v22 draft specs once the v18 human checkpoint is confirmed.
+
+## Scope
+
+### Included
+
+- Fix `normalizeDependencyRef` in `src/create-quiver/lib/slice-graph.js` to silently drop legacy spec-name bare deps.
+- Add a test case covering the legacy format.
+- Close `v0.6 (unreleased)` in `ROADMAP.md`.
+- Delete local stale branches (merged + backup branches).
+- Publish `drafts/v19-v22-orchestration-followups` to origin (gated by human checkpoint).
+
+### Excluded
+
+- Any change to the output or behavior of `plan`, `graph`, or `next` beyond the crash fix.
+- Changes to slice.json schema or validation rules beyond the legacy-dep case.
+- Version bump — this spec does not increment the package version.
+- Any v19 work — that starts only after the checkpoint of this spec passes.
+
+## Slices
+
+| Slice | Title | Status | Estimated hours |
+|-------|-------|--------|-----------------|
+| slice-01 | Fix legacy dependency resolution in `slice-graph.js` | Ready | 0.5 |
+| slice-02 | Close v0.6 in ROADMAP and clean stale branches | Ready | 0.3 |
+| [GATE] | Human checkpoint: v18 real-use validation | — | 1–2 weeks |
+| slice-03 | Publish `drafts/v19-v22-orchestration-followups` to origin | Blocked by gate | 0.1 |
+
+## Gate — Human Checkpoint
+
+slice-03 is blocked until the maintainer:
+1. Uses `quiver:plan`, `quiver:graph`, and `quiver:next` in at least one real work cycle.
+2. Records an observation in `specs/quiver-v18-slice-orchestration/EVIDENCE_REPORT.md`.
+3. Confirms the checkpoint explicitly before delegating slice-03.
+
+## Definition of Done
+
+- `npx create-quiver plan` exits 0 on the Quiver repo.
+- `npx create-quiver plan --json` returns valid JSON.
+- `ROADMAP.md` no longer has `v0.6 (unreleased)`.
+- `git branch` has no backup or already-merged stale branches.
+- `origin/drafts/v19-v22-orchestration-followups` exists and matches local SHA.
+- All existing tests pass.
+
+## Validation Checkpoint
+
+This spec's checkpoint passes when all three slices are merged/executed and the human gate is confirmed. There is no usage-time requirement beyond the gate — this is stabilization, not a new feature.

package/specs/quiver-v18-stabilization/STATUS.md

@@ -0,0 +1,30 @@
+# Quiver v0.18 Stabilization — Status
+
+**Spec:** quiver-v18-stabilization
+**Last updated:** 2026-05-12
+
+Slice numbering is local to this spec. The first slice is `slice-01`.
+
+## Status
+
+| Slice | Title | Status | PR | Estimated hours | Actual hours |
+|-------|-------|--------|----|-----------------|--------------|
+| slice-01 | Fix legacy dependency resolution in `slice-graph.js` | Completed | #54 | 0.5 | 0.5 |
+| slice-02 | Close v0.6 in ROADMAP and clean stale branches | Completed | #56 | 0.3 | 0.1 |
+| slice-03 | Publish `drafts/v19-v22-orchestration-followups` | Completed | — | 0.1 | 0.1 |
+
+## Progress
+
+- Completed slices: 3 / 3
+- Estimated hours: 0.9
+- Actual hours: 0.7
+
+## Blockers
+
+_None — spec complete._
+
+## Dependencies
+
+- slice-01 has no dependencies (can run immediately)
+- slice-02 has no dependencies (can run immediately, parallel to slice-01)
+- slice-03 depends on human gate confirmation — not on slice-01 or slice-02 in code, but run last

package/specs/quiver-v18-stabilization/slices/slice-01-fix-legacy-dependency-resolution/CLOSURE_BRIEF.md

@@ -0,0 +1,29 @@
+# CLOSURE BRIEF — slice-01: Fix legacy dependency resolution
+
+**Spec:** quiver-v18-stabilization
+**Slice:** slice-01-fix-legacy-dependency-resolution
+
+---
+
+## Checklist antes de abrir el PR
+
+- [ ] `node --test tests/` → exit 0, sin tests en rojo.
+- [ ] `node bin/create-quiver.js plan` → exit 0, imprime el plan del repo.
+- [ ] `node bin/create-quiver.js plan --json` → JSON válido con `plan`, `critical_path`, `total_hours`.
+- [ ] `git diff --stat` muestra exactamente dos archivos: `src/create-quiver/lib/slice-graph.js` y el archivo de test.
+- [ ] El test nuevo cubre: (a) legacy bare dep no tira error, (b) nuevo formato `depends_on` sigue funcionando.
+- [ ] El commit tiene un mensaje que explica el *por qué* (ver EXECUTION_BRIEF).
+
+## Checklist del PR
+
+- [ ] Branch: `bugfix/QUIVER-01-fix-legacy-dependency-resolution` → `main`.
+- [ ] Título del PR: `bugfix(QUIVER-01): ignore legacy bare spec deps in normalizeDependencyRef`.
+- [ ] Body del PR sigue las secciones del `docs/GITFLOW_PR_GUIDE.md.template`: Title, Summary, Scope, Files, How to Test, Evidence, Rollback, Risks / Notes.
+- [ ] En "Evidence": incluir la salida de `npx create-quiver plan` (primeras líneas) y `npx create-quiver plan --json | head`.
+- [ ] En "Rollback": `git revert HEAD --no-edit` es suficiente.
+- [ ] En "Risks / Notes": mencionar que el drop silencioso es intencional y que los slices legacy ya están completados.
+
+## Post-merge
+
+- [ ] Actualizar `specs/quiver-v18-stabilization/STATUS.md`: slice-01 → `Completed`, agregar número de PR y `actual_hours`.
+- [ ] Actualizar `specs/quiver-v18-stabilization/EVIDENCE_REPORT.md`: registrar evidencia del slice.

package/specs/quiver-v18-stabilization/slices/slice-01-fix-legacy-dependency-resolution/EXECUTION_BRIEF.md

@@ -0,0 +1,134 @@
+# EXECUTION BRIEF — slice-01: Fix legacy dependency resolution
+
+**Spec:** quiver-v18-stabilization
+**Slice:** slice-01-fix-legacy-dependency-resolution
+**Estimated time:** 30 min
+**Branch:** `bugfix/QUIVER-01-fix-legacy-dependency-resolution` from `main`
+
+---
+
+## Contexto
+
+`npx create-quiver plan` crashea en el repo de Quiver con:
+
+```
+SliceGraphError: Missing dependency reference(s):
+quiver-v02-bootstrap-hardening/slice-01-path-remote-safety -> quiver-v02-bootstrap-hardening/quiver-v01
+```
+
+**Causa:** `normalizeDependencyRef` en `src/create-quiver/lib/slice-graph.js` (línea ~65) toma el valor bare `"quiver-v01"` del campo legacy `"dependencies"`, no encuentra `/`, y devuelve `"quiver-v02-bootstrap-hardening/quiver-v01"`. Ese ref no existe en el mapa de slices → `buildGraph` tira error.
+
+---
+
+## El único archivo que tocás
+
+```
+src/create-quiver/lib/slice-graph.js
+```
+
+---
+
+## Cambio exacto
+
+Localizá la función `normalizeDependencyRef`. Actualmente luce así:
+
+```js
+function normalizeDependencyRef(slice, dependency) {
+  const dep = String(dependency || '').trim();
+  if (!dep) {
+    return null;
+  }
+
+  if (dep.includes('/')) {
+    return dep;
+  }
+
+  if (!slice || !slice.specSlug) {
+    return dep;
+  }
+
+  return `${slice.specSlug}/${dep}`;
+}
+```
+
+Agregá una sola guarda antes del `return` final:
+
+```js
+function normalizeDependencyRef(slice, dependency) {
+  const dep = String(dependency || '').trim();
+  if (!dep) {
+    return null;
+  }
+
+  if (dep.includes('/')) {
+    return dep;
+  }
+
+  if (!slice || !slice.specSlug) {
+    return dep;
+  }
+
+  // Legacy format: bare spec names (no 'slice-' prefix) are spec-level deps already
+  // satisfied by definition. Return null so they are filtered and not validated.
+  if (!dep.startsWith('slice-')) {
+    return null;
+  }
+
+  return `${slice.specSlug}/${dep}`;
+}
+```
+
+Eso es todo el cambio funcional.
+
+---
+
+## Test a agregar
+
+Ubicá `tests/lib/slice-graph.test.js` (o el archivo de test existente para slice-graph). Agregá un caso que cubra:
+
+1. Un slice con `"dependencies": ["quiver-v01"]` (formato legacy bare) no tira error en `buildGraph` y no produce aristas para ese dep.
+2. Un slice con `"depends_on": ["other-spec/slice-01-foo"]` sigue produciendo la arista correcta (regresión).
+
+Seguí el estilo de los tests existentes en ese archivo.
+
+---
+
+## Verificación antes de commitear
+
+```bash
+# 1. Todos los tests pasan
+node --test tests/
+
+# 2. El comando ya no crashea
+node bin/create-quiver.js plan
+
+# 3. JSON válido
+node bin/create-quiver.js plan --json | node -e \
+  "const d=JSON.parse(require('fs').readFileSync('/dev/stdin','utf8')); \
+   if(!Array.isArray(d.plan)||typeof d.total_hours!=='number') process.exit(1); \
+   console.log('ok:', d.plan.length, 'slices')"
+
+# 4. Diff limpio — solo los dos archivos esperados
+git diff --stat HEAD
+```
+
+---
+
+## Restricciones
+
+- **No** toques `buildGraph`, `inferDependencies`, ni ninguna otra función.
+- **No** agregues warnings ni logs para los deps descartados — el drop es silencioso.
+- **No** edites ningún `slice.json` de specs antiguas.
+- **No** cambies el comportamiento del nuevo formato `"depends_on"` con `spec/slice-id`.
+- **Un solo commit.** Mensaje sugerido:
+
+```
+bugfix(QUIVER-01): ignore legacy bare spec deps in normalizeDependencyRef
+
+Old slice.json files use "dependencies": ["quiver-vNN"] with bare spec names.
+normalizeDependencyRef was expanding them to "spec-slug/quiver-vNN" which
+doesn't match any slice, causing buildGraph to throw MISSING_DEPENDENCY.
+
+Guard: values without '/' that don't start with 'slice-' are spec-level refs
+already satisfied — return null so they are filtered before graph validation.
+```