simt-dev 0.3.1__tar.gz → 0.4.0__tar.gz

{simt_dev-0.3.1 → simt_dev-0.4.0}/CHANGELOG.md

@@ -6,6 +6,114 @@ All notable changes to this package are recorded here. The format follows
 
 ## [Unreleased]
 
+## [0.4.0] — 2026-10-20
+
+### Hybrid retrieval fuses BM25, the code graph, and the resolver
+
+`simt index` indexes full-text tokens across `code`, `docs`, `skills`, `decisions` and
+`lessons` into the SQLite FTS5 `fts` table (with an Okapi BM25 fallback when the index is
+JSON-lines). `simt map` and `simt brief` fuse FTS5 `bm25()`, PageRank graph proximity and
+resolver signals with reciprocal-rank fusion (`RRF_K = 40`), raising gold-file recall@10 on
+the 20 mined tasks here from 54.3% to 61.3% (above the 60% bar in ADR-091). With `--embed`
+and a configured `local.embed` endpoint, `simt index` stores `Float32Array` vector blobs in
+the `embeddings` table and `simt map --embed` adds brute-force cosine similarity; embeddings
+stay off by default unless they raise recall@10 by at least 10 percentage points.
+
+### A local model adapter that opens zero sockets until named
+
+`simt local doctor` probes the OpenAI-compatible `local.chat` and `local.embed` endpoints
+declared in `simt.json` (`/v1/models`, `/v1/chat/completions`, `/v1/embeddings` for Ollama,
+`llama-server`, LM Studio and MLX servers) and reports reachability, model presence and
+latency. Non-loopback URLs are refused unless `--allow-remote` is given (ADR-075, ADR-090),
+and when `local` is unset nothing opens a socket.
+
+### Estate learning and ADR drafts across a workspace
+
+`simt compare --learn` aggregates benchmark uplift (`ΔR`, `ΔC`) per rule section across
+adopted sibling repositories, promotes lessons repeated across at least two repositories as
+shared candidates, and flags gates that fail more than 20% of the time as `NOISY-GATE`.
+`simt compare --draft-adr <pattern>` writes a proposed ADR draft under `docs/decisions/`
+carrying `Origin: simt compare --draft-adr` and the workspace evidence behind it.
+
+### Rule text variants have to win on the bench
+
+A rule may declare candidate wordings under `simt-variants:` in its frontmatter (or supply
+them with `--variants-file`). `simt bench variants <rule-id>` evaluates each candidate on
+paired benchmark runs with McNemar on resolved rate and Wilcoxon signed-rank on cost,
+promotes a wording only when `ΔR > 0` (or `ΔR == 0` and `ΔC < 0`) at `p < 0.05`, and records
+the winning variant and its `p`-value in `simt-dev.lock.json`.
+
+### Decision records carry structured supersession frontmatter
+
+`simt decide "<title>"` scaffolds the next numbered ADR in `docs/decisions/` with structured
+frontmatter (`Status`, `Date`, `Supersedes`, `Superseded-by`, `Affects`) and updates the
+records it supersedes when `--supersedes` and `--yes` are given. `simt rules lint` reports
+`PARTIAL-SUPERSEDE` when prose claims to supersede part of an earlier record without
+matching frontmatter links.
+
+### Lessons are captured from failure-to-fix pairs, recalled on match, and expire
+
+When a failing gate or test run in `.simt-dev/ledger.jsonl` is followed by a passing run on
+the same package, `simt lessons` records a deterministic candidate in
+`.simt-dev/lessons-candidates.jsonl`. `simt lessons promote <id> --yes` writes a reviewed
+lesson to `docs/lessons/<id>.md` with `Paths`, `Check`, `Expires` and `ADR` fields, and
+`simt check` reports `LESSON-EXPIRED` once the date passes or the linked ADR is superseded.
+Matching lessons (at most two) are recalled in `simt brief` and by `simt agent-hook
+after-tool` when a tool call fails on the same package or error signature.
+
+### Skills compile to the Agent Skills standard and report their triggers
+
+`simt skills compile` validates and compiles skill sources against the Agent Skills standard
+(frontmatter `name` and `description`, description under 1024 characters, `SKILL.md` body at
+most 500 lines, and on-demand `references/` and `scripts/` links). `simt skills triggers
+"<prompt>"` previews which skills match a task and the score breakdown behind each match.
+
+### A task brief fits in the bytes a prompt can carry
+
+`simt brief "<task>"` assembles what a task needs into one packet: the kind of the task
+and the commands that kind needs, the files the map ranks highest, the tests the index
+knows for them, the decisions that govern them, the skills the resolver selects, the
+lessons that name those paths, and the cautions — dirty files to leave alone, generated
+paths, files no test covers. The packet stays inside `--budget` bytes (2048 by default,
+`0` for all of it), ends with the number of items it had to cut, and prints the same bytes
+on the same tree; `--explain` prints every item with the reason it was kept or dropped.
+The accept figure it was designed against — 20% fewer turns, 15% cheaper than the kernel
+arm at no loss of resolved rate — is unmeasured here, because it needs a bench run and an
+installed agent CLI and neither is on this machine. `simt skills brief` keeps its own
+behaviour for now: retiring it changes two accepted decisions and an MCP output schema,
+and this slice carries no decision to do it.
+
+### The packet arrives without being asked for
+
+A repository that declares a `brief` key in its manifest gets the packet injected as context
+before every prompt: `simt agent-hooks install` writes a `UserPromptSubmit` hook into Claude
+Code's and Codex's own config, and `simt agent-hook prompt-submit --harness <id>` answers in
+that harness's dialect with `hookSpecificOutput.additionalContext`. It never decides and never
+exits 2 — no prompt text, no opt-in, a cold index or an assembly error all print why on stderr
+and exit 0. The injection is capped at 2048 bytes; `brief.bytes` may lower that and may not
+raise it. Cursor and Gemini CLI are not in the table: Cursor's prompt event can only block a
+prompt, and Gemini CLI's replacement is not in the reader table. The pre-tool path pays nothing
+for this — the repository is reached through a dynamic import only a prompt event opens. MCP
+gains a `brief` tool so a client can pull the same packet, assembled by the same code as the
+command.
+
+### A brief can cite a code graph it did not build
+
+A repository may declare a `federation` block in `simt.json` naming external code-graph
+servers, each with the command that starts it and, optionally, the MCP tool to ask, the
+argument the question goes in, the languages it covers and the timeout to wait. `simt brief`
+and the MCP `brief` tool then ask each declared server one structural question for the task
+and add the answer to a `FEDERATION` section that names its source; a `covers <languages>`
+line records what a server claims without yet skipping the index's own extraction of those
+languages. The list is the repository's own committed declaration, the same trust model as
+`gates.commands`, and nothing is started that the manifest did not name. A malformed entry, a
+spawn failure, a protocol error or a timeout all become a caution and the brief still exits
+`0`; a server that never answers is bounded by its own per-server timeout. MCP also gains a
+`federation_query` tool, which asks a named server (or every declared one) one structural
+question on demand and returns the answer with its source; like the brief's fan-out it goes
+only to the tool and argument the manifest declared. The packet delivered at prompt submit
+does not federate — starting someone else's process is not a wait a 300 ms submit may take.
+
 ## [0.3.1] — 2026-10-18
 
 ### Who a change reaches
