simt-dev 0.1.1 → 0.2.0

package/CHANGELOG.md

@@ -4,6 +4,41 @@ 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).
 
+## [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
@@ -126,5 +161,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.0
 
 # 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.0
 
 # or with no install at all, for a one-off
-npx -y simt-dev@0.1.1 check
+npx -y simt-dev@0.2.0 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.
 

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.
 

package/docs/decisions/ADR-018-an-unset-hooks-path-is-not-an-absent-hook.md

@@ -6,14 +6,14 @@ Affects: `simt-dev hooks install`, `simt-dev hooks status`, `simt-dev compare`,
 
 ## Context
 
-Phase 4 began by piloting `simt-dev init` on `simt-space`. The dry run was
+Phase 4 began by piloting `simt-dev init` on `repo-15`. The dry run was
 unremarkable. The defect appeared when I read what `hooks install` would actually
 do to that repository, which is something I had not done in any of the earlier
 phases.
 
-`simt-space` has a hand-written `.git/hooks/pre-commit` — 4088 bytes, with prose
+`repo-15` has a hand-written `.git/hooks/pre-commit` — 4088 bytes, with prose
 explaining why it deliberately does not run tests. `core.hooksPath` is unset.
-`simt-dev hooks status --root ../simt-space --json` reported:
+`simt-dev hooks status --root ../repo-15 --json` reported:
 
 ```json
 { "hooksPath": null, "installed": [{ "event": "pre-commit", "present": false }],
@@ -64,7 +64,7 @@ question, which is why fixing the shared one changed nothing visible.
 1. **Ask git where hooks are, never infer it from whether config exists.**
    `resolveHooksDir(root)` implements the two rules directly: `core.hooksPath`
    when set (a relative value resolves against the top of the working tree, which
-   is what makes `simt-app`'s `hooks` work), otherwise `<git-common-dir>/hooks`.
+   is what makes `repo-05`'s `hooks` work), otherwise `<git-common-dir>/hooks`.
 
    `git rev-parse --git-path hooks` is the obvious shortcut and is unusable. It
    returns `.git/hooks` in a normal repository, `hooks` in a linked worktree, and
@@ -103,7 +103,7 @@ question, which is why fixing the shared one changed nothing visible.
 7. **A foreign hook for an event this tool does not gate is chained, not stopped.**
    `core.hooksPath` does not scope this tool to the events it cares about and leave
    the rest to git; git reads *every* hook from the named directory and from nowhere
-   else. So the moment routing lands, `simt-app`'s `post-checkout`, `post-commit`
+   else. So the moment routing lands, `repo-05`'s `post-checkout`, `post-commit`
    and `post-merge` — events this tool gates nothing about — stop running. Nothing
    fails, nothing is logged, and the hook is still on disk looking intact: the
    failure is indistinguishable from the hook having passed. Ruling 3's refusal
@@ -128,9 +128,9 @@ question, which is why fixing the shared one changed nothing visible.
    anything the author sees.
 
    "Does this tool gate it" is a fact about the manifest, not about the event vocabulary,
-   and reading it the second way cost `simt-app` its `pre-push`. That hook is git-lfs.
+   and reading it the second way cost `repo-05` its `pre-push`. That hook is git-lfs.
    `pre-push` is an event this tool gates *in general*, so a vocabulary check displaced it
-   — and because `simt-app` declares no `pre-push` gate there is no shim for that event
+   — and because `repo-05` declares no `pre-push` gate there is no shim for that 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 same silent failure this ruling
    exists to prevent, reached by fixing the wrong half of it. The test asks the manifest.
@@ -154,8 +154,8 @@ a list that rots, so one test now asserts the two agree and another asserts ever
 row carries `notes` and `foreignHooks` even when empty.
 
 Measured across the estate after the fix, six repositories run hooks simt-dev did
-not write — `simt-space` (4088 B), `simt-app` (four hooks), `simt-social` (two),
-`simt-social-api` (two), `simt-landing` (one), and the `.wt-wear-redesign`
+not write — `repo-15` (4088 B), `repo-05` (four hooks), `repo-14` (two),
+`repo-11` (two), `repo-10` (one), and the `.wt-wear-redesign`
 worktree (five, including the `git-lfs` `pre-push`). Every one of them would have
 been silently taken over.
 

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

@@ -8,21 +8,21 @@ Affects: `simt-dev init`, `simt-dev check`, `simt-dev hooks status`, `simt-dev h
 ## Context
 
 ADR-017 made `simt-dev init` declare only gates a repository can actually run, and it shipped
