backlog: file #1077-#1080, four findings from the cwd-is-not-the-caller round - #265
Merged
Conversation
…er round
All four surfaced while fixing #1057, #1060 and #1063 and were held unfiled under the
no-new-items directive; filed on the owner's instruction. Docs-only, so the claim gate does
not apply; all four numbers were allocated from this worktree.
#1077 announce-session.ps1 skips reachable peers on isRunning:false. MEASURED: false means
IDLE and send_message DELIVERS; true means mid-turn and it QUEUES. The field reads
backwards as reachability, so the rule drops the peers that are ready to answer. It
already cost a wrong report to the owner -- a session reported no live coordinator
while presence.ps1 listed it live throughout. Highest value of the four at 6/10.
#1078 new.ps1 prints cleanup advice that throws when followed. Run from a worktree it
anchors on $PSScriptRoot and creates the tree beside itself, then tells you to run
remove.ps1 from the MAIN checkout -- where the path does not exist. Third instance of
the #1032/#1057 class, this time in new.ps1's own output about a worktree it had just
created, so only the sentence is wrong and the anchoring is right.
#1079 security.yml's header says "NO push-to-main trigger" while its on: block carries
push: branches:[main]. No build effect. Filed because the rest of that header is
load-bearing -- it documents how continue-on-error leaves branch protection green
while discarding findings -- and one demonstrably false paragraph costs the reader
any way to know which others still hold.
#1080 setup-leak-gate.ps1 prints "Installed the SYNTHETIC template" then "CONFIGURED with
the real token set". Both true when MEFOR_FORBIDDEN_TOKENS overrides the file, but
nothing says the override happened. The script's own docstring says the verify step
exists so a green gate says what it was green ABOUT; printing counts without their
provenance leaves exactly that ambiguity.
Each carries the measurement rather than the inference, and each names its fix shape as
offered rather than decided.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Files BACKLOG #1077-#1080. Docs-only, one file, +67. Filed on the owner's direct instruction.
#1077 announce-session.ps1 SKIPS REACHABLE PEERS on isRunning:false. 6/10, P2 -- the one that
matters. MEASURED: false means IDLE and send_message DELIVERS; true means mid-turn and it
QUEUES. So the field reads BACKWARDS as a reachability signal, and the SKIP outcome is
recorded as NOT_RUNNING, which a reader takes as 'gone'. It has already cost a wrong report.
#1078 new.ps1 prints cleanup advice that THROWS when followed -- in its own output, about a
worktree it had just created. Third instance of the #1032/#1057 class: correct tool, correct
name, unrunnable as printed.
#1079 security.yml's header says 'NO push-to-main trigger'; its on: block has one.
#1080 setup-leak-gate.ps1 reports the LOADED token set as if it were what it INSTALLED.
⭐ #1080 WAS PREVIOUSLY TRIAGED AS NOT-WORTH-FILING BY THE COORDINATOR, and the item PRESERVES that
reasoning in its severity paragraph rather than discarding it. An item that records why it was once
declined is more useful than one that silently appears -- the next reader needs the argument, not just
the verdict.
VERIFICATION: allocated atomically from the committing worktree, never grepped. Based on 3d061eb
(current main), merge-tree clean. backlog_status_check: 341 items, each declaring exactly one status.
Docs-only, so the claim gate correctly does not apply.
Deliberately cut on its own branch so neither frozen PR moves: #260 stays a042c0f, #261 stays
3606532.