fred
dc6b593c1e
ci/woodpecker/pr/ci Pipeline was successful
Two assertions in packages/mosaic/src/mutator-gate/runtime_tools_unittest.py pinned the behaviour D29 identifies as the defect: an envless revoke-lease.py returning rc=2. They are changed here under the test-is-the-defect exemption, stated on the record rather than made quietly. One new assertion is added to cover what the relaxation must NOT reach. Why the reclassification is justified. Not because the old pin was careless: it was deliberate entrypoint doctrine, born ine4d7d45(WI-3, #842) alongside the tool itself, and its twin pins the identical property for mutator-gate. Two measurements beat the doctrine. 1. Unsatisfiable precondition. The doctrine's only reachable firing point cannot be reached by the live fleet. Seats launch with zero MOSAIC_LEASE_* (measured, pane pid 8596; 19 of 19 live panes, see #1340), the framework ships no provisioning path for fleet launches, and the deployed extension does not enforce the total gate, since live seats use tools daily. 2. Gate-enforced redundancy. For the one case the doctrine protects, a leased session whose identity env is stripped: the strip must occur in the extension host's own env to reach the observer, at which point the gate also loses identity and denies GATE_UNAVAILABLE rc=2 on every tool call (measured). The stripped session may compact but cannot mutate. Pre-fix it merely died at compaction instead. No mutation path opens either way. The no-ungated-mutation property lives in the gate, not the revoker. That is why the revoker moves and the gate does not. Changes: 1. test_revoker_entrypoint_denies_when_identity_environment_is_absent becomes test_revoker_entrypoint_noops_when_identity_environment_is_absent and asserts rc=0. The stem is kept so history greps still find it. 2. NEW: test_revoker_entrypoint_denies_when_identity_environment_is_half_provisioned asserts rc=2 for socket-only and session-only environments. The no-op is reachable only on TOTAL absence; half-provisioned is a machinery-present failure and must still fail closed. main() already pinned this, but the entrypoint did not, and the entrypoint is what the runtime extension spawns. 3. In test_revoker_fails_closed_on_identity_reply_and_transport_errors, ONLY the ({}, ...) element leaves the cases list. The five machinery-present cases (malformed session id, ok:false, state:VERIFIED, OSError, JSONDecodeError) stay fail-closed and are untouched. 4. test_gate_entrypoint_denies_when_identity_environment_is_absent is left UNCHANGED, with a comment recording why. Relaxing it the same way would be a real downgrade. The revoker/gate asymmetry is intentional and must not be "fixed" later. Controls run, all three directions, none assumed: - Fix plus amendments: 26/26 OK, rc=0. - revoke-lease.py alone reverted to origin/next, amendments kept: FAILED (failures=1), rc=1. The amended entrypoint assertion still bites. - Guard weakened to `len(present) < 2` so half-provisioned falls through to the no-op: FAILED (failures=1), rc=1. The new assertion bites. Required by two independent re-verdicts, both REQUEST_CHANGES on head9fed3838, both of which superseded their own earlier APPROVE after CI surfaced the pinned contract: rev-security-01 review id 242, rev-security-02 review id 243. Each was asked to refute the reclassification before accepting it and each attempted it in writing. Item 2 above is rev-security-02's requirement and was not in the first re-verdict. Both re-affirm the guard's own semantics as correct; what was missing was the second half of a deliberate contract change. Refs #1338, #1340