Repository navigation
chore(tooling): delete comments from the verifier, tests and repository config (#218) - #220
Conversation
…ry config (#218) Applies the AGENTS.md no-comments rule to the repository's own tooling: the verify-open-pstack scripts and recipes, tests/*.sh, .gitignore, .mergify.yml and the Windows hooks workflow. Comments that state a Claude Code, Codex, Git, GitHub or Linux fact stay. freshRoot's "EEXIST rejects reuse and symlinks" comment becomes a test. tests/setup-config-home-repro.sh is registered as nonRuntime so a change to it classifies instead of failing closed. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Merge Protections🔴 1 of 2 protections blocking · waiting on 🙋 you
🔴 🚦 Auto-queueWaiting for
This rule is failing.When all merge protections are satisfied and these conditions match, this pull request will be queued automatically.
Show 1 satisfied protection🟢 Queue ready pull requestsAutomatically queue non-draft pull requests targeting main after verify, Unfret, and live-gate pass on the head and every review thread is resolved.
|
Live evidence: Open Pstack
|
|
[Low impact] The PR appears safe to merge; no actionable defects were found. SummaryRemoves comments from repository-owned tooling and configuration.
Scope acknowledged by Reviews (1) · Last reviewed commit: "chore(tooling): delete comments from the..." · Reviewed by Greptile |
✅ No blocking findingsWalkthroughThis PR applies the repository's no-comments rule to its own tooling. It deletes roughly 160 comments from the verify-open-pstack skill's recipes, scripts and tests, from the collision repro shell script, and from the Windows hooks workflow,
Since the last review
Details
Reviewed the whole pull request. @unfret review · @unfret status · @unfret help |
There was a problem hiding this comment.
🛑 1 blocking finding
🔴 High · Executable setup repro is incorrectly exempted from live verification
Check
… sweep (#218) Registering tests/setup-config-home-repro.sh as nonRuntime would let a change to it publish live-gate success without exercising it. The script stays unmapped, so a change to it still fails classification closed, and its comment stays until its ownership is mapped. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Live evidence: Open Pstack
|
|
Queued — the merge queue status continues in this comment ↓. |
|
@Mergifyio refresh |
✅ Pull request refreshed |
|
@Mergifyio queue |
Merge Queue Status
This pull request spent 2 minutes 5 seconds in the queue, including 1 minute 14 seconds running CI. Required conditions to merge
|
Live evidence: Open Pstack
|
Part of #218. Applies the
AGENTS.mdno-comments rule (#219) to the repository's own tooling.Summary
Every file here is authored by this repository: none exists in Cursor's pstack at the sync commit. 11 comments stay because each states a Claude Code, Codex, Git, GitHub or Linux fact. Examples: Codex
workspace-writeblocks network access, aclaude -pstream-json replay carries the slash command, Linux mtimes are coarser thanDate.now(), and the# v7.0.1tag pin.One edit is not a deletion.
freshRoot's comment "EEXIST deliberately rejects reuse and symlinks" stated a constraint that nothing enforced, so it is now a test. The test fails whenmkdirgetsrecursive: true.tests/setup-config-home-repro.shis left out.features/registry.jsonmaps no owner for it, so any change to it fails classification closed. The follow-up issue records it.The module docstrings of
scripts/upstream-merge.pyandscripts/upstream-merge-probe.pystay. They are each script's only usage text, which is the CLI's contract.Evidence
#comments dropped. Result on292659d: 22 filescomment-only, 1CODE-CHANGED(io.test.ts, the new test), 1NOT-CODE(registry.json).220d24areturnsregistry.jsonandtests/setup-config-home-repro.shto main's content.mkdir(root, { recursive: true, mode: 0o700 })infreshRoot, the new test fails (11 pass, 1 fail). With the real code it passes.Live gate features: this PR changes the verifier, so it runs from this head with
--self-test.claude:project-skill: the installed candidate discovers this skill and runsverify.sh doctor --candidatethrough it. Classification addscodex:project-skill.Merge Danger
Door: two-way
Blast Radius: tooling
The code paths are unchanged, except for one added test and one registry entry.
.github/workflows/windows-hooks.ymlchanges, so Mergify does not queue this PR automatically. The operator queues it after the plugin sweep merges.Acceptance criteria
UPSTREAM.md,CHANGES.mdandNOTICE.mdidentify as local adaptations or additions." Verified: every changed path is outsideplugins/pstack/, and upstream is onlypstack/.verifyand the other required checks." Verified locally below. CIverify, Unfret andlive-gatereport on this PR.Gate results
On head
220d24a:bun run test(501 tests)bun run typecheckbun run static(167 tests)publisher request boundaries > a manifest is version-only …hit Bun's 5000 ms default timeout at a load average of 565claude plugin validate plugins/pstackbun run typecheckin.claude/skills/verify-open-pstackThat test changed only in comments, and it passes alone (5.84 s). On
292659dall five checks exited 0.Review rounds
292659d(full panel): one blocking finding. Registeringtests/setup-config-home-repro.shasnonRuntimewould let a change to that script publishlive-gatesuccess without exercising it. Class:verdict-changing(gate integrity). Fix in220d24a: drop the registry entry and leave the script out of the sweep.Not verified
catalog.test.ts,runner.test.tsandreflect.test.tscover them.🤖 Generated with Claude Code