@skyf0xx/hedgehog 6.1.3 → 6.1.5

package/bin/cli.mjs

@@ -62,6 +62,16 @@ import {
 } from '../src/db/community.mjs';
 import { rebuildDb } from '../src/db/rebuild.mjs';
 import { loadOverrides, addOverride, orphanedOverrides, OVERRIDES_DIR } from '../src/db/overrides.mjs';
+import {
+  gatherEvidence,
+  formatEvidence,
+  evidenceForTask,
+  confirmReconciliation,
+  loadReconciliations,
+  orphanedReconciliations,
+  formatReconciliations,
+  RECONCILED_DIR,
+} from '../src/db/reconcile.mjs';
 import { HOSTS, HOST_FLAGS, DEFAULT_HOST, availableHosts } from '../src/hosts/index.mjs';
 import { recordHosts, installedHosts } from '../src/hosts/installed.mjs';
 import { wrapSection } from '../src/hosts/claude-md-merge.mjs';
@@ -545,6 +555,12 @@ ${bold('Usage')}
   npx @skyf0xx/hedgehog override add <task-id> --scope <glob> [--scope <glob>...] --reason "<why>"
                                                    record a committed, additive-only scope exception for one task
   npx @skyf0xx/hedgehog override list             list recorded scope overrides
+  npx @skyf0xx/hedgehog reconcile                 propose which open tasks hand-written commits may have
+                                                   already satisfied; reads only, changes nothing
+  npx @skyf0xx/hedgehog reconcile confirm <task-id> --reason "<why>"
+                                                   close one task on your judgment — no scope gate and no
+                                                   verify command run; records it under .hedgehog/reconciled/
+  npx @skyf0xx/hedgehog reconcile list            list recorded reconciliations
   npx @skyf0xx/hedgehog intent add [flags]        add an intent (rules/requirements/dependencies)
   npx @skyf0xx/hedgehog intent add --file <path>  add an intent from a JSON file
   npx @skyf0xx/hedgehog next                      print the task packet for one ready task
@@ -1186,6 +1202,21 @@ async function dbRebuildCommand() {
   console.log(
     `${green('rebuilt')}  ${dim(`${result.intentsReplayed} intent(s) replayed, ${result.tasksMarkedComplete} task(s) marked complete`)}\n`,
   );
+  // Reported separately from the count above, not folded into it: a task
+  // closed from a committed reconciliation had no verify run behind it,
+  // and a rebuild is exactly where that distinction would otherwise
+  // vanish into a single "marked complete" number.
+  if (result.tasksReconciled > 0) {
+    console.log(
+      `${dim(`${result.tasksReconciled} task(s) replayed from ${RECONCILED_DIR}/ — closed by reconciliation, not verification`)}\n`,
+    );
+  }
+  if (result.orphanedReconciled?.length > 0) {
+    console.log(
+      `${yellow(bold('Reconciliations without a task.'))} ${result.orphanedReconciled.join(', ')} —\n` +
+        `no task with this id exists in the rebuilt graph, so each closes nothing.\n`,
+    );
+  }
   warnOrphanedNotes(result);
   warnRebuildDrift(result, corePath);
 }
@@ -3134,6 +3165,107 @@ async function overrideCommand(args) {
   process.exitCode = 1;
 }
 
+// `hedgehog reconcile` / `hedgehog reconcile confirm <task-id> --reason
+// "<why>"` / `hedgehog reconcile list` — absorbs work that landed outside
+// the loop into the build graph (see src/db/reconcile.mjs).
+//
+// The bare form only reads: it prints which commits since the newest
+// graph-written commit touched files inside each open task's scope, and
+// changes nothing. `confirm` takes exactly one task id — there is no
+// bulk form, because a single "yes to all" is the unexamined assertion
+// this command exists to avoid. Nothing else in the CLI calls into this;
+// `status`, `next`, and `claim` never reconcile on their own.
+async function reconcileCommand(args) {
+  await ensureDb();
+
+  if (!(await exists(DB_PATH))) {
+    console.error(`${red('No build graph found.')} Run ${bold('hedgehog db init')} first.\n`);
+    process.exitCode = 1;
+    return;
+  }
+
+  const sub = args[0];
+
+  if (sub === 'list') {
+    const reconciliations = await loadReconciliations();
+    const db = openDb({ readOnly: true });
+    let orphaned = [];
+    try {
+      orphaned = orphanedReconciliations(db, reconciliations);
+    } finally {
+      db.close();
+    }
+    console.log(`${formatReconciliations(reconciliations, orphaned)}\n`);
+    return;
+  }
+
+  if (sub === 'confirm') {
+    const taskId = args[1];
+    const reasonIdx = args.indexOf('--reason');
+    const reason = reasonIdx !== -1 ? args[reasonIdx + 1] : undefined;
+
+    if (!taskId || taskId.startsWith('--') || !reason) {
+      console.error(
+        `${red('Usage:')} hedgehog reconcile confirm <task-id> --reason "<why this work satisfies it>"\n`,
+      );
+      process.exitCode = 1;
+      return;
+    }
+
+    printDbTarget();
+    const db = openDb();
+    let result;
+    try {
+      const evidence = evidenceForTask(db, taskId);
+      result = await confirmReconciliation(db, { taskId, reason, evidence });
+    } catch (err) {
+      console.error(`${red('Failed to reconcile:')} ${err.message}\n`);
+      process.exitCode = 1;
+      return;
+    } finally {
+      db.close();
+    }
+
+    const file = `${RECONCILED_DIR}/${result.record.task.toLowerCase()}.json`;
+    console.log(`  ${green('complete')}  ${bold(result.record.task)} ${dim('(reconciled, not verified)')}`);
+    console.log(`  ${green('recorded')}  ${file}`);
+    if (result.unlocked.length > 0) {
+      console.log(`  ${dim(`unlocked: ${result.unlocked.join(', ')}`)}`);
+    }
+    console.log(
+      `\n  ${bold('Commit that file.')} ${dim('The build graph is derived and gitignored — an')}\n` +
+        `  ${dim('uncommitted reconciliation is reverted by the next `hedgehog db rebuild`.')}\n`,
+    );
+    return;
+  }
+
+  if (sub !== undefined) {
+    console.error(
+      `${red('Unknown reconcile subcommand:')} ${sub}\n\n` +
+        `Usage: hedgehog reconcile\n` +
+        `   or: hedgehog reconcile confirm <task-id> --reason "<why>"\n` +
+        `   or: hedgehog reconcile list\n`,
+    );
+    process.exitCode = 1;
+    return;
+  }
+
+  // Bare `hedgehog reconcile` — read only.
+  const reconciliations = await loadReconciliations();
+  const db = openDb({ readOnly: true });
+  let evidence;
+  try {
+    evidence = gatherEvidence(db, { reconciliations });
+  } catch (err) {
+    console.error(`${red('Failed to read evidence:')} ${err.message}\n`);
+    process.exitCode = 1;
+    return;
+  } finally {
+    db.close();
+  }
+  console.log(`${formatEvidence(evidence)}\n`);
+}
+
 // `hedgehog debt add <task-id> "<note>"` / `hedgehog debt list [<task-id>]`
 // — declared debt between tasks. A note recorded against a task is
 // rendered into the INHERITED DEBT section of the packet of every task
@@ -3595,6 +3727,11 @@ async function main() {
     return;
   }
 
+  if (cmd === 'reconcile') {
+    await reconcileCommand(args.slice(1));
+    return;
+  }
+
   console.error(`${red('Unknown command:')} ${cmd}\n`);
   await help();
   process.exitCode = 1;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@skyf0xx/hedgehog",
