create-quiver 0.7.0 → 0.8.0

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.
+```

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

@@ -0,0 +1,56 @@
+{
+  "slice_id": "slice-01-fix-legacy-dependency-resolution",
+  "ticket": "QUIVER-01",
+  "type": "bugfix",
+  "title": "Fix legacy dependency resolution in `slice-graph.js`",
+  "objective": "Make `npx create-quiver plan` exit 0 on the Quiver repo by ignoring bare spec-name values in the legacy `\"dependencies\"` field instead of crashing with `MISSING_DEPENDENCY`.",
+  "description": "Old slice.json files (v01–v16) declare cross-spec dependencies with bare spec names in a `\"dependencies\"` array, e.g. `[\"quiver-v01\"]`. The `normalizeDependencyRef` function in `slice-graph.js` expands bare values by prepending the current spec slug, producing refs like `quiver-v02-bootstrap-hardening/quiver-v01`. These refs do not match any slice key, causing `buildGraph` to throw `SliceGraphError: Missing dependency reference(s)`. The fix is one guard: if a bare value does not start with `slice-`, it is a spec-level legacy ref and must be returned as null (filtered). The new `\"depends_on\"` format with full `spec/slice-id` paths is unaffected.",
+  "git": {
+    "branch_type": "bugfix",
+    "base_branch": "main",
+    "branch_slug": "fix-legacy-dependency-resolution",
+    "branch_name": "bugfix/QUIVER-01-fix-legacy-dependency-resolution"
+  },
+  "must": [
+    "Add a guard in `normalizeDependencyRef` that returns `null` when the bare dependency value does not start with `slice-`",
+    "Leave all other logic in `normalizeDependencyRef` and `buildGraph` unchanged",
+    "Add a unit test that exercises the legacy `\"dependencies\": [\"quiver-vNN\"]` format and confirms no error is thrown and no edge is produced",
+    "Run `node --test tests/` and confirm all tests pass",
+    "Run `npx create-quiver plan` on the Quiver repo and confirm exit 0"
+  ],
+  "not_included": [
+    "Changing the output or behavior of `plan`, `graph`, or `next`",
+    "Migrating old slice.json files to the new `depends_on` format",
+    "Adding warnings or notices for legacy deps — silent drop is intentional",
+    "Any other file besides `src/create-quiver/lib/slice-graph.js` and `tests/`"
+  ],
+  "acceptance": [
+    "`npx create-quiver plan` exits 0 on the Quiver repo",
+    "`npx create-quiver plan --json` returns valid JSON with `plan`, `critical_path`, and `total_hours`",
+    "A test with `\"dependencies\": [\"quiver-v01\"]` does not throw and produces zero edges for that dep",
+    "A test with `\"depends_on\": [\"other-spec/slice-01-foo\"]` still produces the expected edge (regression)",
+    "`node --test tests/` exits 0"
+  ],
+  "files": [
+    "src/create-quiver/lib/slice-graph.js",
+    "tests/lib/slice-graph.test.js"
+  ],
+  "tests": [
+    "node --test tests/",
+    "node bin/create-quiver.js plan > /dev/null",
+    "node bin/create-quiver.js plan --json | node -e \"const d=JSON.parse(require('fs').readFileSync('/dev/stdin','utf8')); if(!Array.isArray(d.plan)) process.exit(1)\""
+  ],
+  "documentation": [],
+  "depends_on": [],
+  "assumptions": [
+    "All old slices using bare spec names in `\"dependencies\"` are already completed — silently dropping them causes no operational loss",
+    "No slice uses a bare dep that starts with `slice-` and refers to a different spec (would be an ambiguous format)"
+  ],
+  "estimated_hours": 0.5,
+  "actual_hours": 0.5,
+  "status": "completed",
+  "blocked_reason": null,
+  "ready_at": "2026-05-12T00:00:00Z",
+  "started_at": "2026-05-12T00:00:00Z",
+  "completed_at": "2026-05-12T00:00:00Z"
+}

