What
The guard that blocks a publish based on a stale document version can now let the publish through. If the model already observed the live version, the publish adopts that version as its base rather than failing with a "publish again in your next turn" style refusal.
Details
- The guard result gained a
proceedWithfield carrying the live version, returned with no refusal text plus a replay record. - Telemetry labels this path
proceed_own_version, distinguishing it from the seeded-refusal path. - The proceed branch also depends on two further checks in the same condition whose meaning is not resolved in this build.
Evidence
mode: c("proceed_own_version")
Strings lifted out of the shipped bundle, so the claim above can be checked against them.