Stage Post-Core native mail and scoped Yuan/Wake control

[WQMYH]

This stage adds explicit native mail receiver notifications, native-local Codex creation through Yuan, and scoped QoderWake Session control. Yuan selections remain independent: mismatched sends cannot consume another selection, and new selections are refused at the 256-entry limit. Unknown dispatches retain protection against replay.

Distribution uses portable paths and synthetic fixture identifiers, excluding private plans, runtime configuration, transcripts and native evidence. Offline CI discovers Chat read/inventory/events and companion expiry checks, copies the current Qoder dependencies into fixtures, and completes MCP initialization before Mailboard requests.

Windows CI corrections preserve production identity and notification guards: fixtures use canonical temporary paths with matching cleanup bounds; the test-only observer has a five-second SQLite busy timeout. The real OS identity query has one ten-second deadline, retaining its command, output cap, validation and fail-closed handling, without retry or identity fallback. One query can wait up to five seconds longer; serial Kimi scans of N instances can add up to 5N seconds.

The runner executes 59 test entries and four builds once. Standalone npm run smoke retains its nine suites and original manifest/public-MCP assertions, extracted into public-mcp.test.mjs; manifest validation runs after the nine suites. Native-turn retains all assertions with a 300-second limit; other entries retain 180 seconds within a 20-minute CI job.

Validation: affected local checks, receiver 23/23, real-OS identity checks, extracted MCP assertions, and complete standalone smoke passed. Independent reviews accepted each bounded correction. Local source and Core/mail archives match the current commit byte-for-byte and passed privacy scans. Native acceptance remains scoped in docs/compatibility.md.

Exact head 8432f5e6ebad21d68c0a9836160f227988e7f6a8: push CI and PR CI both completed successfully with 63/63 offline checks and zero failures. Previous failing runs remain in history; their results are not claimed as passes.

This draft covers the frozen stage and accepted corrections. Later cloud-control work and Wake reader development are outside this candidate. Main merge, version tags, release assets and installation remain separate decisions.