feat: OACP v0.4.6

[kiloloop-release]

Promotes v0.4.6 from staging. Merging this and pushing the v0.4.6 tag triggers the PyPI publish and the GitHub Release.

What's in this release

Added

• Autonomy audits distinguish expected pauses from unplanned pauses.
• Human outcome records can retain the changes made when approving a modified task.

Fixed

• Startup safety and dispatch guidance follow the current exact-file archive lifecycle.
• Startup guidance preserves project memory reads and retrieves org memory on demand.

Full detail in CHANGELOG.md.

Contract version: no change — spec_version stays 0.4.5. The release adds one optional advisory field to the sender task profile (expected_pauses) and optional audit evidence (pause_classification, expected_pause_codes, unplanned_pause_codes, human_outcome.modification). All of it is additive and ignorable within audit schema v2: existing records validate unchanged, and a reader may skip the new fields without changing an admission, finalization, doctor, or enforcement decision. No required field was added and no existing field changed meaning.

Verification

Byte-identical promote. The staged tree hash equals the staging repo's tree hash:

source (staging HEAD^{tree}):  53ec5c41ff2b18c62e5694672a06a864df9c5168
target (this commit's tree):   53ec5c41ff2b18c62e5694672a06a864df9c5168

Delta: 36 files, +1,009 / −56. The deletion sweep came back empty, so nothing needed explicit removal; the tree hash, not the diffstat, is the proof.

Pre-public audit on the staged tree:

Check	Result
Hardcoded paths	0
Personal identifiers	0
Internal roadmap jargon	0
Secrets	0
Bare issue refs in added lines	0 — 977 added lines scanned
SPDX headers	90/90 .py files

Build validated on the staging tree (uv build), executed rather than inspected:

• Metadata-Version: 2.5, which the pinned publish action's packaging==26.2 accepts — the compatibility axis that failed in v0.4.3 was checked before the first push, not after a red gate.
• The wheel carries 7 entries under oacp/_protocol/ (6 protocol documents plus dispatch_states.yaml), all 38 oacp/_scripts/ force-include entries, and the packaged agent_status template.
• oacp/guides/memory-context.md now ships (3,892 B), and every ../guides/ link in the shipped protocol documents resolves inside the wheel — 2 links checked, 0 dangling. That link target is the reason the guide is packaged.
• The source distribution's own test suite, run from inside an extraction of the built artifact: 1688 passed, 7 subtests.