simt-dev 0.5.0__tar.gz → 0.6.0__tar.gz

simt_dev-0.6.0/.gitignore

@@ -0,0 +1,22 @@
+# Editors and operating systems
+.DS_Store
+.idea/
+# Per-developer git identity, written by `simt init`. Not a file to share:
+# it carries whoever is committing into the tree, and a repository has more than
+# one of those. See ADR-057.
+git.config
+
+.pybuild/
+dist/
+.sea-cache/
+
+# Local index, evidence ledger, benchmark run outputs and local-model proposals
+# (plan 0003 §4). Task descriptors in .simt/bench/tasks/*.json are committed;
+# runs, distilled summaries and review proposals are not.
+.simt/index.sqlite
+.simt/index.jsonl
+.simt/ledger.jsonl
+.simt/bench/runs/
+.simt/gate/
+.simt/distilled/
+.simt/reviews/

{simt_dev-0.5.0 → simt_dev-0.6.0}/CHANGELOG.md

@@ -6,6 +6,128 @@ All notable changes to this package are recorded here. The format follows
 
 ## [Unreleased]
 
+## [0.6.0] — 2026-10-27
+
+### Added
+
+`simt plugin <claude|gemini|cursor> --out <dir>` generates one of the three
+harness packages from the same tables `agent-hooks install` writes — the hooks
+file, the MCP registration and, for cursor, the kernel rules — each carrying a
+self-contained copy of the runtime so it installs into a clean profile. Dry-run
+unless `--yes`. The Gemini reader row gains its hooks file (`.gemini/settings.json`),
+which extends `agent-hooks install` and `status` to a fifth adapter.
+
+The MCP server answers `prompts/list` and `prompts/get` with two templates:
+`simt-brief` starts a task from the pre-assembled brief packet, and `simt-slice`
+implements one slice of the working plan (the next one whose dependencies are
+complete, or a named one) — reading the repo's rules through `simt://kernel`
+first, testing per the slice's acceptance check, committing locally and pushing
+only on explicit approval. A prompt names the tools; the server stays read-only.
+
+Two fixed resources join `simt://rules/{id}` and `simt://decisions/{adr}`:
+`simt://kernel` serves the collaborating region rendered in kernel mode for
+whatever repository the server runs in — the URI promises the kernel's bytes,
+whatever `mode` the manifest declares — and `simt://plan/next` serves the
+section of the next ready plan slice, listed only while one is ready. A listed
+resource's size is the size its read returns.
+
+The tool descriptions in `tools/list` are cut from 2,783 bytes to 1,949,
+inside the 2 KB budget plan 0003 R41 sets for a cacheable tools list; the
+input and output schemas stay full, per ADR-068.
+
+`harness detect` reports the MCP registration files the loader table records —
+`.mcp.json` (Claude Code), `.codex/config.toml`, `.cursor/mcp.json`,
+`.agents/mcp_config.json`, `.gemini/settings.json`, `.vscode/mcp.json` — as
+`kind: 'mcp'` rows whose provenance is the vendor page each path was read from.
+A row rests on the file existing, never on a directory's presence, and never
+counts toward the no-rule-channel note: a config file doesn't claim one.
+
+The loader table gains the Gemini CLI reader, whose configuration reference the
+table previously recorded as unavailable: it is live again (read 2026-10-26), so
+the row carries the GEMINI.md chain with `.git` boundary markers, the
+`context.fileName` rename (the only documented way this reader picks up
+AGENTS.md), depth-5 `@path` imports, no published cap, and the `mcpServers`
+registration. It stays a facts row — the `gemini-md` pointer remains the one
+rule channel for that reader.
+
+Each release now carries a fourth artefact beside the tarball, the wheel and the
+formula: one single-file executable per target (`darwin-arm64`, `darwin-x64`,
+`linux-x64`), built from the same `files` set with a pinned Node runtime, published to
+the GitHub release with a `.sha256` beside it and a build-provenance attestation. It is
+the channel for a machine that has no toolchain to install one with — the binary lands
+as one file in `.simt/bin/` and carries its own runtime — and its acceptance is
+executable: a Gradle fixture with every directory containing a node removed from `PATH`
+runs `check` and the hook shim from the built bytes.
+
+`simt pack new <name> --source <npm:<package>|git+https://…>` scaffolds a
+versioned pack — `pack.json`, an unmeasured `bench.json`, one stack rule — and
+`simt pack lint [dir]` validates it and states its measured ΔR, rejecting a pack
+with no bench summary under `--require-measured`. `simt pack publish [dir]` lints
+first, publishes an npm-sourced pack idempotently (a live version is skipped),
+and names the tag-and-push for a git-sourced one. The summary binds to every
+byte but itself, so recording a measurement cannot invalidate it.
+
+### Changed
+
+`harness detect`'s "some readers read AGENTS.md" rows no longer say bare "some"
+when the row knows which one: the `readsAgentsMdNote` travels to the text
+output, and `.gemini` graduates from unverified candidate to verified detection
+facts (presence implies Gemini CLI; AGENTS.md only when `context.fileName`
+names it).
+
+The one-line description the three channels publish (npm, PyPI and Homebrew) now
+names the goal plan `0003` is building toward — an intelligence amplifier for AI
+coding agents — instead of the adoption-only story it grew out of.
+
+The per-repository state directory is renamed from `.simt-dev/` to `.simt/`: the
+index, ledger, lessons, bench artifacts, local-model proposals (`distilled/`,
+`reviews/`) and repo-local profiles all live under `.simt/` now. Existing state is
+not migrated — a repository that carries a `.simt-dev/` directory moves it once by
+hand (`mv .simt-dev .simt`); everything in it is cache or ledger, regenerable from
+git. The names this tool writes into files it does not own stay put: the `simt.json`
+manifest, the `simt-dev-check.yml` gate, the user-level config directory and the
+`SIMT_DEV_*` environment variables keep their names.
+
+The skill registry leaves the published set again, as ADR-061 ruled when it
+first left in 0.2.1. It is a catalogue of one workspace's skills — the
+repositories whose bodies it resolves — and an installed copy serving that
+catalogue to an adopting repository is a confident wrong answer: the skills
+it names do not live in the reader's workspace. 0.5.0 carried the registry
+because a fresh install's `simt skills *` and `simt distill` otherwise found
+none; the fix is the honest absence the tiered loader already reports — the
+path it would have read, and the `simt graph lint <path>` remedy — with a
+workspace that owns the registry naming it through `--workspace`,
+`SIMT_DEV_WORKSPACE` or the user config file. Custom skills were never part
+of the registry: they live in each repository, and the disclosure scan
+projects them into AGENTS.md.
+
+The entry point file is renamed from `bin/simt-dev.mjs` to `bin/simt.mjs`,
+matching the command it installs: the command has been `simt` for a long
+time, the package is still `simt-dev`, and the file path was the last place
+that carried the old spelling. `BIN_REL` in `src/name.mjs` is the single
+source of truth, so the generated hook shim and CI workflow pick up the new
+path on their next regeneration; the channels (npm, PyPI, Homebrew), the
+repository's own CI and the test harnesses follow.
+
+The hook shim's remedy and the generated CI workflow now install the release binary
+for a repository without npm, instead of the pinned global npm install (`npm i -g`)
+that needed the npm that repository kind is defined by not having. The remedy is the
+one-line download the binary channel names, with its platform derived from `uname`;
+the CI step verifies the download against the published `.sha256` and runs with no
+`setup-node` step at all — a file that runs without a Node toolchain should not have
+one installed to run it.
+
+The locator resolves `.simt/bin/simt` between `node_modules` and `PATH`, so the bytes
+a repository downloaded are the bytes its gate runs and a machine-wide install cannot
+shadow them. The dispatcher's version check is unchanged and still refuses a stale
+copy, whichever path found it.
+
+Homebrew's formula downloads the release binaries rather than the npm tarball — one
+`url`/`sha256` pair per target, chosen at install time — and no longer declares
+`depends_on "node"`. `scripts/release-formula.mjs` patches each pair by content, and
+the release refuses to publish a formula whose checksums are not the bytes the tagged
+tree builds (ADR-098).
+
 ## [0.5.0] — 2026-10-25
 
 ### An offline distiller that proposes, never projects