-green because the first adopter — `simt-social-media` — is a Node repository whose scripts
+green because the first adopter — `repo-13` — is a Node repository whose scripts
 and binaries are exactly what the filter understood. It was verified by running that
 repository's own tests.
 
-`simt-app`, the third pilot, is a Gradle repository. It has **no `package.json` at all**. The
+`repo-05`, the third pilot, is a Gradle repository. It has **no `package.json` at all**. The
 dry run dropped all five proposed gates, and the remedy for each one was an instruction the
 reader cannot follow. The output as it stood, before this record was written:
 
 ```
-$ simt-dev init --root ../simt-app
+$ simt-dev init --root ../repo-05
   dropped   gate test: no "test" script in package.json
             remedy: add a "test" script to package.json, then re-run: simt-dev init --yes
 ```
 
-Ruling 4 changes both lines. `simt-app` will never have a `package.json`. "Install prettier as
+Ruling 4 changes both lines. `repo-05` will never have a `package.json`. "Install prettier as
 a dev dependency" is equally impossible. The filter was right about the facts and wrong about
 what followed from them, and the reader's only honest reaction to that remedy is to stop
 trusting the next one.
@@ -75,10 +75,10 @@ One manifest. Three answers. The one I would have shipped if I had only run `che
 
 ## Consequences
 
-- `simt-app` declares `i18n-completeness: scripts/check_string_translations.sh` on
+- `repo-05` declares `i18n-completeness: scripts/check_string_translations.sh` on
   pre-commit — the gate its own hand-written pre-commit hook already runs — and
   `test: ./gradlew check` on pre-push.
-- The `simt-social-media` and `simt-space` manifests are unaffected: they declare no commands.
+- The `repo-13` and `repo-15` manifests are unaffected: they declare no commands.
 - A Node repository that wants to override a gate now can, without abandoning the gate name it
   shares with every other repository. `gates.commands.format` is a supported thing to write.
 - `readCapability` reads one more file per invocation, and it reads it in a `try` that cannot
@@ -104,7 +104,7 @@ One manifest. Three answers. The one I would have shipped if I had only run `che
 
 ## Evidence
 
-`simt-app` is the first adopter with a non-npm runner and the first to declare a command for a
+`repo-05` is the first adopter with a non-npm runner and the first to declare a command for a
 gate that is not of kind `command`. Every earlier adopter was a Node repository, which is why
 ADR-017's own verification passed. The estate's three runners — npm, Gradle and Python — were
 all in the repository set the whole time; only the pilot order had not reached them.

package/docs/decisions/ADR-023-the-gate-ships-as-a-file-the-repo-owns.md

@@ -14,7 +14,7 @@ the machine of whoever remembers to run it, and a hook is a developer's machine.
 review is somebody else's, and every merge is a machine nobody gated.
 
 The plan called this "a reusable workflow", and named
-`QuazarMedia/simt-dev/.github/workflows/sync-check.yml` as a file "referenced by every
+`the organisation/simt-dev/.github/workflows/sync-check.yml` as a file "referenced by every
 consumer". Nothing in this repository had a `.github/` at all. There were three ways to
 close the gap, and they differ in who the resulting file belongs to:
 
@@ -93,7 +93,7 @@ rules once told readers to edit a source tree they did not have.
 
 ## Rejected
 
-- **`uses: QuazarMedia/simt-dev/.github/workflows/sync-check.yml@main`.** Rejected under
+- **`uses: the organisation/simt-dev/.github/workflows/sync-check.yml@main`.** Rejected under
   ruling 1: it is the plan's own suggestion, and it points every reader at bytes they do
   not have. Worth recording that the plan wrote it, because the next person to read §6
   will find it there.

