@bongos/core 1.21.175 → 1.21.177

package/scripts/gds/ship-escalation.js

@@ -1,167 +1,6 @@
+// scripts/gds/ship-escalation.js — @bongos-forwarder (task 1004848). Generated by
+// scripts/bongos/codemod-rename-scripts-gds.js; do not edit.
+// The real script is scripts/bongos/ship-escalation.js. This forwarder keeps callers that still name
+// the old path working, and warns once so they get repointed. Task 1003706 removes it.
 'use strict';
-//
-// scripts/gds/ship-escalation.js — the exit for a no-artifact close (task 1003950)
-//
-// THE DEAD END THIS REPLACES. A task that is legitimately artifact-free — an ops
-// verification, a DB-only close, or one whose premise turned out to be already-done —
-// could not be closed by any builder below archon, and the two documented paths pointed
-// at each other:
-//
-//     ship.js NNNN --allow-empty   → implies --skip-grade → 403 task.confirm.grade_bypass
-//                                  → "re-run WITHOUT --skip-grade and use --regrade"
-//     ship.js NNNN --regrade       → "Nothing to grade: the committed diff is empty"
-//                                  → "if this task is DELIBERATELY artifact-free, use --allow-empty"
-//
-// Neither exit is reachable at metic. The task parks at `completed` with the claim
-// released — the strand shape the reconciler cannot heal (no branch, no diff, and
-// `completed` sits BEFORE the confirm gate the reconciler sweeps from). Reproduced live
-// 2026-09-16 on task 1003822.
-//
-// WHAT THIS DOES, AND DELIBERATELY DOES NOT DO. It does not move the gate. The owner
-// decision recorded on task 1003950 scoped this to the third of the three shapes the
-// bug offered — "give the refusal a working escalation that does not require the builder
-// to know an archon personally" — because `task.confirm.grade_bypass` is `system: true`
-// in modules/government/catalog.js, one of the four trust-boundary keys ADR 0157 names
-// in its escalation-chain argument. Lowering or forking it is a governance migration and
-// an ADR, filed as task 1004010; grading the NOTES instead of the diff is task 1004011.
-//
-// So the close stays archon-gated. What stops is the LOOP: the refusal now files the
-// escalation on the builder's behalf and terminates, instead of returning them to a flag
-// that will send them back here.
-//
-// IDEMPOTENT BY TASK, not by run — the same reasoning artifact-audit.js carries.
-// POST /blockers dedupes on (source, source_ref), so a builder who re-runs --allow-empty
-// three times while waiting gets ONE blocker, not three. A check that spams is a check
-// that gets muted, and this one is aimed at the surface a person actually reads.
-
-const NO_ARTIFACT_SOURCE = 'no-artifact-close';
-const { postWithAsk } = require('./ask.js');
-
-// One blocker per task. Deliberately NOT keyed on the builder or the run: two builders
-// hitting the same stuck task should land on the same blocker, not race to file two.
-function escalationSourceRef(taskId) {
-  return `${NO_ARTIFACT_SOURCE}:${taskId}`;
-}
-
-function escalationTitle(taskId, title) {
-  const t = String(title || '').slice(0, 90);
-  return `No-artifact close needs an archon: task ${taskId}${t ? ` — ${t}` : ''}`;
-}
-
-// Pure so the wording is unit-testable without git or network. The body has to carry
-// enough for the archon to make the call WITHOUT re-interviewing the builder — that is
-// the whole point of filing it rather than telling them to go find someone.
-function escalationBody({ taskId, title, floor, summary, notes, builder }) {
-  const reason = [summary, notes].filter(Boolean).join('\n\n');
-  const lines = [
-    `Task **${taskId}** is claimed to be legitimately artifact-free and cannot be closed by its builder.`,
-    '',
-    `- **Task:** ${title || '(untitled)'}`,
-    `- **Declared by:** ${builder || 'the claim holder'} (ran \`ship.js ${taskId} --allow-empty\`)`,
-    `- **Blocked on:** \`task.confirm.grade_bypass\`${floor ? ` (floor: ${floor})` : ''}`,
-    '',
-    '### Why it is stuck',
-    '',
-    'The committed diff is empty and the working tree is clean, so the subagent grader has',
-    'nothing to read. Confirming without a passing grade is archon-gated, and the builder',
-    'holds no route past it. Left alone the task parks at `completed` with the claim',
-    'released — the strand shape the publish reconciler cannot heal, because `completed`',
-    'sits before the `confirmed` gate it sweeps from.',
-    '',
-    '### The reason the builder gave',
-    '',
-    reason || '_(none given — the ship carried no --summary or --notes)_',
-    '',
-    '### What is being asked of you',
-    '',
-    'Decide whether this task is genuinely artifact-free. That claim is the thing worth',
-    'checking here; the absent diff is not evidence either way.',
-    '',
-    `- If yes: \`POST /api/bongos/tasks/${taskId}/confirm\`, or run \`node scripts/gds/ship.js ${taskId} --allow-empty\` yourself.`,
-    '- If no: the work was never done, or never committed — release the claim back to `ready` and say so here.',
-    '',
-    'Filed automatically by the ship path (task 1003950). Re-running `--allow-empty` will',
-    'not file a second copy.',
-  ];
-  return lines.join('\n');
-}
-
-// The card the archon answers (task 1004704): the escalation as an ask, so the
-// review queue shows one short question instead of the body above. The body
-// still carries everything; the card is what a person answers at a glance.
-function escalationAsk(taskId) {
-  return {
-    question: `Close task ${taskId} with no code to grade?`,
-    options: [
-      { key: 'close', label: 'Close it', result: 'It closes as done, without a grade.', act: 'go ahead' },
-      { key: 'return', label: 'Send it back', result: 'The claim is released and the task returns to ready.', act: 'need more' },
-    ],
-    recommend: { key: 'close', why: 'The builder says no code was needed; read their reason first.' },
-    waits_on: 'lead:release',
-    if_nobody_answers: 'The task stays at completed and its builder is not paid.',
-  };
-}
-
-// The terminating refusal. THE ONE INVARIANT: these lines must never send the builder to
-// --regrade, because --regrade on an empty diff sends them straight back to --allow-empty.
-// That mutual advice IS the bug (task 1003950). Pure + exported so a test can assert the
-// loop stays closed rather than trusting a reviewer to notice it reopening.
-function noArtifactRefusalLines({ taskId, floor, escalation }) {
-  const lines = [
-    '',
-    'This task has no artifact to grade, and confirming without a passing grade is',
-    `permission-gated: task.confirm.grade_bypass${floor ? ` (floor: ${floor})` : ''}.`,
-    'This is an authorization wall, not a verdict on your work.',
-    '',
-  ];
-  if (escalation && escalation.filed) {
-    lines.push(`Escalated for you: blocker ${escalation.id} is now on the archon review queue,`);
-    lines.push('carrying this task, the reason you gave, and what is being asked. You do not');
-    lines.push('need to know an archon personally, and there is nothing further to re-run.');
-  } else if (escalation && escalation.reason === 'already-filed') {
-    lines.push('Already escalated: a blocker for this task is open on the archon review queue.');
-    lines.push('Re-running will not speed it up. Nothing further to do here.');
-  } else {
-    // Fail-open: the close is still blocked, so the builder must not be told it worked.
-    const why = escalation && escalation.reason ? ` (${escalation.reason})` : '';
-    lines.push(`Could not file the escalation automatically${why}.`);
-    lines.push('File it by hand so this does not sit silently — post a blocker naming this task,');
-    lines.push('with an ask (check the card first: node scripts/gds/ask.js check <file>):');
-    lines.push('    node scripts/gds/api.js POST /blockers --body-file <path-to-json>');
-  }
-  lines.push('');
-  lines.push(`Your claim on task ${taskId} is unchanged. Do NOT re-run with --regrade:`);
-  lines.push('the diff is empty, so a re-grade has nothing to read and will point you back here.');
-  return lines;
-}
-
-// Best-effort by design: a failure to file must not turn a blocked close into a crash,
-// but it must also never read as success — noArtifactRefusalLines prints the manual
-// fallback when `filed` is false.
-async function fileNoArtifactEscalation({ taskId, title, floor, summary, notes, builder }, { call } = {}) {
-  const post = call || require('./cli-lib').apiCall;
-  let r;
-  try {
-    r = await postWithAsk((body) => post('POST', '/api/bongos/blockers', body), {
-      title: escalationTitle(taskId, title),
-      body_md: escalationBody({ taskId, title, floor, summary, notes, builder }),
-      source: NO_ARTIFACT_SOURCE,
-      source_ref: escalationSourceRef(taskId),
-    }, escalationAsk(taskId));
-  } catch (err) {
-    return { filed: false, reason: `POST /blockers threw: ${err && err.message}` };
-  }
-  if (!r || !r.ok) return { filed: false, reason: `POST /blockers -> ${r && r.status}` };
-  if (r.data && r.data.skipped) return { filed: false, reason: 'already-filed' };
-  return { filed: true, id: r.data && r.data.blocker && r.data.blocker.id };
-}
-
-module.exports = {
-  NO_ARTIFACT_SOURCE,
-  escalationSourceRef,
-  escalationTitle,
-  escalationBody,
-  escalationAsk,
-  noArtifactRefusalLines,
-  fileNoArtifactEscalation,
-};
+require('../bongos/forwarder.js').forward(module, 'ship-escalation.js');