package/specs/quiver-v18-stabilization/slices/slice-02-roadmap-and-branch-cleanup/CLOSURE_BRIEF.md

@@ -0,0 +1,29 @@
+# CLOSURE BRIEF — slice-02: ROADMAP v0.6 y limpieza de branches
+
+**Spec:** quiver-v18-stabilization
+**Slice:** slice-02-roadmap-and-branch-cleanup
+
+---
+
+## Checklist antes de abrir el PR
+
+- [ ] `grep 'unreleased' ROADMAP.md` → retorna vacío (exit 1 en grep, que es lo correcto).
+- [ ] `grep 'v0.6 (shipped)' ROADMAP.md` → retorna match.
+- [ ] `git branch | grep backup` → retorna vacío.
+- [ ] `git branch --merged main` → lista solo `main` (y `develop` si aplica). No hay branches de feature/docs/ci/test.
+- [ ] `git diff --stat HEAD` → solo `ROADMAP.md`.
+
+## Checklist del PR
+
+- [ ] Branch: `docs/QUIVER-02-close-v06-roadmap` → `main`.
+- [ ] Título: `docs(QUIVER-02): close v0.6 as shipped in ROADMAP`.
+- [ ] Body del PR sigue las secciones del `docs/GITFLOW_PR_GUIDE.md.template`.
+- [ ] En "Summary": mencionar ambas acciones (ROADMAP edit + branch cleanup local).
+- [ ] En "Scope": aclarar que la limpieza de branches es local-only, sin diff.
+- [ ] En "How to Test": `grep 'unreleased' ROADMAP.md` debe retornar sin match.
+- [ ] En "Rollback": `git revert HEAD --no-edit` restaura ROADMAP.md. Las branches borradas no se recuperan automáticamente (pero estaban mergeadas, sin trabajo único).
+
+## Post-merge
+
+- [ ] Actualizar `specs/quiver-v18-stabilization/STATUS.md`: slice-02 → `Completed`, agregar PR y `actual_hours`.
+- [ ] Actualizar `specs/quiver-v18-stabilization/EVIDENCE_REPORT.md`: registrar evidencia.

package/specs/quiver-v18-stabilization/slices/slice-02-roadmap-and-branch-cleanup/EXECUTION_BRIEF.md