package/docs/decisions/ADR-027-the-one-gitattributes-line-that-is-neither-dangerous-nor-empty.md

@@ -19,8 +19,8 @@ empty", and deferred it to a record of its own.
 
 The estate confirms the first half and not the conclusion. Thirteen of sixteen repositories
 have no `.gitattributes` at all. The three that do disagree about almost everything:
-`simt-app` declares only LFS filters for `.tif` and `.zip`; `simt-garmin` declares line
-endings plus ConnectIQ binary markers; `simt-social-api` declares exactly one whitespace
+`repo-05` declares only LFS filters for `.tif` and `.zip`; `repo-07` declares line
+endings plus ConnectIQ binary markers; `repo-11` declares exactly one whitespace
 suppression for hash-locked vendored content. There is no divergence here of the kind a
 baseline fixes by being consistent. There is a file missing.
 
@@ -48,7 +48,7 @@ to be the line ruling 7 sent this file to make.
    because nothing in the pattern says those are binary. `text=auto` is a detection: git
    sniffs each path and applies normalisation only to files it concludes are text. This is
    the most common way a repository corrupts its own binaries, and it is invisible until
-   someone diffs an image. `simt-garmin` had independently arrived at `text=auto eol=lf` on
+   someone diffs an image. `repo-07` had independently arrived at `text=auto eol=lf` on
    its first line, which is the strongest available evidence that the estate would pick the
    cautious form if asked — this ruling does not ask, it supplies.
 
@@ -96,8 +96,8 @@ what any file is". A future baseline for a per-stack attribute would have to arr
 different row with its own record, which is what §3.2's keep-it-local rule asks for anyway.
 
 The repositories with an existing `.gitattributes` are the interesting case and they are not
-in conflict: `simt-app`'s LFS filters, `simt-garmin`'s binary markers and
-`simt-social-api`'s whitespace suppression all stay beneath the region and all keep winning,
+in conflict: `repo-05`'s LFS filters, `repo-07`'s binary markers and
+`repo-11`'s whitespace suppression all stay beneath the region and all keep winning,
 because git takes the last match. No repository loses a line it wrote.
 
 This repository adopts neither baseline for itself, and the reason is the same one that keeps

package/docs/decisions/ADR-028-a-base-file-is-a-floor-so-the-disagreement-it-cannot-repair-becomes-a-check.md

@@ -10,7 +10,7 @@ a copied byte range. Settles the `tsconfig.base.json` item of §3.1 row 5 and ro
 ## Context
 
 Row 5 promised eight baselines and named two problems among them that are not about a file
-being missing: simt-goto's seven absent strictness flags, and `moduleResolution` spelled
+being missing: repo-08's seven absent strictness flags, and `moduleResolution` spelled
 inconsistently across the workspace. ADR-025 ruled `tsconfig.base.json` out of the region
 mechanism because JSON has no comments, and its consequences promised that "the next fix is
 three more JSON files and therefore a different mechanism". ADR-026 supplied that mechanism
@@ -95,7 +95,7 @@ one an external document uses.
 
 A TypeScript repository now gets twelve flags it did not have, and one of them — the floor
 arriving through `extends` — is a behaviour change that can surface real type errors in
-`simt-goto`, which is the point of the record and also the reason adoption is one commit
+`repo-08`, which is the point of the record and also the reason adoption is one commit
 with a `tsc` run rather than a silent upgrade. A base file is a floor, and a repository
 that had not been standing on one is the case where raising it finds something.
 

package/docs/decisions/ADR-029-the-pins-a-repository-declares-are-its-own.md

@@ -104,7 +104,7 @@ nobody has been asked, and it is the record to read next for either.
 
 - **A shipped `.nvmrc` or an `engines` value in a shared baseline.** Rejected as
   unrulable: the value is per-repository and the tool can only guess it. Shipping `22` would
-  break `simt-social`, which pins 24.
+  break `repo-14`, which pins 24.
 - **Reporting cross-repository node divergence as a finding.** Rejected by the Context. The
   plan's premise was wrong and the correction is recorded here so it is not re-derived from
   the plan text.