simt-dev 0.2.0__py3-none-any.whl

simt_dev/vendored/package.json

@@ -0,0 +1,43 @@
+{
+  "name": "simt-dev",
+  "version": "0.2.0",
+  "description": "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.",
+  "license": "Apache-2.0",
+  "author": "Said Elimam",
+  "private": false,
+  "type": "module",
+  "engines": {
+    "node": ">=22.20.0"
+  },
+  "os": [
+    "darwin",
+    "linux"
+  ],
+  "bin": {
+    "simt": "bin/simt-dev.mjs"
+  },
+  "files": [
+    "bin",
+    "src",
+    "graph",
+    "rules",
+    "docs/decisions",
+    "CHANGELOG.md"
+  ],
+  "keywords": [
+    "agent",
+    "agents",
+    "ai",
+    "codex",
+    "cursor",
+    "git-hooks",
+    "lint",
+    "llm",
+    "rules",
+    "skills"
+  ],
+  "scripts": {
+    "test": "node --test test/*.test.mjs",
+    "lint": "node bin/simt-dev.mjs doctor"
+  }
+}

simt_dev/vendored/rules/core.md

@@ -0,0 +1,76 @@
+---
+simt-id: core
+simt-title: Shared rules
+simt-applies: always
+---
+
+# Shared rules
+
+Where a rule cites a decision, run `simt-dev rules why ADR-NNN` to read it,
+including whether it is still in force.
+
+These rules are stack-agnostic. Whatever is specific to your stack, your product or your
+commands belongs in this repository, not here.
+
+## Truth
+
+- Never claim a test you did not run, a check you did not execute, or a deploy you did not
+  perform.
+- Read the real runner manifest before running anything. A command absent from it is not a
+  command. (Which file that is depends on the stack: `package.json` scripts, Gradle tasks,
+  `pyproject.toml` entry points.)
+- Report what you left alone: unrelated dirty files, skipped checks, unreviewed scope.
+
+## Git
+
+- Commit locally, report the SHA. **Push only on explicit approval.** (ADR-001)
+- Before asking for push approval, state whether the push triggers a deployment, a migration
+  or any remote mutation.
+- Never use `--no-verify`, amend, rebase, reset or rewrite history unless explicitly asked.
+- Never commit failing, partial, secret-bearing or unrelated work.
+
+## Refactoring
+
+- Outside the current change's blast radius, do not refactor. (ADR-002)
+- Inside it, a second real use extracts, and the extraction is finished: no orphaned imports,
+  exports, styles, messages or files remain.
+- A third copy of the same logic is a defect. So is an abstraction invented for one caller.
+
+## Validation
+
+- Focused tests are the default gate. A full suite runs only against a named trigger: phase
+  exit, release gate, cross-system behaviour, a repo-declared numeric gate, explicit
+  instruction, or pre-push on a declared protected branch. (ADR-003)
+- Name the exact commands and test files. Partial pass is a blocker; `6/8 pass` is the
+  canonical example of a blocked state. Never justify a skip without a pre-existing written
+  reason. (ADR-006)
+- Evidence discipline is mandatory everywhere. A **numeric** bar is declared per repo in
+  `simt-dev.json`, never assumed centrally. (ADR-006)
+- The pre-commit hook owns format and lint for staged files; do not re-run what it just ran.
+  Manual runs are correct when the hook is absent, when diagnosing a failure, or for a check
+  the hook does not cover. (ADR-004)
+- Declare a gate only if this repository can run it — a script that exists, a tool that is
+  installed, a command you name. A gate that cannot run blocks every commit until someone
+  reaches for `--no-verify`. (ADR-017)
+- Invoke tools through the repository's own runner — `npm run`, `uv run -m`, `./gradlew` —
+  never a package runner like `npx` or a bare console entrypoint. (ADR-010)
+
+## Code and review
+
+- No type-system escapes, no unawaited async work, no debug printing in application code.
+- 400 lines is a review trigger; 1000 lines is a hard ceiling. Generated files are exempt
+  when the hook names the generator. (ADR-005)
+- Never weaken CSP, CORS, auth, audit, cache or validation controls to silence a test, warning
+  or alert.
+- Review verdicts are exactly three: `BLOCK`, `APPROVE WITH RESIDUAL RISK` (must list what was
+  not reviewed), `APPROVE`. (ADR-008)
+- Accessibility, correctness, privacy and security are hard gates, not subjective tradeoffs.
+- Never direct two agents to edit the same files concurrently. Select the minimum viable team.
+- Every agent works to a stated budget and stops at a concrete blocker rather than drifting.
+  Approval by budget never converts a known failure into an approval.
+
+## Scope of these rules
+
+Product policy, stack-specific rule bodies, repo commands and paths stay in the repo. A rule
+here states only what holds everywhere; the moment one repository needs an exception, it is that
+repository's rule, not a widening of this one.

