simt-dev 0.2.0__tar.gz

simt_dev-0.2.0/.gitignore

@@ -0,0 +1,10 @@
+# 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/

simt_dev-0.2.0/CHANGELOG.md

@@ -0,0 +1,166 @@
+# Changelog
+
+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
+
+`0.1.0` chained the wrong set of hooks and is worth replacing rather than
+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
+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.
+
+`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.
+*(ADR-018, as amended)*
+
+Upgrade with `npm i -D simt-dev@0.1.1`, then `simt hooks install --yes`. Any
+repository already routed with `0.1.0` should re-run it: the shims it writes
+will differ where a gated event was previously displaced.
+
+## [0.1.0] — 2026-10-11
+
+The first release with real contents in it. `1.0.0` was an empty reservation of the name
+and `0.0.0-stage` was its rehearsal; neither shipped a byte anyone could run, so this entry
+is the whole history. The decisions behind it are readable in the package under
+`docs/decisions/`, and from any checkout with `simt rules why <id>`.
+
+### The command is `simt`
+
+The package is `simt-dev` and the command is `simt`. They are not the same thing and were
+never required to be: the command appears only in text the tool itself writes, and that
+text migrates on the next write. The package name, the `.simt-hooks/` directory and the
+`simt-dev-check.yml` gate already exist in every repository that adopted this tool, and
+they did not move. The manifest and the region markers did — see below.
+
+### The manifest is `simt.json`
+
+The manifest was called `simt-dev.json`; it is now `simt.json`. The move is a
+read-both/write-new, so nothing in an adopting repository has to be done:
+
+- Every read takes `simt.json` if it exists, else `simt-dev.json`, so a repository that
+  has not written since the upgrade is still seen as adopted.
+- Every write goes to `simt.json`, and a lone `simt-dev.json` is moved, not shadowed.
+- The old name keeps working until the first `init` or manifest write in each repository,
+  and that write closes it. *(ADR-056)*
+
+### The region markers are `simt:`
+
+The generated region was stamped `<!-- simt-dev:begin -->` / `<!-- simt-dev:end -->` — and
+so was the provenance header inside it; every one of those lines is now `simt:`. The move
+is the same read-both/write-new as the manifest:
+
+- Every read accepts either spelling, so a repository that has not written since the
+  upgrade is still seen as adopted.
+- Every write emits `simt:` only, so the first `sync` in each repository migrates its
+  regions in place, and that write closes the window.
+- A file holding two regions — one of each spelling — is a state only a hand edit can
+  make, and it is reported malformed rather than merged. *(ADR-056)*
+
+### A hook you already had keeps running
+
+`hooks install` points `core.hooksPath` at `.simt-hooks/`, and git reads **every** hook from
+that one directory — not just the two events this tool gates. So adopting a repository that
+had its own `post-commit`, `post-checkout` or `post-merge` would have quietly stopped them:
+nothing fails, nothing is logged, and the hook is still on disk looking intact.
+
+Those hooks are now **chained**. Install writes a shim for them that runs the repository's
+own hook and forwards git's arguments, so nothing is lost and the reason is in the file. If
+the hook is gone, the shim refuses and names the path instead of passing quietly. A hook on
+an event this tool *does* gate (`pre-commit`, `pre-push`) is deliberately not chained —
+declare it under `gates.commands` so the dispatcher runs it and its verdict appears in the
+gate report. *(ADR-018, as amended)*
+
+### What a first release has to say out loud
+
+These are the behaviours a reader is most likely to trip over. Each one is deliberate,
+and each has a numbered decision record behind it — but a behaviour nobody can discover
+without reading the source is not a documented one.
+
+- **`sync` and `init` write nothing without `--yes`.** Both print a plan and exit. `sync`
+  exits **1** when the plan is non-empty, so bare `sync` doubles as a check. Neither ever
+  commits or pushes. *(ADR-035, ADR-036)*
+- **`upgrade` moves a pin and nothing else.** It never adopts a repository, never repairs
+  one, and never rewrites a manifest. Every consumer moves to the same version as one set.
+- **A pre-commit hook with no reachable binary fails closed.** The refusal is the correct
+  behaviour, not a bug; the remedy it prints is the command that obtains one.
+  *(ADR-010, ADR-018)*
+- **A gate whose tool is not installed is dropped, with a remedy naming the package.**
+  It is never declared and silently unrunnable. *(ADR-017)*
+- **Two rules are never loaded twice.** Each rule projects to exactly one place, chosen by
+  what the harness actually reads. *(ADR-021, ADR-046)*
+- **macOS and Linux only.** Windows `npm i` fails with npm's `EBADPLATFORM`, which npm
+  will not let a package explain; use WSL2. See the platform section of the README.
+  *(ADR-012)*
+
+### Packaging
+
+- Licence set to Apache-2.0; the `LICENSE` file is the canonical, unmodified text.
+- `files` no longer lists `skills`, `agents`, `tooling` or `hooks`, none of which exist,
+  and no longer ships `docs/plans`. The tarball is the tool and the decisions behind it,
+  and nothing else.
+- The package `description` no longer names an internal ecosystem. It is the first line
+  anybody outside the project reads.
+- Unscoped, so the install command is `npm i -D simt-dev` rather than a name under an
+  organisation. The `@simt` and `@quazarmedia` scopes were both free; an unscoped name is
+  the one a reader can guess.
+
+### Notes for anyone upgrading a hook
+
+A shim installed by an earlier version looks for `SIMT_DEV_BIN`, then for
+`node_modules/simt-dev/bin/simt-dev.mjs`, then for a program named `simt` on `PATH`. The
+last of those is new, so a machine that installed the package before this release and
+never ran `simt hooks install` again will find nothing until the dependency is refreshed
+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

simt_dev-0.2.0/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

simt_dev-0.2.0/PKG-INFO

@@ -0,0 +1,150 @@
+Metadata-Version: 2.4
+Name: simt-dev
+Version: 0.2.0
+Summary: Shared agent rules, skills and git hooks for a repository: one command adopts a repo, and every gate it declares is probed before it is written.
+Project-URL: Homepage, https://github.com/QuazarMedia/simt-dev
+Project-URL: Repository, https://github.com/QuazarMedia/simt-dev
+Project-URL: Changelog, https://github.com/QuazarMedia/simt-dev/blob/main/CHANGELOG.md
+Author: Said Elimam
+License-Expression: Apache-2.0
+License-File: LICENSE
+Keywords: agent,agents,ai,codex,cursor,git-hooks,llm,rules,skills
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Operating System :: MacOS
+Classifier: Operating System :: POSIX :: Linux
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Programming Language :: Python :: 3.9
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Software Development :: Quality Assurance
+Requires-Python: >=3.9
+Provides-Extra: node
+Requires-Dist: nodejs-wheel-binaries; extra == 'node'
+Description-Content-Type: text/markdown
+
+# simt-dev
+
+Shared agent rules, skills and git hooks for a repository.
+
+One command adopts a repository: it reads what the repo actually runs, projects the
+matching rules into the files your agent already reads, and installs a pre-commit hook
+that refuses a commit which breaks a gate that repo can genuinely run.
+
+- **Nothing is declared that cannot run.** Every gate is probed against the working tree
+  before it is written. A gate whose tool is absent is dropped, with a remedy naming the
+  package to install — never silently present, never silently absent.
+- **Nothing an agent reads is written twice.** Each rule goes to exactly one place, chosen
+  by what the harness actually reads.
+- **The rules are a projection, not a copy.** They carry markers, so `check` can tell
+  drift from a deliberate edit, and `sync` can regenerate.
+- **The tool explains itself.** `rules why` answers "why did I get told this?" from a
+  numbered record of the decisions behind the rules, with the rejected alternatives
+  attached.
+
+## Install
+
+Requires **Node >= 22.20.0** (the PyPI install can supply it, see below).
+
+```sh
+# pinned, per repository - what CI and a teammate both get
+npm i -D simt-dev@0.2.0
+
+# or globally, if you would rather not add a dependency
+npm i -g simt-dev@0.2.0
+
+# or with no install at all, for a one-off
+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.
+
+## Use
+
+```sh
+simt init            # adopt or scaffold this repository (dry-run; --yes to write)
+simt doctor          # what this repo is, and whether its config is healthy
+simt check           # the gate: projection drift, manifest validity, policy
+simt sync --yes      # regenerate the projection
+simt upgrade --yes   # move every consumer of this tool to this version
+simt rules why ADR-042   # why a rule says what it says, and what was rejected
+simt compare         # what changed across every repository that adopted it
+```
+
+`init` and `sync` print a plan and write nothing without `--yes`. Neither commits or pushes.
+
+## What it writes
+
+| 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) |
+| `.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 |
+
+Anything outside the markers is yours. simt-dev never edits it and never reverts it.
+
+## Platform
+
+**macOS and Linux.** The hooks are POSIX `sh`; there is no Windows build and no plan for
+one. `npm i` on Windows fails with npm's `EBADPLATFORM`, which npm will not let a package
+explain — so the answer is here: **use WSL2**, and the gate works normally inside it.
+
+A Windows checkout without WSL2 can still read every rule this tool generates, because the
+projection is plain text in `AGENTS.md` and the per-harness rule files. Only the hooks and
+the CI gate need the POSIX host.
+
+## How the rules are chosen
+
+Detection reads what the repository runs — its dependency manifests, its build files, its
+CI workflows — and resolves that against a registry of capabilities. Resolution is a
+scored ranking over path, keyword, name, capability and stack: no model, no network, no
+guessing, so a pull request can meaningfully diff the answer.
+
+**Not every ecosystem has a profile yet.** A Go, Rust, .NET, Ruby, Swift, Dart or Elixir
+repository is detected and gets facts, but it is adopted with the core rules and no gates
+until its gate templates are written. A repository with no gates is a repository with an
+agent and no pre-commit hook — better than one with a hook that runs nothing, but not full
+support, and this README will not pretend otherwise.
+
+Every behaviour that is a choice rather than a detail has a numbered record, and the
+records are readable with `simt rules why <id>`. If the tool ever does something you
+did not expect, that command is the shortest path from the symptom to the reason.
+
+## Licence
+
+Apache-2.0. See [LICENSE](LICENSE).

simt_dev-0.2.0/README.md

@@ -0,0 +1,120 @@
+# simt-dev
+
+Shared agent rules, skills and git hooks for a repository.
+
+One command adopts a repository: it reads what the repo actually runs, projects the
+matching rules into the files your agent already reads, and installs a pre-commit hook
+that refuses a commit which breaks a gate that repo can genuinely run.
+
+- **Nothing is declared that cannot run.** Every gate is probed against the working tree
+  before it is written. A gate whose tool is absent is dropped, with a remedy naming the
+  package to install — never silently present, never silently absent.
+- **Nothing an agent reads is written twice.** Each rule goes to exactly one place, chosen
+  by what the harness actually reads.
+- **The rules are a projection, not a copy.** They carry markers, so `check` can tell
+  drift from a deliberate edit, and `sync` can regenerate.
+- **The tool explains itself.** `rules why` answers "why did I get told this?" from a
+  numbered record of the decisions behind the rules, with the rejected alternatives
+  attached.
+
+## Install
+
+Requires **Node >= 22.20.0** (the PyPI install can supply it, see below).
+
+```sh
+# pinned, per repository - what CI and a teammate both get
+npm i -D simt-dev@0.2.0
+
+# or globally, if you would rather not add a dependency
+npm i -g simt-dev@0.2.0
+
+# or with no install at all, for a one-off
+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.
+
+## Use
+
+```sh
+simt init            # adopt or scaffold this repository (dry-run; --yes to write)
+simt doctor          # what this repo is, and whether its config is healthy
+simt check           # the gate: projection drift, manifest validity, policy
+simt sync --yes      # regenerate the projection
+simt upgrade --yes   # move every consumer of this tool to this version
+simt rules why ADR-042   # why a rule says what it says, and what was rejected
+simt compare         # what changed across every repository that adopted it
+```
+
+`init` and `sync` print a plan and write nothing without `--yes`. Neither commits or pushes.
+
+## What it writes
+
+| 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) |
+| `.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 |
+
+Anything outside the markers is yours. simt-dev never edits it and never reverts it.
+
+## Platform
+
+**macOS and Linux.** The hooks are POSIX `sh`; there is no Windows build and no plan for
+one. `npm i` on Windows fails with npm's `EBADPLATFORM`, which npm will not let a package
+explain — so the answer is here: **use WSL2**, and the gate works normally inside it.
+
+A Windows checkout without WSL2 can still read every rule this tool generates, because the
+projection is plain text in `AGENTS.md` and the per-harness rule files. Only the hooks and
+the CI gate need the POSIX host.
+
+## How the rules are chosen
+
+Detection reads what the repository runs — its dependency manifests, its build files, its
+CI workflows — and resolves that against a registry of capabilities. Resolution is a
+scored ranking over path, keyword, name, capability and stack: no model, no network, no
+guessing, so a pull request can meaningfully diff the answer.
+
+**Not every ecosystem has a profile yet.** A Go, Rust, .NET, Ruby, Swift, Dart or Elixir
+repository is detected and gets facts, but it is adopted with the core rules and no gates
+until its gate templates are written. A repository with no gates is a repository with an
+agent and no pre-commit hook — better than one with a hook that runs nothing, but not full
+support, and this README will not pretend otherwise.
+
+Every behaviour that is a choice rather than a detail has a numbered record, and the
+records are readable with `simt rules why <id>`. If the tool ever does something you
+did not expect, that command is the shortest path from the symptom to the reason.
+
+## Licence
+
+Apache-2.0. See [LICENSE](LICENSE).