simt-dev 0.1.1 → 0.2.1

package/CHANGELOG.md

@@ -4,6 +4,207 @@ 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.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
+
+simt-dev is a *repository* tool, and the people who adopt a repository are not
+all Node developers. Somebody running `simt init` inside a repository with no
+`package.json` has no reason to install a package manager, and a Homebrew user
+has no reason to install Node to install a tool that needs Node.
+
+So it now publishes to three channels, from one version number:
+
+```sh
+npm i -D simt-dev        # a tarball of .mjs files
+pip install simt-dev      # a wheel carrying those same bytes
+brew install QuazarMedia/tap/simt-dev
+```
+
+The wheel is not a wrapper around `npm install`. It carries the tool's own
+source, and `scripts/verify-wheel.mjs` builds both artefacts and hashes every
+file in both — a release fails when a single byte differs between them. That
+check exists because the obvious defect in this arrangement is the wheel and the
+tarball quietly shipping different code.
+
+`simt` is the one command, on every channel. Where node comes from is
+`SIMT_DEV_NODE`, then the bundled node from `pip install "simt-dev[node]"`,
+then `node` on `PATH` — and if none of those resolve you get the remedy rather
+than a placeholder path. There are no required dependencies on any channel.
+*(ADR-058)*
+
+The channels are published in a fixed order rather than in parallel, and the
+reason is not taste: the Homebrew formula downloads the npm tarball at install
+time, so a formula naming a version still sitting in npm's staging area
+installs a 404. Both jobs fail with that stated, and are run again after
+`npm stage approve`.
+
 ## [0.1.1] — 2026-10-11
 
 ### A foreign hook on an event this repo does not gate is chained
@@ -13,17 +214,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
@@ -126,5 +327,6 @@ 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.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

@@ -19,19 +19,46 @@ that refuses a commit which breaks a gate that repo can genuinely run.
 
 ## Install
 
-Requires **Node >= 22.20.0**.
+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.1.1
+npm i -D simt-dev@0.2.1
 
 # or globally, if you would rather not add a dependency
-npm i -g simt-dev@0.1.1
+npm i -g simt-dev@0.2.1
 
 # or with no install at all, for a one-off
