[zts212653]

An admitted Work could apply its date/progress write and then receive HTTP 502 because the write advanced the business revision captured by its wake notice. A real public material suggestion separately persisted but lost its receipt to the ordinary 10s transport deadline while unrelated source publications were reread. Both failures stop the consumer with an unknown outcome.

This patch keeps exact Work revisions for delivery and rechecks current assignment/execution authority during an already admitted invocation. Selected-material operations filter before owner IO and use a bounded 25s outer transport budget. Source reauthorization, CAS, operation replay, revocation, terminal-state and reassignment checks remain; unknown mutations are never retried automatically.

• Accepted source/revision: thread_mvq0gw651w05iglj#0001793064771445-000095-8a6eb884 / 0001793064771445-000095-8a6eb884 (Task3008).
• Integration base: de496d1c9c08dc4fdd4a18d5b46bec9b0de6e544 (refactor(plugins): remove duplicated API permission model #118). Preserve Contract0.3/SDK0.3-beta.1 and all existing package identities. This adds only Collective alpha.15; live catalog is unchanged.
• Client continuity: exact Core 5f055fcc907a67f015bceb84500256d8ad41e65d, 542 inputs, no overrides, assetDigest e4f49753dad6bb564d6b534d28493141d91b32cee17dae2c0982939cdb5ae7a1; no Client or shared schema changes.
• Initial Work-only review: Argon approved f6bb7e9810408d8112821746649df902a6c22b38, fact local-review:0001793093304662-001279-92d84eb8:approved. The material delta at 9165dc24d0af0c3791c175cb45de193c5530f09b is independently approved by Argon: local-review:0001793095494859-001334-1bd7d8e1:approved (0 P0/P1/P2). Its own CI 40485294344 passed at the exact HEAD; the earlier CI pass remains historical.

Validation: a production Service/Connector RED reproduces the Work self-lock. Two material REDs reproduce unrelated owner reads and a committed mutation losing its receipt. Targeted 30/30, lifecycle6/control59/transport3, Business416 in98 files, build/typecheck, source continuity4/4, pinned catalog60/60 and fresh installed dependency closure1/1 pass. Production Service/Connector are real; Host identity/Task ports, scaled latency and SDK consumer are controlled fixtures, not actual installed acceptance. Evidence: docs/evidence/f290-work-wake-time-receipts.md; logs /tmp/f290-work-wake-material-delta-*.log and /tmp/f290-project-source-focused-red.log.

Canonical unpublished alpha.15: 4,762,702 bytes; SHA1 716448a883ee350269b09b5f7a7d63483b00819e; SHA256 5044d0946e89d7607458852d9554d921d3a707d720d8a5bb37259b6a4a342d25; SRI sha512-dYs3Bs4q8e0MJQHK4WzL+3cRAQRC+pvdIN7EReUV9boA/VdSF/U9Y2V9SN6eMAIZrVaScUFNAcPunhj21Ik3lw==. Built with repository-pinned Node24.18.0/npm11.16.0. The earlier f6bb candidate/artifact remains archived and is not the release identity.

The original Alpha/Task/Source Service and installed instances remain intact. Core #6236 is merged as 8b989adb0c8260a8a99225ee985b8ce8fd4105d8; its original owner has released the full Host0.3 intake with Contract0.3.0/SDK0.3.0-beta.1 and paired GitHub Operations alpha.29. There is no prior catalog writer reservation or cohort-activation dependency on that owner. This Task publishes/activates its own Collective forward patch; it does not authorize activating the unrelated #118 cohort. After immutable publication, the same Alpha must load the paired Host and final package and repeat private/public native receipts plus recovery. Task3008 remains open; no real meeting/PhaseD, human visual acceptance, production deployment or parent Task mutation is claimed.

Risk: behavior = two persisted mutations losing their native receipt; data = retain original durable command records with no migration or automatic replay; security = unchanged live source/assignment/execution authorization; contract = no public schema or Host port change; irreversible = new immutable prerelease only after independent review and full native CI, followed by a separately reviewed own-plugin live catalog change.

[zts212653]

Merge gate PASS for exact 9165dc24d0af0c3791c175cb45de193c5530f09b on frozen base de496d1c9c08dc4fdd4a18d5b46bec9b0de6e544.

• Non-author Argon typed approved: local-review:0001793095494859-001334-1bd7d8e1:approved, exact head/subject/immutable accepted source revision verified. Earlier Work-only approval remains historical.
• Full repository-native CI 40485294344 passed; local 30 targeted, 416 Business/98 files, lifecycle6/control59/transport3, installed1, source4 and pinned catalog60 passed. Diff check and clean source tree verified.
• Canonical candidate SHA256 5044d0946e89d7607458852d9554d921d3a707d720d8a5bb37259b6a4a342d25; official registry alpha.15 was still404 before merge. Client unchanged5f055/e4f497/542 inputs.
• headChangeCause=pr-meta, nextGateOwner=author, stale=false, gate_passed=true. Source remains child095; no report commits were added after review.
• Host #6236 intake terminal is independently verified; its owner explicitly holds no prior cohort catalog writer. The earlier assumed wait was removed. This Task does not activate unrelated candidates.
• Same Alpha installed acceptance and restart recovery remain outstanding. Its old node_modules were corrected by frozen-lockfile install; the separate managed-preview cleanup proof failure is being routed to its verified existing owner. No new package has been installed there, so it does not arise from this candidate.

[小太阳·砚砚/gpt-6.1-sol🐾]