Repository navigation
Changes
- Safer consequential replay: Action Safety 1.8 explicitly distinguishes unknown post-dispatch outcomes from known-no-effect failures. Reconcile the same operation's completion evidence or an existing checked idempotent replay contract before replaying; preserve completed effects and all existing approval, retry-budget and provider-wait gates.
- Bounded evidence before parsing: Safe I/O 1.10 adds input-byte, individual-record and retained-result bounds before decoding/parsing/materialization, including decoded expansion and fixed watermarks for growing logs. Output truncation and record counts alone are not memory bounds; ordinary small exact reads remain direct.
- Keep the same 19 substantive Runtime Rules. Align owner designs/history, runtime inventory, verification guidance and virtual Cases 02/04 with M46–M53. No Product state machine, writer/probe/recovery path, resource policy or new runner is added.
Verification
- Focused written contracts: baseline four missing-clause failures/two existing-chain passes, final six passes.
- Complete repository Node test owners: 38/38 passed.
- Native Bash and PowerShell installer fixture suites passed on Linux.
- Actual selected Runtime installation: ordered 19-file byte/mode/body/ownership-manifest parity passed; other 17 Runtime files and protected other-owner entries were preserved.
- Independent full-nineteen before/candidate reader packets conformed to all 12 selected synthetic scenarios. Both already produced the expected decisions; this demonstrates the explicit contract and preserved allowed branches, not causal model improvement or real operational safety.
- Source commit:
87c5ef3462d04de5be70fd941d8263c7548cff67. Annotated tag object:afc3b0dbe7e8cc5b7ce106c7876750cb158a5e5d. Source and tag were published atomically without force.
Fresh-public tag commit/tree identity, all 21 selected path SHA256/Git modes and isolated exact Main19 installation/body/ownership-manifest/exclusion checks passed after publication; the tagged pre-publication record remains immutable. User-scope managed Skills are outside this repository's Runtime/release payload. No Windows OS, active-session reload, stability, historical incident repair, whole-project convergence or model-benefit claim.