-npx -y simt-dev@0.1.1 check
+npx -y simt-dev@0.2.1 check
 ```
 
+### From PyPI
+
+The same tool, from the same bytes. The wheel carries the exact contents the npm
+tarball carries — the wheel is not a wrapper around `npm install`, so nothing is
+fetched when you install it.
+
+```sh
+pip install simt-dev
+
+# and if this machine has no node at all
+pip install "simt-dev[node]"
+```
+
+`simt` is the command on both channels. Where node comes from is resolved in
+this order, and the first one that answers wins: `SIMT_DEV_NODE`, the bundled
+node from the `node` extra, then `node` on your `PATH`. If none of them resolve,
+you get a message naming the remedy rather than a placeholder node path.
+
+### From Homebrew
+
+```sh
+brew install QuazarMedia/homebrew-tap/simt-dev
+```
+
+The formula declares its own `node` dependency, so `brew install` gives you a
+working command on a machine that has never had Node.
+
 Pin the version. The tool writes a content digest into the files it generates, and an
 unpinned upgrade changes them under you.
 
@@ -54,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-001-push-requires-approval.md

@@ -8,14 +8,14 @@ The repos state a commit/push policy. They disagree on whether an agent may push
 
 - A repo outside this estate: "always create a focused Git commit… skip the commit only
   when the user explicitly asks not to commit." Silent on push.
-- `simt-garmin/AGENTS.md` DoD #8: "**Committed and pushed** with a conventional message."
-- `simt-social` and `simt-social-api`: "create a non-interactive Conventional Commit. Report
+- `repo-07/AGENTS.md` DoD #8: "**Committed and pushed** with a conventional message."
+- `repo-14` and `repo-11`: "create a non-interactive Conventional Commit. Report
   the commit SHA; **do not push**."
-- `simt-api`, `simt-social-media`: silent.
+- `repo-04`, `repo-13`: silent.
 
 The Social pair justify it: a push to the production branch triggers Cloudflare Workers Builds,
 so "an approved push is therefore a production deployment action, not only source publication."
-`simt-garmin` has no such coupling, and its rule asks for an autonomous push.
+`repo-07` has no such coupling, and its rule asks for an autonomous push.
 
 ## Ruling
 
@@ -24,7 +24,7 @@ Commit locally, report the SHA, **push only on explicit user approval**.
 When a repo's push triggers a deployment, a migration, or any remote mutation, say so before
 asking for approval — do not treat approval for the push as approval for the deploy.
 
-`simt-garmin` DoD #8 changes to "committed with a conventional message; pushed on approval."
+`repo-07` DoD #8 changes to "committed with a conventional message; pushed on approval."
 This is the single outlier, and the 4:1 majority is also the safe direction.
 
 ## Consequences

package/docs/decisions/ADR-002-refactor-blast-radius.md

@@ -6,7 +6,7 @@ Status: **accepted** · 2026-10-05 · affects all repos
 
 Two repos state opposite philosophies, and both are reasonable in isolation.
 
-- `simt-social` / `simt-social-api`: "When a second real use or a near-duplicate already
+- `repo-14` / `repo-11`: "When a second real use or a near-duplicate already
   exists, refactor the existing code to extract the shared part… A third copy of the same
   logic is a defect, and so is an abstraction invented for a single caller."
 - A repo outside this estate: "Match existing style, naming, and test layout. **Do not

package/docs/decisions/ADR-003-test-breadth.md

@@ -4,13 +4,13 @@ Status: **accepted** · 2026-10-05 · affects all repos
 
 ## Context
 
-- `simt-social` / `simt-social-api`: "Focused tests are the default gate, and full suites are
+- `repo-14` / `repo-11`: "Focused tests are the default gate, and full suites are
   the exception… **absent a named trigger, running a full suite is a defect, not diligence.**"
 - A repo outside this estate: `fail_under = 100` plus a full-suite script as the pre-push
   default, and a contributor loop that says "run the full gate locally (lint + tests +
   coverage)."
-- `simt-garmin`: reframes the axis entirely as a layer-conditional 5a–5m matrix.
-- `simt-social-media`: no policy — it just lists `npm run test:unit && npm run test:e2e`.
+- `repo-07`: reframes the axis entirely as a layer-conditional 5a–5m matrix.
+- `repo-13`: no policy — it just lists `npm run test:unit && npm run test:e2e`.
 
 The Social pair make a full suite a sin. media presents it as unremarkable. The hard-gate
 repo makes it mandatory. These cannot all be org rules as stated.
@@ -34,7 +34,7 @@ adopted as canonical.
 ## Consequences
 
 - Each repo's `simt-dev.json` declares which of the six triggers are active for it. A repo
-  with a declared numeric gate activates 4 and 6; the Social repos activate 1, 2 and 3.
+  with a declared numeric gate activates 4 and 6; one repository activate 1, 2 and 3.
 - A reviewer can ask "which trigger?" and get a number, not an opinion.
 - media gains an explicit policy instead of an implicit one that contradicts its siblings.
 

package/docs/decisions/ADR-004-hook-owns-format.md

@@ -4,16 +4,16 @@ Status: **accepted** · 2026-10-05 · affects all repos
 
 ## Context
 
-- `simt-social-api`: "lint and format are enforced by the pre-commit hook — **do not run them
+- `repo-11`: "lint and format are enforced by the pre-commit hook — **do not run them
   manually.**"
-- `simt-social`: "the local pre-push hook republishes opportunistically when a token happens to
+- `repo-14`: "the local pre-push hook republishes opportunistically when a token happens to
   be present." Never says the hook is the gate; instructs agents to run static checks directly.
 - A repo outside this estate: tells agents to run its linter and `git diff --check` by hand,
   and its contributor guide repeats it.
-- `simt-api`, and 11 repos with no hooks at all: silent.
+- `repo-04`, and 11 repos with no hooks at all: silent.
 
 The audit also found the estate's hook reality: 4 incompatible conventions, and
-`simt-app/hooks/pre-push` is **0 bytes** while the real git-lfs pre-push sits unused in
+`repo-05/hooks/pre-push` is **0 bytes** while the real git-lfs pre-push sits unused in
 `scripts/hooks/`.
 
 ## Ruling
@@ -33,7 +33,7 @@ skip.
 ## Consequences
 
 - The shared hook dispatcher from plan 0001 lands in every repo that has one, which also
-  delivers the dead `simt-app/hooks/pre-push` fix.
+  delivers the dead `repo-05/hooks/pre-push` fix.
 - `simt-dev doctor` reports hook installation state, so "the hook will cover it" is a
   verifiable claim rather than an assumption.
 - The 11 hook-less repos get a pre-commit on adoption, which ends the silent case entirely.

package/docs/decisions/ADR-005-file-length.md

@@ -4,9 +4,9 @@ Status: **accepted** · 2026-10-05 · affects all repos
 
 ## Context
 
-- `simt-social` / `simt-social-api`: "**Split any file once it exceeds 1000 lines**; extract
+- `repo-14` / `repo-11`: "**Split any file once it exceeds 1000 lines**; extract
   along the nearest cohesive boundary instead of growing the file further."
-- `simt-garmin`: "**File length: 400 lines is a smell threshold, not a hard gate.**" Generated
+- `repo-07`: "**File length: 400 lines is a smell threshold, not a hard gate.**" Generated
   `.mc` files are exempt, with a named exception for a 408-line template.
 - Several repos: no file-length rule stated at all.
 
@@ -27,10 +27,10 @@ Per-repo overrides are permitted via `limits.fileLines` in `simt-dev.json`.
 
 ## Consequences
 
-- The Social repos' hard 1000 gate and garmin's soft 400 both survive unchanged in force.
+- one repository' hard 1000 gate and garmin's soft 400 both survive unchanged in force.
 - The generated-file exemption that garmin had to state in prose becomes a declared property,
   so the hook can honour it without hardcoding `.mc`.
-- `simt-social`'s pre-commit file-size check (currently inlined as 1000 lines of shell, and
+- `repo-14`'s pre-commit file-size check (currently inlined as 1000 lines of shell, and
   duplicating `scripts/check-file-sizes.ts`) becomes one implementation in the shared
   dispatcher.
 
@@ -38,5 +38,5 @@ Per-repo overrides are permitted via `limits.fileLines` in `simt-dev.json`.
 
 - **One number org-wide.** Either it is too tight for legitimately long declarative files or
   too loose to prompt a human at 400.
-- **No rule.** The Social repos' pre-commit check exists precisely because a rule was missing,
+- **No rule.** one repository' pre-commit check exists precisely because a rule was missing,
   and it is now implemented twice.

package/docs/decisions/ADR-006-coverage-bar.md

@@ -9,9 +9,9 @@ The coverage bar is the one concept that is mutually incompatible *in kind* acro
 | Repo | Bar |
 |---|---|
 | Repos with a declared numeric bar (outside this estate) | Quantitative. `fail_under = 100`, branch coverage, "a behavioural coverage gate, not a line-count scoreboard" |
-| `simt-garmin` | Quantitative, but a different quantity. Memory: 64 KB app / 24 KB Glance against a 32 KB ceiling, plus 12 named lint scripts |
-| `simt-social`, `simt-social-api`, `simt-social-media` | Qualitative. No number anywhere. Evidence discipline: named commands, 100 % pass, no unjustified skips, behavioural test delta |
-| `simt-api` | Neither. Three verification commands. |
+| `repo-07` | Quantitative, but a different quantity. Memory: 64 KB app / 24 KB Glance against a 32 KB ceiling, plus 12 named lint scripts |
+| `repo-14`, `repo-11`, `repo-13` | Qualitative. No number anywhere. Evidence discipline: named commands, 100 % pass, no unjustified skips, behavioural test delta |
+| `repo-04` | Neither. Three verification commands. |
 
 You cannot average these. 100 % line coverage is unreachable for Kotlin/Compose UI code and for
 Monkey C memory budgets; a memory ceiling is not a coverage proxy; "no number" is not a weaker

package/docs/decisions/ADR-007-section-skeleton.md

@@ -8,9 +8,9 @@ Six `AGENTS.md` files use the same conceptual sections under three different hea
 
 | File | Authority | Invariants |
 |---|---|---|
-| `simt-api`, `simt-social-media` | "Authority and Scope" | "Non-Negotiable Invariants" |
-| `simt-garmin`, `simt-social` | "Authority and scope" | "Non-negotiable invariants" |
-| `simt-social-api` | "Authority and **ownership**" | "Non-negotiable invariants" |
+| `repo-04`, `repo-13` | "Authority and Scope" | "Non-Negotiable Invariants" |
+| `repo-07`, `repo-14` | "Authority and scope" | "Non-negotiable invariants" |
+| `repo-11` | "Authority and **ownership**" | "Non-negotiable invariants" |
 
 At least one repo outside this estate uses a numbered 12-part layout with no equivalent
 sections at all.
@@ -43,12 +43,12 @@ knows immediately what breaking it costs and who may change it.
 
 - Cross-repo reading becomes possible: section N means the same class of thing everywhere.
 - A future grep for "what are the invariants" returns a comparable list across all 16 repos.
-- "Ownership" is kept in the heading because `simt-social-api` earned it by being the only
+- "Ownership" is kept in the heading because `repo-11` earned it by being the only
   file that enumerates ownership explicitly.
 
 ## Rejected
 
-- **Standardise on Title Case** (`simt-api`'s variant). Capitalisation in headings is noise;
+- **Standardise on Title Case** (`repo-04`'s variant). Capitalisation in headings is noise;
   three repos already use sentence case.
 - **Normalise a differently-shaped layout immediately.** A mechanical conversion of 12
   numbered parts would produce a worse document than a mapping.

package/docs/decisions/ADR-008-verdict-vocabulary.md

@@ -6,7 +6,7 @@ Status: **accepted** · 2026-10-05 · affects all repos
 
 The estate has two incompatible verdict vocabularies.
 
-`.cursor/rules/test-gate.mdc` — used by all three Social repos — allows one outcome:
+`.cursor/rules/test-gate.mdc` — used by all three one repository — allows one outcome:
 
 > Return `BLOCK` when: any test fails, is skipped without pre-existing justification, or is
 > unrun; the executable diff has no test delta without explicit justification; the coordinator

package/docs/decisions/ADR-009-skill-layout.md

@@ -23,7 +23,7 @@ to come from the graph registry instead — which is why `paths` lives in
 - A skill is a directory `<name>/` containing `SKILL.md`.
 - `name` and `description` are **mandatory** in frontmatter.
 - `argument-hint` is recommended for any skill invoked by hand, and is optional otherwise —
-  simt-app's 7 skills omit it legitimately, since they are task-shaped rather than
+  repo-05's 7 skills omit it legitimately, since they are task-shaped rather than
   user-invoked.
 - Body size and reference-file count are declared in `graph/skills.graph.json`, not in
   frontmatter, so the registry stays the single source of truth for resolution metadata.

package/docs/decisions/ADR-010-runner-invocation.md

@@ -6,7 +6,7 @@ Status: **accepted** · 2026-10-05 · affects all repos
 
 Four repos independently arrived at the same rule, in two ecosystems, with the same rationale.
 
-- `simt-social` / `simt-social-api`: "Run tests and quality checks through repository `npm run
+- `repo-14` / `repo-11`: "Run tests and quality checks through repository `npm run
   ...` scripts… **Do not invoke local package binaries through `npx` or `npm exec`** unless no
   repository script supports the required operation."
 - A Python repo outside this estate, in the same form: "**Do not use `uv run pytest`**; the

package/docs/decisions/ADR-012-drop-windows-support.md

@@ -20,8 +20,8 @@ work:
 5. CI must carry a permanent `windows-latest` job.
 
 Against that: **no Windows developer appears anywhere in the repos**, and no repo's own
-toolchain is Windows-ready either — `simt-garmin` drives the Monkey C toolchain, and
-`simt-app`/`wakt-app`/`app-ui` drive Gradle and Android tooling. So the CLI would have been the
+toolchain is Windows-ready either — `repo-07` drives the Monkey C toolchain, and
+`repo-05`/`repo-03`/`repo-01` drive Gradle and Android tooling. So the CLI would have been the
 *only* Windows-ready artefact in the estate, serving nobody.
 
 The deciding argument is not the cost, it is the shape: obligations 1–3 are correctness

package/docs/decisions/ADR-015-a-source-is-content-not-a-location.md

@@ -9,9 +9,9 @@ Affects: `resolve/source.mjs`, `skills install`, `skills show`, `skills brief`
 single-repo use first class. It fixed resolution, not lookup, and the next defect was found
 immediately by the user who asked for the previous one.
 
-Someone who cloned **only `simt-social`** has the `simt-social` body of `slice-commit` on disk at
+Someone who cloned **only `repo-14`** has the `repo-14` body of `slice-commit` on disk at
 `.agents/skills/slice-commit`. They have no workspace. The registry entry
-`simt-social/.agents/skills/slice-commit` is satisfied by that file. Both commands refused:
+`repo-14/.agents/skills/slice-commit` is satisfied by that file. Both commands refused:
 
 ```
 $ simt-dev skills install slice-commit

