@bongos/core 1.21.176 → 1.21.177

package/scripts/bongos/goal-names.js

@@ -1,102 +0,0 @@
-#!/usr/bin/env node
-// scripts/bongos/goal-names.js — give every open goal a NAME, and move its
-// explanation into `subtitle` (task 1003225, goal 1000072, criterion
-// legibility-goal-names-and-claude-text).
-//
-// Owner directive: a goal's subtitle should not sit on its title. 28 open goals
-// carried theirs after a dash and 3 more after a colon — the punctuation is not
-// the point, the jamming is. Task 1003224 gave `goals` a `subtitle` column and
-// taught the hall to render name / subtitle / Claude's prose at three weights;
-// this moves the existing text into that shape.
-//
-// WHY A MAPPING FILE AND NOT 31 AD-HOC PATCHES. A rename is a judgment call, and
-// judgment that lives only in a shell history cannot be reviewed, re-run, or
-// argued with. The table below IS the decision: it can be read in a diff, its
-// invariants are unit-tested (no duplicate names, no name still carrying its own
-// explanation, nothing dropped), and re-running is a no-op.
-//
-// IT IS NOT A MECHANICAL SPLIT, which is the whole reason this is its own task.
-// Splitting on the separator works where the head already names the thing
-// ("Findability — the grep path"). It FAILS where the head is not distinctive:
-// goals 1000038/1000039/1000040 all head "Agents module" and differ ONLY in the
-// tail, so a split would leave three identically-named goals — strictly worse
-// than today. Those three, the version catch-all, and three wordy heads get
-// written names; the rest keep theirs verbatim.
-//
-// SAFETY. Dry-run by DEFAULT (`--apply` to write). Every write goes through
-// PATCH /goals/:id, which is authorized (owner|manager|Archon) and records
-// prose-edit deltas — so the rename is audit-trailed, unlike the prod SQL UPDATE
-// that would otherwise be the only channel. It REFUSES to run at all if the
-// server does not yet return `subtitle`, because renaming titles against a
-// server that cannot store the subtitle would DELETE the explanations.
-
-'use strict';
-
-// id → { title, subtitle, why? }. `why` is recorded only where the name is
-// NEW rather than the existing head — i.e. where judgment was applied.
-const GOAL_NAMES = Object.freeze({
-  // ── names written, because the head was not usable ───────────────────────
-  1000003: { title: 'Work with no goal yet',
-    subtitle: 'The version catch-all. Tasks land here when nothing else fits — and nothing here can satisfy a criterion (ADR 0183), so it is a holding pen, not a home.',
-    why: 'was "BONGOS-V1 — general": a version id and the word general name nothing. Named for what it actually is.' },
-  1000038: { title: 'Agent framework & registry',
-    subtitle: 'The foundation — the plugin surface an agent is written against, and the registry that holds the roster.',
-    why: 'one of THREE goals heading "Agents module"; a mechanical split would have left three identically-named goals. Written without a colon on purpose: "Agents: framework" is the same name-plus-qualifier shape this task exists to remove, and the test flagged it.' },
-  1000039: { title: 'Agent authoring & first roster',
-    subtitle: 'Owner and builder authoring, plus the first real roster — event-driven and on-demand agents.',
-    why: 'second of the three "Agents module" goals. Named for what it adds — authoring and the first roster — rather than by a tail no list ever showed.' },
-  1000040: { title: 'Agent scheduling & spend limits',
-    subtitle: 'Scheduled agents, and the guardrails on what they are allowed to spend.',
-    why: 'third of the three "Agents module" goals. Scheduling and spend are what separate it from the framework and authoring goals.' },
-  1000053: { title: 'Sessions start knowing',
-    subtitle: 'Front-load auth, environment and instance facts so a session does not spend its first minutes rediscovering them.',
-    why: 'was "Session efficiency: sessions start knowing" — the head restated the tail. Kept the half that is a name.' },
-  1000064: { title: 'The hall as the room',
-    subtitle: 'Agora, Monitor & Contribute, and chat that does not care which channel it came from.',
-    why: 'colon-separated rather than dashed; same jamming, so treated identically.' },
-  1000075: { title: 'Collaboration & the social hall',
-    subtitle: 'Ask for help by craft, and let the hall become a mode rather than a page.',
-    why: 'was "Collab, then the social hall" — an ordering, not a name.' },
-  1000077: { title: 'Guards, not notes',
-    subtitle: 'The four failure modes that prose already documented and nothing refused.',
-    why: 'colon-separated; the head is already a good name, the tail is the explanation.' },
-  1000078: { title: 'Project money out',
-    subtitle: 'A funded balance, real builder payouts, visible outflows, and work that cannot outrun the money.',
-    why: 'colon-separated rather than dashed. The head is already the name; the tail is a four-part explanation that belongs underneath it.' },
-
-  // ── heads kept verbatim; only the tail moves ─────────────────────────────
-  1000025: { title: 'Builder experience', subtitle: 'Hall, dev box, and skills.' },
-  1000027: { title: 'Findability', subtitle: 'The grep path (ADR 0095).' },
-  1000029: { title: 'Module upstreaming & catalog', subtitle: 'Instances contribute modules back into core.' },
-  1000032: { title: 'Instance hosting + domains', subtitle: 'The `provisioning` module.' },
-  1000044: { title: 'Living project sky', subtitle: 'A shared, persistent, data-driven orb gate.' },
-  1000045: { title: 'Public builder profiles', subtitle: 'Track record, apply-to-project, and owner recruiting.' },
-  1000046: { title: 'Project creation', subtitle: 'Visibility and customization.' },
-  1000048: { title: 'SEO & public discoverability', subtitle: 'Rankable per-project profiles.' },
-  1000049: { title: 'Orb Physics', subtitle: 'Orb motion and space-whale flight.' },
-  1000052: { title: 'First-run onboarding', subtitle: 'From a bare machine to a first ship.' },
-  1000054: { title: 'Public distribution', subtitle: 'CLI installer and Claude plugin.' },
-  1000057: { title: 'Rank blocker matrix', subtitle: 'Empirically verify intended vs unintended blockers across xenos, thetes and metic.' },
-  1000058: { title: 'Non-cloudbongos project lifecycle', subtitle: 'Creation, governance, planning, building — the whole flow works and feels right.' },
-  1000063: { title: 'The front door', subtitle: 'Enter the Future: hero-only landing, wormhole transit, About on the map.' },
-  1000065: { title: 'Community surface', subtitle: 'Builder discovery on the hub.' },
-  1000067: { title: 'Ideator compensation', subtitle: 'The idea credit stream, separate from cost-plus.' },
-  1000068: { title: 'Government, not governance', subtitle: 'Ranks are ranks, and "role" belongs to the crafts.' },
-  1000070: { title: 'Scan-before-install', subtitle: 'First-real-run hardening.' },
-  1000071: { title: 'Idea routing', subtitle: 'Work that has a home lands in it.' },
-  1000072: { title: 'Human legibility', subtitle: 'Seeing, sorting and steering an AI-run project.' },
-  1000073: { title: 'Finish the GDS→Bongos rename', subtitle: 'Retire a legacy Primea term without rewriting history.' },
-  1000074: { title: "The artist's loop", subtitle: 'Review authority, copy an artist can change, and a place to do it.' },
-  // 1000080 already carried a subtitle, so the tail is PREPENDED to it rather than
-  // replacing it — overwriting would delete text, the exact loss this task guards.
-  1000080: { title: 'Apex UI pass 2', subtitle: 'One top bar, two dropdowns, and a project card worth opening — the chrome and the card on cloudbongos.com and /projects.' },
-});
-
-// A name must not carry its own explanation — that is the whole point.
-const SEPARATOR = / [—-] |: /;
-
-// Goals deliberately untouched: their titles are already names. Listed so the
-// coverage test can tell "already fine" from "forgotten".
-const ALREADY_NAMES = Object.freeze([1000009, 1000024, 1000028, 1000037, 1000047, 1000050]);
-
-module.exports = { GOAL_NAMES, ALREADY_NAMES, SEPARATOR };

