Preserve repository authority across recovery

[bigboateng]

Summary

• retain requested repository-policy authority across installation, configuration, and recovery receipts
• re-materialize repository authority once from exact verified configuration evidence before re-resolution
• keep Update installation-scoped and regenerate identical Autoplan, Run, and Update projections for all interactive hosts

Boundary conformance

• Boundary: generated operation driver to the V2 resolver/effect boundary
• Control law: selected delivery operations may retain requested authority sources, but repository-policy receipts are derived only from verified configuration and no operation gains provider, publication, or merge authority
• Positive: detached initialization continues through engagement.begin to plan.create in one command context
• Negative: unverifiable configuration rejects repository authority without repository mutation
• Relation: static contracts inventory status, next, apply, recover, re-materialization, re-resolution, and terminal stopping

Verification

• release-note validation and preflight
• 26 Python repository-contract tests
• complete sharded Go suite (100 tests)
• go test -race ./...
• go vet ./...
• go build ./...
• git diff --check

Release note: release-notes/2026-08-11-preserve-repository-authority-context.md