build: ship the access check, which merged without its build line #646
No reviewers
Labels
No labels
move-to-repo
coilyco-bridge-deploy
move-to-repo
coilyco-flight-deck-agent-compose
move-to-repo
coilyco-gaming-eco-app
move-to-repo
coilysiren-inbox
move-to-repo
unknown
🔒⚠️📦⚠️🔒 SANDBOXED 🔒⚠️📦⚠️🔒
autonomy
async-consult
autonomy
epic
autonomy
headless
autonomy
live-collab
c#
priority
P0
priority
P1
priority
P2
priority
P3
priority
P4
role/ai
role/creator
role/design
role/director
role/engineer
role/exec
role/human
role/ops
role/qa
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
coilyco-gaming/sirens-echo!646
Loading…
Reference in a new issue
No description provided.
Delete branch "build/ship-the-access-check-claude"
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?
closes #644
cmd/sirens-echo-access-checkis onmain. TheDockerfiledoes not build it:The binary exists in source, has tests, and cannot be invoked by the only caller it was written for. Deploy's CI runs against the released image, which is the entire reason #628 asked for it.
What happened
I checked reachability before opening #628's pull request, found the binary was not built, and fixed it in a second commit on the same branch. The pull request merged at the first commit. The command landed and the build line did not.
Same shape as #563 and #609 — a merge capturing a branch state that has moved — and the same mechanism as #568.
Why I filed an issue rather than pushing quietly
This is the defect the tool was written to prevent, in the tool itself. #628 exists because a bad access policy is only caught after it goes live; its fix shipped in a state where it cannot run.
It is also the fourth instance today of the class in #618, and the only one I introduced after writing #592, which names it. I checked the property once and did not check that the check survived.
Checking a property once is not the same as the property holding.
Two lines: built beside the other commands, copied into the runtime image rather than only the build stage.
ward exec gategreen.