-  "version": "6.1.3",
+  "version": "6.1.5",
   "description": "Install the Hedgehog build discipline (agents + skills) into a repo, for Claude Code, Cursor, or Gemini CLI.",
   "type": "module",
   "repository": {

package/src/agents/tweaker.md

@@ -1,27 +1,29 @@
 ---
 name: tweaker
-description: Use once a core's build is complete (every task in the build graph `complete`) and the user is offered a fresh-context session to iterate. Takes post-build tweak requests one at a time from a clean context, and — separately — reviews accumulated build friction and asks the user directly for feedback, filing each as its own GitHub issue (friction as `bug`/`help wanted`, user feedback as `suggestion`), gated by explicit user approval at every step, then makes a single one-time, no-pressure mention that Hedgehog itself takes contributions via `ROADMAP.md`. Shared by every core with a Stop Condition — not the `adopted` core, which has none; there, new change-work goes straight through `hedgehog-adopt` and `hedgehog-authored-loop` instead.
+description: Use when a change request lands on a project that already has a build graph and nothing in flight (`hedgehog status --brief` names no task) — a finished build being adjusted, or an adopted repo's next piece of work — and the user is offered a fresh-context session to iterate. Takes change requests one at a time from a clean context, sizing each with the `hedgehog-daily` gate, and — separately — reviews accumulated friction and asks the user directly for feedback, filing each as its own GitHub issue (friction as `bug`/`help wanted`, user feedback as `suggestion`), gated by explicit user approval at every step, then makes a single one-time, no-pressure mention that Hedgehog itself takes contributions via `ROADMAP.md`. Shared by every core, the `adopted` core included.
 model: sonnet
 color: green
 tools: Read, Glob, Grep, Edit, Write, Bash
 ---
 
 You are the tweaker role in the Hedgehog discipline. You exist for the
-session after a build finishes: the core's own loop skill has run to its
-Stop Condition, `hedgehog status` shows every task `complete`, and the user
-now wants to adjust something — a color, a copy line, a button's
-behavior — without carrying the entire build's context into the
+session with no build in flight: `hedgehog status --brief` names no task,
+and the user now wants to change something — a color, a copy line, a
+button's behavior, or the next piece of work on a repo Hedgehog was
+adopted into — without carrying a whole build's context into the
 conversation. You start from a cleared context on purpose. Re-read the
 friction log (`hedgehog friction list`) and the commit log rather than
 expecting anything to be remembered.
 
-**Not for the `adopted` core (`.hedgehog/core.yaml` written by
-`hedgehog-adopt`).** That core has no Stop Condition and no "build
-finished" moment for you to follow — adoption is the permanent way
-change lands, not a project with an end. A request there is just the
-next unit of change-work: it goes through `hedgehog-adopt`'s "Adding the
-first (or next) change-work" and `hedgehog-authored-loop`, not through
-this agent.
+**Every core reaches you, the `adopted` core included.** You size a
+request rather than assuming it: `hedgehog-daily` reads the installed
+core's own `.hedgehog/core.yaml`, which every core has. On an adopted
+repo, a small single-layer change stops at that gate's tweak exit and is
+made and committed here; anything above that line routes onward to
+`hedgehog-adopt`'s "Adding the first (or next) change-work" and
+`hedgehog-authored-loop`, per job 1's change-work and re-plan exits
+below. Adoption is the permanent way change lands on that repo, so both
+paths stay live there indefinitely — you are not an epilogue.
 
 You have two separate jobs. Don't blend them:
 
@@ -29,23 +31,25 @@ You have two separate jobs. Don't blend them:
    way any other Hedgehog change is (read the relevant code, make the
    smallest correct change, verify it, commit it).
 2. **Review the friction log, and separately ask the user for
-   feedback**, once, at the start of your first run for this build, and
-   — for each real friction pattern and each piece of user feedback
-   actually given — walk the user through turning it into its own GitHub
-   issue against the Hedgehog repo itself (`skyf0xx/hedgehog`), never the
+   feedback**, once per batch of accumulated friction, and — for each
+   real friction pattern and each piece of user feedback actually
+   given — walk the user through turning it into its own GitHub issue
+   against the Hedgehog repo itself (`skyf0xx/hedgehog`), never the
    user's own project repo. Friction-sourced issues get `bug` and
    `help wanted`; user-feedback-sourced issues get `suggestion`.
 
-Job 2 runs once per build, not once per tweak session. If the friction
-log is empty or has already been reviewed (see Constraints), skip
-straight to job 1.
+Job 2 is triggered by the log, not by the session: it runs when at least
+three rows have been logged since the last `reviewed:` marker (see
+Constraints). Below that, skip straight to job 1 — a stray entry or two
+is not a batch worth interrupting the user for, and it stays in the log
+for the review that does fire.
 
 ## Stack (locked)
 
 None of its own — you work inside whichever core's stack is already
-installed (a shipped core's, or the stack an authored core's
-`.hedgehog/core-design.md` names — the `adopted` core never reaches you,
-per the note above), editing the same files the core's own build agents
+installed (a shipped core's, the stack an authored core's
+`.hedgehog/core-design.md` names, or the existing repo's own stack on an
+adopted core), editing the same files the core's own build agents
 would. `gh` (GitHub CLI) for issue creation only, and only against
 `skyf0xx/hedgehog`, never the project's own remote.
 
@@ -53,17 +57,17 @@ would. `gh` (GitHub CLI) for issue creation only, and only against
 
 ### Job 1 — Tweak requests
 
-**In:** a user request to change something already built (copy, a
+**In:** a user request to change something that already exists (copy, a
 style, a piece of behavior), the existing codebase, the commit log.
 **Out:** the change, verified and committed, same conventional-commit
-discipline as the rest of the build (`fix(<scope>): <what>` or
+discipline as the rest of the project (`fix(<scope>): <what>` or
 `style(<scope>): <what>`, whichever fits).
 
 **Size every request with the `hedgehog-daily` skill.** That skill owns
 the tweak / change-work / re-plan decision and its conditions, and it
 reads them against the installed core's own `.hedgehog/core.yaml` — run
-it rather than judging the size here. A completed build is extendable,
-not sealed, so a request above the tweak line gets routed, not refused.
+it rather than judging the size here. Nothing here is sealed, so a
+request above the tweak line gets routed, not refused.
 
 What each exit means for you:
 
@@ -72,11 +76,13 @@ What each exit means for you:
 - **Change-work** — route it onward. On a module axis, that is `planner`
   running `hedgehog-planning-intake`'s **Re-entry pass**, which adds
   intents for the new work without re-running planning from scratch and
-  without disturbing anything already built. A core with no module axis
-  has no intent for `planner` to add, so it goes to the **Correction
-  Protocol's post-build entry** in the core's own loop skill instead,
-  which re-runs whichever phases the change reaches and rebuilds the
-  artifact.
+  without disturbing anything already built. On the `adopted` core, that
+  is `hedgehog-adopt`'s "Adding the first (or next) change-work" and
+  `hedgehog-authored-loop`, which own change-work on that repo. A core
+  with neither a module axis nor the `adopted` core's own routing has no
+  intent for `planner` to add, so it goes to the **Correction Protocol's
+  post-build entry** in the core's own loop skill instead, which re-runs
+  whichever phases the change reaches and rebuilds the artifact.
 - **Re-plan** — the locked planning artifact no longer holds. Route to
   `planner`'s re-entry pass, or, where that artifact's failure means the
   request is a different project rather than an extension of this one,
@@ -87,10 +93,10 @@ What each exit means for you:
 
 **In:** `hedgehog friction list` (see "Friction log" below) — the
 running list of things that went wrong, caused repeated back-and-forth,
-or were implied by user feedback during the build, logged live by
+or were implied by user feedback while work was landing, logged live by
 whichever agent hit the friction, or by the orchestrating session
 itself, via `hedgehog friction add` — plus a direct question to the user
-asking whether they have any feedback on the build itself, separate from
+asking whether they have any feedback on working this way, separate from
 what the friction log shows.
 **Out:** one suggested Hedgehog GitHub issue per real, distinct friction
 pattern the log actually shows (labeled `bug` and `help wanted`), and
@@ -137,24 +143,26 @@ discipline as `.hedgehog/BMAD/`. A later related incident is its own new
 
 ## Workflow
 
-1. **Run `hedgehog status`** and check the recent commit log to confirm
-   the build actually reached its Stop Condition (every task
-   `complete`) — you're not the right agent for a build still in
-   progress.
-2. **First run only for this build** (see Constraints for how to tell):
-   run `hedgehog friction list` in full, and separately ask the user
-   directly whether they have any feedback on the build. Treat these as
+1. **Run `hedgehog status --brief`** and check the recent commit log.
+   One line, and if it names any task, work is in flight: stop — that
+   belongs to the core's own loop skill, not to you. Nothing named is
+   your entry condition, on every core.
+2. **When the friction log has a batch to review** (see Constraints for
+   how to tell): run `hedgehog friction list` in full, and separately ask
+   the user directly whether they have any feedback. Treat these as
    two independent sources feeding the same show → edit → approve →
    create sequence, each pattern/item tagged with the label its source
    determines.
-   - **Friction source.** If the log is empty: tell the user plainly
-     there's no friction on record. If it has entries: run **Detect** —
-     look for explicit user feedback about the discipline itself (not
-     the product), feedback that implies a discipline gap even where it
-     wasn't stated as a complaint, or the same kind of friction
-     recurring across different entries. A single one-off entry with no
-     recurrence and no explicit-or-implied "this should be different"
-     from the user is not a pattern; it stays in the log and move on.
+   - **Friction source.** Run **Detect** over the unreviewed rows — the
+     ones logged after the last `reviewed:` marker, which are the batch
+     that woke this job. Look for explicit user feedback about the
+     discipline itself (not the product), feedback that implies a
+     discipline gap even where it wasn't stated as a complaint, or the
+     same kind of friction recurring across different entries. A single
+     one-off entry with no recurrence and no explicit-or-implied "this
+     should be different" from the user is not a pattern; it stays in
+     the log and move on. A batch that yields no pattern at all is a
+     real outcome — say so plainly rather than manufacturing one.
      Group entries that trace to the same underlying gap into one
      pattern — don't count them as separate patterns just because
      they're separate log entries. The friction hotspots under
@@ -168,7 +176,7 @@ discipline as `.hedgehog/BMAD/`. A later related incident is its own new
      correlate so you know how much of the log the ranking covers. Each
      resulting issue is labeled `bug` and `help wanted`.
    - **User-feedback source.** Ask the user plainly whether they have any
-     feedback on the build — what went well, what didn't, anything
+     feedback on the work so far — what went well, what didn't, anything
      they'd want the discipline to do differently. If they say no or give
      nothing usable: note "no feedback given" and move on. If they give
      feedback, split it into distinct items the same way as friction
@@ -181,7 +189,8 @@ discipline as `.hedgehog/BMAD/`. A later related incident is its own new
    - Run **Ask permission to review**: state plainly how many distinct
      patterns and how many feedback items were found (as separate
      counts) and ask whether the user wants to see them. A "no" here ends
-     job 2 for this build — don't re-offer later in the same session.
+     job 2 for this batch — log the reviewed marker and don't re-offer
+     later in the same session.
    - If yes, **show exactly what will be shared, one item at a time**:
      the literal issue title and body, verbatim, as it would be filed —
      not a paraphrase of it. Include the repo it targets
@@ -201,8 +210,9 @@ discipline as `.hedgehog/BMAD/`. A later related incident is its own new
      approval on one issue is never approval for another.
    - Once every detected pattern and feedback item has been shown
      (created, edited-then-created, or declined), log the reviewed
-     marker (see Constraints) so this doesn't re-run on the next tweak
-     session for the same build.
+     marker (see Constraints). That marker is what closes this batch:
+     the rows it follows are reviewed, and the count that wakes job 2
+     again starts from zero.
    - **Once, after the above is done** (regardless of whether anything
      was actually filed): mention plainly that Hedgehog itself takes
      contributions, and that `ROADMAP.md` in the Hedgehog repo has scoped
@@ -243,7 +253,7 @@ discipline as `.hedgehog/BMAD/`. A later related incident is its own new
   split a single pattern into multiple issues just because multiple
   entries mention it.
 - A pattern that doesn't clear the "real pattern" bar (Workflow, step 2)
-  stays in the log for a future build's review — don't manufacture an
+  stays in the log for a later batch's review — don't manufacture an
   issue just to have something to show. The same applies to feedback:
   don't manufacture a suggestion issue when the user said they had none.
 - Friction-sourced issues are always labeled `bug` and `help wanted`;
@@ -253,8 +263,13 @@ discipline as `.hedgehog/BMAD/`. A later related incident is its own new
   `hedgehog friction add "reviewed: <date>, issues: <url[, url...] or
   none filed>"` (no `--task`) rather than a separate state file — one
   table, append-only, same as the rest of this file's discipline. Job 2's
-  first-run check is: does `hedgehog friction list` already end with a
-  `reviewed:` row logged after every other row currently in the log?
+  wake-up check reads that marker out of `hedgehog friction list`: count
+  the rows logged after the last `reviewed:` row (every row, when there
+  is none yet), and run job 2 only at **three or more**. The floor is
+  what makes the trigger a property of the log rather than of the
+  session — a project with no build boundary to hang "once" on still
+  gets exactly one review per accumulated batch, and a single stray
+  entry never interrupts a one-line fix.
 - Never edit or delete a prior row in the `friction` table — it's
   write-once per row, same as `.hedgehog/BMAD/`.
 - Don't expand a tweak into a rebuild. A request `hedgehog-daily` sizes
@@ -262,9 +277,9 @@ discipline as `.hedgehog/BMAD/`. A later related incident is its own new
   tweak that turns out mid-edit to reach a second layer or need a file
   that doesn't exist stops and re-enters that gate.
 - When the route is the Correction Protocol, use its **post-build entry**
-  (in this core's own loop skill): the build is already at its Stop
-  Condition, so there's no task in flight to stop and no loop to resume,
-  and the correction is fixed forward in new commits rather than by
+  (in this core's own loop skill): your entry condition is that nothing
+  is in flight, so there's no task to stop and no loop to resume, and
+  the correction is fixed forward in new commits rather than by
   reopening a `complete` task. The orchestrating session runs it and owns
   the commits, the same way `hedgehog verify` always is.
 - Don't run job 2's friction detection against anything other than

package/src/db/rebuild.mjs

@@ -2,8 +2,10 @@
 // source-of-truth files, for a fresh clone (no `.hedgehog/hedgehog.db`)
 // or after suspected corruption. The DB itself is a derived artifact:
 // everything it holds is either replayable from `.hedgehog/intents/*.json`
-// (via the same normalize/insert path `intent add`/`plan` already use) or
-// recoverable from git history (which tasks' commits already landed).
+// (via the same normalize/insert path `intent add`/`plan` already use),
+// recoverable from git history (which tasks' commits already landed), or
+// replayable from `.hedgehog/reconciled/*.json` (which tasks a user
+// confirmed as done by work git history cannot credit — reconcile.mjs).
 // What isn't recoverable — `verifications.output`, the ephemeral
 // diagnostics of a run that already passed — is an accepted loss; this
 // only reconciles `tasks.status`.
@@ -23,6 +25,13 @@ import { planTasks, CORE_MODULE } from './plan.mjs';
 import { loadCore } from './core.mjs';
 import { detectDrift } from './drift.mjs';
 import { loadOverrides, OVERRIDES_DIR } from './overrides.mjs';
+import {
+  loadReconciliations,
+  orphanedReconciliations,
+  reconciledNote,
+  RECONCILED_DIR,
+  RECONCILED_NOTE_PREFIX,
+} from './reconcile.mjs';
 
 // Alphabetical by filename, purely to make the *tie-break* deterministic
 // across machines and runs. It is NOT the replay order — see
@@ -59,9 +68,19 @@ function intentExists(db, id) {
 // so a note re-attaches to the same task the replay recompiles). A note
 // whose task no longer exists in the new graph has nowhere to live and is
 // reported rather than silently dropped.
+//
+// One class of decision row is excluded from that carry-across: the
+// provenance note a reconciliation writes (reconcile.mjs). That one DOES
+// have a committed source — `.hedgehog/reconciled/*.json` — and
+// replayReconciliations below re-writes it from that file. Carrying it
+// across as well would give a reconciled task two identical notes after
+// the first rebuild, and one more on every rebuild after that.
 function clearDerivedGraph(db) {
   const debt = db.prepare('SELECT task_id, note, logged_at FROM debt').all();
-  const decisions = db.prepare('SELECT task_id, note, logged_at FROM decisions').all();
+  const decisions = db
+    .prepare('SELECT task_id, note, logged_at FROM decisions')
+    .all()
+    .filter((row) => !row.note.startsWith(RECONCILED_NOTE_PREFIX));
   const friction = db.prepare('SELECT task_id, note, logged_at FROM friction').all();
 
   db.prepare('DELETE FROM intents').run();
@@ -312,10 +331,48 @@ function markCompletedTasks(db, commitSubjects) {
   return complete.size;
 }
 
+// Replays `.hedgehog/reconciled/*.json` — the committed record of every
+// task a user confirmed as already done by work that landed outside the
+// loop (reconcile.mjs).
+//
+// This runs after markCompletedTasks and does the same job by a different
+// route. markCompletedTasks credits a task only when some commit subject
+// matches its `commit_message` exactly, which is the subject `verify`
+// itself writes — a hand-written commit never matches, by construction,
+// which is the whole reason reconcile exists. So a reconciled task needs
+// no commit-message match here: the committed confirmation IS the source,
+// exactly as an override file is the source for a widened scope.
+//
+// Without this step a rebuild silently reverts every confirmed
+// reconciliation and reintroduces the problem reconcile was run to fix,
+// which is worse than never reconciling — it looks like it worked.
+//
+// The provenance note is re-written here too, so a reconciled task's
+// "closed without a verify run" fact reaches its dependents' packets on a
+// fresh clone the same as it did on the machine that confirmed it.
+function replayReconciliations(db, reconciliations) {
+  const setComplete = db.prepare(
+    "UPDATE tasks SET status = 'complete', blocked_reason = NULL WHERE id = ?",
+  );
+  const insertNote = db.prepare('INSERT INTO decisions (task_id, note) VALUES (?, ?)');
+  const taskExists = db.prepare('SELECT 1 FROM tasks WHERE id = ?');
+
+  let replayed = 0;
+  for (const [taskId, record] of reconciliations) {
+    if (taskExists.get(taskId) === undefined) continue;
+    setComplete.run(taskId);
+    insertNote.run(taskId, reconciledNote(record));
+    replayed++;
+  }
+  return replayed;
+}
+
 // Rebuilds `db` from scratch: schema, then every committed intent
 // replayed in dependency order, then planTasks to re-derive tasks +
 // dependencies, then git history to reconcile which tasks already
-// completed. Returns a summary for the CLI to print.
+// completed, then `.hedgehog/reconciled/*.json` for the tasks a user
+// confirmed as done by work that git history cannot credit. Returns a
+// summary for the CLI to print.
 //
 // `drift` in the return is the honest disclosure this rebuild owes its
 // caller. A rebuild re-derives every task's layer-derived fields from
@@ -330,7 +387,12 @@ function markCompletedTasks(db, commitSubjects) {
 // of something they discover three layers later.
 export async function rebuildDb(
   db,
-  { corePath, intentsDir = INTENTS_DIR, overridesDir = OVERRIDES_DIR } = {},
+  {
+    corePath,
+    intentsDir = INTENTS_DIR,
+    overridesDir = OVERRIDES_DIR,
+    reconciledDir = RECONCILED_DIR,
+  } = {},
 ) {
   applySchema(db);
 
@@ -340,15 +402,26 @@ export async function rebuildDb(
 
   const core = await loadCore(corePath);
   const overrides = await loadOverrides(overridesDir);
+  const reconciliations = await loadReconciliations(reconciledDir);
 
   planTasks(db, core, overrides);
 
   const commitSubjects = loadCommitSubjects();
   const tasksMarkedComplete = markCompletedTasks(db, commitSubjects);
 
+  const tasksReconciled = replayReconciliations(db, reconciliations);
+  const orphanedReconciled = orphanedReconciliations(db, reconciliations);
+
   const orphanedNotes = restoreNotes(db, notes);
 
   const drift = detectDrift(db, core, { overrides });
 
-  return { intentsReplayed, tasksMarkedComplete, orphanedNotes, drift };
+  return {
+    intentsReplayed,
+    tasksMarkedComplete,
+    tasksReconciled,
+    orphanedReconciled,
+    orphanedNotes,
+    drift,
+  };
 }

package/src/db/reconcile.mjs

@@ -0,0 +1,591 @@
+// `hedgehog reconcile` — absorbs work that landed outside the loop into
+// the build graph, on the user's word rather than on the engine's.
+//
+// `hedgehog claim` fingerprints the working tree at claim time and
+// `verify` excludes every path that did not move during the lease
+// (claim.mjs, verify.mjs#attributedToTask), so a hand edit is correctly
+// never *blamed* on a task. It is also never *credited* to one.
+// `hedgehog db rebuild` does not close that gap either: it recovers
+// `tasks.status` by matching each task's `commit_message` against commit
+// subjects exactly (rebuild.mjs#markCompletedTasks), and that subject is
+// the one `verify` itself writes from core.yaml. A hand-written commit
+// never matches, by construction. So `hedgehog next` and `hedgehog
+// status` point at work that is already done, and the only remaining
+// moves are to redo the work through the loop or to hand-patch a task row
+// — which every loop skill forbids, because the graph is derived and
+// gitignored and the patch dies at the next rebuild.
+//
+// Four properties, each load-bearing:
+//
+//   - **It proposes; it never asserts.** `gatherEvidence` reports which
+//     commits since the newest graph-written commit touched files inside
+//     an open task's compiled scope_globs. A diff cannot tell you a
+//     task's intent was met, so nothing here closes a task on its own.
+//   - **The user confirms one task at a time.** `confirmReconciliation`
+//     takes exactly one task id and one reason. There is deliberately no
+//     bulk confirm: a single "yes to all" is exactly the unexamined
+//     assertion the evidence path refuses to make.
+//   - **A confirmed task records why.** Closing a task from reconciliation
+//     is not the fact `verify` records: no scope gate ran and no verify
+//     command ran. That distinction is inherited context for everything
+//     downstream, so `applyReconciliation` writes it as a `decisions` row
+//     (decision.mjs) which next.mjs renders into every dependent task's
+//     packet.
+//   - **It survives a rebuild.** The confirmation is a committed file
+//     under `.hedgehog/reconciled/`, in the same shape overrides.mjs uses
+//     for the same reason: a decision with no other committed source has
+//     to be replayable, or the next `db rebuild` silently reverts it and
+//     reintroduces the problem. `rebuild.mjs` replays these alongside
+//     `.hedgehog/overrides/*.json`.
+//
+// It never runs on its own. No `status`, `next`, or `claim` path calls
+// into this file — reconciliation is a deliberate act, because it is the
+// one way a task reaches `complete` without the engine having checked
+// anything.
+
+import { readdir, readFile, mkdir, writeFile, rename, rm } from 'node:fs/promises';
+import { execFileSync } from 'node:child_process';
+import { applySchema } from './schema.mjs';
+
+export const RECONCILED_DIR = '.hedgehog/reconciled';
+
+// The note attached to a reconciled task, and the prefix every such note
+// carries. next.mjs renders `decisions` rows into each dependent task's
+// INHERITED DECISIONS section, so a dependent's packet says outright that
+// its prerequisite closed unverified. The prefix is also how the replay
+// and the status surface recognize their own rows without a second table.
+export const RECONCILED_NOTE_PREFIX = 'Closed by reconciliation, not verification';
+
+export function reconciledNote(record) {
+  return (
+    `${RECONCILED_NOTE_PREFIX}: ${record.reason} ` +
+    `(no scope gate and no verify command ran; evidence: ${record.evidence.commits.length} commit(s), ` +
+    `${record.evidence.paths.length} path(s) in scope)`
+  );
+}
+
+function reconciledFilePath(taskId, reconciledDir = RECONCILED_DIR) {
+  return `${reconciledDir}/${taskId.toLowerCase()}.json`;
+}
+
+// Runs git with an argv array and no shell, so a path or a glob reaches
+// git as one literal argument — the same rule verify.mjs#git follows for
+// the same reason.
+function git(args, options = {}) {
+  return execFileSync('git', args, { encoding: 'utf8', ...options });
+}
+
+// Validates one parsed reconciliation record. Throws with the offending
+// file's path, since this runs at load time over the whole directory and
+// a bad record has to name itself to be findable — overrides.mjs's
+// validateOverride, same contract.
+function validateReconciled(record, path) {
+  if (record === null || typeof record !== 'object') {
+    throw new Error(`${path}: reconciliation must be a JSON object`);
+  }
+  let { task } = record;
+  const { reason, confirmed_at: confirmedAt, evidence } = record;
+
+  if (!task || typeof task !== 'string') {
+    throw new Error(`${path}: reconciliation requires a "task" id (string)`);
+  }
+  // plan.mjs#taskId upper-cases every id it compiles a task under, and
+  // the replay looks tasks up by that exact string. Normalizing here,
+  // once, keeps the id space exact-match everywhere else — the same
+  // reason overrides.mjs normalizes.
+  task = task.toUpperCase();
+
+  if (!reason || typeof reason !== 'string') {
+    throw new Error(
+      `${path}: reconciliation "${task}" requires a "reason" (string) — this is the permanent record of why a task closed without a verify run`,
+    );
+  }
+  if (!confirmedAt || typeof confirmedAt !== 'string') {
+    throw new Error(`${path}: reconciliation "${task}" requires a "confirmed_at" timestamp (string)`);
+  }
+  if (evidence === null || typeof evidence !== 'object' || Array.isArray(evidence)) {
+    throw new Error(`${path}: reconciliation "${task}" requires an "evidence" object`);
+  }
+  for (const field of ['commits', 'paths']) {
+    if (!Array.isArray(evidence[field])) {
+      throw new Error(`${path}: reconciliation "${task}" requires "evidence.${field}" (array)`);
+    }
+    for (const entry of evidence[field]) {
+      if (typeof entry !== 'string' || entry.trim() === '') {
+        throw new Error(
+          `${path}: reconciliation "${task}" has a non-string or empty entry in evidence.${field}`,
+        );
+      }
+    }
+  }
+
+  return {
+    task,
+    reason,
+    confirmed_at: confirmedAt,
+    evidence: { commits: [...evidence.commits], paths: [...evidence.paths] },
+  };
+}
+
+// Every *.json in `reconciledDir`, validated, as a Map from task id to
+// its record. One file per task: a second confirmation of the same task
+// is a mistake rather than a second distinct fact, unlike an override,
+// where two separately-reasoned widenings of one task are both real.
+// Absent directory reads as "nothing reconciled", the same way
+// overrides.mjs#loadOverrides treats a missing overrides directory.
+export async function loadReconciliations(reconciledDir = RECONCILED_DIR) {
+  let entries;
+  try {
+    entries = await readdir(reconciledDir);
+  } catch {
+    return new Map();
+  }
+
+  const byTask = new Map();
+  for (const name of entries.filter((n) => n.endsWith('.json')).sort()) {
+    const path = `${reconciledDir}/${name}`;
+    let parsed;
+    try {
+      parsed = JSON.parse(await readFile(path, 'utf8'));
+    } catch (err) {
+      throw new Error(`could not read reconciliation file ${path}: ${err.message}`);
+    }
+    const record = validateReconciled(parsed, path);
+    byTask.set(record.task, record);
+  }
+  return byTask;
+}
+
+// Reconciled task ids matching no row in `tasks` — a typo'd id, a task
+// from a renamed module or layer, or one whose intent file is gone. The
+// read side that keeps a dead record discoverable, exactly as
+// overrides.mjs#orphanedOverrides does: the replay skipping an unknown id
+// is a no-op, not a throw, so without this the file would sit there
+// closing nothing forever.
+export function orphanedReconciliations(db, reconciliations) {
+  const known = new Set(db.prepare('SELECT id FROM tasks').all().map((r) => r.id));
+  return [...reconciliations.keys()].filter((taskId) => !known.has(taskId)).sort();
+}
+
+// ── evidence ──────────────────────────────────────────────────────────
+
+// The newest commit the graph itself wrote — the newest commit whose
+// subject matches some task's `commit_message`, which is the exact
+// predicate rebuild.mjs#markCompletedTasks uses to decide a task ran.
+// Everything above it in history is the window this command reads: it is
+// where hand-written work necessarily sits, because a graph-written
+// commit below it has already been credited by rebuild.
+//
+// Returns null when no commit matches any task's message (nothing has
+// been verified yet) — the caller then reads the whole history, which is
+// the honest window for a project whose loop has not closed a task.
+function newestGraphCommit(db) {
+  const messages = new Set(
+    db.prepare('SELECT commit_message FROM tasks').all().map((r) => r.commit_message),
+  );
+  if (messages.size === 0) return null;
+
+  const output = git(['log', '--topo-order', '--format=%H%x00%s']);
+  for (const line of output.split('\n')) {
+    if (!line) continue;
+    const [sha, subject] = line.split('\0');
+    if (subject !== undefined && messages.has(subject)) return sha;
+  }
+  return null;
+}
+
+// Every commit after `sinceSha` (exclusive), newest first, with the paths
+// it touched. `sinceSha` null means the whole history.
+function commitsSince(sinceSha) {
+  const range = sinceSha ? [`${sinceSha}..HEAD`] : ['HEAD'];
+  let output;
+  try {
+    output = git(['log', '--topo-order', '--name-only', '--format=%x01%H%x00%s', ...range]);
+  } catch {
+    // An empty repository has no HEAD to log.
+    return [];
+  }
+
+  const commits = [];
+  for (const block of output.split('\x01')) {
+    if (!block.trim()) continue;
+    const [header, ...rest] = block.split('\n');
+    const [sha, subject] = header.split('\0');
+    if (!sha) continue;
+    const paths = rest.map((p) => p.trim()).filter(Boolean);
+    commits.push({ sha, subject: subject ?? '', paths });
+  }
+  return commits;
+}
+
+// True when `path` matches `glob`.
+//
+// The scope globs compiled onto a task are git pathspec globs
+// (`apps/api/src/orders/**`), and verify.mjs's gate hands them straight
+// to git as `:(glob)…` pathspecs. Here the paths already came out of `git
+// log --name-only`, so there is no second git call to make: the match is
+// done in-process against the same syntax git implements — `**` spans
+// separators, a single `*` and `?` do not, and a trailing `/**` also
+// matches the directory's own path, which is what makes a glob and the
+// directory it names agree.
+//
+// Segment-by-segment rather than character-by-character, so the two `**`
+// forms (a whole segment, versus a `*` pair inside one) can't be confused
+// for each other.
+function globToRegExp(glob) {
+  const escape = (s) => s.replace(/[.*+?^${}()|[\]\\]/g, '\\$&');
+
+  // A `*` or `?` inside one path segment never crosses a separator.
+  const segmentPattern = (segment) =>
+    segment
+      .split(/(\*|\?)/)
+      .map((part) => (part === '*' ? '[^/]*' : part === '?' ? '[^/]' : escape(part)))
+      .join('');
+
+  const segments = glob.split('/');
+  let out = '';
+  for (const [i, segment] of segments.entries()) {
+    if (segment === '**') {
+      // `**` and the separator on one side of it are optional together,
+      // so `a/**` also matches `a` and `**/x.ts` also matches `x.ts`.
+      if (i === segments.length - 1) {
+        // Trailing: the separator *before* it goes optional with it —
+        // unless there is nothing before it, and the glob is the bare
+        // `**` that matches everything.
+        out += i === 0 ? '.*' : '(?:/.*)?';
+      } else {
+        // Interior or leading: the separator *after* it goes optional
+        // with it. A preceding literal segment still needs its own
+        // separator written first.
+        if (i > 0) out += '/';
+        out += '(?:.*/)?';
+      }
+      continue;
+    }
+    // Only a preceding literal segment contributes the separator — a
+    // preceding `**` already carried its own.
+    if (i > 0 && segments[i - 1] !== '**') out += '/';
+    out += segmentPattern(segment);
+  }
+
+  return new RegExp(`^${out}$`);
+}
+
+export function pathInScope(path, scopeGlobs) {
+  return scopeGlobs.some((glob) => globToRegExp(glob).test(path));
+}
+
+// Tasks a reconciliation could apply to: `planned` or `ready`, the two
+// statuses `hedgehog next` would still hand out. A `building`/`verifying`
+// task is leased and belongs to whoever holds it; a `blocked` task failed
+// a gate the loop already ran and has `retry` as its way back; a
+// `complete` task is done.
+const OPEN_TASKS_SQL = `
+  SELECT id, layer, module, objective, scope_globs, status
+  FROM tasks
+  WHERE status IN ('planned', 'ready')
+  ORDER BY priority, id;
+`;
+
+// The read path. For every open task, which of the commits since the
+// newest graph-written commit touched files inside that task's compiled
+// scope_globs.
+//
+// Returns { since, commits, candidates, alreadyReconciled }:
+//   - `since` the sha the window starts above, or null for whole history
+//   - `commits` every commit in the window (so a caller can report a
+//     window that contained nothing)
+//   - `candidates` one entry per open task with at least one matching
+//     path: { task, commits: [{sha, subject, paths}], paths }
+//   - `alreadyReconciled` open task ids that already have a committed
+//     confirmation on disk (their file exists but the graph has not been
+//     rebuilt since)
+//
+// This is evidence, not proof. A commit touching a task's scope says
+// files moved where that task would have moved them; it says nothing
+// about whether the task's objective was met. Every caller must put the
+// judgment to the user.
+export function gatherEvidence(db, { reconciliations = new Map() } = {}) {
+  const since = newestGraphCommit(db);
+  const commits = commitsSince(since);
+  const openTasks = db.prepare(OPEN_TASKS_SQL).all();
+
+  const candidates = [];
+  const alreadyReconciled = [];
+  for (const task of openTasks) {
+    if (reconciliations.has(task.id)) alreadyReconciled.push(task.id);
+
+    const scopeGlobs = JSON.parse(task.scope_globs);
+    const matched = [];
+    const paths = new Set();
+    for (const commit of commits) {
+      const hits = commit.paths.filter((p) => pathInScope(p, scopeGlobs));
+      if (hits.length === 0) continue;
+      matched.push({ sha: commit.sha, subject: commit.subject, paths: hits });
+      for (const p of hits) paths.add(p);
+    }
+    if (matched.length > 0) {
+      candidates.push({ task, commits: matched, paths: [...paths].sort() });
+    }
+  }
+
+  return { since, commits, candidates, alreadyReconciled };
+}
+
+// ── confirmation ──────────────────────────────────────────────────────
+
+// Writes one reconciliation record to
+// RECONCILED_DIR/<task-id-lowercased>.json via temp file + rename, so a
+// crash mid-write can never leave a half-written file for
+// loadReconciliations to trip on — overrides.mjs#writeOverrideFile and
+// intent.mjs#writeIntentFile use the same pattern for the same reason.
+//
+// Refuses to overwrite silently. A task is reconciled once; a second
+// confirmation for the same id is a wrong id or a forgotten first run,
+// and either is worth stopping for.
+export async function writeReconciledFile(record, reconciledDir = RECONCILED_DIR) {
+  const path = reconciledFilePath(record.task, reconciledDir);
+  try {
+    await readFile(path, 'utf8');
+    throw new Error(
+      `${path} already exists — ${record.task} is already recorded as reconciled. Edit that file directly rather than re-confirming.`,
+    );
+  } catch (err) {
+    if (!err || err.code !== 'ENOENT') throw err;
+  }
+
+  await mkdir(reconciledDir, { recursive: true });
+  const tempPath = `${path}.tmp-${process.pid}`;
+  try {
+    await writeFile(tempPath, `${JSON.stringify(record, null, 2)}\n`);
+    await rename(tempPath, path);
+  } catch (err) {
+    await rm(tempPath, { force: true }).catch(() => {});
+    throw err;
+  }
+  return record;
+}
+
+// Applies one confirmed reconciliation to the graph: the task goes
+// `complete`, its provenance note is written as a `decisions` row, and
+// its dependents are re-evaluated for readiness the same way verify.mjs
+// does on a pass.
+//
+// Marking the status directly is correct here for the same reason
+// rebuild.mjs#markCompletedTasks does it: there is no lease to check, no
+// working-tree diff to gate, and no verify_command to run. The difference
+// from verify is exactly what the note records.
+export function applyReconciliation(db, record) {
+  applySchema(db);
+
+  const task = db.prepare('SELECT id, status FROM tasks WHERE id = ?').get(record.task);
+  if (!task) throw new Error(`no such task: ${record.task}`);
+  if (task.status === 'complete') return { taskId: record.task, unlocked: [], alreadyComplete: true };
+  if (task.status === 'building' || task.status === 'verifying') {
+    throw new Error(
+      `Task ${record.task} is leased (${task.status}) — release it with \`hedgehog release ${record.task} --owner <owner>\` before reconciling it.`,
+    );
+  }
+
+  let unlocked;
+  db.exec('BEGIN IMMEDIATE');
+  try {
+    db.prepare(
+      "UPDATE tasks SET status = 'complete', blocked_reason = NULL WHERE id = ?",
+    ).run(record.task);
+    db.prepare('INSERT INTO decisions (task_id, note) VALUES (?, ?)').run(
+      record.task,
+      reconciledNote(record),
+    );
+    unlocked = unlockDependents(db, record.task);
+    completeIntentIfDone(db, record.task);
+    db.exec('COMMIT');
+  } catch (err) {
+    try {
+      db.exec('ROLLBACK');
+    } catch {
+      // Rollback failing must not mask the original error.
+    }
+    throw err;
+  }
+
+  return { taskId: record.task, unlocked, alreadyComplete: false };
+}
+
+// Marks `taskId`'s direct dependents `ready` wherever every one of their
+// dependencies is now complete — the same rule and the same restriction
+// verify.mjs#unlockReadyDependents applies: a dependent already `blocked`
+// is stalled on its own failure, not on this dependency, and must not be
+// cleared back to ready here.
+function unlockDependents(db, taskId) {
+  const dependents = db
+    .prepare(
+      `SELECT t.id, t.status FROM tasks t
+       JOIN dependencies d ON d.task_id = t.id
+       WHERE d.depends_on_task_id = ?
+       ORDER BY t.priority, t.id`,
+    )
+    .all(taskId);
+
+  const unlocked = [];
+  for (const dependent of dependents) {
+    if (dependent.status !== 'planned') continue;
+    const blocker = db
+      .prepare(
+        `SELECT 1 FROM dependencies d
+         JOIN tasks dep ON dep.id = d.depends_on_task_id
+         WHERE d.task_id = ? AND dep.status <> 'complete'`,
+      )
+      .get(dependent.id);
+    if (blocker !== undefined) continue;
+    db.prepare("UPDATE tasks SET status = 'ready' WHERE id = ?").run(dependent.id);
+    unlocked.push(dependent.id);
+  }
+  return unlocked;
+}
+
+// Closes the task's intent once every task compiled from it is complete
+// — the same terminal bookkeeping verify.mjs#completeIntentIfDone does,
+// so an intent whose last open task closes by reconciliation does not sit
+// `active` forever.
+function completeIntentIfDone(db, taskId) {
+  const row = db.prepare('SELECT intent_id FROM tasks WHERE id = ?').get(taskId);
+  if (!row) return;
+  const openTask = db
+    .prepare("SELECT 1 FROM tasks WHERE intent_id = ? AND status <> 'complete'")
+    .get(row.intent_id);
+  if (openTask !== undefined) return;
+  db.prepare("UPDATE intents SET status = 'complete' WHERE id = ?").run(row.intent_id);
+}
+
+// The `hedgehog reconcile confirm <task-id> --reason "<why>"` entry
+// point: builds the record from the task's own evidence, writes the
+// committed file first, then applies it to the graph.
+//
+// File before graph, deliberately. The graph is derived and gitignored;
+// the file is the permanent record. If the write fails, nothing has been
+// closed on a fact that would not survive the next rebuild.
+export async function confirmReconciliation(
+  db,
+  { taskId, reason, evidence },
+  reconciledDir = RECONCILED_DIR,
+) {
+  if (!taskId) throw new Error('reconcile requires a task id');
+  if (!reason) throw new Error('reconcile requires a --reason');
+
+  const id = taskId.toUpperCase();
+  const task = db.prepare('SELECT id, status FROM tasks WHERE id = ?').get(id);
+  if (!task) throw new Error(`no such task: ${id}`);
+  if (task.status === 'complete') {
+    throw new Error(`Task ${id} is already complete — there is nothing to reconcile.`);
+  }
+
+  const record = validateReconciled(
+    {
+      task: id,
+      reason,
+      confirmed_at: new Date().toISOString(),
+      evidence: {
+        commits: evidence?.commits ?? [],
+        paths: evidence?.paths ?? [],
+      },
+    },
+    '(new reconciliation)',
+  );
+
+  await writeReconciledFile(record, reconciledDir);
+  const applied = applyReconciliation(db, record);
+  return { record, ...applied };
+}
+
+// Evidence for exactly one task, in the shape confirmReconciliation
+// wants. Returns null when that task is not an open candidate — a caller
+// confirming a task the evidence path never proposed still gets to
+// record the confirmation, with an empty evidence set that says so.
+export function evidenceForTask(db, taskId) {
+  const { candidates } = gatherEvidence(db);
+  const entry = candidates.find((c) => c.task.id === taskId.toUpperCase());
+  if (!entry) return null;
+  return {
+    commits: entry.commits.map((c) => c.sha),
+    paths: entry.paths,
+  };
+}
+
+// ── rendering ─────────────────────────────────────────────────────────
+
+// Renders a gatherEvidence() result as a proposal. Every line is written
+// to read as a question the user answers, not as a finding the command
+// acted on — the confirm command is printed per task, one at a time, and
+// no "confirm all" form exists to print.
+export function formatEvidence({ since, commits, candidates, alreadyReconciled }) {
+  const lines = [];
+
+  lines.push(
+    since
+      ? `Reading ${commits.length} commit(s) since ${since.slice(0, 8)} — the newest commit the build graph itself wrote.`
+      : `Reading ${commits.length} commit(s) — no commit in this history was written by the build graph.`,
+  );
+  lines.push('');
+
+  if (candidates.length === 0) {
+    lines.push('No open task has files in its scope touched by those commits.');
+    lines.push('');
+    lines.push('Nothing to propose. No task was changed.');
+    return lines.join('\n');
+  }
+
+  lines.push('PROPOSED — evidence only. None of these tasks has been changed.');
+  lines.push('');
+  for (const { task, commits: matched, paths } of candidates) {
+    lines.push(`  ${task.id}   ${task.layer}   ${task.objective}`);
+    for (const commit of matched) {
+      lines.push(`    ${commit.sha.slice(0, 8)}  ${commit.subject}`);
+    }
+    for (const path of paths) {
+      lines.push(`      in scope: ${path}`);
+    }
+    lines.push('');
+  }
+
+  lines.push('A commit touching a task\'s scope is not proof the task\'s objective was met.');
+  lines.push('Read the work, then confirm each task you judge done, one at a time:');
+  lines.push('');
+  lines.push('  hedgehog reconcile confirm <task-id> --reason "<why this work satisfies it>"');
+  lines.push('');
+  lines.push('Confirming closes the task without a scope gate or a verify run, and records');
+  lines.push(`that in ${RECONCILED_DIR}/<task-id>.json — commit that file, or the next`);
+  lines.push('`hedgehog db rebuild` reverts the reconciliation.');
+
+  if (alreadyReconciled.length > 0) {
+    lines.push('');
+    lines.push('ALREADY CONFIRMED (still open in this graph — run `hedgehog db rebuild`)');
+    for (const taskId of alreadyReconciled) lines.push(`  ${taskId}`);
+  }
+
+  return lines.join('\n');
+}
+
+// Renders loadReconciliations() as a listing — `hedgehog reconcile list`.
+export function formatReconciliations(reconciliations, orphaned = []) {
+  if (reconciliations.size === 0) return 'No reconciliations recorded.';
+
+  const lines = [];
+  for (const [taskId, record] of reconciliations) {
+    lines.push(taskId);
+    lines.push(`  ${record.reason}`);
+    lines.push(`  confirmed ${record.confirmed_at}`);
+    for (const sha of record.evidence.commits) lines.push(`  commit ${sha.slice(0, 8)}`);
+    for (const path of record.evidence.paths) lines.push(`  path   ${path}`);
+    lines.push('');
+  }
+
+  if (orphaned.length > 0) {
+    lines.push(
+      `Orphaned: ${orphaned.join(', ')} — no task with this id exists in the build graph. ` +
+        `Each closes nothing until the id matches.`,
+    );
+  }
+
+  return lines.join('\n').trimEnd();
+}

package/src/db/status.mjs

@@ -15,6 +15,7 @@ import { listDebt } from './debt.mjs';
 import { detectDrift, formatDrift } from './drift.mjs';
 import { listFriction } from './friction.mjs';
 import { orphanedOverrides } from './overrides.mjs';
+import { RECONCILED_DIR, RECONCILED_NOTE_PREFIX } from './reconcile.mjs';
 import { formatMissingRequirements } from './requires.mjs';
 import { readyTasks, heldBackReason } from './ready.mjs';
 
@@ -123,6 +124,34 @@ function loadDebtByTask(db) {
     .sort((a, b) => a.taskId.localeCompare(b.taskId));
 }
 
+// Every task that reached `complete` through `hedgehog reconcile` rather
+// than through `hedgehog verify`, in task-id order.
+//
+// A reconciled task is `complete` like any other, so it is invisible in
+// the counts above and in every list below them — and it is the one
+// `complete` status the engine never checked: no scope gate ran and no
+// verify command ran on it. Reading it back off the provenance note
+// reconcile.mjs writes (a `decisions` row carrying
+// RECONCILED_NOTE_PREFIX) keeps that fact in one place rather than adding
+// a task column that every other command would then have to know about,
+// and it survives a rebuild for free, since the replay re-writes the same
+// note from the committed file.
+function loadReconciledTasks(db) {
+  try {
+    return db
+      .prepare(
+        `SELECT DISTINCT d.task_id AS taskId, t.layer AS layer
+         FROM decisions d JOIN tasks t ON t.id = d.task_id
+         WHERE d.note LIKE ? || '%'
+         ORDER BY d.task_id`,
+      )
+      .all(RECONCILED_NOTE_PREFIX);
+  } catch {
+    // No `decisions` table yet (a build graph from before it existed).
+    return [];
+  }
+}
+
 // The friction row count, or 0. `listFriction` reads the table
 // unguarded, so a build graph predating it throws here where `listDebt`
 // would return [] — caught rather than propagated for the same reason
@@ -138,7 +167,7 @@ function countFriction(db) {
 }
 
 // Returns { counts, ready, heldBack, inFlight, attention, drift,
-// orphanedOverrides, debt, frictionCount, total } —
+// orphanedOverrides, debt, frictionCount, reconciled, total } —
 // counts keyed by every status in the tasks CHECK constraint (present
 // even at zero), ready the full list of currently-pickable tasks,
 // heldBack the subset of those that `hedgehog claim` would skip over
@@ -181,6 +210,14 @@ function countFriction(db) {
 // only the existence signal: `debt list` needs a task id the operator
 // has no way to guess, and `friction list` needs the operator to
 // already suspect there is something to read.
+//
+// `reconciled` is the tasks that reached `complete` through `hedgehog
+// reconcile` rather than through `hedgehog verify`. Those are the only
+// `complete` tasks the engine never checked — no scope gate, no verify
+// command — and they are otherwise indistinguishable from verified ones
+// in every count and list here. Reported unconditionally, not as a
+// warning: reconciling is a supported act, and the point is that the
+// distinction stays visible after the session that made it is gone.
 export function graphStatus(db, { core = null, overrides = new Map() } = {}) {
   const counts = countTasksByStatus(db);
   const ready = loadReadyTasks(db);
@@ -191,6 +228,7 @@ export function graphStatus(db, { core = null, overrides = new Map() } = {}) {
   const orphaned = orphanedOverrides(db, overrides);
   const debt = loadDebtByTask(db);
   const frictionCount = countFriction(db);
+  const reconciled = loadReconciledTasks(db);
   const total = Object.values(counts).reduce((a, b) => a + b, 0);
   return {
     counts,
@@ -202,6 +240,7 @@ export function graphStatus(db, { core = null, overrides = new Map() } = {}) {
     orphanedOverrides: orphaned,
     debt,
     frictionCount,
+    reconciled,
     total,
   };
 }
@@ -216,8 +255,9 @@ const BLOCKED_REASON_LABELS = {
 // status (only non-zero ones, in lifecycle order), any declared binary
 // this environment can't resolve, the ready list, tasks currently in
 // flight, anything needing attention, core.yaml drift, overrides
-// pointing at no task, and what has been recorded in the two
-// append-only side channels (declared debt, logged friction).
+// pointing at no task, what has been recorded in the two append-only
+// side channels (declared debt, logged friction), and which complete
+// tasks closed by reconciliation rather than by verification.
 //
 // `missingRequirements` comes from the core definition rather than the
 // database (src/db/requires.mjs#coreMissingRequirements), so the caller
@@ -235,6 +275,7 @@ export function formatStatus({
   orphanedOverrides = [],
   debt = [],
   frictionCount = 0,
+  reconciled = [],
   total,
   missingRequirements,
 }) {
@@ -346,5 +387,22 @@ export function formatStatus({
     lines.push('  Reviewed as a batch at the end of a build. See: hedgehog friction list');
   }
 
+  // Last, because it is the only section here that reports something
+  // already settled rather than something outstanding. It is reported at
+  // all because a reconciled task is `complete` in every count above and
+  // is the one `complete` the engine never checked — the distinction is
+  // invisible without this line, and it is exactly what a reader deciding
+  // how much to trust the graph needs.
+  if (reconciled.length > 0) {
+    lines.push('');
+    lines.push(`CLOSED BY RECONCILIATION  ${reconciled.length}`);
+    for (const { taskId, layer } of reconciled) {
+      lines.push(`  ${taskId}   ${layer}   confirmed by the user, not verified`);
+    }
+    lines.push('');
+    lines.push(`  No scope gate and no verify command ran on these. Recorded in ${RECONCILED_DIR}/.`);
+    lines.push('  See: hedgehog reconcile list');
+  }
+
   return lines.join('\n');
 }

package/src/db/verify.mjs

@@ -63,19 +63,21 @@ import { reapExpiredLeases, pathFingerprint } from './claim.mjs';
 import { ensureTaskColumns } from './schema.mjs';
 import { FRICTION_DIR } from './friction.mjs';
 import { OVERRIDES_DIR } from './overrides.mjs';
+import { RECONCILED_DIR } from './reconcile.mjs';
 import { INTENTS_DIR } from './intent.mjs';
 import { COMMUNITY_PATH } from './community.mjs';
 
 // Build-graph state directories: written by their own command
-// (`friction add`, `override add`, `intent add`/`db rebuild`), committed
-// by that command's own next step, never by a layer's verify_command. A
+// (`friction add`, `override add`, `intent add`/`db rebuild`, `reconcile
+// confirm`), committed by that command's own next step, never by a
+// layer's verify_command. A
 // layer's own work never lands here, so a path under one of these is
 // never this task's doing regardless of when it changed relative to
 // claim time — unlike attributedToTask's fingerprint check, which only
 // excludes a path unchanged since claim and so still attributes a
 // friction note logged mid-layer (exactly what the loop skill instructs)
 // to whichever task happened to be building when it was logged.
-const BUILD_GRAPH_STATE_DIRS = [FRICTION_DIR, OVERRIDES_DIR, INTENTS_DIR];
+const BUILD_GRAPH_STATE_DIRS = [FRICTION_DIR, OVERRIDES_DIR, INTENTS_DIR, RECONCILED_DIR];
 
 function isBuildGraphStatePath(path) {
   return BUILD_GRAPH_STATE_DIRS.some((dir) => path === dir || path.startsWith(`${dir}/`));

package/src/hosts/gemini/gemini-extension.json

@@ -1,6 +1,6 @@
 {
   "name": "hedgehog",
-  "version": "6.1.3",
+  "version": "6.1.5",
   "description": "Hedgehog build discipline: ordered, tested, verified build steps.",
   "contextFileName": "GEMINI.md"
 }