@@ -0,0 +1,118 @@
+# EXECUTION BRIEF — slice-02: ROADMAP v0.6 y limpieza de branches
+
+**Spec:** quiver-v18-stabilization
+**Slice:** slice-02-roadmap-and-branch-cleanup
+**Estimated time:** 20 min
+**Branch:** `docs/QUIVER-02-close-v06-roadmap` from `main`
+
+---
+
+## Contexto
+
+Dos fuentes de ruido a eliminar:
+
+1. `ROADMAP.md` tiene `## v0.6 (unreleased)` aunque su scope (Node-native runtime, `quiver:*` scripts) fue absorbido y publicado en v0.7. Es una entrada engañosa.
+2. El repo tiene ~35 branches locales que son backup artifacts o branches de PRs ya mergeados a main. No bloquean nada, pero añaden ruido a `git branch`.
+
+**La limpieza de branches es local y no produce commit.** El único artefacto que va al PR es el cambio en `ROADMAP.md`.
+
+---
+
+## Parte A — Limpieza de branches (local, sin commit)
+
+### Paso 1: Listar branches ya merged a main
+
+```bash
+git branch --merged main
+```
+
+Deberías ver una lista larga. Anotá mentalmente las excepciones que NO debes borrar:
+- `main`
+- `develop`
+- `drafts/v19-v22-orchestration-followups`
+
+Todo lo demás en esa lista es candidato a eliminar.
+
+### Paso 2: Verificar que no hay trabajo no mergeado en esas branches
+
+```bash
+git branch --no-merged main
+```
+
+Si aparece algo inesperado que no sean las tres excepciones de arriba, revisalo antes de borrar. Si hay dudas, no borrés esa branch.
+
+### Paso 3: Borrar branches mergeadas (una por una o en lote)
+
+```bash
+# Borra todas las merged excepto main/develop/drafts de un golpe:
+git branch --merged main \
+  | grep -vE "^\*|^  main$|^  develop$|^  drafts/" \
+  | xargs git branch -d
+```
+
+### Paso 4: Borrar las dos branches de backup explícitamente
+
+```bash
+git branch -d backup/main-before-reconcile-20260512-094512
+git branch -d backup/main-before-reconcile-20260512-094712
+```
+
+### Paso 5: Verificar
+
+```bash
+git branch | wc -l   # debería ser significativamente menor que 35
+git branch | grep backup   # debe retornar vacío
+```
+
+---
+
+## Parte B — ROADMAP.md (sí va al PR)
+
+### El único cambio
+
+En `ROADMAP.md`, localizá la sección:
+
+```markdown
+## v0.6 (unreleased)
+
+- Cross-platform CI matrix (macOS, Linux, Windows) for Node-native runtime
+- Node-native generated project npm scripts (`quiver:*`)
+- Additive migration support for existing projects
+```
+
+Reemplazá el encabezado y agregá la nota:
+
+```markdown
+## v0.6 (shipped)
+
+> Scope absorbed into v0.7. Node-native runtime and `quiver:*` npm scripts
+> landed together with the token-efficient context pack work.
+
+- Cross-platform CI matrix (macOS, Linux, Windows) for Node-native runtime
+- Node-native generated project npm scripts (`quiver:*`)
+- Additive migration support for existing projects
+```
+
+Nada más. No toques ninguna otra sección.
+
+---
+
+## Commit y PR
+
+```bash
+git add ROADMAP.md
+git commit -m "docs(QUIVER-02): close v0.6 as shipped in ROADMAP"
+git push origin docs/QUIVER-02-close-v06-roadmap
+```
+
+Abrí el PR con `gh pr create` apuntando a `main`. El body del PR documenta ambas partes (aunque la limpieza de branches no tiene diff, mencionala en el Summary para trazabilidad).
+
+---
+
+## Restricciones
+
+- **No** toques ninguna otra sección de ROADMAP.md.
+- **No** borres branches en origin — solo local.
+- **No** borres `drafts/v19-v22-orchestration-followups` ni `develop` ni `main`.
+- **No** agregues nada a CHANGELOG.md — este cambio no es una feature.
+- El diff del PR debe mostrar solo `ROADMAP.md`.

package/specs/quiver-v18-stabilization/slices/slice-02-roadmap-and-branch-cleanup/slice.json

