Preserve scoped authorization across agent handoffs

[HLLMR]

Linked issue

Closes #35

What changed

Preserve scoped Owner authorization across General and Operator handoffs without inventing new authority or repeatedly asking for the same decision.

• One shared seven-field authorization-continuity section carries approval reference, action, scope, exclusions, delegation permission, lifecycle conditions, and completion boundary.
• Generated General, Operator, compatibility, external-operation and inspect packets distinguish missing/revoked/out-of-scope authority from provider denial or an environment prerequisite.
• Legacy valid approvals remain usable without mandatory new paperwork. Task creation and additional data transmission still require applicable approval.
• Source tests, installed-wheel checks, and synchronized onboarding documentation cover the emitted contract.
• Retained public governance records report accepted evidence and qualify omitted private records. No private transactional history is included.

This updates public main through a PR; it does not change the existing immutable v0.11.0 release, create a new release, or implement issues #36–38.

Evidence

• Test-first implementation and accepted affected-suite evidence; source/static-doc checks distinguish retrospective coverage where applicable.
• Final public candidate: Windows CPython 3.12.14, 817 tests OK, 11 skipped (400.519s).
• Independent final public candidate: Ubuntu CPython 3.12.3, 817 tests OK, 4 skipped (265.706s).
• Installed-wheel coordinator gate passed on both platforms, including all generated authorization-continuity packets and unchanged candidate bytes.
• Distribution, license, projection integrity and whitespace checks pass.
• Two independent 136-file candidates have identical complete-tree ledgers: 3d92f1b9b6fe3dd262f01d31f2bd08128c028f5fe31e5cdd173a3098fce42920.
• Public index and worktree match all 136 candidate files byte-for-byte.
• Fresh distinct read-only Sonnet publication reviewer: ACCEPT; no implementation performed by that reviewer.

The accepted bounded role-play covered ten scenarios. This is behavioral evidence, not mechanical enforcement, proof of universal provider compliance, or measured reduction in Owner effort.

Retained publication diagnostics

The first test wrapper omitted the explicit test directory and ran zero tests; it was rejected and corrected. An initial build lacked source identity because of a post-reinstall Git ownership mismatch. That candidate was superseded by two rebuilt candidates with exact source provenance, and both full native gates were repeated on the corrected bytes. The reviewer withdrew an incorrect interpretation that unavailable source identity was intentional. No checker or implementation was weakened.

Local privacy screening used the documented machine-path-only profile. It does not certify optional private identifiers absent from that profile; positive allowlisting and the fresh public review remain separate controls.

Review boundary

• Only public projection files are committed.
• No new Doctrine ratification, adopter changes, provider permissions, or environment authority are implied.
• Contributor commit includes DCO sign-off.
• Complete live required CI matrix passes (pending GitHub execution).

Owner authorized opening this PR, not merging it or releasing. Issue #35 remains open until an authorized merge.