package/scripts/bongos/rename-goals.js

@@ -1,109 +0,0 @@
-#!/usr/bin/env node
-// scripts/bongos/rename-goals.js — apply the goal-names.js mapping (task 1003225).
-//
-// Usage:
-//   node scripts/bongos/rename-goals.js            # DRY RUN — prints the diff, writes nothing
-//   node scripts/bongos/rename-goals.js --apply    # writes, via PATCH /goals/:id
-//
-// Writes go through PATCH /goals/:id, never SQL: that route is authorized
-// (owner|manager|Archon) and records prose-edit deltas, so a rename of somebody's
-// goal is audit-trailed. A prod UPDATE would be invisible.
-//
-// THE GUARD THAT MATTERS: it refuses to run when the server does not return
-// `subtitle`. Renaming a title against a server that cannot store the subtitle
-// would DELETE the explanation — the exact data loss this task exists to avoid.
-// core_224 ships the column; a live instance one release behind does not have it.
-
-'use strict';
-
-const { cliClient, requireSession, hasFlag } = require('./cli-lib');
-const { GOAL_NAMES, SEPARATOR } = require('./goal-names.js');
-
-// Nothing to do when the goal already reads the way the mapping wants.
-function planFor(goal, want) {
-  const patch = {};
-  if ((goal.title || '') !== want.title) patch.title = want.title;
-  if ((goal.subtitle || '') !== want.subtitle) patch.subtitle = want.subtitle;
-  return patch;
-}
-
-async function main() {
-  await requireSession();
-  const apply = hasFlag('--apply');
-  const api = await cliClient();
-
-  const res = await api.goals.getGoals({ query: { version: 'BONGOS-V1' } });
-  if (!res.ok) {
-    console.error(`could not list goals: ${res.status}`);
-    process.exit(1);
-  }
-  const goals = (res.data.goals || []).filter((g) => g.status === 'open');
-  if (!goals.length) {
-    console.error('no open goals returned — refusing to act on an empty read.');
-    process.exit(1);
-  }
-
-  // The refusal above all others.
-  if (!Object.prototype.hasOwnProperty.call(goals[0], 'subtitle')) {
-    console.error('REFUSING: this server does not return `subtitle`, so it cannot store one.');
-    console.error('Renaming titles now would drop every explanation on the floor.');
-    console.error('core_224 adds the column — wait for the release carrying it to DEPLOY, then re-run.');
-    process.exit(2);
-  }
-
-  let changed = 0; let already = 0; let missing = 0; let failed = 0;
-  for (const g of goals.sort((a, b) => Number(a.id) - Number(b.id))) {
-    const want = GOAL_NAMES[Number(g.id)];
-    if (!want) {
-      // Not an error: goals whose titles were already names are deliberately absent.
-      if (SEPARATOR.test(g.title || '')) {
-        console.error(`!  ${g.id} has a jammed title but no mapping entry: ${g.title}`);
-        missing += 1;
-      }
-      continue;
-    }
-    const patch = planFor(g, want);
-    if (!Object.keys(patch).length) { already += 1; continue; }
-    console.log(`${apply ? '→' : '·'}  ${g.id}`);
-    if (patch.title) console.log(`     title    ${JSON.stringify(g.title)}  ->  ${JSON.stringify(patch.title)}`);
-    if (patch.subtitle !== undefined) console.log(`     subtitle ${JSON.stringify(g.subtitle || '')}  ->  ${JSON.stringify(patch.subtitle)}`);
-    if (!apply) { changed += 1; continue; }
-    const r = await api.goals.patchGoalsId({ id: g.id, body: patch });
-    if (!r.ok) {
-      console.error(`     FAILED ${r.status} ${JSON.stringify(r.data)}`);
-      failed += 1;
-    } else {
-      changed += 1;
-    }
-  }
-
-  console.log('');
-  console.log(`${apply ? 'applied' : 'would change'}: ${changed} · already correct: ${already}`
-    + `${missing ? ` · UNMAPPED jammed titles: ${missing}` : ''}${failed ? ` · FAILED: ${failed}` : ''}`);
-  if (!apply) console.log('dry run — re-run with --apply to write.');
-
-  // THE POST-CONDITION, CHECKED AGAINST REAL DATA — not against the mapping.
-  // The task's deliverable is a STATE of the live goal set ("no open goal's title
-  // contains a dash-appended subtitle"), and unit tests over the mapping's internal
-  // consistency cannot witness that: they would pass just as happily if --apply had
-  // never been run. This re-reads what the server actually holds now and reports it,
-  // so the claim is falsifiable by anyone re-running the command.
-  //
-  // SCOPED TO THIS VERSION, deliberately. The read above is `version: BONGOS-V1`;
-  // CB-V1 carries jammed titles of its own (id 4, 1000043, 1000066, 1000079) which
-  // are ANOTHER version's work, and sweeping them in here would rename goals this
-  // task never reviewed.
-  const stillJammed = goals.filter((g) => SEPARATOR.test(g.title || ''));
-  console.log('');
-  console.log(`post-condition (BONGOS-V1 open goals): ${goals.length} checked · `
-    + `${stillJammed.length} still carrying an explanation in the title`);
-  for (const g of stillJammed) console.log(`  ! ${g.id} ${JSON.stringify(g.title)}`);
-
-  process.exit(failed || missing ? 1 : 0);
-}
-
-if (require.main === module) {
-  main().catch((err) => { console.error('fatal:', err); process.exit(1); });
-}
-
-module.exports = { planFor };