package/docs/decisions/ADR-016-a-divergent-rule-is-retired-not-merged.md

@@ -15,8 +15,8 @@ Affects: `rules/mdc/*.mdc`, `projection/mdc.mjs`, `projection/project.mjs`, `pro
 The estate carried three always-on `.mdc` rule families across three repos, in eight
 files, with no two byte-identical.
 
-The worst pair differed by **one byte** (`simt-social/.cursor/rules/intake-questions.mdc`
-at 1280 against `simt-social-api`'s at 1281) while hiding three semantically loaded line
+The worst pair differed by **one byte** (`repo-14/.cursor/rules/intake-questions.mdc`
+at 1280 against `repo-11`'s at 1281) while hiding three semantically loaded line
 changes: a plan-tracker path rewritten to point at the other repo, `migrations` added to the
 list of decisions worth asking about, and a requirement silently dropped. No size-, hash-,
 hash-adjacency- or line-count-based duplicate detector could ever have flagged that pair. The
@@ -26,18 +26,18 @@ difference, it is a semantic loss**, and the smaller copy is the one missing a r
 Reading all eight produced three findings that a variant mechanism cannot represent:
 
 1. `test-gate`'s fourth `BLOCK` bullet is **complementary across the pair, not alternative**.
-   `simt-social` blocks a consumer that requires an API field with no backward-compatibility
-   or deploy-order evidence; `simt-social-api` blocks a producer that ships without a test
+   `repo-14` blocks a consumer that requires an API field with no backward-compatibility
+   or deploy-order evidence; `repo-11` blocks a producer that ships without a test
    asserting the new invariant. Each repo's reviewer was told to check only its own half.
 2. `preview-postflight`'s second Requirements bullet is likewise complementary, and looks
-   like a conflict because the two files put different rules in the same slot: `simt-social`
+   like a conflict because the two files put different rules in the same slot: `repo-14`
    says set `SOCIAL_API_BASE_URL` in the Cloudflare Workers Builds preview environment;
-   `simt-social-api` says credentials live in the operator keychain only, never in source,
+   `repo-11` says credentials live in the operator keychain only, never in source,
    chat, D1 or logs.
-3. Two deletions left no trace. `simt-social-api` dropped `simt-social`'s worked example
+3. Two deletions left no trace. `repo-11` dropped `repo-14`'s worked example
    (`Partial pass (e.g. 6/8 pass) is a hard blocker`) — the example is what does the work,
    and its removal is invisible in a diff review because the rule's normative force looks
-   unchanged. `simt-social-media` dropped the entire `## Allowed Without Account` section, so
+   unchanged. `repo-13` dropped the entire `## Allowed Without Account` section, so
    it has no documented set of probes that are legal without credentials.
 
 A variant mechanism models "these are the same rule, rendered per stack". None of these three
