myc

Self-custodial remote signer for Radroots apps
git clone https://radroots.dev/git/myc.git
Log | Files | Refs | README | LICENSE

AGENTS.md (27783B)


      1 # myc — repository agent contract
      2 
      3 ## 1. Scope and operating model
      4 
      5 - This file applies to the complete repository unless a nearer `AGENTS.md` is
      6   stricter.
      7 - This repository owns `myc`, the standalone Radroots NIP-46 signer service.
      8   Treat identity custody, signing, approval, session, persistence, and
      9   signer-facing transport as security-critical behavior.
     10 - Keep the repository independently buildable, testable, packageable, and
     11   operable. Do not depend on private repositories, unreachable or unlocked
     12   artifacts, internal monorepo paths, absolute workstation paths, or private
     13   harnesses. An unpublished public dependency is allowed only when its exact
     14   commit is reachable from the governed public Git source and pinned by the
     15   checked-in source lock.
     16 - `.github/**` and capsule-local CI workflows are forbidden; keep validation
     17   forge-agnostic, and place any required monorepo orchestration exclusively
     18   under the parent monorepo's root `.act/**` authority.
     19 - Do not add or retain tracked `docs/**`, `.github/**`, or `.act/**` content in
     20   this capsule. Human-facing Myc specifications, decisions, runbooks, and
     21   qualification evidence belong under the parent monorepo's
     22   `docs/oss/myc/**` authority; standalone machine-enforced declarations belong
     23   under this repository's governed contract surfaces.
     24 - Myc does not own relay storage or tenancy, general relay fanout, SDK contract
     25   generation, wallet UX, hosted accounts, telemetry, artifact promotion, or
     26   deployment transport.
     27 
     28 ## 2. Authority and preflight
     29 
     30 - Before editing, read this file, `README`, `Cargo.toml`,
     31   `radroots.service.source_lock.v4.toml`, the relevant implementation and tests,
     32   and `flake.nix` or migrations when they are in scope.
     33 - Current compiler/source preparation uses the V4 lock and
     34   `contracts/services_hardening/native_release.v4.json`. Nix inputs are bound;
     35   executed current qualification remains separate. Generate a staged migration
     36   with the source-locked Lib `service-source-lock --mode prepare`, verify and
     37   commit it, then require its clean-source check. The unchanged archived V3
     38   lock and V2/V3 declarations retain historical scope. Step 300 tooling is
     39   replay-only for its original source and does not qualify current inputs.
     40 - `.radroots-consumer-root` is the standalone source-lock identity and must
     41   remain exactly `myc`. The implemented control-plane contract is
     42   `contracts/services_hardening/operator_contract.v1.json`.
     43   Service implementation must use its exact routes, operation IDs, model
     44   fields, doctor checks, and shared host/exit references; prototype CLI or
     45   HTTP behavior is not authority to reinterpret that contract.
     46 - The exact signer-provider inventory and resource boundary is
     47   `contracts/services_hardening/provider_contract.v1.json`. Keep its role,
     48   provider, capability, call-identity, deadline, limit, credential-reference,
     49   cancellation, and no-publication facts synchronized with the sealed Rust
     50   models. Provider wire encoding and result verification may refine only the
     51   later checkpoints that own those boundaries; they may not widen this
     52   contract.
     53 - The encrypted-file implementation is frozen by
     54   `contracts/services_hardening/encrypted_identity_envelope.v1.json`. It must
     55   use the source-locked `radroots_secrets` v2 context-bound envelope, explicit
     56   caller-supplied entropy, create-new owner-only persistence, expected-public-
     57   key verification, and state-backup exclusion. Credential artifact resolution
     58   remains a separate boundary and may not introduce a sibling-key fallback.
     59 - Wrapping-credential resolution is frozen by
     60   `contracts/services_hardening/wrapping_credential_resolution.v1.json`. It
     61   derives one validated shared artifact name beneath the canonical instance
     62   secrets root, reads only an existing exact owner-only artifact, and exposes
     63   neither a caller path nor caller bytes. Production injection/mounting and
     64   repo-local provisioning are external/offline; ordinary run, TOML,
     65   environment, arguments, envelope siblings, and state backup never create or
     66   carry the credential.
     67 - Local-signer transport is frozen by
     68   `contracts/services_hardening/local_signer_transport.v1.json`. It uses the
     69   hardened Lib `AdminClient` for one fixed HTTP/1.1 JSON endpoint over a Unix
     70   socket, carries the complete provider-operation binding in closed tagged
     71   request/response models, enforces configured body/deadline/concurrency
     72   limits, and returns only semantically untrusted output for Step 135.
     73 - Provider verification is frozen by
     74   `contracts/services_hardening/provider_verification.v1.json`. It requires
     75   injected observation time, rebinds the complete response to the configured
     76   provider and original operation, verifies peer/direction/version and exact
     77   protocol shapes, cryptographically verifies signed events, retains their
     78   exact canonical bytes, and returns only a sealed redacted result.
     79   Verification is not publication and performs no provider execution or
     80   database mutation.
     81 - Step 136 removes the orphaned prototype provider tree and its keyring,
     82   managed-account, plaintext/adjacent-key, child-process, implicit-identity,
     83   generic remote-session, legacy logging/client, and unused dependency
     84   surfaces. Do not restore those files, dependencies, or Tokio process
     85   capability; `radroots_nostr_connect` remains only as the active NIP-46
     86   protocol dependency.
     87 - Step 137 owns only the existing-state runtime foundation and exact startup
     88   prerequisite inventory. Encrypted-file opening runs in joined one-shot
     89   supervisor tasks; local-signer construction performs no probe, and no
     90   provider is ready before its governed verification. Do not add detached
     91   handles, a library runtime, signals, process exit, relay/admin execution, or
     92   a false readiness transition here.
     93 - Step 138 freezes a root-only public API. Keep every implementation module
     94   private, expose only curated crate-root names, keep public errors crate-owned
     95   and source-free, and update the reviewed API baseline and package guards for
     96   every intentional public-surface change. Shared runtime-path, SQLite, and
     97   storage identity types are deliberate governed contract dependencies;
     98   provider, SQLx, Serde, transport, and task implementation types are not.
     99 - Step 139 established the predecessor service source lock and pre-promotion
    100   native package metadata. Keep the exact Lib revision consistent across every
    101   direct Radroots dependency, Cargo.lock, the verified source archive, and the
    102   generated v2 service lock. Deferred `flake.nix` and `flake.lock` material is
    103   independently digest-bound and may select an older reachable Lib revision;
    104   it is not active native revision authority. Native target metadata does not
    105   qualify an artifact; Nix, OCI, signing, tags, publication, and deployment
    106   remain deferred.
    107 - RCLD-RSHR-195 Step 245 advances the active native Lib source lock and freezes
    108   Myc state creation behind the runtime-path directory plan plus the sealed
    109   service-SQLite initializer. Explicit initialization may provision only the
    110   exact governed service-instance suffix after identity and catalog validation;
    111   every existing-only open remains non-creating. Do not restore raw paths, raw
    112   SQLx connections, filesystem probes, or directory-creation fallbacks at the
    113   state-host boundary.
    114 - Step 148 closes the production NIP-46 response authority in
    115   `contracts/services_hardening/nip46_response_commit.v1.json`. Production
    116   code may commit a completion only through the atomic exact-response method;
    117   a retained completion without its immutable response and initial delivery
    118   state is inconsistent evidence and must never be repaired implicitly.
    119 - Step 150 introduced the historical 21-route and 35-model Myc Unix-admin
    120   adapter. Step 159 unit 13 owns its final 19-route and 32-model form by
    121   removing live identity rekey and replacement. Keep the shared Lib router
    122   private; reject model drift, unknown/duplicate/null
    123   fields, noncanonical response bytes, invalid path/query values, and unsafe
    124   errors at the adapter boundary. Domain handlers must bind authenticated
    125   cursors to route/filter/snapshot identity and must retain exact operation-ID
    126   replay/conflict evidence before returning success. Do not infer relay
    127   delivery from a successful local mutation and do not add TCP admin routes.
    128 - Step 152 freezes the one-parse CLI execution split. Every admitted command
    129   must select exactly daemon, offline, or permissioned Unix-admin authority;
    130   only the explicitly contracted read-only status, backup, and public-identity
    131   operations may fall back after proving the daemon writer lock is free.
    132   Identity rekey and replacement are offline create-new/config-apply
    133   operations and have no live command or route. Every retained live mutation
    134   has no direct-state fallback.
    135   Do not reparse process arguments or let a live CLI plan obtain SQLite,
    136   provider, relay, task, signal, or runtime authority.
    137 - Step 153 freezes one ordered 13-check doctor engine. Check adapters retain
    138   their operation-specific authority and may return only closed observations;
    139   the engine owns exact deadlines, required/optional aggregation, fixed safe
    140   summaries/remediation codes, bounded canonical JSON, and exit 6 for required
    141   failure or timeout. Do not admit raw errors, paths, URLs, keys, credentials,
    142   arbitrary details, unbounded output, detached probe work, or
    143   liveness/readiness probe authority. A pass must prove every contracted scope
    144   facet, and deadline cancellation must stop or synchronously own cleanup.
    145 - Step 154 freezes one passive latest-value status cache around the shared Lib
    146   lifecycle primitive. The non-clone publisher encodes the complete bounded v1
    147   local-status envelope before atomic replacement; cloneable readers may only
    148   return the retained immutable snapshot. Status reads never query SQLite,
    149   providers, relays, credentials, DNS, time, or fresh probes and never spawn a
    150   task. Keep connection-count keys and identity roles closed, preserve the last
    151   valid snapshot on any failed publication, admit only the fixed twelve status
    152   reasons, and keep detailed status on the permissioned Unix-admin boundary.
    153 - Step 159 unit 10 owns schema-v10 offline configuration lifecycle. Keep the
    154   configuration-binding ledger append-only and capped at 1,024 generations;
    155   seed one post-migration generation without rewriting the immutable birth
    156   record. Startup must match the latest config/public-identity binding. Identity
    157   changes revoke live connection/challenge authority, permission narrowing
    158   revokes affected sessions only, and an existing relay referenced by
    159   nonterminal delivery work cannot be removed or changed. Do not persist relay
    160   URLs, paths, credentials, provider envelopes, or protected values in the
    161   binding history.
    162 - Step 159 unit 11 owns schema-v11 bounded admin idempotency. Keep operation
    163   identifiers on the fixed ASCII grammar, bind route plus canonical request
    164   digest, cap replay models at 8,192 bytes, prune only expired Completed rows,
    165   reserve completion capacity at admission, and retain unresolved Prepared
    166   evidence as outcome-unknown. The configured admin response cap must admit the
    167   maximum model in its bounded success envelope. Never persist a
    168   request body, path, correlation ID, credential, bundle path, or secret in the
    169   journal. Database-only mutations must later compose their effect, audit, and
    170   completion in one transaction; online backup records Prepared before capture
    171   and completes only after the bundle is durable.
    172 - Step 159 unit 12 owns the crate-private provider executor, the exact
    173   source-locked `radroots_transport_nostr` adapter, and the durable delivery
    174   worker. Provider results remain untrusted until independently verified.
    175   Delivery preparation performs no relay I/O; the worker persists Submitted
    176   immediately before execution, maps post-submit cancellation or lost
    177   acknowledgement to UnknownAcknowledgement, and retries only the exact
    178   committed signed bytes. Never hold a SQLite transaction across provider or
    179   relay work, detach protected blocking work, expose the executor/client, or
    180   create one task per relay. Unit 15 alone wires these components into the
    181   fixed runtime graph and startup handshake.
    182 - Step 159 unit 13 owns the final 19-route/32-model production Unix-admin
    183   server around the exact handler boundary, the configured transport-limit
    184   projection, the canonical permissioned `admin.sock` binding, and the
    185   machine-bound composition facts for the existing sole status publisher,
    186   passive three-route operations server, and injected 13-check doctor. Keep
    187   shared routers, listeners, entropy, and cancellation private. Unit 14 owns
    188   secure CLI/config bootstrap and concrete doctor probes; Unit 15 alone owns
    189   server task spawning, provider/relay wiring, readiness, reconnect, and
    190   shutdown.
    191 - Step 159 unit 14 owns the one-pass process executor, descriptor-bound config
    192   loading and create-new persistence, fixed zeroizing identity-provisioning
    193   input, actual existing-state metadata discovery, explicit backup/restore
    194   inputs, one binary-owned configured Tokio runtime, and concrete bounded
    195   doctor probes. Keep result bytes on stdout and fixed diagnostics on stderr.
    196   The executable must not provision deployment directory trees, derive runtime
    197   limits from host CPUs, read secret arguments or environment variables, open
    198   an existing live database before validating a restore manifest, publish from
    199   doctor, or return success without the Unit 15 daemon `run` graph. Unit 15
    200   owns that graph, process signals, readiness/reconnect, and phase-aware drain.
    201 - Step 160 owns the standalone native release-artifact boundary in
    202   `contracts/services_hardening/native_release.v2.json` and `cargo xtask
    203   native-release`. Keep its exact two Linux targets, clean committed source,
    204   caller-supplied binary, positive deterministic epoch, bounded generated
    205   inventory, vendored offline source archive, source lock, CycloneDX SBOM,
    206   notices, checksums, unsigned provenance, and fixed systemd template closed.
    207   Outputs remain external to the source tree. Do not accept a caller service
    208   root, arbitrary member name, Nix/NixOS/OCI input or output, signing key,
    209   parent-owned human document, private harness, protected material, or
    210   publication/deployment authority.
    211 - RCLD-RSHR-150 Step 227 owns the fixed standalone systemd unit and
    212   `systemd_qualification.v1.json`. Keep the canonical service-host directory
    213   directives, stable exit-code restart split, bounded stop, empty capability
    214   sets, no environment-carried credentials, systemd 252 minimum, and maximum
    215   offline exposure 3.0 exact. The Linux verifier must fail closed when
    216   `systemd-analyze` is absent. Do not enable compatibility-sensitive
    217   `MemoryDenyWriteExecute` or syscall filters until the Step 229 integration
    218   wave proves them against the real binary; do not install, enable, start, or
    219   deploy a production service here.
    220 - Step 221 integration requires a signer-transport-authored `pending_connection` response for an
    221   explicitly approval-gated NIP-46 connect request. Keep that exact response
    222   and its initial delivery job atomic and immutable without recording a false
    223   terminal operation completion; relay delivery and exact replay use only the
    224   retained signed bytes, and terminal response authority must not conflict
    225   with the pending response.
    226 - Step 161 owns the closed executable qualification matrix in
    227   `contracts/services_hardening/process_qualification.v1.json`. Keep its
    228   process deadlines, parallelism, soak count, crash fixture, output bound,
    229   actual-process corpus, and component evidence exact. Crash injection is an
    230   external test-process termination only; do not add a production failpoint,
    231   hidden command, environment selector, detached test worker, or public test
    232   API. Failed backup and restore work must retain collision/recovery evidence,
    233   preserve the live database, and recover only through the governed next
    234   process open.
    235 - Treat checked-in source, tests, and prototype behavior as implementation
    236   evidence, not permission to preserve behavior that the active requirement
    237   removes.
    238 - Do not invent protocol behavior, APIs, dependencies, release processes,
    239   identity authority, migration behavior, or external integration semantics.
    240 - Inspect `git status --short`, the exact repository root, and nearby tests
    241   before changing behavior. Preserve unrelated work and stop on an unresolved
    242   security or custody conflict.
    243 - Keep changes narrowly scoped and independently reviewable. Do not mix
    244   unrelated cleanup, speculative abstractions, roadmap work, or compatibility
    245   scaffolding into a checkpoint.
    246 
    247 ## 3. Clean-slate service rule
    248 
    249 - Do not add or preserve prototype configuration readers, `.env` or
    250   `--env-file` runtime configuration, `MYC_*` runtime selectors, JSON/JSONL
    251   mutable state, prototype config/state importers or migrations, worker paths,
    252   old-path probes, aliases, fallbacks, dual readers/writers, deprecated
    253   modules/APIs/re-exports, or old/new feature switches. Offline production
    254   schema migration must never accept an unreleased prototype format.
    255 - Remove superseded behavior and update every affected Radroots-owned consumer
    256   directly. Do not hide a breaking change behind a compatibility adapter unless
    257   an accepted public requirement explicitly requires one.
    258 - Preserve canonical NIP-04, NIP-44, and NIP-46 interoperability. Clean-slate
    259   product behavior never authorizes protocol drift or relaxed wire validation.
    260 - A breaking config, CLI, state, provider, admin, error, or wire change must
    261   update its public machine contracts, examples, tests, generated surfaces, and
    262   release qualification in the same coherent sequence.
    263 
    264 ## 4. Identity, provider, and secret boundaries
    265 
    266 - Keep transport, user, and optional discovery identities explicit. Never
    267   generate, replace, infer, or collapse an identity during ordinary `run`.
    268 - Support only the governed `encrypted_file` and permissioned Unix-socket
    269   `local_signer` providers. Do not add plaintext keys, arbitrary child
    270   commands, shells, desktop/server keyrings, managed accounts, TCP signers, or
    271   sibling wrapping-key fallback.
    272 - Treat every provider result as untrusted. Verify contract version, operation
    273   and correlation IDs, expected identity and role, bounds, exact unsigned event
    274   fields, author, event ID, signature, and applicable NIP semantics before use.
    275 - Keep plaintext keys, decrypted key material, wrapping credentials, provider
    276   secrets, and equivalent protected material out of config, logs, status,
    277   metrics, audit output, fixtures, backups, process arguments, environment
    278   contracts, error strings, and ordinary `Debug` output. A governed backup may
    279   contain the encrypted ciphertext envelope, but never the material needed to
    280   unwrap it. Minimize and zeroize protected values where practical.
    281 - Use typed request, response, approval, permission, session, provider, and
    282   error models. Raw provider, relay, SQL, or source-chain errors never cross a
    283   public or operator boundary.
    284 
    285 ## 5. Configuration, state, and process boundaries
    286 
    287 - Load exactly one immutable, strictly versioned TOML document. Reject unknown
    288   fields, implicit relays, unsafe defaults, environment overlays, includes,
    289   interpolation, fragments, hot reload, and arbitrary leaf flags.
    290 - Each service instance owns one explicitly initialized SQLite catalog and one
    291   live writer lock. Normal `run` opens existing state only and never creates,
    292   imports, guesses, or silently migrates prototype state.
    293 - Keep raw SQLite pools and write authority private to the store. The daemon is
    294   the only live writer; live mutations and online backup use the typed,
    295   permissioned Unix-socket admin boundary and never fall back to direct writes.
    296   Offline state operations must prove that no daemon writer lock is held.
    297 - Never hold a database transaction while waiting for a provider, relay, DNS,
    298   clock, entropy, or other external effect.
    299 - Parse the process CLI and initialize the tracing subscriber only in the
    300   binary composition boundary. Library modules may emit tracing events but
    301   must not install signal handlers, create nested Tokio runtimes, call
    302   `process::exit`, or detach authoritative tasks.
    303 - Inject wall time, monotonic time, entropy, providers, transport, and
    304   failpoints. Supervise and join every authoritative task; panic, error, or
    305   unexpected successful return from a critical task must coordinate shutdown
    306   and produce a nonzero process result.
    307 - Keep the Myc critical-task graph bounded and sealed. A task receives only its
    308   cooperative cancellation observer; callers cannot name tasks, extract task
    309   handles, detach work, install signals, or select process exits through this
    310   library boundary. Step 159 owns signal and forced-shutdown composition.
    311 
    312 ## 6. Admission, commit, and publication invariants
    313 
    314 - Bound and validate signed event bytes, tags, authored time, recipient,
    315   signature, event ID, decrypted plaintext, request identity, method, replay,
    316   conflicting reuse, connection admission, authorization challenges, and rate
    317   retention before accepting work.
    318 - Keep authorization-challenge URLs and display-only client metadata under
    319   operator policy; untrusted clients never choose redirect or display
    320   authority. Use separate bounded rate budgets for connection admission and
    321   authorization challenges so exhaustion of one cannot bypass or disable the
    322   other.
    323 - Commit the request decision, session effects, audit, exact serialized signed
    324   response bytes, immutable target set, and initial outbox state atomically
    325   before any relay submission.
    326 - Treat stored signed bytes as the sole publication authority. Retry, crash
    327   recovery, and reopen must submit the identical bytes and digest without
    328   deserializing, rebuilding, re-signing, or changing targets.
    329 - Create delivery jobs only inside the atomic signed-response or discovery
    330   transaction. Recovery is a bounded, cursor-driven repository operation with
    331   injected time/jitter evidence; final supervised startup looping remains a
    332   later runtime owner.
    333 - Render NIP-05 only from verified committed discovery state through an
    334   explicit desired/current offline operation. The service library must not
    335   silently host the document or acquire network authority while rendering it.
    336 - Distinguish submitted, delivered, failed, and unknown outcomes. Lost
    337   acknowledgement never becomes proof of failure or delivery.
    338 - Bound every queue, pool, request, response, event, tag set, retry schedule,
    339   deadline, rate window, retention set, audit query, and in-memory collection.
    340   Saturation must reject or defer safely without dropping committed work.
    341 
    342 ## 7. Admin and observability boundaries
    343 
    344 - Detailed status and every live mutation use bounded, versioned HTTP/JSON over
    345   the permissioned Unix socket. Do not add TCP admin, browser auth, CORS, or a
    346   direct writable CLI fallback.
    347 - Optional TCP operations expose only cached `/livez`, `/readyz`, and
    348   `/metrics`. They must not perform SQLite, provider, relay, credential, DNS,
    349   or other active probes.
    350 - Keep the Myc TCP adapter sealed around the source-locked service-host server.
    351   Do not add route registration, raw listener/server access, dependency-owned
    352   public types, or a second independently observed lifecycle cache. Publish
    353   only the fixed cached phase/readiness metric families and closed phase label.
    354 - Keep logs as safe structured stderr output. Keep result data on stdout and
    355   diagnostics on stderr. Use stable bounded public codes and messages, bounded
    356   metric labels, and explicit redaction.
    357 - Emit only the sealed `MycLogRecord` vocabulary. Do not log caller text, raw
    358   errors or sources, paths, SQL, relay URLs, identifiers, credentials,
    359   protected content, or decrypted payloads. Keep the exact 0-6 process result
    360   mapping synchronized with the operator contract; do not call process exit
    361   from library code or add file logging.
    362 - Backup and restore must preserve lock, manifest, integrity, schema, service,
    363   instance, identity, permission, fsync, atomic-rename, and protected-material
    364   exclusion invariants.
    365 
    366 ## 8. Rust and test discipline
    367 
    368 - The current stable compiler and MSRV are exact Rust 1.99.0, edition 2024
    369   and resolver 3. Keep package minimums, `rust-toolchain.toml` and Cargo metadata
    370   in exact agreement. Preserve original compiler identities in frozen release
    371   history and dedicated nightly tooling. A current minimum change does not
    372   qualify old source-lock, artifact or acquisition descriptors for a new
    373   candidate; update and verify those through their owning producers first.
    374 - Prefer pure transformations, explicit state machines, validated newtypes,
    375   tagged enums, narrow side-effect boundaries, and private visibility.
    376 - Avoid hidden production panics. Use typed errors for expected failures and
    377   reserve `unwrap` or `expect` for tests or locally proven invariants.
    378 - Keep `#![forbid(unsafe_code)]` at the crate roots; unsafe code is forbidden.
    379 - Add deterministic positive, negative, boundary, crash/retry, cancellation,
    380   saturation, redaction, and interoperability tests for every behavior change.
    381   Tests and examples must not contain real secrets, realistic private keys,
    382   reusable credentials, or sensitive event content.
    383 - Treat generated files as generated. Update them through the owning command
    384   and run the corresponding freshness check.
    385 
    386 ## 9. Canonical verification
    387 
    388 Through RCLD-RSHR-170, run the standalone native command authority through
    389 extbuild. Do not install, repair, invoke, or require Nix, and do not claim Nix,
    390 NixOS-module, or Nix-produced OCI qualification:
    391 
    392 ```text
    393 cargo extbuild doctor
    394 cargo extbuild run -- cargo fmt --all --check
    395 cargo extbuild run -- cargo check --workspace --locked
    396 cargo extbuild run -- cargo test --workspace --all-targets --locked
    397 cargo extbuild run -- cargo clippy --workspace --all-targets --locked -- -D warnings
    398 cargo extbuild run -- ./scripts/verify-boundaries.sh
    399 cargo extbuild run -- ./scripts/verify-supply-chain.sh
    400 cargo extbuild run -- ./scripts/verify-systemd.sh
    401 cargo extbuild run -- ./scripts/release-acceptance.sh
    402 ```
    403 
    404 The supply-chain gate requires exact cargo-deny 0.19.8 and cargo-vet 0.10.2,
    405 the checked-in exemption inventory, the locked graph, approved licenses and
    406 sources, and only the explicitly justified Nostr 0.44 advisories. Exemptions
    407 are visible accepted review debt, not claims of independent source audits.
    408 The release-acceptance contract requires formatting, locked metadata, locked
    409 all-target checking and testing, warnings-denied all-target Clippy, rustdoc with
    410 warnings denied, and diff hygiene. Run any gate not yet covered by the current
    411 release script explicitly; do not describe the script as sufficient until it
    412 enforces the complete contract. Run additional SQLx freshness, source-lock,
    413 systemd, package, SBOM, checksum, notice, and fresh-install gates when their
    414 surfaces change. Checked-in Nix material remains deferred source data through
    415 RCLD-RSHR-170 and is not a verification gate. Every OCI production or
    416 qualification path is likewise deferred and unclaimed through RCLD-RSHR-170.
    417 Use narrower checked-in commands only for iteration, and never claim a command
    418 passed unless it ran successfully.
    419 
    420 ## 10. Commits and irreversible actions
    421 
    422 - Format commits as `<scope>: <imperative summary>`, with a blank line and
    423   `- ` bullets when a body is useful. Split unrelated changes.
    424 - Report the exact files changed, behavior changed, commands run, results,
    425   unresolved risks, and whether the next checkpoint is safe.
    426 - Do not publish, push, tag, sign, deploy, rotate credentials, change ownership,
    427   or mutate trusted-publisher or external runtime state without explicit
    428   authorization for that exact action.