Loading…
Reference in a new issue
No description provided.
Delete branch "cue/2875-gatorwalk-factory-small"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Small driving fixes from the gatorwalk dogfood run on swamp-club #2711 (swamp-club #2875).
Changes
post_attestationnames the attestation id. The swamp-club adapter now logs "posted the attestation for<commit>as<id>", and on an exact repeat "already posted for<commit>as<id>; posted nothing". Before, the id was only in the stored record. swamp-club model2026.10.01.3.evidence-recordedgates onclassification) used to print the same failure twice.gates.tsnow drops exact repeats inevaluateTransitionsandmakeGateEvaluator, sostatus,advance's refusal, saved scenarios and the studio show the line once. An exit still keeps one check per gate. Work-item model2026.10.01.1; studio bundle rebuilt.onBehalfOfonapprove,decline,grant_override,advance,resetandretargetsince #2793, but the skill only showed it for evidence a person records. SKILL.md rule 4, driving.md and the build-swamp-extension worked example now pass it on every decision made on a person's word. An advance the driver takes on its own names no one.Left out (agreed in triage)
statusis fixed in swamp itself (swamp #2764), which shipped after the swamp build used for the dogfood run.initcopying scenarios: there is noinitsince #2884.Testing
gates_test(one failure from two identical gates, on both paths) andswamp_club_test(the id appears in both messages).tracker_testchecks the id in the CLI output, andskill_testchecks the newonBehalfOfflags against the method schemas.🤖 Generated with Claude Code