@@ -79,7 +79,7 @@ the rule would either hard-code one repo's paths for everyone or push the decisi
 prose, which is the drift this mechanism exists to remove.
 
 An **empty** value, or an empty default, drops the line it sits on. That is how one canonical
-file reaches `simt-social-media` (no plan-tracker note) and `simt-space` (not a Workers repo
+file reaches `repo-13` (no plan-tracker note) and `repo-15` (not a Workers repo
 at all) without printing a blank bullet. A placeholder with neither a default nor a
 declaration is a **gate failure**, because a rule shipping a literal `{{key}}` reads as
 finished and is not.
@@ -88,7 +88,7 @@ finished and is not.
 
 `preview-postflight` declares `applies: []` and `optIn: true`. It names specific preview
 Workers, `AUTH_PROVIDER_POLICY`, `POSTFLIGHT_PASSWORD_UID` and specific production domains.
-Selecting it on `cloudflare-workers` would hand it to `simt-space` and `simt-goto` — Workers
+Selecting it on `cloudflare-workers` would hand it to `repo-15` and `repo-08` — Workers
 repos with no preview Workers and no Social identity — which is the same over-match bug that
 `rules/stacks/react-web.md` had when it declared `typescript` and `vitest`.
 
@@ -128,7 +128,7 @@ Silent deletion is the one thing a reviewer cannot audit.
 
 `RULE_FILES` named only `AGENTS.md`, `CLAUDE.md` and `CONTRIBUTING.md` for the whole life of
 the tool. `simt-dev init` therefore reported **`CONFLICTS none detected`** on
-`simt-social-api` — the repo holding the worst-drifted content in the estate — because it
+`repo-11` — the repo holding the worst-drifted content in the estate — because it
 never looked at the `.mdc` files at all.
 
 A detector that only knows the filenames it was written for will quietly miss a whole rule
@@ -144,7 +144,7 @@ the same failure, one level down.
 
 ### 6. An autonomous-push probe must match every phrasing the estate actually used
 
-The probe matched `committed and pushed`, which is `simt-garmin`'s exact DoD wording. A
+The probe matched `committed and pushed`, which is `repo-07`'s exact DoD wording. A
 different author wrote `Always commit and pushed`; another would write `commit and push`. The
 first version matched only the first form and reported a real autonomous-push rule as clean.
 
@@ -168,7 +168,7 @@ the estate's real text, not against text written to match the probe.**
 
 - **A variant mechanism per stack** (one `test-gate.mdc` per repo). This is what produced the
   drift; modelling it as intended behaviour would make the drift permanent and legitimate.
-- **Picking the "best" copy per family and adopting it as canonical.** `simt-social`'s
+- **Picking the "best" copy per family and adopting it as canonical.** `repo-14`'s
   `test-gate` is the better copy only by accident; it is missing the producer-side `BLOCK`
   bullet that social-api has. Choosing one per family would have discarded a real rule.
 - **Deleting the 8 files outright** rather than generating over them. A repo with no

package/docs/decisions/ADR-017-a-declared-gate-must-be-runnable.md

@@ -5,7 +5,7 @@ Affects: `hooks/capability.mjs`, `projection/manifest.mjs`, `commands/init.mjs`,
 
 ## Context
 
-The first real adoption wrote a manifest declaring five gates into `simt-social-media`.
+The first real adoption wrote a manifest declaring five gates into `repo-13`.
 Three of them could not run:
 
 | Gate | Kind | Why it could not run |
@@ -25,7 +25,7 @@ user does after adopting simt-dev is discover that the tool makes committing imp
 the only escape any of them will find is `--no-verify`.
 
 That is the exact spiral the dispatcher was built to prevent. Step 8's design note says a gate
-that cannot run must be a failure rather than a skip, precisely because `simt-space` removed
+that cannot run must be a failure rather than a skip, precisely because `repo-15` removed
 tests from `pre-commit` for being slow and the team's answer was `--no-verify`. Failing closed
 is right; declaring an unrunnable gate is wrong.