fix(reply): one spelling for the status vocabulary the two surfaces share #450
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!450
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/one-spelling-for-the-status-vocabulary"
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?
447 fixed two reaction glyphs that had drifted from Kai's approved set while
their test passed, because it asserted only that the four differed from each
other. The disclosure footer had the same precondition: I wrote it with its own
literals, so the cross existed twice with nothing relating the two.
The footer now reads the reaction constants for the hammer and the cross rather
than copying them. Drifting the surfaces apart requires editing the thing that
says what the symbol means, which is what 447 shows is worth having.
The tick and the mailbox have no reaction counterpart, so they stay defined in
the footer, as escapes for the same reason 447 escaped the reactions. That is
not special-casing the cross: every glyph in the file is now either a reference
or an escape, and none is a bare literal.
The test asserts the shared pair agree, pins the two that are the footer's own,
and keeps the all-distinct property the reaction test had rather than replacing
it. Distinctness was worth checking; it was not the property that was violated.
Mutation checked, and the first attempt was not. Substituting a perl escape
produced invalid Go, so the build failed rather than the test, which is a red
result from the wrong cause and proves nothing. The valid substitution fails the
assertion naming both spellings.
No member-visible glyph changes.
closes #448
Co-authored-by: Kai Siren coilysiren@gmail.com
Co-authored-by: Claude noreply@anthropic.com