@@ -625,6 +733,7 @@ never ran `simt hooks install` again will find nothing until the dependency is r
 and `simt hooks install --yes` is re-run. That is a real upgrade step and it is called out
 here rather than discovered.
 
+[0.4.0]: https://github.com/QuazarMedia/simt-dev/releases/tag/v0.4.0
 [0.3.1]: https://github.com/QuazarMedia/simt-dev/releases/tag/v0.3.1
 [0.3.0]: https://github.com/QuazarMedia/simt-dev/releases/tag/v0.3.0
 [0.2.2]: https://github.com/QuazarMedia/simt-dev/releases/tag/v0.2.2

{simt_dev-0.3.1 → simt_dev-0.4.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: simt-dev
-Version: 0.3.1
+Version: 0.4.0
 Summary: Shared agent rules, skills and git hooks for a repository: one command adopts a repo, and every gate it declares is probed before it is written.
 Project-URL: Homepage, https://github.com/QuazarMedia/simt-dev
 Project-URL: Repository, https://github.com/QuazarMedia/simt-dev
@@ -30,6 +30,8 @@ Description-Content-Type: text/markdown
 
 # simt-dev
 
+![simt-dev, the intelligence amplifier for coding agents, and its four claims. One: say less, always — a kernel under 2 KB whose bytes stay stable so the prompt cache survives. Two: answers over exploration — a local code graph and a short task brief. Three: enforce, don't instruct — dual gates, before a tool call and at git time. Four: close the loop — benches and memory. Beneath them, the harnesses it works across and its three channels.](https://raw.githubusercontent.com/QuazarMedia/simt-dev/main/res/59e21e6d-6bf2-4d7d-b6ea-c7349a697d11.jpg)
+
 `simt` adopts a repository for the agents that work in it.
 
 It reads what the repository actually runs, projects the rules that are not already
@@ -111,18 +113,18 @@ this order of purpose:
 
 ## Install
 
-Requires **Node >= 22.20.0**. The current published release is **0.3.1**. Pin it.
+Requires **Node >= 22.20.0**. The current published release is **0.4.0**. Pin it.
 The tool writes a content digest into the files it generates, and an unpinned upgrade
 changes them under you.
 
 ```sh
-npm i -D simt-dev@0.3.1
+npm i -D simt-dev@0.4.0
 
 # or globally
-npm i -g simt-dev@0.3.1
+npm i -g simt-dev@0.4.0
 
 # or once, with no install
-npx -y simt-dev@0.3.1 check
+npx -y simt-dev@0.4.0 check
 ```
 
 ### From PyPI
@@ -163,6 +165,14 @@ Node installed.
 
 Text outside the markers is left alone. A regeneration does not revert it.
 
+`simt.json` also carries a `federation` block when the repository names external
+code-graph servers, each with the command that starts it. A brief may then ask one of
+them one structural question for a task and cite the answer's source, and the MCP
+`federation_query` tool asks one on demand, naming the server it asked. The question goes
+to the tool and argument the manifest declared, so no foreign tool is reachable that the
+repository did not name. Nothing is started unless the manifest declared it, and a server
+that does not answer costs the packet a sentence, never the packet.
+
 These are caches, gitignored, and rebuildable. They are not repository content:
 
 | Path | What |

{simt_dev-0.3.1 → simt_dev-0.4.0}/README.md

@@ -1,5 +1,7 @@
 # simt-dev
 
+![simt-dev, the intelligence amplifier for coding agents, and its four claims. One: say less, always — a kernel under 2 KB whose bytes stay stable so the prompt cache survives. Two: answers over exploration — a local code graph and a short task brief. Three: enforce, don't instruct — dual gates, before a tool call and at git time. Four: close the loop — benches and memory. Beneath them, the harnesses it works across and its three channels.](https://raw.githubusercontent.com/QuazarMedia/simt-dev/main/res/59e21e6d-6bf2-4d7d-b6ea-c7349a697d11.jpg)
+
 `simt` adopts a repository for the agents that work in it.
 
 It reads what the repository actually runs, projects the rules that are not already
@@ -81,18 +83,18 @@ this order of purpose:
 
 ## Install
 
-Requires **Node >= 22.20.0**. The current published release is **0.3.1**. Pin it.
+Requires **Node >= 22.20.0**. The current published release is **0.4.0**. Pin it.
 The tool writes a content digest into the files it generates, and an unpinned upgrade
 changes them under you.
 
 ```sh
-npm i -D simt-dev@0.3.1
+npm i -D simt-dev@0.4.0
 
 # or globally
-npm i -g simt-dev@0.3.1
+npm i -g simt-dev@0.4.0
 
 # or once, with no install
-npx -y simt-dev@0.3.1 check
+npx -y simt-dev@0.4.0 check
 ```
 
 ### From PyPI
@@ -133,6 +135,14 @@ Node installed.
 
 Text outside the markers is left alone. A regeneration does not revert it.
 
+`simt.json` also carries a `federation` block when the repository names external
+code-graph servers, each with the command that starts it. A brief may then ask one of
+them one structural question for a task and cite the answer's source, and the MCP
+`federation_query` tool asks one on demand, naming the server it asked. The question goes
+to the tool and argument the manifest declared, so no foreign tool is reachable that the
+repository did not name. Nothing is started unless the manifest declared it, and a server
+that does not answer costs the packet a sentence, never the packet.
+
 These are caches, gitignored, and rebuildable. They are not repository content:
 
 | Path | What |

{simt_dev-0.3.1 → simt_dev-0.4.0}/package.json

@@ -1,6 +1,6 @@
 {
   "name": "simt-dev",
-  "version": "0.3.1",
+  "version": "0.4.0",
   "description": "Shared agent rules, skills and git hooks for a repository: one command adopts a repo, and every gate it declares is probed before it is written.",
   "license": "Apache-2.0",
   "author": "Said Elimam",
@@ -37,7 +37,7 @@
     "skills"
   ],
   "scripts": {
-    "test": "node --test test/*.test.mjs",
+    "test": "node --test --test-concurrency=4 test/*.test.mjs",
     "lint": "node bin/simt-dev.mjs doctor"
   }
 }

{simt_dev-0.3.1 → simt_dev-0.4.0}/rules/core.md

@@ -7,7 +7,7 @@ simt-priority: hard
 
 # Shared rules
 
-Where a rule cites a decision, run `simt-dev rules why ADR-NNN` to read it,
+Where a rule cites a decision, run `simt rules why ADR-NNN` to read it,
 including whether it is still in force.
 
 These rules are stack-agnostic. Whatever is specific to your stack, your product or your

{simt_dev-0.3.1 → simt_dev-0.4.0}/src/agenthooks/policy.mjs

@@ -21,8 +21,16 @@
 
 import { CLI } from '../name.mjs';
 
-/** The events an agent-time hook can answer, normalised across harnesses. */
-export const EVENTS = ['pre-tool-use'];
+/**
+ * The events an agent-time hook can answer, normalised across harnesses.
+ *
+ * `pre-tool-use` is a decision: a payload in, a deny or nothing out, and exit 2 means
+ * block. `prompt-submit` is a delivery: the same payload shape in, context out, and it
+ * never denies anything — a hook that could stop a person's prompt would be a hook whose
+ * own bug is a person who cannot type (R29). `post-tool-use` recalls a lesson as one
+ * paragraph when a tool call fails with a signature matching `docs/lessons/*.md` (R33).
+ */
+export const EVENTS = ['pre-tool-use', 'prompt-submit', 'post-tool-use'];
 
 /** The environment variable that lifts named policies for one session. */
 export const ALLOW_ENV = 'SIMT_ALLOW';

simt_dev-0.4.0/src/agenthooks/prompt.mjs

@@ -0,0 +1,81 @@
+// The prompt-submit surface: the packet delivered where the agent will read it.
+//
+// This module must stay off the tool-call path, and the code's shape is what keeps it
+// there: `src/commands/agenthook.mjs` reaches it through a dynamic `import()` that only a
+// prompt event takes. The pre-tool hook is a latency promise — it answers before every
+// shell command an agent runs — so it imports the policy table, the decision and the
+// renderer and nothing that walks the repository, and `test/agenthooks.test.mjs` asserts
+// exactly that set. A delivery, by contrast, is the one thing here that must read the
+// repository, so it lives behind a door the pre-tool path never opens.
+//
+// Three rules shape what gets delivered:
+//
+//   * The repository opts in. The opt-in is a `brief` key in the repository's manifest,
+//     not the presence of a hook in a harness config: a repository that declared nothing
+//     is not spending its owner's context on a packet they did not ask for, and the
+//     manifest is the one file a person reviews before they commit the change.
+//   * The packet is capped, at PROMPT_CAP_BYTES. A packet is delivered into a prompt that
+//     already exists, and the ceiling is the measured bar of this slice rather than a
+//     value a repository is free to raise.
+//   * A delivery never blocks and never fails loudly. Everything that could go wrong —
+//     no index, no prompt in the payload, a registry that will not load — ends in no
+//     injection and a line on stderr. A hook that stopped a person's prompt because this
+//     tool could not answer would be worse than a hook that said nothing.
+
+import { readManifest } from '../projection/manifest.mjs';
+import { DEFAULT_BRIEF_BYTES, PROMPT_CAP_BYTES } from '../brief/packet.mjs';
+import { assembleBrief } from '../brief/assemble.mjs';
+import { deliveryJson, factsFrom, promptText } from './render.mjs';
+
+/**
+ * Whether this repository asked for a delivered packet, and the ceiling it asked for.
+ *
+ * Presence is the opt-in and the value is a preference, so `"brief": {}` means "yes, at
+ * whatever you measured" and `"brief": { "bytes": 900 }` means "yes, and keep it small".
+ * A declared zero is not honoured as a ceiling: zero is this tool's word for "no ceiling"
+ * on the command line, and a delivered packet that meant "the whole repository" would be
+ * the one thing the cap exists to prevent. It is read from the manifest rather than from
+ * the harness config because the manifest is the file the repository reviews.
+ */
+export async function promptOptIn(root) {
+  const { manifest, exists, error } = await readManifest(root);
+  if (!exists || error) {
+    return { optedIn: false, bytes: DEFAULT_BRIEF_BYTES, why: `${exists ? error : 'no manifest'}` };
+  }
+  if (manifest?.brief === undefined || manifest.brief === null) {
+    return { optedIn: false, bytes: DEFAULT_BRIEF_BYTES, why: 'no `brief` key in the manifest' };
+  }
+  const declared = manifest.brief?.bytes;
+  const asked = Number.isFinite(declared) && declared > 0 ? declared : PROMPT_CAP_BYTES;
+  return { optedIn: true, bytes: Math.min(asked, PROMPT_CAP_BYTES) };
+}
+
+/**
+ * The context one prompt-submit call should deliver, or the reason it delivers nothing.
+ *
+ * `build: false` is the latency promise in one argument: a delivery reports a cold index
+ * rather than building one, so the first prompt in a fresh clone gets nothing and the
+ * second gets the packet. The alternative — a person watching their first prompt sit for
+ * a minute while a repository is walked — is how the hook gets uninstalled, and the
+ * packet is not worth a prompt that cannot be typed.
+ */
+export async function deliverPrompt(row, payload) {
+  const task = promptText(row, payload);
+  if (task === null) return { skipped: 'the payload carries no prompt this harness documents' };
+
+  // The root is the same dialect fact for both events, so it is read the same way.
+  const root = factsFrom(row, payload).root;
+  const optIn = await promptOptIn(root);
+  if (!optIn.optedIn) return { skipped: optIn.why };
+
+  // Federation is off on this path and on no other: a delivery has 300 ms to answer, and
+  // starting a declared server is a wait a prompt submit must not take. The task is the
+  // question a federation would ask, and a person is not made to wait for it here.
+  const result = await assembleBrief({ root, task, budget: optIn.bytes, build: false, federate: false });
+  if (result.error) return { skipped: 'the packet could not be assembled' };
+  if (result.cold) return { skipped: 'the index is empty, and a delivered packet never builds one' };
+
+  const json = deliveryJson(row, result.packed.text);
+  if (json === null) return { skipped: `${row.id} has no prompt event that can inject` };
+  return { json, root, bytes: result.packed.after };
+}

{simt_dev-0.3.1 → simt_dev-0.4.0}/src/agenthooks/render.mjs

@@ -11,6 +11,26 @@
 //   cursor       .cursor/hooks.json      preToolUse      {"version":1,"hooks":{E:[h]}}
 //   antigravity  .agents/hooks.json      PreToolUse      {"<name>":{E:[{matcher,hooks:[h]}]}}
 //
+// The prompt-submit event (R29) is a second table, and it is shorter because the vendors
+// are: two of the four document a prompt event that can put text into the model's context,
+// and a delivery is the only thing this tool does there. Neither takes a matcher — both
+// document that field for tool events, and a matcher a harness ignores is a matcher the
+// next person believes is filtering something.
+//
+//   claude       .claude/settings.json   UserPromptSubmit   hookSpecificOutput.additionalContext
+//   codex        .codex/hooks.json       UserPromptSubmit   hookSpecificOutput.additionalContext
+//   cursor       .cursor/hooks.json      beforeSubmitPrompt CANNOT INJECT: block-only
+//   antigravity  .agents/hooks.json      (no prompt event documented)
+//
+// Cursor is the one that would be a mistake to write anyway. Its `beforeSubmitPrompt` hook
+// can only continue or block, so the entry would carry no packet and a broken one would
+// stop a person from typing — and its only injection point, `sessionStart.additional_context`,
+// fires once when the session is created, which is a different lifetime from the brief a
+// task needs. Gemini CLI documents `BeforeAgent`, which does inject, but the product was
+// replaced by Antigravity CLI on 2026-06-18 and its config is not in the reader table this
+// module takes its paths from; a harness this tool did not verify is a harness it does not
+// write to.
+//
 // The paths are not written here. They come from the reader table (R14) because that is
 // where each one was verified against its vendor page, and a second copy of a verified
 // fact is a copy that drifts the first time a vendor moves the file.
@@ -36,8 +56,8 @@ const TIMEOUT_SECONDS = 10;
  * harness's dialect when a payload arrived in an unexpected shape, and the harness would
  * read a decision it does not understand as no decision at all.
  */
-export function hookCommand(id) {
-  return `${CLI} agent-hook ${EVENTS[0]} --harness ${id}`;
+export function hookCommand(id, event = EVENTS[0]) {
+  return `${CLI} agent-hook ${event} --harness ${id}`;
 }
 
 /** The path a config file lives at, from the reader table rather than a second list. */
@@ -73,6 +93,20 @@ const ADAPTERS = {
     deny: (message) => ({
       hookSpecificOutput: { hookEventName: 'PreToolUse', permissionDecision: 'deny', permissionDecisionReason: message },
     }),
+    // The delivery door. `additionalContext` is documented for this event and is
+    // wrapped into the conversation at the point the hook fired, which is why the
+    // packet goes here rather than into a system prompt: the cached prefix survives.
+    prompt: {
+      event: 'UserPromptSubmit',
+      verified: 'code.claude.com/docs/en/hooks, read 2026-10-19',
+      context: (text) => ({ hookSpecificOutput: { hookEventName: 'UserPromptSubmit', additionalContext: text } }),
+    },
+    post: {
+      event: 'PostToolUse',
+      matcher: 'Bash',
+      verified: 'code.claude.com/docs/en/hooks, read 2026-10-19',
+      context: (text) => ({ hookSpecificOutput: { hookEventName: 'PostToolUse', additionalContext: text } }),
+    },
   },
   codex: {
     id: 'codex',
@@ -96,6 +130,17 @@ const ADAPTERS = {
     deny: (message) => ({
       hookSpecificOutput: { hookEventName: 'PreToolUse', permissionDecision: 'deny', permissionDecisionReason: message },
     }),
+    prompt: {
+      event: 'UserPromptSubmit',
+      verified: 'developers.openai.com/codex/hooks, read 2026-10-19',
+      context: (text) => ({ hookSpecificOutput: { hookEventName: 'UserPromptSubmit', additionalContext: text } }),
+    },
+    post: {
+      event: 'PostToolUse',
+      matcher: 'Bash',
+      verified: 'developers.openai.com/codex/hooks, read 2026-10-19',
+      context: (text) => ({ hookSpecificOutput: { hookEventName: 'PostToolUse', additionalContext: text } }),
+    },
   },
   cursor: {
     id: 'cursor',
@@ -111,6 +156,11 @@ const ADAPTERS = {
         : [],
     }),
     deny: (message) => ({ permission: 'deny', user_message: message, agent_message: message }),
+    // beforeSubmitPrompt is documented as continue/block and nothing else, so there is no
+    // key to deliver a packet in. Writing the entry anyway would put a command that reads
+    // a repository on the path of every prompt a person types, to say nothing.
+    prompt: null,
+    post: null,
   },
   antigravity: {
     id: 'antigravity',
@@ -133,6 +183,10 @@ const ADAPTERS = {
       };
     },
     deny: (message) => ({ decision: 'deny', reason: message }),
+    // No prompt event is documented for this harness's hooks file, and a guessed event
+    // name is a hook that never fires while its config says it does.
+    prompt: null,
+    post: null,
   },
 };
 
@@ -160,6 +214,37 @@ export function decisionJson(row, decision) {
   return row.deny(decision.messages.join('\n'));
 }
 
+/**
+ * The document to print for a delivery, or null when the harness takes none.
+ *
+ * A delivery is never a decision: nothing here can deny, and the caller exits 0 whatever
+ * this returns. That is the whole difference between the two events, and it is why the
+ * prompt event has no `denyExit` — there is no exit code that means "here is some context".
+ */
+export function deliveryJson(row, text) {
+  return row.prompt ? row.prompt.context(text) : null;
+}
+
+/** The document to print for a post-tool lesson recall delivery, or null when the harness takes none. */
+export function postDeliveryJson(row, text) {
+  return row.post ? row.post.context(text) : null;
+}
+
+/**
+ * The submitted text a prompt payload carries, or null when it carries none we recognise.
+ *
+ * Marked inferred rather than documented: both harnesses that take this event place the
+ * prompt at the top level, but only in the example on each page, not as a stated contract.
+ * An unrecognised payload therefore delivers nothing and says so on stderr. The failure
+ * this must not have is the opposite one — a packet delivered as though it answered a task
+ * it never saw, which reads as a confident answer about the wrong question.
+ */
+export function promptText(row, payload) {
+  if (!row.prompt) return null;
+  const text = payload?.prompt ?? payload?.user_prompt ?? payload?.message;
+  return typeof text === 'string' && text.trim().length > 0 ? text : null;
+}
+
 // ---------------------------------------------------------------------------
 // The config file: reading ours out of somebody else's JSON, and putting it back.
 // ---------------------------------------------------------------------------
@@ -180,9 +265,36 @@ function container(row, config, { create = false } = {}) {
   return config.hooks ?? null;
 }
 
+/** The vendor's name for one of our events on this row, or null when it has none. */
+function vendorEvent(row, event) {
+  if (event === EVENTS[0]) return row.event;
+  if (event === 'prompt-submit') return row.prompt?.event ?? null;
+  if (event === 'post-tool-use') return row.post?.event ?? null;
+  return null;
+}
+
+/** The events a row answers, and the name each one goes under in its config file. */
+function eventsOf(row, { prompt = false, post = false } = {}) {
+  const pairs = [[EVENTS[0], row.event]];
+  if (prompt && row.prompt) pairs.push(['prompt-submit', row.prompt.event]);
+  if (post && row.post) pairs.push(['post-tool-use', row.post.event]);
+  return pairs;
+}
+
 /** The group this tool owns for one event, in that harness's shape. */
-function group(row) {
-  const command = hookCommand(row.id);
+function group(row, event = EVENTS[0]) {
+  const command = hookCommand(row.id, event);
+  if (event === 'prompt-submit') {
+    // No matcher: both vendors document that field for tool events, and a matcher a
+    // harness ignores is a matcher the next reader believes is filtering something.
+    return { hooks: [{ type: 'command', command, timeout: TIMEOUT_SECONDS }] };
+  }
+  if (event === 'post-tool-use') {
+    const matcher = row.post?.matcher;
+    return matcher
+      ? { matcher, hooks: [{ type: 'command', command, timeout: TIMEOUT_SECONDS }] }
+      : { hooks: [{ type: 'command', command, timeout: TIMEOUT_SECONDS }] };
+  }
   if (row.id === 'cursor') {
     // failClosed is set because a hooks file this tool wrote should not silently
     // degrade to fail-open on its own crash: the vendor's default turns a broken hook
@@ -197,35 +309,44 @@ function ours(entry) {
   return JSON.stringify(entry).includes(`${CLI} agent-hook`);
 }
 
-function entries(row, config) {
-  const box = container(row, config);
-  const list = box?.[row.event];
+function entries(row, config, event = EVENTS[0]) {
+  const name = vendorEvent(row, event);
+  if (name === null) return [];
+  const list = container(row, config)?.[name];
   return Array.isArray(list) ? list : [];
 }
 
-/** Our entries in this document, for `status`; the document is not modified. */
-export function installedIn(row, config) {
-  return entries(row, config).filter(ours);
+/** Our entries in this document for one event, for `status`; the document is not modified. */
+export function installedIn(row, config, event = EVENTS[0]) {
+  return entries(row, config, event).filter(ours);
 }
 
 /**
- * The document with this tool's hook added, everything else left alone.
+ * The document with this tool's hooks added, everything else left alone.
  *
  * Written as JSON with two spaces and a trailing newline because that is what a file in
  * a repository reads like; a config that is rewritten with different indentation on
  * every run is a diff nobody can review. Keys this tool does not own are preserved
  * exactly, including their order, because the file belongs to the repository.
+ *
+ * One file can carry both events — Claude and Codex each hold a tool hook and a prompt
+ * hook in the same document — so this writes one group per event the row answers rather
+ * than one group per file. `prompt` is the caller's opt-in: a repository that has not
+ * asked for a delivered packet gets the tool hook and nothing extra, and the file it never
+ * asked to change is a file this tool does not touch.
  */
-function withHook(row, config) {
+function withHook(row, config, { prompt = false, post = false } = {}) {
   const box = container(row, config, { create: true });
-  const kept = entries(row, config).filter((e) => !ours(e));
-  box[row.event] = [...kept, group(row)];
+  for (const [event, name] of eventsOf(row, { prompt, post })) {
+    const kept = entries(row, config, event).filter((e) => !ours(e));
+    box[name] = [...kept, group(row, event)];
+  }
   return config;
 }
 
 /** The text `install` would write, or the reason the existing file cannot be read. */
-export function rendered(row, existing) {
-  if (existing === null) return { text: `${JSON.stringify(withHook(row, {}), null, 2)}\n`, action: 'created' };
+export function rendered(row, existing, options = {}) {
+  if (existing === null) return { text: `${JSON.stringify(withHook(row, {}, options), null, 2)}\n`, action: 'created' };
   let config;
   try {
     config = JSON.parse(existing);
@@ -235,6 +356,6 @@ export function rendered(row, existing) {
   if (config === null || typeof config !== 'object' || Array.isArray(config)) {
     return { error: 'not a JSON object; left alone' };
   }
-  const text = `${JSON.stringify(withHook(row, config), null, 2)}\n`;
+  const text = `${JSON.stringify(withHook(row, config, options), null, 2)}\n`;
   return { text, action: text === existing ? 'unchanged' : 'updated' };
 }

{simt_dev-0.3.1 → simt_dev-0.4.0}/src/argv.mjs

@@ -74,6 +74,12 @@ export const BOOL_FLAGS = new Set([
   // Off by default because a path is the change the caller named, and the diff
   // is a different question.
   'changed',
+  // local doctor: allow non-loopback model URLs. Off by default because nothing leaves
+  // the machine unless explicitly overridden (ADR-075, plan 0003 R37).
+  'allow-remote',
+  // index / map / brief: opt into local vector embeddings configured under local.embed
+  // (plan 0003 R28, R37). Off by default unless recall@10 gains at least 10 points.
+  'embed',
 ]);
 
 export const VALUE_FLAGS = new Set([
@@ -118,6 +124,8 @@ export const VALUE_FLAGS = new Set([
   // map: outline (paths), names (exported symbols) or signatures (the line).
   // A boolean would not say which of the three the caller wanted.
   'level',
+  // decide: structured supersession spec (ADR-NNN or ADR-NNN:<ruling>[:<kind>], repeatable).
+  'supersedes',
 ]);
 
 /**
@@ -133,7 +141,7 @@ export const VALUE_FLAGS = new Set([
  * is a superset of the old behaviour, not a replacement: `--skill a,b` parsed before it
  * parses now.
  */
-export const REPEATABLE_FLAGS = new Set(['skill', 'arm', 'compare']);
+export const REPEATABLE_FLAGS = new Set(['skill', 'arm', 'compare', 'supersedes']);
 
 /**
  * @param {string[]} argv raw arguments, excluding node and the script path
@@ -207,6 +215,13 @@ export function parse(argv) {
   return { ok: true, value: { flags, positional } };
 }
 
+export function parsePathList(value) {
+  return String(value ?? '')
+    .split(',')
+    .map((s) => s.trim())
+    .filter(Boolean);
+}
+
 /** `--max-bytes` -> `maxBytes`. Callers use camelCase; users type kebab-case. */
 function camel(name) {
   return name.replace(/-([a-z])/g, (_, c) => c.toUpperCase());

{simt_dev-0.3.1 → simt_dev-0.4.0}/src/bench/grade.mjs

@@ -173,6 +173,7 @@ export async function gradeWorkspace(workDir, task, { vaultRoot, initialHead, ti
       resolved: false,
       gatesPassed: false,
       diff,
+      goldFiles: [...goldFiles],
       agentPatch: diffPatchRes.stdout,
     };
   }
@@ -183,6 +184,7 @@ export async function gradeWorkspace(workDir, task, { vaultRoot, initialHead, ti
       resolved: false,
       gatesPassed: false,
       diff,
+      goldFiles: [...goldFiles],
       agentPatch: diffPatchRes.stdout,
     };
   }
@@ -224,6 +226,7 @@ export async function gradeWorkspace(workDir, task, { vaultRoot, initialHead, ti
     resolved,
     gatesPassed,
     diff,
+    goldFiles: [...goldFiles],
     agentPatch: diffPatchRes.stdout,
   };
 }