simt_dev/vendored/rules/mdc/intake-questions.mdc

@@ -0,0 +1,50 @@
+---
+simt-id: intake-questions
+simt-target: .cursor/rules/intake-questions.mdc
+description: Ask only unresolved business/technical decisions before work
+alwaysApply: true
+simt-applies: always
+simt-substitutions:
+  - key: plansGlob
+    default: docs/plans/*
+    describe: glob for this repo's active plan tracker tables
+  - key: askTool
+    default: Ask the user, offering choices with the recommended one first
+    describe: how this repo asks a question; the default names no harness, because one body is written for every selected surface
+---
+
+# Intake Questions
+
+When starting, resuming, or scoping a feature slice or plan task, do not jump into code
+without resolving open material decisions.
+
+## Agent Defaults (Do Not Ask)
+
+Apply documented defaults without questions for:
+
+- Operational/procedural choices (tracker updates, commit vs push, validation depth,
+  artifact shape).
+- Slice sequencing and repository ownership when already defined in the active plan
+  tracker table (`{{plansGlob}}`).
+- Standard engineering conventions.
+
+## When To Ask (1-5 Questions Max)
+
+Ask only when a functionality, business, privacy, security, or technical decision is not
+settled in authority docs, and the answer materially changes behavior, scope, contracts,
+migrations, or risk.
+
+Five is a ceiling, not a quota. Ask fewer when fewer decisions are genuinely open; never pad
+the list to reach it, and never split one decision into several questions to fit under it.
+
+- {{askTool}}.
+- If that is not available, present numbered choices with `(recommended)` on the first option.
+- Do not ask operational or procedural choices; apply the best documented option.
+
+## Required First Turn
+
+1. State the smallest independently valuable slice, the owning repo, the active plan
+   tracker task ID (from `{{plansGlob}}`), and the acceptance checks.
+2. Either ask the unresolved material decision questions, or state that the authority docs
+   leave no material open decision and proceed to implementation.
+3. Proceed without waiting when no material decision remains.

simt_dev/vendored/rules/mdc/preview-postflight.mdc

@@ -0,0 +1,61 @@
+---
+simt-id: preview-postflight
+simt-target: .cursor/rules/preview-postflight.mdc
+description: Authenticated remote postflight uses dedicated preview Workers
+alwaysApply: true
+# Opt-in, not stack-detected. Detection cannot tell a Workers repo that deploys
+  # preview Workers from one that does not, so a stack tag would hand this rule to the
+  # latter. The repo declares it instead. See ADR-016 section 3.
+simt-applies: []
+simt-opt-in: true
+simt-substitutions:
+  - key: previewWorkers
+    default: the dedicated preview Workers
+    describe: the preview Worker names this family deploys
+  - key: previewUrlHost
+    default: https://<preview-worker>.<account>.workers.dev
+    describe: the preview URL shape authenticated checks must target
+  - key: productionDomains
+    default: the repo's production domains
+    describe: domains authenticated postflight must never target
+  - key: productionDomainNote
+    default: ""
+    describe: one clause naming this repo's own production domain binding
+  # These two arrived as one slot in the divergent files: one repo put a build-config
+  # instruction where another put a domain-binding note, which read as a conflict. They
+  # are not alternatives, so the union carries both — but a repo that needs one, or
+  # neither, declares that. A worker that serves derivatives and calls no API has no
+  # API base URL to set, so it declares only its own custom-domain binding.
+  - key: previewApiBaseUrlNote
+    default: "- Point the preview build at the preview API Worker: set `SOCIAL_API_BASE_URL` in the Cloudflare Workers Builds preview environment to the preview API Worker URL."
+    describe: build-config instruction, when this repo actually has a preview API base URL to set
+  - key: googleOnlyNote
+    default: "- Production and public browser flows remain Google-only."
+    describe: the identity policy this repo enforces in production
+---
+
+# Preview-Only Authenticated Postflight
+
+Authenticated remote postflight and release checks use only {{previewWorkers}}, deployed
+with `AUTH_PROVIDER_POLICY=preview_postflight_password` and a secret-bound Firebase password
+identity (`POSTFLIGHT_PASSWORD_UID`).
+
+## Requirements
+
+- Authenticated checks must target preview URLs (`{{previewUrlHost}}`).
+- Postflight credentials live in the operator keychain only; never in source, chat, D1, or
+  logs.
+{{googleOnlyNote}}
+{{previewApiBaseUrlNote}}
+{{productionDomainNote}}
+
+## Forbidden
+
+- Authenticated postflight against production domains ({{productionDomains}}).
+- Using real Social Google accounts for feature slice verification.
+- Demanding, pasting, or storing production Google OAuth tokens in chat or tickets.
+
+## Allowed Without Account
+
+- Unauthenticated production probes (`/health`, `/openapi.json`, a fail-closed `401`),
+  Cloudflare API inventory, D1 migration verification, and Worker deployment status.

simt_dev/vendored/rules/mdc/slice-commit.mdc

@@ -0,0 +1,52 @@
+---
+simt-id: slice-commit
+simt-target: .cursor/rules/slice-commit.mdc
+description: How a completed change becomes one commit, and what happens before anything is pushed
+alwaysApply: true
+# `simt-applies: always` is what makes a rule reachable at all. Without it this rule was
+# authored, shipped, tested for its presence on disk -- and projected into no repo,
+# silently. Reached by running `init` against a real repo, not by reading the file.
+simt-applies: always
+---
+# Slice Commit
+
+A slice is the smallest change that is independently valuable on its own. Committing
+one is a mechanical procedure with a fixed order, because every step after it depends
+on the one before: you cannot review a diff you have not staged, and you cannot claim
+evidence for a test you have not run.
+
+## Order
+
+1. **Run the focused test the change needs**, through the repository's own runner,
+   naming the exact command and the exact file — see `test-gate`. A full suite is
+   for a named trigger, not for progress.
+2. **Stage only what the slice touched.** `git status` first, and leave unrelated work
+   alone. Report what you left alone; silence about it reads as "I reverted it".
+3. **Read the staged diff.** Not the working tree — the diff. It is what will be
+   committed, and it is the last chance to notice a file that does not belong.
+4. **Write the message.** Conventional Commits, imperative subject, no trailing period:
+   `fix(gates): declare only gates a repo can run, and report the ones it cannot`.
+   The subject says what changed; the body says why, and what was deliberately not
+   changed.
+5. **Commit.** `git commit`, non-interactive. Report the SHA.
+6. **Stop.**
+
+## Pushing is a separate decision
+
+**Never push because the work is finished.** Push is a separate act with its own
+approval, and pushing the branch a remote treats as production can deploy it.
+
+Before asking for approval, state what the push will do: which branch, how many
+commits, and whether it triggers a deployment, a migration, or any other remote
+mutation. Then wait. Approval to commit is not approval to push.
+
+Never use `--no-verify`. A hook that fails is telling you something about the change;
+skipping it turns a gate into a suggestion and the next person has no way to know it
+was skipped.
+
+## What never belongs in a commit
+
+- Failing, partial, or unrun work. A commit is a claim; a partial one is a false one.
+- Secrets, tokens, or generated artefacts that drift.
+- Work nobody asked for. Unrelated changes in a slice commit are invisible in review
+  and impossible to revert on their own.

simt_dev/vendored/rules/mdc/test-gate.mdc

@@ -0,0 +1,54 @@
+---
+simt-id: test-gate
+simt-target: .cursor/rules/test-gate.mdc
+description: Full-pass tests and test deltas are mandatory before commit or reviewer approval
+alwaysApply: true
+simt-applies: always
+simt-substitutions:
+  - key: exampleRunner
+    default: your test runner, through the repository's own script or task
+    describe: how this repo actually runs one named test file
+  - key: exampleTestPath
+    default: path/to/the.changed.test.ts
+    describe: one real test file for this repo, used only as the named example
+  - key: pathKinds
+    default: feature/contract/route
+    describe: this repo's executable path vocabulary
+  - key: producerNoun
+    default: API producer
+    describe: what produces a contract this repo consumes
+---
+
+# Test Gate
+
+Applies to every feature slice, bugfix, and plan tracker task. Docs/config-only chores are
+exempt from test deltas but require named doc/format checks to pass.
+
+## Implementer Requirements
+
+1. **Name exact commands and test files**: {{exampleRunner}}, selecting
+   `{{exampleTestPath}}` on its own.
+2. **100% Pass Required**: the named commands must exit 0 with every test passing. A
+   partial pass (e.g. 6/8 passing) is a hard blocker, and so is quoting the passing subset.
+3. **Behavioral Test Deltas**:
+   - New {{pathKinds}} path -> new or extended test asserting the behavior.
+   - Bugfix -> regression test reproducing the failure mode.
+   - If no test file changed, justify why the existing tests fully prove the invariant.
+4. **Cross-Repo Order**: commit the {{producerNoun}} (contract/migration) before any
+   consumer generates against it. Never apply remote migrations or deploy from uncommitted
+   code.
+
+## Reviewer Mandatory Block
+
+Return `BLOCK` when:
+
+- Any test fails, is skipped (without pre-existing justification), or is unrun.
+- An executable diff has no test delta and no explicit justification.
+- The coordinator cites partial suite results or defers a failing test.
+- **Consumer side:** a consumer requires a new API field with no backward-compatibility or
+  deploy-order evidence.
+- **Producer side:** the {{producerNoun}} ships without a test asserting the new invariant
+  or field.
+
+The last two are complementary, not alternatives. A reviewer that checks only one of them
+misses half of the failure they exist to catch.

simt_dev/vendored/rules/stacks/android.md

@@ -0,0 +1,63 @@
+---
+simt-id: android
+simt-title: Android
+# Selected on the one thing that makes a repository an Android application: a
+# module with an `AndroidManifest.xml`. `gradle` and `kotlin` are shared with every
+# JVM backend, which is how a Spring or Ktor service used to receive this profile
+# (S28, ADR-047).
+simt-applies: [has-android-manifest]
+---
+
+# Stack profile: Android
+
+Applies to: `has-android-manifest` — some module has a
+`src/main/AndroidManifest.xml`. A JVM backend with no Android module does not get
+this profile; see `jvm`.
+
+## Build
+
+- `./gradlew` only. Never a system `gradle`. Never `--configuration-cache` where a
+  repo documents that it breaks.
+- `./gradlew spotlessApply` is the formatting entrypoint in repos that use Spotless.
+- The manifest is not hand-edited for a build-level change: `applicationId`, `versionCode`
+  and `versionName` are declared in the module's build file and land in the merged
+  manifest. A value in two places is a value that will disagree.
+
+## Modules and layers
+
+- `:core:domain` depends on no other internal module. Enforce it; do not add an
+  import that breaks the direction.
+- Layer suffixes: `*Repository`, `*ViewModel`, `*UiState`, `*Screen`, `*Service`.
+- Feature modules never import `androidx.compose.ui.window.Dialog`, M3 `AlertDialog`
+  or M3 `ModalBottomSheet`. The raw `Dialog` window belongs to allowlisted `core:ui`
+  surfaces, and `checkOverlayModalPolicy` fails `./gradlew check` when a feature
+  bypasses it.
+
+## Accessibility
+
+- Every user-facing string is a resource, with a `cd_` content description where an
+  icon or image carries meaning. Decorative images declare `contentDescription = null`
+  explicitly.
+- Touch targets meet the platform minimum, and the minimum is asserted rather than
+  eyeballed.
+- Respect the system font scale and the display size the user has chosen; a fixed
+  `sp` value or a hard-coded cell height breaks both.
+
+## Wear OS
+
+- `applicationId` in the wear module must equal the phone app's. Divergence makes the
+  Data Layer fail silently — no error, no delivery.
+- Wear and phone target SDKs differ by design for Play Console reasons. Do not "align"
+  them.
+
+## Data
+
+- Room: bump the version, add the migration, extend the migration test. Never edit an
+  applied migration.
+
+## Testing
+
+- Unit tests for view models, repositories and mappers; instrumentation tests for UI.
+- `Dispatchers.setMain` in a `@BeforeTest`, restored in `@AfterTest`.
+- Assert behaviour, not implementation. Never weaken an assertion, an accessibility
+  check or a fixture to match current behaviour.

simt_dev/vendored/rules/stacks/cloudflare-workers.md

@@ -0,0 +1,65 @@
+---
+simt-id: cloudflare-workers
+simt-title: Cloudflare Workers (TypeScript)
+# What the repo runs on, not what it is written in. `typescript` was here and put
+# this profile on every TypeScript repository in the estate that had no more
+# specific one; `hono` was here too, and Hono runs on Node, Bun and Deno as
+# happily as on Workers. A wrangler config or the `wrangler` dependency is the
+# only evidence that this is a Worker (S28, ADR-047).
+simt-applies: [cloudflare-workers]
+---
+
+# Stack profile: Cloudflare Workers (TypeScript)
+
+Applies to: `cloudflare-workers` — a `wrangler.json`, `wrangler.jsonc` or
+`wrangler.toml`, or a `wrangler` dependency.
+
+## Schema and config
+
+- `wrangler.jsonc` is the single source of binding and environment truth. Do not read
+  configuration from a second file.
+- Bindings are the integration surface. A Worker calls a service binding, not a REST endpoint
+  over the network to its own account.
+- Secrets come from the runtime binding. Never commit them, never log them, never accept one
+  from a query parameter.
+
+## Data
+
+- D1: one new sequential immutable migration per change. Never edit an applied migration.
+  Define coexistence order and forward repair; do not promise SQL rollback.
+- Prefer D1 constraints and triggers over read-then-write in application code.
+- Prepared, parameterised statements only. Never interpolate a value into SQL.
+- Durable Objects: one owner per piece of state. Use alarms for scheduling, and RPC for
+  internal calls rather than self-fetch.
+- Queues are at-least-once: consumers must be idempotent, keyed by an idempotency token that
+  is stable across retries.
+
+## Request handling
+
+- Validate at the edge with the schema layer. Authorization is server-authoritative; a
+  client-side role, claim, cache entry or URL parameter grants nothing.
+- `Request`/`Response` are globals. Do not pass them through as values into domain code.
+- Caching defaults to `private, no-store`. Never cache token, account, block, reveal, admin
+  decisions or authenticated errors.
+- Streaming is the default for large bodies; do not buffer without a stated reason.
+
+## Module state
+
+- No module-scope mutable state. A Worker instance is reused across requests, so a counter or
+  cache at module scope leaks between users.
+
+## Observability
+
+- Structured logs through the logger interface, with an allowlist. Never log bodies, tokens,
+  UIDs, user text, exact coordinates or full URLs.
+- Use `Math.random` never for anything security-relevant; use Web Crypto.
+
+## Types and tests
+
+- `strict` plus `noUncheckedIndexedAccess`, `exactOptionalPropertyTypes`,
+  `noImplicitOverride`, `noFallthroughCasesInSwitch`, `noImplicitReturns`, `isolatedModules`.
+  With `exactOptionalPropertyTypes`, pass optionals through conditional spreads or an explicit
+  `prop: value | undefined`; never `prop?: T` into a `prop: T | undefined` parameter.
+- Generate Wrangler types from the config; do not hand-write binding types.
+- Test with the real Workers runtime pool (`@cloudflare/vitest-pool-workers`) so Workers APIs,
+  D1 and Durable Objects behave as they will in production.

simt_dev/vendored/rules/stacks/connectiq.md

@@ -0,0 +1,62 @@
+---
+simt-id: connectiq
+simt-title: Connect IQ (Monkey C)
+simt-applies: [connectiq]
+---
+
+# Stack profile: Connect IQ (Monkey C)
+
+Applies to: `connectiq`.
+
+## The platform is not the language you know
+
+This profile exists because the most expensive failures in this stack are silent. Read the
+repo's own known-defects table before assuming any platform behaviour; the entries there are
+empirically verified and will otherwise be rediscovered one bug at a time.
+
+Known traps to assume until verified otherwise:
+
+- `String.toNumber()` can truncate rather than fail.
+- `==` on two `String`s compares identity, not value.
+- `Number` is 32-bit. Values outside that range are wrong, not approximate.
+- `logger.error()` does not fail a test. A passing suite can contain a logged error.
+- `getGlanceView()` is unavailable on the Simulator.
+
+## Memory
+
+- Memory budgets are hard limits, not targets, and they are the repo's declared gate
+  (`simt-dev.json`). Zero allocation in `onUpdate`; no allocation in a draw callback.
+- A memory check that "currently exits 1 by design" is not a gate — it is noise that teaches
+  everyone to ignore it. Declare the budget or drop the check.
+
+## Language and style
+
+- Four-space indent, LF, 300-char line limit.
+- `initialize()`, `_camelCase` for private members, `UPPER_SNAKE_CASE` for constants.
+- `typeCheckLevel: "gradual"` — do not raise it to chase a build; fix the types instead.
+- One responsibility per class. A class that draws, computes and persists is three classes.
+- 400 lines is a review trigger, 1000 a ceiling (ADR-005). Generated `.mc` is exempt when the
+  generator is named.
+
+## Data and protocol
+
+- A model that crosses the wire is **generated, never hand-written**. Hand edits are overwritten
+  by the next codegen run and the drift is discovered in production.
+- Validate every field at construction. A target with `bearingDeg = 400` cannot be created.
+- A positional parser makes field order part of the contract. Reordering a field is a protocol
+  change, not a refactor.
+- `schemaVersion` is checked before parsing, never after.
+
+## Security
+
+- Never commit the developer key, an app UUID hardcoded as a literal, or any credential.
+  The developer key is unrecoverable if lost — treat its loss as unrecoverable and rotate.
+- Data minimisation: a field not needed on the device is not sent to it.
+- No payload logging. Log the shape of a failure — field name and reason — never the data.
+
+## Build
+
+- `monkeyc -f monkey.jungle` with the documented product ids. Verify with the identity and
+  settings-defaults checks before every build; they catch the two mistakes that otherwise reach
+  a device.
+- Do not pass `--configuration-cache` to Gradle.

simt_dev/vendored/rules/stacks/container.md

@@ -0,0 +1,31 @@
+---
+simt-id: container
+simt-title: Containers
+simt-applies: [has-dockerfile]
+simt-fallback: false
+---
+
+## Containers
+
+A Dockerfile is the build. If a rule here and the repo's own instructions disagree, the
+repo wins — but the disagreement is worth raising, because these are the mistakes that
+survive to production.
+
+- **Pin the base image by digest.** A floating `FROM node:22` means last night's build is
+  not reproducible and a compromised upstream tag is your problem. If the repo deliberately
+  tracks a tag, do not "fix" it silently.
+- **Never bake a secret.** No `ARG` that holds a token, no `ENV` holding a key, no `COPY
+  .env`. Build args are recorded in image history, which is world-readable in most
+  registries. Read secrets from the runtime environment.
+- **Copy as little as possible.** Copy manifests first, install, then copy source: a
+  dependency layer invalidates on every source edit otherwise. And never `COPY . .` when a
+  `.dockerignore` exists to be honoured.
+- **Run as a non-root user**, and do not need root to write to the application directory.
+- **One process per container.** Signals, restart policy and log collection all assume the
+  entrypoint is the app, not a shell wrapping it.
+- **Expose only what is served.** An unpublished port is still reachable on the container
+  network; an `EXPOSE` is documentation, not a control.
+- **Health endpoints are not debug endpoints.** A health check runs often, automatically,
+  and on every replica. It must not leak counts, versions, or stack traces.
+- **The image is the unit of rollback.** A change you cannot rebuild byte-identically is a
+  change you cannot roll back, which is a worse position than not shipping it.

simt_dev/vendored/rules/stacks/jvm.md

@@ -0,0 +1,54 @@
+---
+simt-id: jvm
+simt-title: JVM backend
+# The build tool and the language, which is what a JVM backend is identified by.
+# This profile used to be `jvm-android` and applied on `gradle` alone, so a Spring
+# or Ktor service received rules about Compose, Wear OS application ids and
+# instrumentation tests — advice with nothing to apply it to (S28, ADR-047).
+simt-applies: [gradle, has-maven-pom, kotlin, java]
+---
+
+# Stack profile: JVM backend
+
+Applies to: `gradle`, `has-maven-pom`, `kotlin`, `java` — a JVM build. The Android
+rules live in the `android` profile, which selects on `has-android-manifest`.
+
+## Build
+
+- `./gradlew` only, never a system `gradle`; `./mvnw` where a wrapper is committed,
+  never a system `mvn`. Never `--configuration-cache` where a repo documents that it
+  breaks.
+- `./gradlew spotlessApply` is the formatting entrypoint in repos that use Spotless.
+- Pin the JVM toolchain in the build file (`java.toolchain`, `sourceCompatibility`).
+  A JDK on the developer's PATH is not a floor anything enforces.
+
+## Modules and layers
+
+- `:core:domain` depends on no other internal module. Enforce it; do not add an
+  import that breaks the direction.
+- Layer suffixes: `*Repository`, `*Service`, `*Mapper`, `*Controller`. A class named
+  `*Repository` that talks to HTTP is not a repository.
+
+## Kotlin
+
+- Four-space indent, LF, 300-char line limit.
+- No `!!`. Prefer a sealed `RepositoryResult<T>` over exceptions for expected failures.
+- Expose `MutableStateFlow` as `StateFlow` via `.asStateFlow()`; update state with
+  `_state.update { }`.
+- Java and Kotlin interop: `Optional` in a Java signature, a nullability annotation in
+  a Kotlin one, and never a platform type left untyped at the boundary.
+
+## Testing
+
+- Unit tests for services, repositories and mappers; an integration test only when the
+  behaviour is genuinely cross-system.
+- Assert behaviour, not implementation. Never weaken an assertion to match current
+  behaviour.
+- Test the narrowest layer that proves the behaviour.
+
+## Data
+
+- One new sequential immutable migration per change. Never edit an applied migration.
+  Define coexistence order and forward repair; do not promise SQL rollback.
+- Prepared, parameterised statements only. Never interpolate a value into SQL, and
+  never assemble SQL by string concatenation from a caller-supplied identifier.

simt_dev/vendored/rules/stacks/node.md

@@ -0,0 +1,45 @@
+---
+simt-id: node
+simt-title: Node (general)
+simt-applies: [node]
+simt-fallback: true
+---
+
+# Stack profile: Node (general)
+
+Applies to: `node`, `node-web`, `typescript` when no more specific profile matches.
+
+## Manifest
+
+- One `packageManager` field, matching the committed lockfile. A repo with no declared
+  package manager has no enforced one.
+- `engines.node` states a floor. A version floor nobody enforces is a comment.
+- `.nvmrc` pins the development version and must agree with `engines` and with CI.
+
+## Scripts
+
+- Run through `npm run <script>` (ADR-010). Never `npx` or `npm exec` for a declared
+  dependency: `npx` will fetch a version the project does not pin.
+- A script name is the contract. Rename a script and rename every caller, including docs,
+  hooks and CI, in the same change.
+
+## Formatting and linting
+
+- Prettier owns formatting. ESLint disables the stylistic rules Prettier already owns —
+  otherwise the two tools fight over every file.
+- `format` and `format:check` are both present. `format:check` is what CI and hooks run.
+- `.prettierignore` covers generated and vendored output: build directories, coverage,
+  generated clients, graph output. Formatting generated output is a review finding, not a fix.
+
+## Types
+
+- `strict` plus the full strictness set, and `noEmit` for any project that bundles elsewhere.
+  A bare `tsc` in a bundler project writes JavaScript next to the sources.
+- `moduleResolution` spelled consistently across every repo in the workspace.
+
+## Tests
+
+- `vitest`, `jest` or `node --test` — one runner per repo, declared, not inherited.
+- Focused selection is the default invocation. A full suite runs against the triggers in
+  `simt-dev.json` (ADR-003).
+- No snapshot-only acceptance: a snapshot proves the code did not change, not that it is right.