@@ -0,0 +1,57 @@
+{
+  "slice_id": "slice-02-roadmap-and-branch-cleanup",
+  "ticket": "QUIVER-02",
+  "type": "chore",
+  "title": "Close v0.6 in ROADMAP and clean stale local branches",
+  "objective": "Remove two sources of noise: the `v0.6 (unreleased)` entry in ROADMAP.md (the scope shipped in v0.7) and ~35 stale local branches that are already merged to main or are backup artifacts.",
+  "description": "v0.6 was never formally closed in ROADMAP.md even though its scope (Node-native runtime, `quiver:*` scripts) landed in v0.7. The entry currently reads `v0.6 (unreleased)`, which is misleading. Additionally, 35 local branches accumulate since earlier in development — two are explicit backup branches created today, the rest are feature/docs/ci branches whose PRs were merged to main months ago. The branch cleanup is a local-only operation with no commit. The ROADMAP fix is a one-line edit that goes in a docs PR.",
+  "git": {
+    "branch_type": "docs",
+    "base_branch": "main",
+    "branch_slug": "close-v06-roadmap",
+    "branch_name": "docs/QUIVER-02-close-v06-roadmap"
+  },
+  "must": [
+    "Edit `ROADMAP.md`: replace `## v0.6 (unreleased)` with `## v0.6 (shipped)` and add a one-line note: scope (Node-native runtime, `quiver:*` npm scripts) was absorbed and shipped as part of v0.7",
+    "Delete locally: `backup/main-before-reconcile-20260512-094512` and `backup/main-before-reconcile-20260512-094712`",
+    "Delete locally all branches returned by `git branch --merged main` except `main`, `develop`, and `drafts/v19-v22-orchestration-followups`",
+    "Confirm no branch with unmerged work is deleted — run `git branch --no-merged main` and verify the list before deleting anything",
+    "Commit only `ROADMAP.md` — branch cleanup produces no commit"
+  ],
+  "not_included": [
+    "Editing any other section of ROADMAP.md",
+    "Deleting branches on origin — local cleanup only",
+    "Closing or editing CHANGELOG.md",
+    "Any source code changes"
+  ],
+  "acceptance": [
+    "`grep 'unreleased' ROADMAP.md` returns no match",
+    "`grep 'v0.6 (shipped)' ROADMAP.md` returns a match",
+    "`git branch` shows no `backup/*` branches",
+    "`git branch --merged main` returns only `main` (and `develop` if present) — no stale feature/docs/ci branches",
+    "PR diff contains only `ROADMAP.md` changes"
+  ],
+  "files": [
+    "ROADMAP.md"
+  ],
+  "tests": [
+    "grep -c 'unreleased' ROADMAP.md | grep -q '^0$'",
+    "git branch --merged main",
+    "git branch | grep backup | wc -l | grep -q '^0$'"
+  ],
+  "documentation": [
+    "ROADMAP.md"
+  ],
+  "depends_on": [],
+  "assumptions": [
+    "All branches returned by `git branch --merged main` (except main/develop/drafts) are safe to delete — they were created from merged PRs",
+    "No branch other than `drafts/v19-v22-orchestration-followups` contains uncommitted or unmerged work worth preserving"
+  ],
+  "estimated_hours": 0.3,
+  "actual_hours": 0.1,
+  "status": "completed",
+  "blocked_reason": null,
+  "ready_at": "2026-05-12T00:00:00Z",
+  "started_at": "2026-05-12T00:00:00Z",
+  "completed_at": "2026-05-12T00:00:00Z"
+}

package/specs/quiver-v18-stabilization/slices/slice-03-publish-drafts-branch/CLOSURE_BRIEF.md

@@ -0,0 +1,23 @@
+# CLOSURE BRIEF — slice-03: Publicar rama de drafts
+
+**Spec:** quiver-v18-stabilization
+**Slice:** slice-03-publish-drafts-branch
+
+---
+
+## Checklist de cierre (sin PR)
+
+- [ ] Gate confirmada: el mantenedor declaró explícitamente que el checkpoint de v18 pasó.
+- [ ] `git ls-remote origin drafts/v19-v22-orchestration-followups` retorna un SHA no vacío.
+- [ ] El SHA remoto coincide con `git rev-parse drafts/v19-v22-orchestration-followups`.
+- [ ] No se abrió ningún PR para esta rama.
+
+## Post-ejecución
+
+- [ ] Actualizar `specs/quiver-v18-stabilization/STATUS.md`: slice-03 → `Completed`, `actual_hours: 0.1`.
+- [ ] Actualizar `specs/quiver-v18-stabilization/EVIDENCE_REPORT.md`: registrar SHA y fecha de push.
+- [ ] Si todos los slices de esta spec están `Completed`, actualizar el campo `Status` del EVIDENCE_REPORT a `Completed`.
+
+## Nota sobre el checkpoint de v18
+
+Una vez que este slice cierra, la spec `quiver-v18-stabilization` está completa. El siguiente paso en el BACKLOG es la promoción de v19 (Project Visibility) desde la rama de drafts a una spec activa. Ese es un proceso editorial del mantenedor, no un slice de esta spec.