simt-dev 0.2.0 → 0.2.2

package/CHANGELOG.md

@@ -4,6 +4,372 @@ All notable changes to this package are recorded here. The format follows
 [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and the project follows
 [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [Unreleased]
+
+## [0.2.2] — 2026-10-14
+
+### A repository can ask for a smaller projection
+
+`simt tokens` measured the cost and `check` now holds the line the repository draws: `budget.bytes`
+in `simt.json` is how many always-on bytes that repository has agreed to carry, and both the meter and
+the gate report the overflow with the two numbers in them. It sits beside `gates` rather than inside
+`projection`, because that key belongs to this tool and an upgrade replaces it.
+
+`mode: kernel` is the other half. It keeps the rules a reader cannot do without — the ones a hard
+constraint or a command depends on — and defers the rest behind a `## Deferred rules` section that
+names each one and the command that shows it. A Python fixture projects 16% smaller. `full` is still
+the default, because nobody has measured yet whether the smaller projection loses compliance, and a
+tool that made that trade silently would be deciding it on the reader's behalf (ADR-073).
+
+### A repository can declare how many always-on bytes it is willing to carry
+
+`simt tokens` has reported that number since the meter landed, against a constant nobody
+could argue with. A repository can now say what it will carry — `budget: { bytes: N }`
+beside `limits` and `gates` in the manifest — and both `simt tokens` and `simt-dev check`
+measure against that line. One declaration, one meter, one function that words the finding.
+
+The declaration is deliberately *not* inside `projection`, which is the one block this tool
+owns and `upgrade` is allowed to replace: a number written there would be deleted silently
+on the next upgrade and never reported as drift. And a repository that declares nothing is
+reported as declaring nothing, rather than being quietly handed the default as though it
+had chosen it.
+
+Over budget is reported and never fails the gate. Nothing was cut — the projection is
+still full mode, every rule loaded as written — so the honest thing to say is "you are
+over your line", not to fail a repository over a ceiling it wrote down itself. Which rules
+move behind skills stays with the evaluation that has to decide it (ADR-072).
+
+### A repository can declare the always-on bytes it intends to carry
+
+`simt tokens` measured the number; it could not be held to one. A manifest now carries
+`budget.bytes` — a declaration beside `limits` and `gates`, not inside `projection`,
+because that block is regenerated on every upgrade and nothing in the repair would notice
+its budget disappearing. A repository that declares nothing is measured against the
+review's 30 KB and reports `declared: false` rather than looking like it chose it.
+
+Over budget is reported, never enforced, and the report says what was not done: nothing
+was cut, because the projection is still in full mode. Which rules move behind skills is a
+measurement that has not been taken yet, and a budget that quietly dropped rules would be
+enforcing a decision nobody made (ADR-072).
+
+### A stack profile loads only when a matching file is in play
+
+A stack profile used to be always-on everywhere, because profiles reached a reader through
+the generated region in AGENTS.md and through nothing else. A profile can now declare
+`simt-scope`, and a repository on Cursor, Copilot or Antigravity gets it as a file the
+surface attaches on patterns: `.cursor/rules/python.mdc` with `globs` and
+`alwaysApply: false`, an Antigravity rule with `trigger: glob`, a Copilot
+`.instructions.md` with `applyTo`. AGENTS.md keeps one line naming the profile, the
+patterns and the file it moved to — a profile that vanishes from the region reads as one
+that was deleted.
+
+The narrowing happens only when every selected surface can do it. Claude Code's `paths:`
+key is documented and silently fails to lazy-load for quoted values, and opencode has no
+per-rule channel at all, so a repository carrying either keeps its profiles in the region
+and is told which surface stopped it. A rule that never loads is worse than a rule that
+loads eagerly.
+
+Reading the two vendors' docs changed the shape of this: Antigravity requires patterns
+starting with `*` to be quoted or YAML reads them as an alias anchor and the rule is
+discarded with no message, and it documents a 20,000-token budget for always_on rules past
+which they are demoted to pointers — so eager profiles cost the reader a real budget. A
+`simt-scope` that matches everything is now refused, since that is the same behaviour with
+a narrowing-looking spelling (ADR-071).
+
+### Every `--json` payload says which version it is
+
+An agent that parses `--json` had no way to notice that a field had moved: the parse
+succeeds, the lookup returns `undefined`, and the answer is quietly wrong. Every payload now
+opens with `schemaVersion`, and a version in a comment is not a version, so it travels in
+the document every reader is guaranteed to see.
+
+The same document is now one line rather than four columns of whitespace, because the reader
+of `--json` is a program and it pays for every byte. `--pretty` asks for the other form, and
+a terminal gets it without being asked, because there the reader is a person.
+
+Writing the contract test found two things the review that asked for this missed. Eight
+commands — `doctor`, `mcp --list`, `graph lint`, `rules list`, and the `skills` ones — had a
+private `emit(JSON.stringify(..., null, 2))` instead of the shared helper, so `--json` meant
+something different depending on which command you asked. And a command that *failed* under
+`--json` wrote only to stderr, so a scripted caller got an empty document and a non-zero
+exit and no way to learn what went wrong. It now answers in the shape it was asked in (ADR-070).
+
+### `graph lint` now checks skills against the published specification
+
+The Agent Skills specification sets limits nobody here was checking: a name of lowercase
+letters, digits and single hyphens that equals the directory it lives in; a description
+under 1,024 characters; a compatibility note under 500; a body recommended under 5,000
+tokens because an agent loads all of it once the skill activates. `graph lint --spec
+agentskills` checks every skill against those, and the specification was fetched rather
+than recalled — reading it turned up four rules the review that asked for this did not
+list, including the one that breaks installs.
+
+What the specification calls a must fails the exit code; what it calls a recommendation
+warns. A lint that fails on advice is a lint that gets skipped. `skills install` now asks
+the same name rules, since the directory is created from the name and an unaddressable
+skill would be the last thing anyone notices.
+
+### The MCP surface speaks three protocol revisions, and answers in the shape each asks for
+
+The server was pinned to one revision and returned pretty JSON in a text block, so a
+client could read the answer but could not validate it, could not cache it, and could not
+tell a read-only tool from one that writes. All three published revisions were read rather
+than guessed at, and each is answered in its own shape: the newest drops the handshake for
+a version carried on every request, adds a discovery method servers must implement,
+requires a result-type field and a cache lifetime on list results, and deleted the liveness
+method — which older clients still get, and newest clients are told is gone by name.
+
+Every tool now declares what it returns and says it is a reader, and every call returns
+the answer in both shapes: the text block for a client that predates structured content,
+the structured block for one that validates against the declared schema. The byte ceiling
+bounds the text only, so the block a client can check still checks. The schema checker
+that makes this testable lives in the package rather than in a dependency.
+
+### Which harnesses a repository is set up for is now answerable
+
+`simt-dev harness detect` looks at the configuration directories that exist and says
+which harnesses this repository — and, with `--user`, its reader — is set up for. It
+claims presence and nothing else: a directory found is not a claim about what its owner
+reads, because the tool cannot answer that without a vendor document, and a guess here
+would be the reader's problem the first time it was wrong. A harness that reads
+AGENTS.md is served by the standard surface whatever else it reads, and every surface row
+now records that in three values rather than two, because "reads AGENTS.md" and "is
+covered for this harness" are not the same sentence — Copilot's CLI reads it and its
+editor, code review and cloud agent do not.
+
+No new harness rows ship with it. The candidates are recorded as directory names, which
+claim presence and not coverage; a row still requires the vendor document it cites, and
+one that reads nothing has to be added on purpose.
+
+### A monorepo gets rules for each of its packages
+
+One repository, one projection: every package under the root was given the root's rules,
+so a React application inside a node workspace was handed the node profile and nothing
+else, and the profile that should have applied to it was applied by nobody. The rule that
+package needed was not wrong — it was missing.
+
+Packages are now discovered from the declarations that already list them (npm and pnpm
+workspaces, turbo, Cargo members, `go.work`, Gradle includes) rather than by walking the
+tree, because a declaration states which directories are members and a marker file only
+says there is a build here. The root keeps what every package shares; each package that
+selects something new gets a generated region carrying exactly its own delta, and a
+package that selects nothing new gets no file at all. `check` reports every package
+region and fails on any one of them, and `compare` counts the drifted regions rather than
+the repositories that hold them.
+
+A gate can also name the directory it runs in, which is what a monorepo with no root test
+script needs: `gates.cwd` maps a gate to a directory, a directory that does not exist or
+resolves outside the repository fails the event and is reported by `check` before the
+commit rather than at it, and a directory named for a gate that is not declared is
+reported as the inert entry it is.
+
+### One rule set, shared by the repositories that agreed on it
+
+Several repositories want the same rules and each kept its own copy, so a policy change
+was several edits that could be several-minus-one, and the repository that missed it
+carried instructions nobody there wrote. A pack is that shared set: `packs` in the manifest
+declares it, the bytes live in the repository, and a digest of them is recorded so nobody
+has to trust that the two agree.
+
+A pack's rules are selected by the same matcher as any profile and appear in the region's
+source list under the pack's own directory. Precedence is the repository, then a pack it
+declares, then what the tool ships, and every replacement is reported rather than silent.
+
+A pack that disagrees with its pin still projects — the gate blocks and prints both
+digests, because dropping it would let the repair delete the rules it is reporting. One
+that is missing blocks with a remedy that restores it, and one with no digest is reported
+without failing anything, since its rules render correctly. `compare` lists every pack and
+the digest it is pinned to, so a repository behind a shared change is visible before
+anyone follows stale instructions. Nothing is fetched: the bytes are in the repository,
+which is what makes the rendered region reproducible from what the reader has (ADR-065).
+
+### `simt tokens` counts what a reader loads
+
+Review 0002 filed the estate's always-on context at 90 KB per turn, 72% of it a paragraph
+an earlier repository had already loaded — a number produced by reading seven
+repositories by hand, which ages the moment a rule is edited and cannot be re-derived by
+the reader who has to act on it.
+
+`simt tokens` is that reading, as a command. It reports the bytes this tool wrote per
+channel (region, rule files, skill metadata), an approximate token figure, and — with
+`--repos` — the same figure across a workspace, with every repeated paragraph attributed
+to the first root that carries it. A region that ends past a harness's read limit is
+reported with its byte offset, using the same numbers the existing check uses.
+
+Three choices keep the figure honest, and all three are recorded in ADR-064: the meter
+counts what the projection wrote and reports hand-written bytes beside it rather than
+folding them into the budget; a region is the span between its two markers, so the blank
+line a person left above the marker is billed to nobody; and an over-budget repository is
+reported rather than failed, because a meter that went red would train people to ignore
+the number.
+
+S38 stays open — this is the instrument. Whether the estate gets under 30 KB is R07's
+kernel, R08's budget field and R11's dedupe, measured with this.
+
+## [0.2.1] — 2026-10-13
+
+### `init` writes in place; the backup tag and adopt branch are opt-in
+
+`simt init --yes` used to always tag the pre-adoption commit and branch onto a dedicated
+adopt branch before writing. The safety argument was sound, but consumers kept reporting
+the branch switch as a surprise — a well-announced surprise is still a surprise.
+
+The default now writes in place on the branch you already have: nothing is tagged, nothing
+is branched, and the run says so in an `in place` line. The reviewable diff survives —
+`git diff` shows the whole adoption, and discarding it is a checkout and a clean.
+
+The old behaviour moves behind `--backup`: `simt init --yes --backup` tags the pre-adoption
+commit and branches as before, for readers who want the named undo path. ADR-063 records
+the decision and the one behaviour it invalidates: consumers who scripted against the old
+default add `--backup`.
+
+### A fresh adoption seeds the gates it can run — and only those
+
+The eight common ecosystems outside the JavaScript world — Rust, Go, .NET, Swift, Deno,
+Ruby, Dart and Elixir — were recognised by the fingerprint and served by nothing: no
+profile selected them, no gate was proposed for them. A fresh Rust repository received the
+core essay and a manifest that runs nothing, while the ecosystems that emit stack tags got
+the full treatment.
+
+Each now has a profile that selects on its own `has-*` fact, so one marker file reaches
+both the rules the repository reads and the gates its commits run. Maven's profile predates
+this; its row is gates-only, wrapper-first, like `gradlew`.
+
+`simt init` now seeds the canonical commands for a detected ecosystem — `cargo fmt
+--check`, `go vet ./...`, `dotnet test`, and the rest of the table — into the manifest's
+gates, but only where a probe found the tool: a binary on PATH, or a file in the repository
+for the Maven wrapper. A marker says the ecosystem is here; the probe says its program can
+run. A declared gate that cannot run fails closed on every commit, so the seed fires only
+when both are true — and where the probe fails, the gate is dropped with a remedy that
+names the install instead of blocking the first commit.
+
+A seed is a default: a command the repository already declared is never re-seeded, and an
+npm runner keeps its own scripts, because `package.json` is the repository's own answer to
+"how do I test and format". ADR-062 rules the shape of all of it.
+
+### The resolver is measured against a gold corpus
+
+`simt skills eval` scores the skill resolver against a corpus of real tasks × real
+repositories, each case carrying a gold list of the skills it should select and a list
+of the ones it must not. It reports precision and recall, prints a PASS/FAIL line per
+case naming the skills it missed or selected that it should not have, and exits
+non-zero on a regression — so it can be run from CI the way the gate is run.
+
+The scoring lives in `src/resolve/eval.mjs`, which the command and
+`test/eval.test.mjs` both call, so a test cannot drift from what the command measures.
+The corpus lives under `test/` because test data does not ship in the package: an
+installed copy names the path it would have read and says so instead of scoring the
+author's.
+
+### The skill registry is workspace data; the package ships none of it
+
+The npm tarball and the wheel carried `graph/skills.graph.json` — the directory
+of skill sources for one workspace, naming the repositories whose bodies it
+resolves. Every installed copy served that catalogue to readers who have none
+of those skills, and `skills install` pointed at paths that exist only in the
+workspace that wrote them. ADR-061 rules the registry out of the published set:
+it is data about one workspace, not content of the package.
+
+The default registry path now resolves in tiers, and every tier is file
+existence plus configuration — nothing a pull request cannot diff:
+
+1. an explicit path, the positional of `simt graph lint`,
+2. the package's own `graph/skills.graph.json` — present in a source checkout,
+   absent from an installed copy,
+3. the member of a configured workspace that holds one — naming the workspace
+   it came from, and refusing when several members hold one, because picking
+   would be a guess.
+
+An installed copy in a workspace with no registry says so, and names the three
+ways to configure one (`--workspace`, `SIMT_DEV_WORKSPACE`, the user config
+file) instead of failing on a path it does not have. `simt graph lint`'s
+no-registry remedy names the path explicitly, because its default is the
+registry it lints.
+
+The provenance digest stops walking `graph/` for the same reason it no longer
+leaves the package: the digest covers what a published copy ships, and the
+registry is no longer among it.
+
+### No published file may name a repository from this estate
+
+The decision records ship in all three channels — npm, the wheel and the sdist — so a
+private repository name written into one is published to three registries. That happened:
+the records were pseudonymised once, across 28 files, and nothing stopped the next one. The
+sweep's own commit says why, and it is the right reason: the redaction it used runs on the
+way *out*, at print time, and the bytes on disk are what get published.
+
+`test/shipped.test.mjs` now fails on an estate name anywhere in a published file, and
+asserts its own scope against `package.json` in **both** directions — a directory added to
+`files` without being guarded fails, and so does one guarded that nothing publishes, because
+a guard nobody can fail is one somebody eventually deletes. It is scoped to the published
+set rather than a hand-written list for the same reason: the sweep took 28 files to undo by
+hand, and the guard should not need undoing at all.
+
+Names are not removed, they are described. The records that use a repository as *evidence* —
+a table of how three repositories answer the same question — carry stable `repo-NN` labels,
+so the comparison survives. Everything else is better off naming what the repository *is*:
+"a Gradle module with no wrapper", "a repository with no package.json". That reads to
+someone outside the estate without a lookup table they do not have.
+
+The one place estate names remain is `docs/reviews/`, which is not published by either
+channel. A review whose subject is fourteen repositories cannot pseudonymise them without
+becoming a document about `repo-01` that never existed.
+
+### Four shipped strings named a command this package does not install
+
+`0.2.0` installs one binary, `simt`, and `package.json`'s `bin` map says so. Four
+places still said `simt-dev`, which a reader types and is met with `unknown command`:
+
+- the default remedy on every bad invocation, `run: simt-dev --help` — so the advice
+  printed after a bad command could not be followed
+- the usage line, `usage: simt-dev <command>`, sitting above a command list that spelled
+  the same tool `simt`
+- `.github/dependabot.yml`'s header, which said `Yours from here: simt-dev` while the
+  gate beside it said `Yours from here: simt`
+- the hook shim, whose own resolution list said `simt-dev on PATH` directly above the
+  `command -v simt` that does the looking
+
+`test/naming.test.mjs` was supposed to prevent this and did not: its rule required a
+verb after the project name, and none of the four is followed by one. It now also
+catches a flag, a `<placeholder>`, the end of a line, and a program name in a
+resolution list — while still accepting the sentences where the project is the
+subject, which is the spelling that is correct. The two `.github` templates get their
+own assertion, because the fourth of these was not a wrong word in a sentence; it was
+two templates disagreeing with each other in the same position.
+
+### Fixed
+
+- `hooks install` removes a shim whose gate was dropped from the manifest instead of leaving it to run nothing. A repository that removed its last gate was refused outright, with a remedy telling it to put the gate back; only un-routing git was left to the reader. install also no longer chains a hook to itself.
+
+- **Dead exports and duplicated frontmatter, with a test that stops them returning (S21).**
+  Eight functions were exported and called by nothing (`gateKind`, `gateWhy`, `gateAdr`,
+  `resetWorkspace`, `tracksIdentity`, `isTty`, `surfaceFrontmatter`, `workspaceOrNull`),
+  three `__internals` testing seams had no importer, and thirteen more bindings were
+  exported while being used only inside their own file — `isExecutable` among them, which
+  a first pass through this list wrongly recorded as dead and which its own callers
+  proved otherwise. `KNOWN_SUBS` was a hand-kept second copy of the dispatch table, and
+  had already drifted: it carried `doctor`, a bare command the group lookup can never
+  reach. `mdcFrontmatter` was a second construction of frontmatter the writer now derives
+  itself, with a test asserting the copy rather than the behaviour.
+
+- **"Did you mean" offered the shortest fragment first, and a misspelt skill was
+  suggested for a correctly spelled one (S22).** `nearMatches` had no test at all.
+  Both directions of substring scored 0 — the same score as an exact match — so the
+  alphabetical tiebreak decided the order, and `skills graphs` suggested `graph`
+  before `graphs`. Worse, the containment test had no length floor, so `test` matched
+  the candidate `e` and the message read `did you mean e, test-writer?`, which an
+  agent has every reason to install. A prefix now scores 1 rather than 0, a fragment
+  counts only when it is at least half the query, and the edit bound scales with the
+  query's length — three edits is a typo in `slice-commmit` and is most of a
+  four-character query.
+
+- **The conflict scanner skipped two of the five rule surfaces, and one pointer file
+  (S22).** `rulePaths` enumerated filenames by hand, so `.claude/rules/` and
+  `.agents/rules/` — added to the surface table after the list was written — were
+  never scanned, and a hand-written rule contradicting a generated one there was
+  invisible. A conflict detector that only looks where it was pointed looks nowhere
+  new. The scan list is now derived from the surface table and the pointer table.
+
 ## [0.2.0] — 2026-10-11
 
 ### Publishable from PyPI and Homebrew as well as npm
@@ -48,17 +414,17 @@ recommending. It chained on the event *vocabulary* — anything that was not
 `pre-commit` or `pre-push` — when the question worth asking is whether **this
 repository** declares a gate for that event.
 
-The difference is `simt-app`, whose `pre-push` is `git-lfs`. `pre-push` is an
+The difference is a repository whose `pre-push` is `git-lfs`. `pre-push` is an
 event this tool gates in general, so `0.1.0` displaced that hook; and because
-`simt-app` declares no `pre-push` gate there was no shim for the event either, so
-git would have found no `pre-push` hook at all. LFS objects would have stopped
-being uploaded, with nothing to notice it — the exact silent failure chaining
-exists to prevent, reached by fixing the wrong half of it.
+that repository declares no `pre-push` gate there was no shim for the event
+either, so git would have found no `pre-push` hook at all. LFS objects would have
+stopped being uploaded, with nothing to notice it — the exact silent failure
+chaining exists to prevent, reached by fixing the wrong half of it.
 
 `0.1.1` asks the manifest. An event the repo declares a gate for is left to
 `gates.commands`, where the hook runs as a gate and its verdict appears in the
-report; every other foreign hook is chained. That also picks up
-`simt-landing`'s Lighthouse pre-push, which declares no gates at all.
+report; every other foreign hook is chained. That also picks up a static
+site's Lighthouse pre-push, which declares no gates at all.
 *(ADR-018, as amended)*
 
 Upgrade with `npm i -D simt-dev@0.1.1`, then `simt hooks install --yes`. Any
@@ -161,6 +527,8 @@ 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.2.2]: https://github.com/QuazarMedia/simt-dev/releases/tag/v0.2.2
+[0.2.1]: https://github.com/QuazarMedia/simt-dev/releases/tag/v0.2.1
 [0.2.0]: https://github.com/QuazarMedia/simt-dev/releases/tag/v0.2.0
 [0.1.1]: https://github.com/QuazarMedia/simt-dev/releases/tag/v0.1.1
 [0.1.0]: https://github.com/QuazarMedia/simt-dev/releases/tag/v0.1.0

package/README.md

@@ -23,13 +23,13 @@ Requires **Node >= 22.20.0** (the PyPI install can supply it, see below).
 
 ```sh
 # pinned, per repository - what CI and a teammate both get
-npm i -D simt-dev@0.2.0
+npm i -D simt-dev@0.2.1
 
 # or globally, if you would rather not add a dependency
-npm i -g simt-dev@0.2.0
+npm i -g simt-dev@0.2.1
 
 # or with no install at all, for a one-off
-npx -y simt-dev@0.2.0 check
+npx -y simt-dev@0.2.1 check
 ```
 
 ### From PyPI
@@ -81,7 +81,7 @@ simt compare         # what changed across every repository that adopted it
 | Path | What |
 | --- | --- |
 | `AGENTS.md` | the projection, between `<!-- simt:begin -->` and `<!-- simt:end -->` (renamed from `simt-dev:`; the old markers are still read, and a region migrates on its next write) |
-| `simt.json` | your manifest: which gates to declare, which substitutions to fill (renamed from `simt-dev.json`; the old name is still read, and moves on the next write) |
+| `simt.json` | your manifest: which gates to declare, which substitutions to fill |
 | `.cursor/rules/*.mdc`, `.claude/rules/*.md`, `.agents/rules/*.md`, `.github/instructions/*.instructions.md` | one file per rule, written only for the harnesses that read their own directory |
 | `.editorconfig`, `.gitattributes` | baseline regions |
 | `.simt-hooks/` and `core.hooksPath` | the shared dispatcher, fail-closed |

package/docs/decisions/ADR-019-a-declared-command-is-the-runner.md

@@ -72,6 +72,33 @@ One manifest. Three answers. The one I would have shipped if I had only run `che
    every file (`ENOTDIR`) and classified every Gradle repository in the estate as having no
    runner at all — a wrong answer from an evidence reader, which is worse than no answer
    because the caller cannot tell them apart.
+8. **A declared command is a shell command line, not an argv.** *(S17, 2026-10-12)*
+
+   It was split on whitespace and handed to `execFile` as an argv. That made a declaration
+   a repository would plausibly write run the wrong thing rather than fail: a flag whose
+   value contains a space became two arguments, and the quotes in a compound line were
+   passed to the program as literal characters. There was no way to express a quoted
+   argument at all, and nothing said so.
+
+   So `gates.commands[name]` is one line, run through `sh -c`, and everything the
+   repository wrote in it survives — quotes, pipes, `&&`, a path with a space. This is the
+   same line the repository would type into its own shell, which is the only definition of
+   "what this repository means by that" that does not require a parser here.
+
+   **The trust boundary is the repository, and it is not a sandbox.** The line comes from
+   the repository's own manifest, which it can read and change, and it runs on its author's
+   own machine when that author commits. `sh -c` adds no privilege: the same person who
+   wrote the line could run it. What `sh -c` must not do is apply to anything this tool
+   resolved itself — a formatter path out of `node_modules/.bin` stays an argv, because
+   handing it to a shell would change who decided its arguments for no gain. The two
+   sources are separate branches in the dispatcher rather than a flag, so the distinction
+   cannot be forgotten by a caller that does not know it exists.
+
+   **Consequence for a repository that relied on the split.** A declaration with no quotes
+   behaves identically, because whitespace-splitting a shell word that needed no quoting
+   is the same thing the shell does. Every use of `gates.commands` in this estate declares
+   a bare path and is unaffected; the change only makes declarations *possible* that were
+   previously impossible rather than making any of them wrong.
 
 ## Consequences
 

package/docs/decisions/ADR-059-the-version-a-repository-runs-is-the-one-it-pinned.md

@@ -0,0 +1,75 @@
+# ADR-059 — The version a repository runs is the one it pinned, and the gate refuses otherwise
+
+Status: **accepted** · 2026-10-12 · affects all repos
+
+## Context
+
+ADR-010 ruled that a tool which is genuinely not a project dependency may be invoked directly,
+**provided its version is pinned**. For a repository with a `package.json`, simt-dev is that
+dependency, and npm does the pinning: it installs the version in `package.json` into
+`node_modules`, and a stale copy is a stale lockfile that `npm ci` reproduces.
+
+For a repository **without** npm — a Gradle build, a Connect IQ project — there is no
+`node_modules` to pin in. simt-dev is a global install, and nothing pins it. The version on
+`PATH` is whatever the last `npm i -g` left there, and it can be anything. The gate that runs
+on commit is the one in that binary. If it is not the version the repository adopted, the gate
+that runs locally is not the one CI runs: a green tick from a check that ran the wrong version
+is the one outcome worse than a red build, because it is a pass that never happened.
+
+The same gap sat in the remedy. The shim and the consumer workflow assumed npm everywhere —
+`npm i -D simt-dev@<v>` and `npm ci`. In a Gradle repository that command installs into a
+`package.json` the repository will never have, so the remedy cannot succeed and the CI step
+cannot start. The install and the remedy each needed to know the kind of repository they were
+in, and neither did.
+
+## Ruling
+
+1. **The manifest records the version a repository adopted.** `projection` carries
+   `version` alongside the existing `simtDevSha`, written at adoption and refreshed by
+   `upgrade`. A node_modules copy is pinned by npm itself, so this field matters only where
+   npm is not the pin — but it is written everywhere, because a manifest that records the
+   version in one shape of repository and not another is two manifests.
+
+2. **The gate compares the running binary against that pin, and refuses on a mismatch.** The
+   comparison is in the dispatcher (a failed `version` gate) and in `check` (a blocking
+   finding), not in the shim's rendered bytes: the dispatcher is where every gate already runs,
+   and a comparison duplicated into bytes a formatter might rewrite would drift from the one
+   that decides. It is placed after the empty-gate check on purpose — a repository that declares
+   no gate has nothing the version could get wrong, and failing it would block commits in repos
+   that deliberately declare none.
+
+3. **The install and the remedy are per kind.** Where a `package.json` exists, simt-dev is pinned
+   as a devDependency and the remedy is `npm i -D simt-dev@<v>`. Where there is no npm, it is a
+   pinned global install and the remedy is `npm i -g simt-dev@<v>` (or `export SIMT_DEV_BIN=…`).
+   The consumer CI workflow makes the same choice by kind — `npm ci` where the package is a
+   declared dependency, the pinned global install otherwise — so the gate that runs in CI is the
+   one the machine remedy names, and a check cannot pass in one place and fail to start in the
+   other.
+
+## Consequences
+
+- A stale global binary can no longer produce a green tick from a check that ran a different gate
+  than CI does. The mismatch is a refusal with the one command that fixes it, and the remedy and
+  the CI step agree on which version to install.
+- A repository adopted before the field existed — a manifest with `simtDevSha` but no
+  `projection.version` — is **skipped, not failed**. There is nothing to compare against, and
+  failing every pre-0.2 repository the moment this check ships would turn the gate red for a
+  reason it cannot fix. `compare` reports that missing field as a stale manifest (ADR-045's
+  defect from the far side), so it is visible and repairable rather than silently absent.
+- The version a repository runs is now an invariant the gate enforces, not a comment: the pin in
+  the manifest and the binary on `PATH` must agree, or the commit does not happen.
+
+## Rejected
+
+- **Shell out to `simt --version` in the shim.** The dispatcher runs from the binary that
+  resolved it, so reading the running package's version is the same answer without a subprocess,
+  and it is correct whether the binary came from `node_modules`, a global install, or a source
+  checkout. A subprocess would answer only for the binary that started it.
+- **Fail a repository with no recorded pin.** There is nothing to compare against; it would make
+  every pre-0.2 repository red on the day this ships, for a mismatch nobody can resolve until
+  they re-adopt. The missing pin is reported as drift, which is the repairable form of the same
+  fact.
+- **Put the check only in the shim's rendered bytes.** The dispatcher is where every gate runs and
+  where `check` already lives, so the comparison belongs in one place. Rendered bytes are read by
+  a formatter and a reviewer; a control that lives in both is two copies of one question, which
+  is the shape this record's siblings keep finding drifting.