package/scripts/gds/ship-finish.js

@@ -1,420 +1,6 @@
-// scripts/gds/ship-finish.js — merge+deploy orchestration, post-ship sync/closeout and the completion card.
-//
-// Carved out of scripts/gds/ship.js by task 1003205 (goal 1000079, the R03
-// de-monolith plan) — a STRUCTURAL move, not a rewrite: the code below is the
-// original ship.js lines 3008-3352 unchanged. ship.js remains the facade that
-// re-exports every name and owns the CLI entry point, so the ship contract and
-// every flag are untouched, and the other scripts that import from it are too.
-
+// scripts/gds/ship-finish.js — @bongos-forwarder (task 1004848). Generated by
+// scripts/bongos/codemod-rename-scripts-gds.js; do not edit.
+// The real script is scripts/bongos/ship-finish.js. This forwarder keeps callers that still name
+// the old path working, and warns once so they get repointed. Task 1003706 removes it.
 'use strict';
-
-const fs = require('node:fs');
-const os = require('node:os');
-const { cliClient, printOnboardingNudge, rewardPolicy, cardFlagsFromMe } = require('./cli-lib');
-const { closeoutPlan } = require('../../modules/lifecycle/ship-preflight');
-const { syncMemoryOnShip } = require('./ship-memory-sync.js');
-const { uploadSessionOnShip } = require('./ship-session-upload.js');
-const { execFileSync } = require('node:child_process');
-const { gitOk } = require('./ship-git.js');
-const { fetchDeployedVersion, resolveInstanceBase } = require('./ship-deploy-target.js');
-const { landBailed, reconciledCardStatus } = require('./ship-land.js');
-const { autoMerge, publishHeld } = require('./ship-merge.js');
-const tweakHold = require('../../modules/lifecycle/page-tweak-hold.js');
-const { normalizeApiError, playShipBell, postLandShipOutcome } = require('./ship-io.js');
-const { getServerReward, noteServerReward } = require('./ship-state.js');
-
-async function mergeAndDeploy({ taskId, summary, advanceToMerge, skipMerge, dbOnly = false }) {
-  if (advanceToMerge && skipMerge) {
-    console.log('');
-    console.log('--no-merge: stopping at confirmed. Run /merge-mode later to land it.');
-    return landBailed('--no-merge was passed, so the land was skipped', '/merge-mode');
-  }
-  // Grade failed: the card renders the 'failed' stage ('not deployed'), so there
-  // is no land outcome to report.
-  if (!advanceToMerge) return null;
-
-  console.log('');
-  console.log('Auto-merge chain (confirmed → shipped):');
-  const merged = await autoMerge(taskId, summary, { dbOnly });
-  // NOTE: `merged` is an OBJECT now — every value is truthy, so this MUST test
-  // .ok. A bare `if (!merged)` would fall through on a bail and POST /ship for a
-  // task that never landed.
-  if (!merged.ok) return merged;
-
-  const shipBody = merged.noArtifact ? { no_artifact: true, no_artifact_reason: merged.noArtifactReason || 'deliberate empty ship (--db-only)' } : {}; // ADR 0184
-  const ship = await (await cliClient()).tasks.postTasksIdShip({ id: taskId, body: shipBody });
-  if (!ship.ok) {
-    // task 1049 / 1002809: the server may have already flipped this task to
-    // shipped (reconcile-on-read, or the reconciler racing this call). Verify
-    // the LIVE status before treating the refusal as a failure — the old
-    // flat-shape string check never matched the R01 envelope, so this success
-    // path was dead and every reconciled land reported as a failed ship.
-    const { code, message } = normalizeApiError(ship.data);
-    let liveStatus = null;
-    try {
-      const t = await (await cliClient()).tasks.getTasksId({ id: taskId });
-      if (t.ok && t.data && t.data.task) liveStatus = t.data.task.status;
-    } catch (_) { /* verify is best-effort; fall back to the code-based call */ }
-    const outcome = postLandShipOutcome({ code, liveStatus });
-    if (outcome.alreadyShipped) {
-      console.log(`Task #${taskId} is now: shipped (${outcome.why}).`);
-    } else {
-      const e = message || code || `HTTP ${ship.status}`;
-      console.error(`  /tasks/${taskId}/ship failed: ${e}${liveStatus ? ` (task is at '${liveStatus}')` : ''}`);
-      // The merge itself succeeded — only the status flip failed, so a re-run
-      // resumes cleanly (task 941). Report it rather than letting the card claim
-      // the land is in progress.
-      return landBailed(`merged, but the ship call failed — ${e}`, `node scripts/gds/ship.js ${taskId}`);
-    }
-  } else {
-    console.log(`Task #${taskId} is now: shipped`);
-  }
-
-  // task 1442: the task-shipped bell used to play HERE, but this point is only
-  // reached on a SYNCHRONOUS merge+deploy. In ci/async landing mode (now the
-  // norm) ship.js exits at 'confirmed' and never gets here, so the bell never
-  // rang. It now plays at the confirmed/shipped success milestone via
-  // playShipBell() (finishShip + resumeMerge), which covers both paths.
-
-  // If the builder was promoted during this ship, write the promotion flag so
-  // the NEXT Claude turn plays the fanfare via the Stop hook.
-  const TMP_FLAGS = process.platform === 'win32'
-    ? (process.env.TEMP || process.env.TMP || os.tmpdir())
-    : '/tmp';
-  if (ship.data?.task?.graduatedTo) {
-    try { fs.writeFileSync(require('path').join(TMP_FLAGS, 'otb-promotion'), ''); } catch (_) {}
-    console.log(`  Rank promotion: ${ship.data.task.graduatedTo} — fanfare queued.`);
-  }
-
-
-  if (summary) {
-    // task 1749: the SERVER is now the SINGLE ship broadcaster. It emits
-    // task.shipped on the confirmed→shipped transition from every entry point
-    // (POST /ship, the publish-status reconcile-on-read, and the 5-min
-    // reconciler sweep — all idempotent via db.shipTask), and the discord
-    // module posts the #ship-feed line off that one event. This local post used
-    // to fire IN ADDITION to the server's, so a single ship announced FOUR
-    // messages (local #ship-news + #ship-feed, then the server's #ship-news +
-    // #ship-feed). Defer unconditionally so exactly one broadcast fires — from
-    // the server, after the deploy lands. (That one broadcast is the #ship-feed
-    // line, plus a plain #ship-news headline for a feature or a bug — the kind
-    // filter in chooseBroadcastTargets, task 1002846.) The security-sensitive
-    // fail-closed routing lives server-side in ship-broadcast.postShipBroadcast,
-    // so it is preserved.
-    console.log('  Discord broadcast: deferred to the server — it posts #ship-feed after the deploy lands.');
-  }
-  return merged;
-}
-
-// Memory + session-digest push, gated on a successful land (confirmed/shipped).
-// Both are best-effort — a failure here is a warning, never a ship failure.
-async function postShipSync(taskId, postGradeStatus) {
-  if (postGradeStatus !== 'confirmed' && postGradeStatus !== 'shipped') return null;
-  console.log('');
-  console.log('Memory sync (best-effort):');
-  await syncMemoryOnShip();
-  console.log('');
-  console.log('Session upload (best-effort):');
-  // task 1270: the upload returns { totalTokens, modelUsage } (or null) so the
-  // completion card can show Claude usage + an estimated cost.
-  return await uploadSessionOnShip(taskId);
-}
-
-// Post-ship onboarding nudge (V3.R13 #237). Best-effort — never let a stale /me
-// read make the script exit non-zero after a successful ship.
-async function onboardingNudgeBestEffort() {
-  try {
-    const meRes = noteServerReward(await (await cliClient()).me.getMe());
-    if (meRes.ok) {
-      console.log('');
-      printOnboardingNudge(meRes.data);
-    }
-  } catch (_) {
-    /* never block on a UX nudge */
-  }
-}
-
-// finishShip — the confirmed→shipped tail shared by shipMain + regradeMain (task
-// 1093 / C9): auto-merge + deploy, then the best-effort memory/session sync, the
-// Done line, and the onboarding nudge. Only this UNIFORM tail is shared;
-// printGradeOutcome + printCreditsAndAchievements stay caller-owned (their inputs
-// differ between the two paths). `doneLine` is a param so each caller keeps its
-// own wording ('Done.' vs the re-grade pass/fail message).
-// task 932 (Lars 2026-06-12): deterministic, no-LLM post-ship working-tree
-// close-out, folded into the delivery process (NOT a separate skill). After a
-// ship lands, scratch often lingers uncommitted — untracked files the preflight
-// lets through, generated artifacts, post-commit edits — making the session
-// hard to archive cleanly. This REPORTS what's left and leaves it in place.
-// task 1004254: it used to `git stash push -u` the leftover, but the stash stack
-// is repo-global across every worktree (task 1003344), so one builder's scratch
-// landed where a parallel agent's pop could apply it to the wrong branch — and
-// it swallowed review renders an owner still needed. It never touches the stash.
-// STRICTLY fail-open: the ship has already succeeded by the time this runs, so
-// nothing here may throw, prompt, or change the exit status — a messy tree must
-// never surface as a ship failure. The caller gates this on a SUCCESSFUL land.
-function postShipCloseout(taskId) {
-  try {
-    // Untrimmed: gitOk's trim() eats the first line's leading status column, so
-    // " M a.txt" was listed as ".txt" (task 1004254).
-    let out;
-    try {
-      out = execFileSync('git', ['status', '--porcelain'], { encoding: 'utf8', stdio: ['ignore', 'pipe', 'ignore'] });
-    } catch (_) { return; } // git unavailable / not a repo — nothing to reconcile
-    const plan = closeoutPlan(out);
-    if (plan.clean) {
-      console.log('Close-out: working tree clean — session is archive-ready.');
-      return;
-    }
-    console.log('');
-    console.log(`Close-out: ${plan.leftover.length} uncommitted/untracked path(s) remain after the ship:`);
-    for (const f of plan.leftover.slice(0, 15)) console.log(`  ${f}`);
-    if (plan.leftover.length > 15) console.log(`  … and ${plan.leftover.length - 15} more`);
-    console.log(`Close-out: left in place (task ${taskId} already shipped) — commit, move or delete them before archiving this worktree.`);
-  } catch (err) {
-    // Fail-open — a post-ship close-out problem must never look like a ship failure.
-    console.log(`Close-out: skipped (${err && err.message ? err.message : 'error'}).`);
-  }
-}
-
-async function finishShip({ taskId, summary, advanceToMerge, skipMerge, postGradeStatus, doneLine, card, dbOnly = false, held = false }) {
-  // task 1004322 (ADR 0341 D7): a page tweak whose grade passed is HELD for its
-  // artist. It publishes its branch and PR and stops; nothing merges.
-  if (held) return finishHeld({ taskId, summary, postGradeStatus, card });
-  // task 1002541: the land outcome carries WHY a land didn't happen. Without it
-  // the card had only the status to go on and printed 'landing automatically'
-  // over a merge that had already bailed.
-  const land = await mergeAndDeploy({ taskId, summary, advanceToMerge, skipMerge, dbOnly });
-  // task 1719: mergeAndDeploy may have landed the task to 'shipped' IN-SESSION — the
-  // enable-success poll (pollCiDeploy) or, since task 1718, the enable-failure server
-  // poll (pollServerPublish). finishShip was handed postGradeStatus from the CONFIRM
-  // step ('confirmed'), so without re-reading it the completion card renders the stale
-  // 'confirmed — landing' banner AND printCompletionCard writes a pending-land
-  // breadcrumb — the SHIPPED banner then only appears on a LATER prompt, in whatever
-  // session is next (the owner-reported confusion). Re-fetch the authoritative status
-  // (exactly as resumeMerge does, task 1275) so a real in-session land shows the
-  // SHIPPED banner here and writes no breadcrumb. Best-effort: any read failure keeps
-  // today's behavior; the grade-fail path (advanceToMerge=false) never re-fetches.
-  let landedStatus = postGradeStatus;
-  if (advanceToMerge && (postGradeStatus === 'confirmed' || postGradeStatus === 'shipped')) {
-    try {
-      const t = await (await cliClient()).tasks.getTasksId({ id: taskId });
-      const live = (t.ok && t.data && t.data.task) ? t.data.task.status : null;
-      landedStatus = reconciledCardStatus(live, postGradeStatus);
-    } catch (_) { /* keep postGradeStatus — the land above already awaited its outcome */ }
-  }
-  // Memory + session sync (#274 / 6D.1 / ADR 0027) — postShipSync itself gates on
-  // a successful land (confirmed/shipped); both legs are best-effort. It returns
-  // the session usage ({ totalTokens, modelUsage } | null) so the completion card
-  // can show Claude usage + an estimated cost (task 1270).
-  const usage = await postShipSync(taskId, landedStatus);
-  console.log('');
-  console.log(doneLine);
-  await onboardingNudgeBestEffort();
-  // task 1270: the ONE deterministic completion card — the same shape every ship.
-  // Replaces the agent's free-form prose recap (the builder-ship skill renders the
-  // rich in-feed card from the HTML this writes; the monospace card below is the
-  // always-printed fallback + the headless summary). Strictly best-effort.
-  // task 1719: pass the reconciled status so a just-landed ship shows SHIPPED (and
-  // writes no breadcrumb), not the stale pre-merge 'confirmed'.
-  await printCompletionCard({ taskId, postGradeStatus: landedStatus, card, usage, land });
-  // task 932: reconcile the working tree — ONLY on a successful land. A
-  // grade-failed ship stays at 'completed'; leave that tree untouched so the
-  // builder can fix findings + re-ship.
-  if (landedStatus === 'confirmed' || landedStatus === 'shipped') {
-    // task 1442: ring the ship bell at the success milestone. 'confirmed' counts —
-    // in ci/async mode the work is done + credited here and the deploy lands later
-    // server-side, so this is the moment the builder experiences as "shipped".
-    playShipBell();
-    postShipCloseout(taskId);
-  }
-}
-
-// finishHeld — the tail of a held pass (task 1004322). The session is finished
-// work, so it syncs exactly as a confirmed ship does (the applier's session
-// reward is computed from the upload, and pays on land). No bell and no tree
-// close-out: nothing landed, and a send-back brings the round back to be
-// re-applied. `deps` is a test seam only.
-async function finishHeld({ taskId, summary, postGradeStatus, card }, deps = {}) {
-  console.log('');
-  console.log('Publishing the applied branch for the artist (ADR 0341 D7):');
-  const land = await (deps.publishHeld || publishHeld)(taskId, summary);
-  if (land && land.held) {
-    for (const line of tweakHold.heldLines(taskId, { prUrl: land.prUrl })) console.log(line);
-  } else {
-    console.error(`  The branch did not publish${land && land.reason ? `: ${land.reason}` : ''}. The task stays at completed with its passed grade.`);
-    console.error(`  Re-run to publish it again (the grade is not re-run): node scripts/gds/ship.js ${taskId}`);
-  }
-  const usage = await (deps.postShipSync || postShipSync)(taskId, 'confirmed');
-  // task 1004379: name the stage — at 'completed' the card would otherwise read a failed grade.
-  await (deps.printCompletionCard || printCompletionCard)({ taskId, postGradeStatus, card, usage, land, stage: 'held' });
-  return land;
-}
-
-// task 1275: sum the committed diffstat (added/removed lines) over baseline...HEAD.
-// Shared by the completion card and the in-review card. Best-effort: returns
-// nulls when there's no baseline or git is unavailable.
-function diffstatFor(baseline) {
-  if (!baseline) return { added: null, removed: null };
-  const numstat = gitOk(`git diff --numstat ${baseline}...HEAD`) || gitOk(`git diff --numstat ${baseline} HEAD`);
-  if (!numstat) return { added: null, removed: null };
-  let added = 0;
-  let removed = 0;
-  for (const line of numstat.split('\n')) {
-    const [a, r] = line.split('\t');
-    if (a !== '-' && a != null && a !== '') added += Number(a) || 0;
-    if (r !== '-' && r != null && r !== '') removed += Number(r) || 0;
-  }
-  return { added, removed };
-}
-
-// task 1270: build + print the deterministic completion card. Prints the
-// alignment-proof monospace card to stdout (always), then writes the branded
-// in-feed HTML to a temp file and prints an [otb-card-html] marker the
-// builder-ship skill picks up to render it in the chat feed. Every step is
-// best-effort — a summary card must NEVER fail or undo a completed ship.
-async function printCompletionCard({ taskId, postGradeStatus, card, usage, land = null, stage = undefined }) {
-  if (!card) return;
-  try {
-    const shipCard = require('../../modules/lifecycle/ship-card');
-
-    // Diffstat from the committed range the grader used (baseline...HEAD).
-    const fileCount = Array.isArray(card.files) && card.files.length ? card.files.length : null;
-    const { added, removed } = diffstatFor(card.baseline);
-
-    // Deployed commit (shipped only): prefer prod /version, fall back to short HEAD.
-    let commit = null;
-    let reach = null;
-    if (postGradeStatus === 'shipped') {
-      const v = fetchDeployedVersion();
-      commit = (v && v.commit) ? String(v.commit).slice(0, 7) : (gitOk('git rev-parse --short HEAD') || null);
-      // task 1004682: say WHO sees this merge — the hub's live build (read, not
-      // assumed) and the hosted-projects rule — in the merge-reach wording.
-      try {
-        reach = require('./deploy-divergence').hubReading({
-          target: resolveInstanceBase(), live: v, sha: gitOk('git rev-parse HEAD'),
-        });
-      } catch (_) { /* the card falls back to the bare commit */ }
-    }
-
-    // Running drachmae total + the builder's card-richness level (task 1279's
-    // knob, a ladder since task 1002518), both from one /me fetch (best-effort).
-    let total = null;
-    let cardFlags = cardFlagsFromMe(null);
-    try {
-      const me = noteServerReward(await (await cliClient()).me.getMe());
-      if (me.ok && me.data) {
-        if (me.data.builder) total = me.data.builder.total_credits;
-        cardFlags = cardFlagsFromMe(me);
-      }
-    } catch (_) { /* total + knob are optional; default to the standard rung */ }
-    const widgetsEnabled = cardFlags.showWidget;
-
-    // Token count + estimated cost from the session usage. Split the tokens into
-    // 'new' (fresh input + output + first-time cache writes) vs 'cached' re-reads
-    // (cache_read — the same large context re-read every turn) so the card can
-    // lead with cost and not with a single all-in count that cache re-reads make
-    // look alarmingly huge (task 1765). The per-model breakdown is already on hand
-    // via usage.modelUsage — no new server data needed.
-    let tokens = null;
-    let costUsd = null;
-    let newTokens = null;
-    let cachedTokens = null;
-    if (usage) {
-      tokens = usage.totalTokens;
-      const mu = usage.modelUsage || {};
-      let cache = 0;
-      let fresh = 0;
-      let sawUsage = false;
-      for (const u of Object.values(mu)) {
-        if (!u) continue;
-        sawUsage = true;
-        cache += Number(u.cache_read) || 0;
-        fresh += (Number(u.input) || 0) + (Number(u.output) || 0) + (Number(u.cache_creation) || 0);
-      }
-      if (sawUsage) { newTokens = fresh; cachedTokens = cache; }
-      try {
-        const { priceModelUsage } = require('../../src/bongos/llm-pricing');
-        costUsd = priceModelUsage(mu).true_cost_usd;
-      } catch (_) { /* cost is optional */ }
-    }
-
-    const cardInputs = {
-      stage, // task 1004379: 'held' from finishHeld; undefined ⇒ derived from postGradeStatus
-      postGradeStatus,
-      taskId,
-      title: card.title,
-      valueSummary: card.valueSummary,
-      notes: card.notes,
-      fileCount,
-      added,
-      removed,
-      grade: card.grade || null,
-      credits: { awarded: card.creditsAwarded, total, perTaskCredit: rewardPolicy(getServerReward()).perTaskCredit },
-      usage: { tokens, costUsd, newTokens, cachedTokens },
-      deploy: { commit, reach },
-      // task 1002541: absent (the default) ⇒ the card behaves exactly as before,
-      // which keeps every other caller — resumeMerge, the claim card, and
-      // land-watch replaying breadcrumbs written by older versions — unchanged.
-      land,
-    };
-    const model = shipCard.buildCardModel(cardInputs);
-
-    // Print the monospace card + write the branded HTML for the in-feed renderer
-    // (shared emitCard, task 1275). The skill reads the printed path and passes
-    // the contents to the visualization tool — the agent authors nothing, so the
-    // card is identical every ship. task 1002518: the resolved richness level
-    // reaches emitCard as flags — at the plain rung no HTML is written or
-    // relayed, at the minimal rung not even the monospace card is printed (the
-    // guaranteed [otb-confirm] line always is), and at the rich rung the
-    // widget's summary arrives already open.
-    shipCard.emitCard(model, taskId, { flags: cardFlags });
-
-    // task 1687: in CI deploy mode this card is 'confirmed — landing' and the real
-    // confirmed->shipped land happens minutes later, server-side — so the SHIPPED
-    // banner would never render in-session. Drop a pending-land breadcrumb; the
-    // land-watch hook renders the shipped card on a later prompt once it lands.
-    // Best-effort: a breadcrumb must never fail a ship (mirrors the card itself).
-    if (postGradeStatus === 'confirmed') {
-      // `cardFlags` carries the resolved rung so the later-rendered shipped card
-      // matches the one this session printed; `widgetsEnabled` stays beside it
-      // so a breadcrumb written by an older CLI still reads correctly.
-      try { require('./land-watch').writeBreadcrumb(taskId, { widgetsEnabled, cardFlags, cardInputs }); }
-      catch (_) { /* breadcrumb is best-effort */ }
-    }
-  } catch (_) {
-    /* a summary card must never fail a ship */
-  }
-
-  // task 1002521: the card above says SHIPPED, which means "merged". Its Deploy
-  // row says who sees that (task 1004682: the hub redeploys on every merge;
-  // hosted projects when a release carries it and their pin moves). This adds
-  // the full divergence report when live and main disagree — blocker 1000097:
-  // 171 commits sat unreleased for ten days while every layer reported success.
-  // Warn, never block — a shipped task is still shipped, and an offline builder
-  // must not be punished for it.
-  try {
-    const { check, report } = require('./deploy-divergence');
-    const r = await check();
-    if (!r.undetermined && !r.ok) report(r);
-  } catch (_) {
-    /* a divergence warning must never fail a ship */
-  }
-}
-
-// Decide whether a builder may re-grade a task via `--regrade` (#678). Pure so
-// it's unit-testable. A re-grade is allowed iff the task is stuck at `completed`
-// (a ship whose grade failed) AND the caller either last held the claim or is an
-// Archon. Every other status gets a tailored, actionable message. Note this is a
-// client-side UX guard, not a trust boundary: /tasks/:id/grade is rank-open by
-// design (the subagent grade is the authority, not builder identity).
-
-module.exports = {
-  diffstatFor,
-  finishShip,
-  finishHeld,
-  mergeAndDeploy,
-  onboardingNudgeBestEffort,
-  postShipCloseout,
-  postShipSync,
-  printCompletionCard,
-};
+require('../bongos/forwarder.js').forward(module, 'ship-finish.js');