package/scripts/bongos/seed-adopt-tasks.js

@@ -1,75 +0,0 @@
-#!/usr/bin/env node
-// seed-adopt-tasks.js
-// Seeds the brownfield adopt-mode task breakdown for BONGOS-V1 goal 35
-// ("Project creation flow"), criterion `adopt-existing-repo`, per ADR 0121
-// (task 1986). Scope-only deliverable: these are the BUILD tasks for
-// `bongos init --adopt`; they are seeded as `backlog` (NOT promoted) so the
-// owner schedules the adopt build deliberately. See ADR 0121 §Consequences.
-//
-// Idempotent: task create on source_ref (`BONGOS-V1-adopt-A0N`), criterion
-// links on (task_id, criterion_id), dependency edges on (task_id,
-// depends_on_task_id). Safe to re-run. Run: node scripts/bongos/seed-adopt-tasks.js
-const { apiCall } = require('./cli-lib.js');
-
-const GOAL_ID = 35;
-const CRIT = 'adopt-existing-repo';
-const RUNBOOK_TASK = 1981; // goal-35 canonical runbook; A05 depends on it (external edge)
-
-// ref → task spec. `deps` are local A0N refs; `extDeps` are literal task ids.
-const TASKS = [
-  { ref: 'A01', kind: 'feature', priority: 4, est: 180, crit: [CRIT], deps: [], extDeps: [],
-    title: 'bongos init --adopt: mode skeleton + additive config layering (no clobber)',
-    description: 'Add an `--adopt` mode to `scripts/bongos/init.js` (ADR 0121 §Decision 1-2). Instead of the greenfield "stand up a NEW instance" path (which refuses where config/branding.json exists and whose --force OVERWRITES), --adopt LAYERS onto the existing tree: add the pinned @bongos/core dependency + the lean config/ overrides + .claude/ ADDITIVELY. For any pre-existing file (package.json, an existing .claude/, a CI workflow) it MERGES or LEAVES-AND-REPORTS — it never overwrites, and it must NOT reuse the --force code path. Writes only the lean branding.json overrides (rest resolves from *.neutral.json). Serves criterion adopt-existing-repo. deps: none (the ADR-0108 configurable-root substrate is shipped).' },
-  { ref: 'A02', kind: 'feature', priority: 4, est: 150, crit: [CRIT], deps: [], extDeps: [],
-    title: 'bongos init --adopt: detect the existing stack + layout',
-    description: 'Before writing anything, --adopt inspects the existing tree — language/runtime, package manager, test + CI setup, directory layout — so the enabled modules, the generated repo-map, and the core<->host fitness boundary (ADR 0062 §1) fit what is already there instead of assuming the reference layout (ADR 0121 §Decision 4). Output: a detected-stack summary consumed by A03 (real-state capture) and A04 (pre-flight). Serves criterion adopt-existing-repo. deps: none.' },
-  { ref: 'A03', kind: 'feature', priority: 3, est: 180, crit: [CRIT], deps: ['A01'], extDeps: [],
-    title: 'bongos init --adopt: reflect REAL state — capture version/goal + import backlog',
-    description: 'Replace the synthetic "V1 — Prove the loop" seed with the repo\'s ACTUAL current version/milestone + open goal (by interview + detection), and IMPORT the existing backlog into GDS tasks — GitHub issues (via the auth the flow already establishes), a TODO/ROADMAP/BACKLOG.md, or an interview fallback — so the ledger starts truthful rather than empty (ADR 0121 §Decision 3). Serves criterion adopt-existing-repo. deps: A01.' },
-  { ref: 'A04', kind: 'feature', priority: 3, est: 150, crit: [CRIT], deps: ['A01', 'A02'], extDeps: [],
-    title: 'bongos init --adopt: conflict pre-flight report (--dry-run default, accept-gated)',
-    description: 'Produce the pre-flight report the owner must ACCEPT before anything is written (ADR 0121 §Decision 5): migration-namespace collisions (ADR 0108 §5), core<->host fitness-boundary violations in existing imports (ADR 0062 §1), incoming files that land on protected paths (ADR 0043), and CI collisions between core\'s expected unit/gate check and the repo\'s own workflows. --dry-run is the default first pass; nothing is written until accepted. Serves criterion adopt-existing-repo. deps: A01, A02.' },
-  { ref: 'A05', kind: 'feature', priority: 3, est: 120, crit: [CRIT], deps: ['A01', 'A03', 'A04'], extDeps: [RUNBOOK_TASK],
-    title: 'bongos init --adopt: wire greenfield-vs-adopt into the runbook + both forms',
-    description: 'Offer the greenfield-vs-adopt choice at the SCAFFOLD leg of goal 35\'s canonical step sequence, across all three forms: the /new-project skill (task 1981), the `bongos onboard` CLI (task 1982), and the hall "start a project" wizard (task 1983). Since --adopt is a branch of the same init, the forms inherit it (ADR 0121 §Decision 1). Serves criterion adopt-existing-repo. deps: A01, A03, A04, and the runbook task 1981.' },
-];
-
-(async () => {
-  const idByRef = {};
-  // Phase 1: create tasks (idempotent on source_ref) + link the criterion.
-  for (const t of TASKS) {
-    const create = await apiCall('POST', '/api/bongos/tasks', {
-      version_id: 'BONGOS-V1',
-      goal_id: GOAL_ID,
-      title: t.title,
-      description: t.description,
-      kind: t.kind,
-      discipline: 'engineer',
-      priority: t.priority,
-      est_minutes: t.est,
-      source: 'planning',
-      source_ref: `BONGOS-V1-adopt-${t.ref}`,
-    });
-    const task = create.data && (create.data.task || create.data);
-    const id = task && task.id;
-    if (!id) { console.log(`  ${t.ref}: CREATE FAILED — ${create.status} ${JSON.stringify(create.data).slice(0, 160)}`); continue; }
-    idByRef[t.ref] = id;
-    const link = await apiCall('POST', `/api/bongos/tasks/${id}/criteria`, { criterion_ids: t.crit });
-    console.log(`  ${t.ref} -> task ${id} (${t.kind}, P${t.priority}, goal ${task.goal_id}) · criterion ${link.status === 200 ? 'ok' : (JSON.stringify(link.data).slice(0, 120))}`);
-  }
-  // Phase 2: dependency edges (idempotent on (task_id, depends_on_task_id)).
-  console.log('--- dependencies ---');
-  for (const t of TASKS) {
-    const id = idByRef[t.ref];
-    if (!id) continue;
-    const localDepIds = t.deps.map((d) => idByRef[d]).filter(Boolean);
-    const allDeps = [...localDepIds, ...t.extDeps];
-    for (const depId of allDeps) {
-      const r = await apiCall('POST', `/api/bongos/tasks/${id}/dependencies`, { depends_on_task_id: depId });
-      console.log(`  ${t.ref}(${id}) -> ${depId} ${r.status === 200 || r.status === 201 ? 'ok' : (JSON.stringify(r.data).slice(0, 120))}`);
-    }
-  }
-  // NOTE: intentionally NO promote step — these are backlog until the owner
-  // schedules the adopt build (ADR 0121; task 1986 is scope-only).
-  console.log('refs:', JSON.stringify(idByRef));
-})().catch((e) => console.log('ERR ' + (e && e.message)));

