Bind prescriptions to exact state and program revisions

[bigboateng]

Summary

• bind every prescription to the durable state revision, executable program fingerprint, and canonical snapshot observed during resolution
• revalidate the binding under the repository lock before journaling or effects
• advance every accepted native, program, extension, and recovery transition exactly once and record both revisions in its receipt
• reject stale or unbound apply and recover requests without managed effects

Boundary

Boundary: resolution to effect execution.

Control law: a prescription may commit only against the exact durable state revision and executable Control Program observed during resolution. A mismatch fails closed and requires re-resolution.

Verification

• 27 Python repository-contract tests
• 164 Go tests across 10 isolated shards
• full Go race suite
• go vet ./...
• go build ./...
• release-note validation and committed-diff preflight
• git diff --check

Release note

Added release-notes/2026-08-12-prescription-transaction-boundary.md.