Repository navigation
docs(triage): classify all 228 open issues into seven actionable tiers - #1333
Conversation
The backlog mixes seven kinds of object under one number: a two-line script
fix, a 400-repository rollout, a question only the owner can answer, and a
tracker that exists to hold other trackers. Nothing on the list said which
was which, which is why the count feels overwhelming.
Every open issue is now in exactly one tier:
C 14 close now probes, dupes, parked, and 5 verified fixed on main
Q 61 quick fix one file or one config edit; acceptance already stated
S 61 small task single repo, half a day to a day
E 47 estate campaign mechanical but multi-repo / needs tokens
D 18 decision owner ruling blocks; most are a sentence
R 6 research the fix is not known yet
U 21 umbrella parents and epics, not work units
Two findings are worth more than the sort itself:
* Eight tier-D questions were already answered in-thread (D129, D131, D134,
D167, D171, D173, #446, #658) and were still sitting in the queue as if
they had not been. They are now work, with the ruling quoted.
* Seven "red on main" issues are green today (Actions Lockfile Gate, Lock
Sync Gate, Workflow security linter, Allowlist Preflight), and #1173's 12
baseline findings are down to 1. Those move to "close now" on evidence
gathered today, not opinion.
The companion script is dry-run by default and only ever touches tier C;
tiers Q/S/E/D/R/U are deliberately left alone, because closing work because
it is small is how a backlog becomes a lie. Tested against a gh shim, so no
test can close a real issue.
Co-authored-by: arena-agent <297053741+arena-agent@users.noreply.github.com>
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 54 minutes. View limit details
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
🟢 conformant · commit
K9 live corpus (L0–L2): 2 finding(s) / scope notes
Scope: DEED syntax and K9 contracts L0–L2. L3 signature verification and routed coordination dialects are not certified. Green is limited to this scope. Orange is missing evidence; grey is an explicit scope exclusion. Logs and report.json are in the dated conformance-evidence artifact on the linked run. |
|
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: c783401909
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| 933,All 12 Rust crates fail cargo fmt --check (pre-existing formatting debt),Q,Quick fix,"priority:p3,scope:repo,status:blocked,tech-debt",repo,p3,0,2026-09-22,2026-09-30,https://github.com/hyperpolymath/standards/issues/933,Run cargo fmt across the 12 crates and commit (mechanical; 'blocked' label is stale). | ||
| 932,validate-lint-format.sh: Rust and Nickel arms ask a different question than their tool,Q,Quick fix,"bug,priority:p1,scope:repo,status:ready",repo,p1,0,2026-09-22,2026-09-30,https://github.com/hyperpolymath/standards/issues/932,validate-lint-format.sh: make the Rust/Nickel arms ask the tool's own question. | ||
| 930,actions-lock gate's remedy text names a repo-relative path that exists in no consumer repo,Q,Quick fix,"bug,priority:p2,scope:estate,status:ready",estate,p2,0,2026-09-22,2026-09-30,https://github.com/hyperpolymath/standards/issues/930,Fix the remedy text to name a path that exists in a consumer repo. | ||
| 929,"Seed CLAUDE.md claims the estate uses GitLab and not GitHub (flag only, owner decision)",C,Close now,"priority:p1,scope:repo",repo,p1,1,2026-09-22,2026-09-30,https://github.com/hyperpolymath/standards/issues/929,Root CLAUDE.md no longer mentions GitLab; the false claim is gone. |
There was a problem hiding this comment.
Running --apply will close #929 based on checking the wrong file. The existing audit in docs/reorg/2026-10-14-tidy/issue-triage-911-1037.adoc identifies the affected seed as 9-archive/rhodium-standard-repositories/CLAUDE.md, not the root CLAUDE.md. That seed still says “GitLab (Never GitHub)” at line 135, “GitLab CI/CD (never GitHub Actions)” at line 711, and “Use GitHub (always GitLab)” at line 899. Keep this issue in a work tier until the seed is corrected or explicitly marked as obsolete guidance; otherwise the script closes an unresolved issue with an incorrect explanation.
Useful? React with 👍 / 👎.
| 674,"Scorecard's PinnedDependencies is wrong for lockfile-enforced repos — 79 alerts on _pathroot, inline pinning would break CI",D,Decision required,"bug,cicd,priority:p3,scope:estate",estate,p3,1,2026-08-27,2026-09-30,https://github.com/hyperpolymath/standards/issues/674,Policy ruling: is inline pinning required for lockfile-enforced repos (Scorecard conflict)? | ||
| 670,Dependabot bumps uses: without regenerating actions.lock — every remediated repo is newly exposed,S,Small task,"bug,cicd,priority:p3,scope:estate",estate,p3,0,2026-08-27,2026-09-30,https://github.com/hyperpolymath/standards/issues/670,Add the actions.lock regeneration step to the Dependabot workflow. | ||
| 669,"Orphaned/phantom action pins still live post-remediation: dtolnay ×35 repos (two orphaned SHAs), trufflehog ≥20, codeql-action ≥14",E,Estate campaign,"bug,cicd,priority:p1,scope:estate,status:ready",estate,p1,3,2026-08-27,2026-10-01,https://github.com/hyperpolymath/standards/issues/669,"Remove orphaned/phantom pins: dtolnay x35, trufflehog >=20, codeql-action >=14." | ||
| 668,gh search/code silently undercounts by up to 31% while reporting incomplete_results:false — adopt enumerate-then-filter as doctrine,C,Close now,"automation,priority:p2,research,scope:estate,status:ready",estate,p2,0,2026-08-27,2026-09-30,https://github.com/hyperpolymath/standards/issues/668,"Doctrine note ('enumerate-then-filter'); knowledge recorded, no repo action left." |
There was a problem hiding this comment.
Running --apply will close #668 as a knowledge-only note, but the earlier audit in docs/reorg/2026-10-14-tidy/issue-triage-633-910.adoc:240-258 records concrete acceptance work: measurement doctrine, a count-without-denominator check, and a general scripts/estate-census.sh <glob> with a test. Repository-wide path and content searches found no general census implementation or completed doctrine; the existing scripts/cicd-census.sh measures required and emitted CI checks rather than enumerating files. Merely recording the phrase “enumerate-then-filter” does not complete those deliverables. Keep this issue in a work tier, or transfer its acceptance criteria to another open issue before closing it.
Useful? React with 👍 / 👎.
What
Every one of the 228 open issues is classified into exactly one tier, with the evidence for the call written next to it:
maintodayTwo things the sort turned up
Eight questions in tier D were already answered and were still sitting in the queue as if they had not been: D129 (#1059), D131 (#941), D134 (#497), D167 (#928), D171 (#1008), D173 (#1058), plus #446 (criteria landed as #734) and #658 (ruled 2026-08-27, never written back). They are now tier S/E with the ruling quoted, because "ruled but not implemented" is work.
Seven "red on main" issues are green today. Actions Lockfile Gate, Lock Sync Gate, Workflow security linter and Allowlist Preflight all pass on
mainas of 2026-10-24 (#935, #992, #1137, #1172), and #1173's 12 baseline findings are down to 1. Those moved to "close now" on evidence gathered today rather than on the issue text.Files
docs/triage/2026-10-24-issue-classification.adoc— the classification, tier by tier, with the ordered quick-fix pass list and the sequence that actually shrinks the number.docs/triage/2026-10-24-issue-classification.csv— the same 228 rows, machine-readable (number, tier, scope, priority, note, url).scripts/triage-2026-10-24-apply.sh— dry-run by default;--applycomments the recorded reason and closes only tier C. Tiers Q/S/E/D/R/U are deliberately untouched, because closing work because it is small is how a backlog becomes a lie.scripts/tests/triage-2026-10-24-apply-test.sh— runs the script against aghshim: asserts dry-run writes nothing,--applywrites exactly the 14 tier-C issues and nothing else, and already-closed issues are skipped. No test can close a real issue.Not done (needs your word)
Nothing on GitHub was changed. The 14 closes are staged behind
--apply, and the 18 rulings are yours to make.