{simt_dev-0.5.0 → simt_dev-0.6.0}/PKG-INFO

@@ -1,7 +1,7 @@
 Metadata-Version: 2.5
 Name: simt-dev
-Version: 0.5.0
-Summary: Shared agent rules, skills and git hooks for a repository: one command adopts a repo, and every gate it declares is probed before it is written.
+Version: 0.6.0
+Summary: An intelligence amplifier for AI coding agents: rules and dual gates adopted by one command, plus local retrieval, task briefs, benches and repo memory — deterministic by default, with local-model adapters that propose and never select.
 Project-URL: Homepage, https://github.com/QuazarMedia/simt-dev
 Project-URL: Repository, https://github.com/QuazarMedia/simt-dev
 Project-URL: Changelog, https://github.com/QuazarMedia/simt-dev/blob/main/CHANGELOG.md
@@ -32,7 +32,10 @@ Description-Content-Type: text/markdown
 
 ![simt-dev, the intelligence amplifier for coding agents, and its four claims. One: say less, always — a kernel under 2 KB whose bytes stay stable so the prompt cache survives. Two: answers over exploration — a local code graph and a short task brief. Three: enforce, don't instruct — dual gates, before a tool call and at git time. Four: close the loop — benches and memory. Beneath them, the harnesses it works across and its three channels.](https://raw.githubusercontent.com/QuazarMedia/simt-dev/main/res/59e21e6d-6bf2-4d7d-b6ea-c7349a697d11.jpg)
 
-`simt` adopts a repository for the agents that work in it.
+`simt` adopts a repository for the agents that work in it, and builds an intelligence
+amplifier around them: a brief that answers before the agent explores, gates that
+validate before a tool call, benches that price every rule text, and memory that puts
+a recorded failure to work on the next one.
 
 It reads what the repository actually runs, projects the rules that are not already
 obvious into the files those agents read, and installs only the gates that repository
@@ -50,7 +53,64 @@ Anything that needs a parser grammar, a local model, or another server is a sepa
 package, off until the repository names it, and it proposes rows or text for a person
 to merge. It does not write the projection.
 
-## Today
+## Install
+
+Requires **Node >= 22.20.0** for the npm and PyPI channels; the release binary carries
+its own runtime. The current published release is **0.5.0**. Pin it. The tool writes a
+content digest into the files it generates, and an unpinned upgrade changes them under
+you.
+
+```sh
+npm i -D simt-dev@0.5.0
+
+# or globally
+npm i -g simt-dev@0.5.0
+
+# or once, with no install
+npx -y simt-dev@0.5.0 check
+```
+
+### From PyPI
+
+The wheel carries the same bytes as the npm tarball. It does not fetch them from npm
+at install time.
+
+```sh
+pip install simt-dev
+
+# when this machine has no node
+pip install "simt-dev[node]"
+```
+
+`simt` is the command on both channels. Node is resolved in this order, and the first
+one that answers wins: `SIMT_DEV_NODE`, the node bundled with the `node` extra, then
+`node` on `PATH`.
+
+### From Homebrew
+
+```sh
+brew install QuazarMedia/homebrew-tap/simt-dev
+```
+
+The formula downloads the single-file binary for this machine, which carries its own
+runtime: the command works with no Node installed.
+
+### As a single-file binary
+
+Each release carries one executable per platform — macOS arm64 and x64, Linux x64 —
+beside its `.sha256`. The channel's first release is the version after 0.5.0; pin that,
+and run this from the repository's top level:
+
+```sh
+mkdir -p .simt/bin && os=$(uname -s | tr A-Z a-z) && arch=$(uname -m | sed "s/x86_64/x64/") && curl -fsSL "https://github.com/QuazarMedia/simt-dev/releases/download/v<version>/simt-dev-<version>-$os-$arch" -o .simt/bin/simt && chmod +x .simt/bin/simt
+```
+
+The locator checks `.simt/bin/simt` before `PATH`, so the repository's own copy is the
+one its hooks and its CI run — this is the same command the hook shim prints as its
+remedy. The generated CI workflow downloads the same asset and verifies it against the
+published `.sha256` before running anything.
+
+## What `simt` does
 
 ```sh
 # Adopt, inspect, and maintain a repository
@@ -113,11 +173,15 @@ simt bench report [--compare a b]   # resolved rate, quality, cost, CPI, bootstr
 simt bench ablate --yes             # leave-one-out rule ablation ranked by value per KB
 simt bench probes --yes             # 12 deterministic rule-compliance probes
 simt bench variants --yes           # evaluate simt-variants slots and lock winners in simt-dev.lock.json
+simt pack new <name> --source <spec> # scaffold a versioned pack: pack.json, bench.json, one rule
+simt pack lint [dir] [--require-measured] # validate a pack and state its measured ΔR
+simt pack publish [dir] --yes       # publish an npm-sourced pack (git packs name the tag-and-push)
 simt mcp [--list]                   # serve the 13 read-only tools over stdio JSON-RPC
 ```
 
 `init`, `sync`, `upgrade`, `hooks install`, `agent-hooks install`, `shared install`,
-`skills install`, `plan done`, `lessons review`, `decide` and the `bench` writers print
+`skills install`, `plan done`, `lessons review`, `decide`, `pack new`, `pack publish`
+and the `bench` writers print
 a plan and write nothing without `--yes`. None of them commit or push. `simt index`
 writes its cache without asking: the file is gitignored and `git ls-files` can rebuild it.
 
@@ -239,7 +303,7 @@ returns a JSON object with `task`, `commands`, `files`, `tests`, `decisions`, `s
    `DRIFT` with `simt sync --yes`, and resolve any rule checker or manifest findings.
 2. **Verify execution evidence matches the current tree.** Run `simt evidence` to confirm
    that the tests and gates you plan to cite were recorded against the current
-   `git write-tree` digest in `.simt-dev/ledger.jsonl`. Any file edit invalidates earlier
+   `git write-tree` digest in `.simt/ledger.jsonl`. Any file edit invalidates earlier
    evidence.
 3. **Record decisions, lessons, and tracker state:**
    - If the change alters what the repository or tool believes, scaffold an ADR with
@@ -262,11 +326,11 @@ returns a JSON object with `task`, `commands`, `files`, `tests`, `decisions`, `s
 | Shape | How to configure and run `simt` optimally |
 | --- | --- |
 | **Single-package repository** (Node, TypeScript, Python/`uv`, Go, Rust, JVM/Gradle/Maven, Android, Swift, .NET, Deno, Ruby, Dart, Elixir, Cloudflare Workers, React Web, React Native, ConnectIQ, Container) | Run `simt init --yes`, `simt hooks install --yes`, `simt agent-hooks install --yes`, and `simt index`. Stack profiles and runnable gates are selected from committed manifests and build files (`simt doctor` shows `stack`, `facts`, and `factEvidence`). Set `"mode": "kernel"` and `"budget": { "bytes": 12000 }` in `simt.json` to keep session-start tokens minimal while keeping convention/style rules reachable via `simt rules show <id>`. |
-| **Custom stack or repo-specific house rules** | An ecosystem with no built-in profile is still adopted with `core` rules. Add repo-local profiles in `.simt-dev/profiles/<id>.md` with `simt-id`, `simt-title`, `simt-applies`, and `simt-priority` (`hard`, `command`, `convention`, `style`); local profiles project alongside or shadow central ones. Declare custom gates under `gates.commands` and placeholders under `substitutions` in `simt.json`. |
+| **Custom stack or repo-specific house rules** | An ecosystem with no built-in profile is still adopted with `core` rules. Add repo-local profiles in `.simt/profiles/<id>.md` with `simt-id`, `simt-title`, `simt-applies`, and `simt-priority` (`hard`, `command`, `convention`, `style`); local profiles project alongside or shadow central ones. Declare custom gates under `gates.commands` and placeholders under `substitutions` in `simt.json`. |
 | **Single-language or polyglot monorepo** (`package.json` `workspaces`, `pnpm-workspace.yaml`, `turbo.json`, `Cargo.toml` `[workspace]`, `go.work`, `settings.gradle`, `settings.gradle.kts`) | `simt init --yes` and `simt sync --yes` discover every workspace member and write both the root `AGENTS.md` and nested `<package>/AGENTS.md` projections carrying only the profiles specific to each package. Set `gates.cwd` in `simt.json` for gates that execute inside a sub-package. Measure nested context load with `simt harness loaders --at <package-dir>`, and use `simt gate --changed` to run only tests for modified packages. |
-| **Multi-repository workspace / estate** (sibling checkouts under a workspace directory or `SIMT_DEV_WORKSPACE`) | Run `simt compare` across the workspace root to inspect adoption, drift, pinned SHAs, hook routing, most-violated rules, noisy/slow gates (`NOISY-GATE`), zero-value rules, and proposed ADR drafts. Run `simt tokens --repos` and `simt shared plan`, then `simt shared install --yes` to move rules repeated across repos into user-level harness files (`~/.claude/CLAUDE.md`, `~/.codex/AGENTS.md`, etc.). Vendor shared rule packs in `.simt-dev/packs/<name>/` pinned by digest in `simt.json`, and upgrade the entire estate atomically with `simt upgrade --yes`. |
+| **Multi-repository workspace / estate** (sibling checkouts under a workspace directory or `SIMT_DEV_WORKSPACE`) | Run `simt compare` across the workspace root to inspect adoption, drift, pinned SHAs, hook routing, most-violated rules, noisy/slow gates (`NOISY-GATE`), zero-value rules, and proposed ADR drafts. Run `simt tokens --repos` and `simt shared plan`, then `simt shared install --yes` to move rules repeated across repos into user-level harness files (`~/.claude/CLAUDE.md`, `~/.codex/AGENTS.md`, etc.). Vendor shared rule packs in `.simt/packs/<name>/` pinned by digest in `simt.json`, and upgrade the entire estate atomically with `simt upgrade --yes`. |
 | **Repositories with external code-graph MCP servers** | Declare external stdio MCP servers under `federation` in `simt.json` (`{ name, command, args, tool, argument, languages, timeoutMs }`). `simt brief "<task>"` and the MCP `federation_query` tool ask each server one bounded structural question and cite the server name in `FEDERATION`. |
-| **Offline or local-model-assisted workflows** (Ollama, `llama-server`, LM Studio, MLX) | By default, `simt` uses zero models and opens zero sockets (`ADR-075`, `ADR-090`). To opt in, add `local: { chat: { url, model }, embed: { url, model } }` in `simt.json` pointing at `http://127.0.0.1:<port>/v1`. Verify with `simt local doctor`, and build/query SQLite vector embeddings with `simt index --embed` and `simt map --embed` (non-loopback URLs are refused without `--allow-remote`). |
+| **Offline or local-model-assisted workflows** (Ollama, `llama-server`, LM Studio, MLX) | By default, `simt` uses zero models and opens zero sockets (`ADR-075`, `ADR-090`). To opt in, add `local: { chat: { url, model }, embed: { url, model } }` in `simt.json` pointing at `http://127.0.0.1:<port>/v1`. Each role accepts an optional `apiKey` (sent as `Authorization: Bearer <key>`) for servers that require a token. Verify with `simt local doctor`, and build/query SQLite vector embeddings with `simt index --embed` and `simt map --embed` (non-loopback URLs are refused without `--allow-remote`). |
 | **Rule, skill, and benchmark maintainers** | Lint skills with `simt graph lint --spec agentskills`, compile and split > 5,000-token skills with `simt skills compile`, and score the resolver with `simt skills eval`. Mine git history tasks with `simt bench mine --yes`, run arms with `simt bench run --yes`, compare arms with `simt bench report --compare bare kernel`, run leave-one-out ablation with `simt bench ablate --yes`, run compliance probes with `simt bench probes --yes`, and lock winning `simt-variants` wordings with `simt bench variants --yes`. |
 
 ## Module and MCP reference
@@ -286,13 +350,9 @@ returns a JSON object with `task`, `commands`, `files`, `tests`, `decisions`, `s
 
 ## Where the plan finishes
 
-Slices `R01`–`R40` are complete and shipped in `0.5.0`. The remaining queued slices
-(`R41`–`R55`) finish packaging and the small ergonomics:
+Slices `R01`–`R45` are complete and shipped in `0.6.0`. The remaining queued slices are the
+small ergonomics:
 
-- **Packaging and declarative harness data (`R41`–`R45`).** MCP 2026-07-28 revision
-  tightening, declarative harness adapter files with provenance, single-command plugin
-  packaging, a single-file binary alongside npm/PyPI/Homebrew, and benchmark-measured rule
-  packs.
 - **The small doors (`R46`–`R55`).** `simt explain <CODE>` for every finding code, safe
   idempotent `simt doctor --fix`, a `< 50 ms` `simt status --line`, a write journal with
   `simt undo`, `--diff` on every writer, shell completions, one cross-harness ignore list
@@ -304,47 +364,6 @@ budgeted summaries with line citations, `simt review` proposes an advisory ADR-0
 verdict over the staged diff, and `simt brief` carries model/effort advice from bench
 history. All remain off until named and propose rather than write projected text.
 
-## Install
-
-Requires **Node >= 22.20.0**. The current published release is **0.5.0**. Pin it.
-The tool writes a content digest into the files it generates, and an unpinned upgrade
-changes them under you.
-
-```sh
-npm i -D simt-dev@0.5.0
-
-# or globally
-npm i -g simt-dev@0.5.0
-
-# or once, with no install
-npx -y simt-dev@0.5.0 check
-```
-
-### From PyPI
-
-The wheel carries the same bytes as the npm tarball. It does not fetch them from npm
-at install time.
-
-```sh
-pip install simt-dev
-
-# when this machine has no node
-pip install "simt-dev[node]"
-```
-
-`simt` is the command on both channels. Node is resolved in this order, and the first
-one that answers wins: `SIMT_DEV_NODE`, the node bundled with the `node` extra, then
-`node` on `PATH`.
-
-### From Homebrew
-
-```sh
-brew install QuazarMedia/homebrew-tap/simt-dev
-```
-
-The formula depends on `node`, so the command works on a machine that has never had
-Node installed.
-
 ## What it writes
 
 | Path | What |
@@ -374,11 +393,11 @@ These are caches, gitignored, and rebuildable. They are not repository content:
 
 | Path | What |
 | --- | --- |
-| `.simt-dev/index.sqlite` | files, symbols, import/call/test/governs/cochange edges, FTS5 `fts` tokens across `code`, `docs`, `skills`, `decisions` and `lessons`, and optional `embeddings` vector blobs. JSON-lines at `.simt-dev/index.jsonl` when this Node cannot open `node:sqlite` with FTS5 |
-| `.simt-dev/ledger.jsonl` | one line per gate or test the dispatcher actually ran, against one git tree, plus normalised failure signatures |
-| `.simt-dev/lessons.jsonl` | deterministic lesson candidates captured from fail-to-fix pairs, reverts, `BLOCK` reviews, and hook denials |
-| `.simt-dev/bench/` | mined tasks (`tasks/`), test patch vault (`vault/`), and benchmark runs (`runs/`) |
-| `.simt-dev/proposals/` | non-authoritative skill description proposals with `{model, promptHash, digest}` provenance |
+| `.simt/index.sqlite` | files, symbols, import/call/test/governs/cochange edges, FTS5 `fts` tokens across `code`, `docs`, `skills`, `decisions` and `lessons`, and optional `embeddings` vector blobs. JSON-lines at `.simt/index.jsonl` when this Node cannot open `node:sqlite` with FTS5 |
+| `.simt/ledger.jsonl` | one line per gate or test the dispatcher actually ran, against one git tree, plus normalised failure signatures |
+| `.simt/lessons.jsonl` | deterministic lesson candidates captured from fail-to-fix pairs, reverts, `BLOCK` reviews, and hook denials |
+| `.simt/bench/` | mined tasks (`tasks/`), test patch vault (`vault/`), and benchmark runs (`runs/`) |
+| `.simt/proposals/` | non-authoritative skill description proposals with `{model, promptHash, digest}` provenance |
 
 `simt shared install --yes` writes a user-level copy of the rules a workspace
 repeats, into the file that harness documents, and records the ids on each

{simt_dev-0.5.0 → simt_dev-0.6.0}/README.md

@@ -2,7 +2,10 @@
 
 ![simt-dev, the intelligence amplifier for coding agents, and its four claims. One: say less, always — a kernel under 2 KB whose bytes stay stable so the prompt cache survives. Two: answers over exploration — a local code graph and a short task brief. Three: enforce, don't instruct — dual gates, before a tool call and at git time. Four: close the loop — benches and memory. Beneath them, the harnesses it works across and its three channels.](https://raw.githubusercontent.com/QuazarMedia/simt-dev/main/res/59e21e6d-6bf2-4d7d-b6ea-c7349a697d11.jpg)
 
-`simt` adopts a repository for the agents that work in it.
+`simt` adopts a repository for the agents that work in it, and builds an intelligence
+amplifier around them: a brief that answers before the agent explores, gates that
+validate before a tool call, benches that price every rule text, and memory that puts
+a recorded failure to work on the next one.
 
 It reads what the repository actually runs, projects the rules that are not already
 obvious into the files those agents read, and installs only the gates that repository
@@ -20,7 +23,64 @@ Anything that needs a parser grammar, a local model, or another server is a sepa
 package, off until the repository names it, and it proposes rows or text for a person
 to merge. It does not write the projection.
 
-## Today
+## Install
+
+Requires **Node >= 22.20.0** for the npm and PyPI channels; the release binary carries
+its own runtime. The current published release is **0.5.0**. Pin it. The tool writes a
+content digest into the files it generates, and an unpinned upgrade changes them under
+you.
+
+```sh
+npm i -D simt-dev@0.5.0
+
+# or globally
+npm i -g simt-dev@0.5.0
+
+# or once, with no install
+npx -y simt-dev@0.5.0 check
+```
+
+### From PyPI
+
+The wheel carries the same bytes as the npm tarball. It does not fetch them from npm
+at install time.
+
+```sh
+pip install simt-dev
+
+# when this machine has no node
+pip install "simt-dev[node]"
+```
+
+`simt` is the command on both channels. Node is resolved in this order, and the first
+one that answers wins: `SIMT_DEV_NODE`, the node bundled with the `node` extra, then
+`node` on `PATH`.
+
+### From Homebrew
+
+```sh
+brew install QuazarMedia/homebrew-tap/simt-dev
+```
+
+The formula downloads the single-file binary for this machine, which carries its own
+runtime: the command works with no Node installed.
+
+### As a single-file binary
+
+Each release carries one executable per platform — macOS arm64 and x64, Linux x64 —
+beside its `.sha256`. The channel's first release is the version after 0.5.0; pin that,
+and run this from the repository's top level:
+
+```sh
+mkdir -p .simt/bin && os=$(uname -s | tr A-Z a-z) && arch=$(uname -m | sed "s/x86_64/x64/") && curl -fsSL "https://github.com/QuazarMedia/simt-dev/releases/download/v<version>/simt-dev-<version>-$os-$arch" -o .simt/bin/simt && chmod +x .simt/bin/simt
+```
+
+The locator checks `.simt/bin/simt` before `PATH`, so the repository's own copy is the
+one its hooks and its CI run — this is the same command the hook shim prints as its
+remedy. The generated CI workflow downloads the same asset and verifies it against the
+published `.sha256` before running anything.
+
+## What `simt` does
 
 ```sh
 # Adopt, inspect, and maintain a repository
@@ -83,11 +143,15 @@ simt bench report [--compare a b]   # resolved rate, quality, cost, CPI, bootstr
 simt bench ablate --yes             # leave-one-out rule ablation ranked by value per KB
 simt bench probes --yes             # 12 deterministic rule-compliance probes
 simt bench variants --yes           # evaluate simt-variants slots and lock winners in simt-dev.lock.json
+simt pack new <name> --source <spec> # scaffold a versioned pack: pack.json, bench.json, one rule
+simt pack lint [dir] [--require-measured] # validate a pack and state its measured ΔR
+simt pack publish [dir] --yes       # publish an npm-sourced pack (git packs name the tag-and-push)
 simt mcp [--list]                   # serve the 13 read-only tools over stdio JSON-RPC
 ```
 
 `init`, `sync`, `upgrade`, `hooks install`, `agent-hooks install`, `shared install`,
-`skills install`, `plan done`, `lessons review`, `decide` and the `bench` writers print
+`skills install`, `plan done`, `lessons review`, `decide`, `pack new`, `pack publish`
+and the `bench` writers print
 a plan and write nothing without `--yes`. None of them commit or push. `simt index`
 writes its cache without asking: the file is gitignored and `git ls-files` can rebuild it.
 
@@ -209,7 +273,7 @@ returns a JSON object with `task`, `commands`, `files`, `tests`, `decisions`, `s
    `DRIFT` with `simt sync --yes`, and resolve any rule checker or manifest findings.
 2. **Verify execution evidence matches the current tree.** Run `simt evidence` to confirm
    that the tests and gates you plan to cite were recorded against the current
-   `git write-tree` digest in `.simt-dev/ledger.jsonl`. Any file edit invalidates earlier
+   `git write-tree` digest in `.simt/ledger.jsonl`. Any file edit invalidates earlier
    evidence.
 3. **Record decisions, lessons, and tracker state:**
    - If the change alters what the repository or tool believes, scaffold an ADR with
@@ -232,11 +296,11 @@ returns a JSON object with `task`, `commands`, `files`, `tests`, `decisions`, `s
 | Shape | How to configure and run `simt` optimally |
 | --- | --- |
 | **Single-package repository** (Node, TypeScript, Python/`uv`, Go, Rust, JVM/Gradle/Maven, Android, Swift, .NET, Deno, Ruby, Dart, Elixir, Cloudflare Workers, React Web, React Native, ConnectIQ, Container) | Run `simt init --yes`, `simt hooks install --yes`, `simt agent-hooks install --yes`, and `simt index`. Stack profiles and runnable gates are selected from committed manifests and build files (`simt doctor` shows `stack`, `facts`, and `factEvidence`). Set `"mode": "kernel"` and `"budget": { "bytes": 12000 }` in `simt.json` to keep session-start tokens minimal while keeping convention/style rules reachable via `simt rules show <id>`. |
-| **Custom stack or repo-specific house rules** | An ecosystem with no built-in profile is still adopted with `core` rules. Add repo-local profiles in `.simt-dev/profiles/<id>.md` with `simt-id`, `simt-title`, `simt-applies`, and `simt-priority` (`hard`, `command`, `convention`, `style`); local profiles project alongside or shadow central ones. Declare custom gates under `gates.commands` and placeholders under `substitutions` in `simt.json`. |
+| **Custom stack or repo-specific house rules** | An ecosystem with no built-in profile is still adopted with `core` rules. Add repo-local profiles in `.simt/profiles/<id>.md` with `simt-id`, `simt-title`, `simt-applies`, and `simt-priority` (`hard`, `command`, `convention`, `style`); local profiles project alongside or shadow central ones. Declare custom gates under `gates.commands` and placeholders under `substitutions` in `simt.json`. |
 | **Single-language or polyglot monorepo** (`package.json` `workspaces`, `pnpm-workspace.yaml`, `turbo.json`, `Cargo.toml` `[workspace]`, `go.work`, `settings.gradle`, `settings.gradle.kts`) | `simt init --yes` and `simt sync --yes` discover every workspace member and write both the root `AGENTS.md` and nested `<package>/AGENTS.md` projections carrying only the profiles specific to each package. Set `gates.cwd` in `simt.json` for gates that execute inside a sub-package. Measure nested context load with `simt harness loaders --at <package-dir>`, and use `simt gate --changed` to run only tests for modified packages. |
-| **Multi-repository workspace / estate** (sibling checkouts under a workspace directory or `SIMT_DEV_WORKSPACE`) | Run `simt compare` across the workspace root to inspect adoption, drift, pinned SHAs, hook routing, most-violated rules, noisy/slow gates (`NOISY-GATE`), zero-value rules, and proposed ADR drafts. Run `simt tokens --repos` and `simt shared plan`, then `simt shared install --yes` to move rules repeated across repos into user-level harness files (`~/.claude/CLAUDE.md`, `~/.codex/AGENTS.md`, etc.). Vendor shared rule packs in `.simt-dev/packs/<name>/` pinned by digest in `simt.json`, and upgrade the entire estate atomically with `simt upgrade --yes`. |
+| **Multi-repository workspace / estate** (sibling checkouts under a workspace directory or `SIMT_DEV_WORKSPACE`) | Run `simt compare` across the workspace root to inspect adoption, drift, pinned SHAs, hook routing, most-violated rules, noisy/slow gates (`NOISY-GATE`), zero-value rules, and proposed ADR drafts. Run `simt tokens --repos` and `simt shared plan`, then `simt shared install --yes` to move rules repeated across repos into user-level harness files (`~/.claude/CLAUDE.md`, `~/.codex/AGENTS.md`, etc.). Vendor shared rule packs in `.simt/packs/<name>/` pinned by digest in `simt.json`, and upgrade the entire estate atomically with `simt upgrade --yes`. |
 | **Repositories with external code-graph MCP servers** | Declare external stdio MCP servers under `federation` in `simt.json` (`{ name, command, args, tool, argument, languages, timeoutMs }`). `simt brief "<task>"` and the MCP `federation_query` tool ask each server one bounded structural question and cite the server name in `FEDERATION`. |
-| **Offline or local-model-assisted workflows** (Ollama, `llama-server`, LM Studio, MLX) | By default, `simt` uses zero models and opens zero sockets (`ADR-075`, `ADR-090`). To opt in, add `local: { chat: { url, model }, embed: { url, model } }` in `simt.json` pointing at `http://127.0.0.1:<port>/v1`. Verify with `simt local doctor`, and build/query SQLite vector embeddings with `simt index --embed` and `simt map --embed` (non-loopback URLs are refused without `--allow-remote`). |
+| **Offline or local-model-assisted workflows** (Ollama, `llama-server`, LM Studio, MLX) | By default, `simt` uses zero models and opens zero sockets (`ADR-075`, `ADR-090`). To opt in, add `local: { chat: { url, model }, embed: { url, model } }` in `simt.json` pointing at `http://127.0.0.1:<port>/v1`. Each role accepts an optional `apiKey` (sent as `Authorization: Bearer <key>`) for servers that require a token. Verify with `simt local doctor`, and build/query SQLite vector embeddings with `simt index --embed` and `simt map --embed` (non-loopback URLs are refused without `--allow-remote`). |
 | **Rule, skill, and benchmark maintainers** | Lint skills with `simt graph lint --spec agentskills`, compile and split > 5,000-token skills with `simt skills compile`, and score the resolver with `simt skills eval`. Mine git history tasks with `simt bench mine --yes`, run arms with `simt bench run --yes`, compare arms with `simt bench report --compare bare kernel`, run leave-one-out ablation with `simt bench ablate --yes`, run compliance probes with `simt bench probes --yes`, and lock winning `simt-variants` wordings with `simt bench variants --yes`. |
 
 ## Module and MCP reference
@@ -256,13 +320,9 @@ returns a JSON object with `task`, `commands`, `files`, `tests`, `decisions`, `s
 
 ## Where the plan finishes
 
-Slices `R01`–`R40` are complete and shipped in `0.5.0`. The remaining queued slices
-(`R41`–`R55`) finish packaging and the small ergonomics:
+Slices `R01`–`R45` are complete and shipped in `0.6.0`. The remaining queued slices are the
+small ergonomics:
 
-- **Packaging and declarative harness data (`R41`–`R45`).** MCP 2026-07-28 revision
-  tightening, declarative harness adapter files with provenance, single-command plugin
-  packaging, a single-file binary alongside npm/PyPI/Homebrew, and benchmark-measured rule
-  packs.
 - **The small doors (`R46`–`R55`).** `simt explain <CODE>` for every finding code, safe
   idempotent `simt doctor --fix`, a `< 50 ms` `simt status --line`, a write journal with
   `simt undo`, `--diff` on every writer, shell completions, one cross-harness ignore list
@@ -274,47 +334,6 @@ budgeted summaries with line citations, `simt review` proposes an advisory ADR-0
 verdict over the staged diff, and `simt brief` carries model/effort advice from bench
 history. All remain off until named and propose rather than write projected text.
 
-## Install
-
-Requires **Node >= 22.20.0**. The current published release is **0.5.0**. Pin it.
-The tool writes a content digest into the files it generates, and an unpinned upgrade
-changes them under you.
-
-```sh
-npm i -D simt-dev@0.5.0
-
-# or globally
-npm i -g simt-dev@0.5.0
-
-# or once, with no install
-npx -y simt-dev@0.5.0 check
-```
-
-### From PyPI
-
-The wheel carries the same bytes as the npm tarball. It does not fetch them from npm
-at install time.
-
-```sh
-pip install simt-dev
-
-# when this machine has no node
-pip install "simt-dev[node]"
-```
-
-`simt` is the command on both channels. Node is resolved in this order, and the first
-one that answers wins: `SIMT_DEV_NODE`, the node bundled with the `node` extra, then
-`node` on `PATH`.
-
-### From Homebrew
-
-```sh
-brew install QuazarMedia/homebrew-tap/simt-dev
-```
-
-The formula depends on `node`, so the command works on a machine that has never had
-Node installed.
-
 ## What it writes
 
 | Path | What |
@@ -344,11 +363,11 @@ These are caches, gitignored, and rebuildable. They are not repository content:
 
 | Path | What |
 | --- | --- |
-| `.simt-dev/index.sqlite` | files, symbols, import/call/test/governs/cochange edges, FTS5 `fts` tokens across `code`, `docs`, `skills`, `decisions` and `lessons`, and optional `embeddings` vector blobs. JSON-lines at `.simt-dev/index.jsonl` when this Node cannot open `node:sqlite` with FTS5 |
-| `.simt-dev/ledger.jsonl` | one line per gate or test the dispatcher actually ran, against one git tree, plus normalised failure signatures |
-| `.simt-dev/lessons.jsonl` | deterministic lesson candidates captured from fail-to-fix pairs, reverts, `BLOCK` reviews, and hook denials |
-| `.simt-dev/bench/` | mined tasks (`tasks/`), test patch vault (`vault/`), and benchmark runs (`runs/`) |
-| `.simt-dev/proposals/` | non-authoritative skill description proposals with `{model, promptHash, digest}` provenance |
+| `.simt/index.sqlite` | files, symbols, import/call/test/governs/cochange edges, FTS5 `fts` tokens across `code`, `docs`, `skills`, `decisions` and `lessons`, and optional `embeddings` vector blobs. JSON-lines at `.simt/index.jsonl` when this Node cannot open `node:sqlite` with FTS5 |
+| `.simt/ledger.jsonl` | one line per gate or test the dispatcher actually ran, against one git tree, plus normalised failure signatures |
+| `.simt/lessons.jsonl` | deterministic lesson candidates captured from fail-to-fix pairs, reverts, `BLOCK` reviews, and hook denials |
+| `.simt/bench/` | mined tasks (`tasks/`), test patch vault (`vault/`), and benchmark runs (`runs/`) |
+| `.simt/proposals/` | non-authoritative skill description proposals with `{model, promptHash, digest}` provenance |
 
 `simt shared install --yes` writes a user-level copy of the rules a workspace
 repeats, into the file that harness documents, and records the ids on each

{simt_dev-0.5.0 → simt_dev-0.6.0}/docs/decisions/ADR-058-one-tool-three-channels-and-the-order-is-forced.md

@@ -2,6 +2,19 @@
 
 Status: **accepted** · 2026-10-11
 
+> Ruling 7's re-run mechanics are superseded by
+> [ADR-097](ADR-097-the-channels-publish-by-hand-and-the-version-rides-in-as-an-input.md):
+> the two channel jobs moved to a manual `workflow_dispatch` workflow whose `version`
+> input dissolves the branch-vs-tag failure recorded below. The ordering ruling —
+> npm live before either channel publishes — stands.
+
+> Ruling 5's artefact choice and the Homebrew half of ruling 7 are superseded by
+> [ADR-098](ADR-098-the-fourth-channel-is-one-file-and-it-needs-no-toolchain.md): the
+> formula now downloads the release binary, not the npm tarball, and the Homebrew job's
+> precondition is that those assets exist rather than that the npm version is live. The
+> PyPI half of ruling 7 — npm live before the wheel publishes — stands, as does ruling
+> 5's refusal of `std_npm_args`.
+
 Affects: `pyproject.toml`, `python/simt_dev/`, `Formula/simt-dev.rb`,
 `.github/workflows/publish.yml`, `scripts/release-formula.mjs`,
 `scripts/verify-wheel.mjs`, `test/packaging.test.mjs`

{simt_dev-0.5.0 → simt_dev-0.6.0}/docs/decisions/ADR-059-the-version-a-repository-runs-is-the-one-it-pinned.md

@@ -1,6 +1,6 @@
 # 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
+Status: **accepted** · 2026-10-12 · affects all repos · ruling 3's no-npm install and remedy superseded by [ADR-098](ADR-098-the-fourth-channel-is-one-file-and-it-needs-no-toolchain.md)
 
 ## Context