package/scripts/bongos/seed-api-contract-goal-tasks.js

@@ -1,141 +0,0 @@
-#!/usr/bin/env node
-// seed-api-contract-goal-tasks.js
-// Seeds BONGOS-V1 goal 36 — "Robust, versioned, easy-to-call public API" — from
-// the 2026-07-04 Archon planning session (task 1987). Five done-when criteria
-// (slugs api-error-envelope · api-versioning · api-client-sdk · api-validation ·
-// api-pagination) were created via POST /versions/BONGOS-V1/done-when before this
-// runs; this seeds the 14 tasks (refs R01-R14) + their criterion links + the
-// dependency edges. Entry point is CONTRACT-FIRST, so only the zero-dep,
-// non-spike Phase-A tasks (R01 envelope contract, R05 versioning policy) plus the
-// independent R13 pagination decision are promoted to `ready`; R07 (the
-// source-of-truth spike) stays backlog by convention and is opened manually when
-// Phase B starts; everything else auto-promotes as its predecessor ships.
-//
-// Idempotent: task create on source_ref, criterion links on (task_id,
-// criterion_id), dependency edges on (task_id, depends_on_task_id). Safe to re-run.
-// Run: node scripts/bongos/seed-api-contract-goal-tasks.js
-const { cliClient } = require('./cli-lib.js');
-
-const GOAL_ID = 36;
-const C = {
-  envelope: 'api-error-envelope',
-  versioning: 'api-versioning',
-  sdk: 'api-client-sdk',
-  validation: 'api-validation',
-  pagination: 'api-pagination',
-};
-
-// ref → task spec. `deps` are local R## refs, resolved to ids after create.
-const TASKS = [
-  // ---- Criterion 1: error envelope (Phase A) ----
-  { ref: 'R01', kind: 'decision', priority: 5, est: 90, crit: [C.envelope],
-    title: 'API error envelope + code taxonomy (contract + ADR)',
-    description: 'Define the single error response envelope `{error:{code,message,details}}` and the taxonomy that collapses today\'s ~339 ad-hoc error strings into a documented registry. Deliverable: an ADR + a shared registry module of canonical codes. No behaviour change — this is the contract R02 implements. Serves C1 (api-error-envelope). deps: none.',
-    deps: [] },
-  { ref: 'R02', kind: 'infra', priority: 5, est: 120, crit: [C.envelope],
-    title: 'Central error-handling middleware + envelope helper',
-    description: 'Add a central Express error-handling middleware + an `ApiError`/`res.fail(code,status,details)` helper (kernel route layer) emitting the R01 envelope; wire the handler last so any thrown/unhandled error returns the envelope. Backward-compatible — existing ad-hoc responses keep working until the R04 sweep. Serves C1. deps: R01.',
-    deps: ['R01'] },
-  { ref: 'R03', kind: 'infra', priority: 4, est: 90, crit: [C.envelope],
-    title: 'Build check: fail on a route emitting a non-envelope error',
-    description: 'Add a fitness/lint check (into fitness.js / the unit gate) that fails the build when a route hand-rolls a flat `res.status(NNN).json({error:\'...\'})` instead of the R02 helper. Holds the line as the sweep progresses. Serves C1. deps: R02.',
-    deps: ['R02'] },
-  { ref: 'R04', kind: 'refactor', priority: 4, est: 240, crit: [C.envelope],
-    title: 'Sweep existing routes onto the error envelope',
-    description: 'Convert the ~219 handlers across core + modules from ad-hoc flat errors to the R02 envelope (the audit found 168 open-coded 500s + 615 flat-error sites). Mechanical but wide — touches every module\'s routes. Serves C1. deps: R02.',
-    deps: ['R02'] },
-  // ---- Criterion 2: versioning (Phase A) ----
-  { ref: 'R05', kind: 'decision', priority: 5, est: 90, crit: [C.versioning],
-    title: 'API versioning + deprecation policy (ADR)',
-    description: 'ADR defining the versioning scheme (a `/v1/` path marker), what counts as a breaking change, the deprecation window, and how the currently-un-updatable consumers (shipped Dev Box binaries, live boxes, status dashboard) are handled. Serves C2 (api-versioning). deps: none.',
-    deps: [] },
-  { ref: 'R06', kind: 'infra', priority: 5, est: 150, crit: [C.versioning],
-    title: 'Serve the API under /v1/ with legacy aliasing',
-    description: 'Mount the current surface under `/v1/` and alias today\'s unversioned paths (`/api/bongos`, `/api/gds`) into it so no consumer breaks on day one. Stamp the version into the OpenAPI spec + `/docs`. Serves C2. deps: R05.',
-    deps: ['R05'] },
-  // ---- Criterion 3: client SDK (Phase B) ----
-  { ref: 'R07', kind: 'spike', priority: 4, est: 120, crit: [C.sdk],
-    title: 'Spike: pick the API contract source-of-truth (schema-first vs code-first)',
-    description: 'Decide whether the OpenAPI spec becomes the SOURCE (schema-first: define request/response schemas -> generate spec + validation + client) or stays GENERATED from code with codegen layered on. This one decision shapes the SDK (C3) and validation (C4). Output: an ADR + a sub-task list refining R08-R12. kind=spike (stays backlog; opened manually when Phase B starts). Serves C3, informs C4. deps: none (do after Phase A).',
-    deps: [] },
-  { ref: 'R08', kind: 'feature', priority: 3, est: 180, crit: [C.sdk],
-    title: 'Generate + publish the typed API client',
-    description: 'Per the R07 decision, generate a typed client from the OpenAPI spec and publish it for install (internal package first). Serves C3. deps: R07.',
-    deps: ['R07'] },
-  { ref: 'R09', kind: 'refactor', priority: 3, est: 240, crit: [C.sdk],
-    title: 'Migrate internal callers onto the client; delete duplicates',
-    description: 'Move the CLI (cli-lib apiCall), the devbox Electron app (its own gds-client), and the web UIs (per-page fetch helpers) onto the generated client; delete the 3 duplicate implementations. Cuts per-call boilerplate from ~15 lines to 1. Touches hall-ui/status-ui/dev-box. Serves C3. deps: R08.',
-    deps: ['R08'] },
-  { ref: 'R10', kind: 'feature', priority: 3, est: 120, crit: [C.sdk],
-    title: 'External-consumer on-ramp + hello-world (proof)',
-    description: 'Document how an outside program authenticates (token acquisition beyond the interactive Device Flow) and makes its first call, with a runnable hello-world using the published client. The PROOF an external self-hoster can actually use the API. Serves C3. deps: R08.',
-    deps: ['R08'] },
-  // ---- Criterion 4: validation (Phase C) ----
-  { ref: 'R11', kind: 'feature', priority: 3, est: 240, crit: [C.validation],
-    title: 'Spec-driven request validation: 100% writes + query params',
-    description: 'Per the R07 decision, drive validation from the spec so every write route AND its query parameters are validated, and unknown/typo\'d fields are rejected with the R02 envelope (today ~55% coverage, extras silently dropped). Serves C4 (api-validation). deps: R07.',
-    deps: ['R07'] },
-  { ref: 'R12', kind: 'infra', priority: 3, est: 90, crit: [C.validation],
-    title: 'Build check: fail on an unvalidated write route',
-    description: 'Add a fitness check that fails the build when a write route (POST/PUT/PATCH/DELETE) has no spec-bound validation. Locks in C4\'s 100% coverage. Serves C4. deps: R11.',
-    deps: ['R11'] },
-  // ---- Criterion 5: pagination (Phase C) ----
-  { ref: 'R13', kind: 'decision', priority: 2, est: 90, crit: [C.pagination],
-    title: 'Pagination contract + shared helper (decision)',
-    description: 'Decide one pagination convention (cursor vs limit/offset) and build the shared helper. Today three styles coexist (limit-only, limit+offset, none) with per-endpoint clamps. Serves C5 (api-pagination). deps: none (independent).',
-    deps: [] },
-  { ref: 'R14', kind: 'refactor', priority: 2, est: 180, crit: [C.pagination],
-    title: 'Adopt the pagination contract across list endpoints; cap unbounded lists',
-    description: 'Apply the R13 helper across all list endpoints and cap the currently-unbounded public lists (leaderboard, blockers, versions). Serves C5. deps: R13.',
-    deps: ['R13'] },
-];
-
-(async () => {
-  const api = await cliClient();
-  const idByRef = {};
-  // Phase 1: create tasks (idempotent on source_ref) + link criteria explicitly
-  // (criterion_ids at create is not honored on this build; /criteria is idempotent).
-  for (const t of TASKS) {
-    const create = await api.tasks.postTasks({ body: {
-      version_id: 'BONGOS-V1',
-      goal_id: GOAL_ID,
-      title: t.title,
-      description: t.description,
-      kind: t.kind,
-      discipline: 'engineer',
-      priority: t.priority,
-      est_minutes: t.est,
-      source: 'planning',
-      source_ref: `BONGOS-V1-api-contract-${t.ref}`,
-    } });
-    const task = create.data && (create.data.task || create.data);
-    const id = task && task.id;
-    if (!id) { console.log(`  ${t.ref}: CREATE FAILED — ${create.status} ${JSON.stringify(create.data).slice(0, 160)}`); continue; }
-    idByRef[t.ref] = id;
-    const link = await api.tasks.postTasksIdCriteria({ id, body: { criterion_ids: t.crit } });
-    console.log(`  ${t.ref} -> task ${id} (${t.kind}, P${t.priority}, goal ${task.goal_id}) · criteria ${link.status === 200 ? 'ok' : (JSON.stringify(link.data).slice(0, 120))}`);
-  }
-  // Phase 2: dependency edges (idempotent on (task_id, depends_on_task_id)).
-  console.log('--- dependencies ---');
-  for (const t of TASKS) {
-    const id = idByRef[t.ref];
-    if (!id || !t.deps.length) continue;
-    for (const dep of t.deps) {
-      const depId = idByRef[dep];
-      if (!depId) { console.log(`  ${t.ref}: dep ${dep} not created — skip`); continue; }
-      const r = await api.tasks.postTasksIdDependencies({ id, body: { depends_on_task_id: depId } });
-      console.log(`  ${t.ref}(${id}) -> ${dep}(${depId}) ${r.status === 200 || r.status === 201 ? 'ok' : (JSON.stringify(r.data).slice(0, 120))}`);
-    }
-  }
-  // Phase 3: promote the zero-dep, non-spike tasks to `ready` (contract-first:
-  // R01 + R05 open Phase A now; R13 is independent). R07 (spike) stays backlog.
-  console.log('--- promote (zero-dep, non-spike) ---');
-  for (const t of TASKS) {
-    if (t.deps.length || t.kind === 'spike') continue;
-    const id = idByRef[t.ref];
-    if (!id) continue;
-    const p = await api.tasks.postTasksIdPromote({ id, body: {} });
-    console.log(`  ${t.ref}(${id}) promote -> ${p.status} ${p.ok ? 'ready' : JSON.stringify(p.data).slice(0, 120)}`);
-  }
-  console.log('refs:', JSON.stringify(idByRef));
-})().catch((e) => console.log('ERR ' + (e && e.message)));