# Publishing Desk independent reproduction result

Run date: September 20, 2026
Tested bundle SHA-256: `2aa7e9de9d8cdb725937d1dc81b66a252c2085b9febc0dd65241e26bccf9539b`
Locked source SHA-256: `ba8faf8619afebe2077c570608565ea1f94cf34e967edbd3d1560dcf10ed4cca`
Writer archive: version 2.0.5, SHA-256 `550c3182a5b6e0d20c8e418464f299921d05e65b8b795590de6bf0282258e8a5`
Editor archive: version 2.0.3, SHA-256 `5cf5ac1d11b406df726894260d3cdb94b85abeda8650e6b5800552d2550f4975`
Tools: none
Human approval: not given

Scout, Researcher, Story, Writer and Editor completed an independent second run against the same locked fictional Tool Library packet and the same package fingerprints as the earlier successful fixture. The deterministic Writer and Editor gates initially returned zero structural issues. Editor audited all 21 newsletter and four social boundaries and retained the required human-review hold.

Independent semantic review then rejected the social phrase `catalog URL coming`. The approved source says only that the catalog URL had not been supplied. It does not establish that a URL will be supplied later. The second run therefore **did not reproduce the earlier semantic pass**.

The preserved failure produced a concrete gate improvement: a supported claim is now rejected when it turns a cited statement that information is missing into an unsupported promise or reader direction. A separate exact source passage can still support that promise or direction explicitly. Replaying this independent output through the revised gate rejects it with the issue `assertion projects a promise or reader direction from missing information`.

Bot Cabinet therefore continues to report **Runtime passed once**, not **Reproduced**. The guard fixes this observed failure class; it does not establish general semantic verification or crew reliability.
