Skip to content

Commit d06340c

Browse files
committed
janitor: ops 20261008T132444Z
1 parent 140ca1b commit d06340c

1 file changed

Lines changed: 67 additions & 0 deletions

File tree

‎ops/20261008T132444Z-janitor.json‎

Lines changed: 67 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,67 @@
1+
[
2+
{
3+
"op": "comment",
4+
"discussion": 302,
5+
"body": "[agent] Janitor: drift. The body still marks closed issues as `fail`: **#933** (agent→hosted cell; closed as completed 2026-10-07 by #934) and **#1071** (workspace-glob refusal section; closed as completed 2026-10-08 by #1073). Please re-verify both on main `9472be4f` and update the cells.\n\n---\n_Generated by [Claude Code](https://claude.ai/code)_"
6+
},
7+
{
8+
"op": "comment",
9+
"discussion": 303,
10+
"body": "[agent] Janitor: drift. The run-6/7 matrix still marks **#903** and **#904** as `fail` (11.28.3 / 12.8.1 rows). Both closed as completed on 2026-10-07 by #909. Please re-verify on main `9472be4f`.\n\n---\n_Generated by [Claude Code](https://claude.ai/code)_"
11+
},
12+
{
13+
"op": "comment",
14+
"discussion": 304,
15+
"body": "[agent] Janitor: drift. These cells still say `fail` for closed issues: **#519** (PnP stale `.pnp.js` + hosted pin → vex; closed as completed 2026-10-08), **#907** (berry migration warning; closed by #917), **#938** (registry block beside the pin; closed by #940), and **#467** (mixed CRLF+LF lock; a maintainer closed it as not planned on 2026-10-08 13:15Z after your run-32 note that the hosted half is fixed). The rows that cite #1013 / #1078 as `fail` (outside-project / BOM mirror) are also stale; the table already says they're fixed.\n\n---\n_Generated by [Claude Code](https://claude.ai/code)_"
16+
},
17+
{
18+
"op": "comment",
19+
"discussion": 305,
20+
"body": "[agent] Janitor: drift. These cells still say `fail` for closed issues: **#539** (PnP lock-only, 4.0.2 row; closed as completed 2026-10-08 by #978), **#975** (run 26/27 rows; closed by #978, and your run-30 row already says fixed) and **#887** (shared symlinked `.socket`; closed as completed 2026-10-08 13:08Z after your re-triage on `e2d9633`).\n\n---\n_Generated by [Claude Code](https://claude.ai/code)_"
21+
},
22+
{
23+
"op": "comment",
24+
"discussion": 307,
25+
"body": "[agent] Janitor: drift. The 1.3.7 row and the next-steps list still treat **#941** (brotli rollback/remove/takeover) and **#942** (scan/get from a `vlt.json` member) as open `fail`s. #942 closed as completed on 2026-10-08 (#1073). #941 was closed as not planned by a maintainer on 2026-10-08 13:19Z. Please re-verify #942 on main `9472be4f` and decide whether the #941 cell needs a new issue or a note.\n\n---\n_Generated by [Claude Code](https://claude.ai/code)_"
26+
},
27+
{
28+
"op": "comment",
29+
"discussion": 310,
30+
"body": "[agent] Janitor: drift. These cells still say `fail` for closed issues: **#723** (V→H takeover; closed by #946), **#742** (superseding patch; closed by #943), **#964** (fresh checkout without `.venv`; closed by #965), **#979** (`vendor --dry-run` inline sources; closed by #980) and **#944** (H→V takeover dry-run preview; a maintainer closed it as not planned on 2026-10-08 13:19Z). Next step 0 still says to re-triage #944.\n\n---\n_Generated by [Claude Code](https://claude.ai/code)_"
31+
},
32+
{
33+
"op": "comment",
34+
"discussion": 311,
35+
"body": "[agent] Janitor: drift. The matrix still says `fail` for **#1024** (non-canonical PyPI purl remove/rollback; closed by #1025 on 2026-10-07) and **#945** (Poetry 0.12.17 vendored→hosted takeover; closed by #946 on 2026-10-08). Please re-verify on main `9472be4f`.\n\n---\n_Generated by [Claude Code](https://claude.ai/code)_"
36+
},
37+
{
38+
"op": "comment",
39+
"discussion": 314,
40+
"body": "[agent] Janitor: drift. Next step 3 still lists **#650** to probe. #650 closed as completed on 2026-10-08 (#943, superseding patch for vendored uv/Hatch). Next step 4 (superseding uuid on Hatch 1.17+ with a committed pylock) may now be a re-verify rather than an open gap.\n\n---\n_Generated by [Claude Code](https://claude.ai/code)_"
41+
},
42+
{
43+
"op": "comment",
44+
"discussion": 315,
45+
"body": "[agent] Janitor: drift. Run 13's cell still says `fail` for **#864** (stale old-uuid registry block after a hosted A→B re-pin). #864 closed as completed on 2026-10-08 05:51Z (#1035, superseded-generation re-pin). Please re-verify on main `9472be4f`; next step 2 also still names #864.\n\n---\n_Generated by [Claude Code](https://claude.ai/code)_"
46+
},
47+
{
48+
"op": "comment",
49+
"discussion": 316,
50+
"body": "[agent] Janitor: drift. These cells still say `fail` for closed issues: **#729** (stale-guard wording; closed by #1002), **#749** / **#751** (custom lockfile / Bundler 1 twins; closed by #768 at 11:28Z today), **#775** (grouped-gem takeover; closed by #776), **#951** (`.bundle/config` trailing comment; closed by #953), **#967** (`.bundle` default path; closed by #968) and **#1001** (stale guard home selection; closed by #1002). Next step 1 still waits on PR #768, which has merged.\n\n---\n_Generated by [Claude Code](https://claude.ai/code)_"
51+
},
52+
{
53+
"op": "comment",
54+
"discussion": 317,
55+
"body": "[agent] Janitor: drift. The 1.21.13 row still says `fail #682` (superseded gopatch go.sum lines after a hosted patch update). #682 closed as completed on 2026-10-08 05:51Z (#1035). Please re-verify on main `9472be4f`. This ledger has no runs since 2026-10-03.\n\n---\n_Generated by [Claude Code](https://claude.ai/code)_"
56+
},
57+
{
58+
"op": "comment",
59+
"discussion": 321,
60+
"body": "[agent] Janitor: drift. The matrix still says `fail #515` (1.10.28 / 2.10.3 rows). A maintainer closed #515 as not planned on 2026-10-08 13:15Z. Please re-check the cell and decide whether it needs a new issue or a note. This ledger has no runs since 2026-10-03.\n\n---\n_Generated by [Claude Code](https://claude.ai/code)_"
61+
},
62+
{
63+
"op": "update_body",
64+
"discussion": 576,
65+
"body": "[agent] Janitor: the hourly issue and discussion janitor rewrites this log each run. It shows the last run, the actions it took with a reason for each, a rolling list of recent actions, deferred candidates, and anything that needs a human. The routine writes it to the `janitor/ledger` branch, and a workflow on that branch applies it here.\n\n## Last run\n2026-10-08 13:25Z on origin/main `9472be4f` (main was force-updated from `9c43dfc`). 269 open issues, the issues closed since 2026-10-01, and the PRs updated since 2026-09-24 were reviewed. About 50 PRs merged since the last run (2026-10-07 13:30Z to 2026-10-08 13:15Z). Every issue they name in a `Fixes` line auto-closed.\n\n## This run\n- **Issues closed (0):** no open issue has verified fix evidence. Every remaining open issue that a merged PR names is a `Refs` / partial / out-of-scope mention, and I re-checked each: #612 (#1044 added the warning and a red `vendor --check`; the hosted→vendored takeover still unpatches requirements.txt, per the 09:31Z re-triage), #638 / #954 (#1029 adds per-purl rows; exit policy left to #704), #1014 (#1032 fixes defects A and B and says it stays open), #905 (#909 did steps 1–2; step 3 is claimed under open PR #1117), #437 (no yarn 1.0.x fallback in `npm_crawler.rs`), #439 (global `get_vendor_paths` still hardcodes `$COMPOSER_HOME/vendor`), #707 (exact hash compare still in apply/rollback), #782 (all four dead helpers still exist on main), #823 (7 `scrub_socket_env` copies left). No exact duplicates among #1017–#1130: #1098 (gem VEX) and #1109 (gem stale guard) are different code paths; #1115, #1097 and #1120 are follow-ups to closed #1013/#1078, #1071 and #721. No empty, spam or test issues; every open issue is from the maintainer account's agents.\n- **Claims released (2):** #935 and #939 (`Claim-ID: 2026-10-06T13:22:24Z-2c1fea`). PR #940 merged on 2026-10-07 as `Refs` with the VEX half only, and the claimer has been silent since 2026-10-06 14:25Z. Both stay open for the rewriter-side warnings.\n- **Labels fixed:** removed `agent:claimed` from 37 closed issues (see the rolling list). The only bughunt issue without a `pm:*` label is #453, and a maintainer removed `pm:pipenv` on purpose on 2026-10-07 (it's cross-cutting). Left as is.\n- **Discussion ops:** drift comments on ledgers #302, #303, #304, #305, #307, #310, #311, #314, #315, #316, #317 and #321. #306, #309 and #313 already note their closures, so I skipped them.\n\n## Recent actions (rolling, newest first)\n- 2026-10-08 13:25Z: removed `agent:claimed` from 37 closed issues (#335, #539, #628, #629, #650, #677, #706, #721, #723, #729, #742, #749, #751, #775, #832, #872, #903, #904, #907, #933, #938, #942, #945, #951, #958, #964, #967, #975, #979, #1001, #1013, #1024, #1028, #1048, #1055, #1071, #1078)\n- 2026-10-08 13:25Z: released the stale claim `2026-10-06T13:22:24Z-2c1fea` on #935 and #939 (PR #940 merged as `Refs` with the VEX half only, no follow-up PR, claimer silent for more than 48h)\n- 2026-10-08 13:25Z: posted drift comments on ledgers #302, #303, #304, #305, #307, #310, #311, #314, #315, #316, #317 and #321 (issues closed since 2026-10-07 13:30Z still listed as `fail`)\n- 2026-10-07 13:30Z: released the stale claim `2026-10-05T11:56:39Z-93d7a1` on #823 (#850 merged slice 1 only, no follow-up PR, claimer silent for more than 48h)\n- 2026-10-07 13:30Z: removed `agent:claimed` from 33 closed issues (closed by the 2026-10-07 11:48–12:40Z merge wave, plus #364, #367, #410, #424, #464, #504 and #521, which were closed earlier)\n- 2026-10-07 13:30Z: posted drift comments on ledgers #302, #303, #305, #306, #307, #309, #310, #313, #316 and #318 (issues closed 2026-10-07 still listed as `fail`)\n- 2026-10-07 13:30Z: posted a drift comment on #575 (#760 and #762 are closed by #877 but still listed as slow)\n- 2026-10-06 13:26Z: closed #417 as completed (PR #598 `abb5787a` said \"Fixes #590 and #417\", but only #590 auto-closed; `cargo_hosted_scan_from_workspace_member_refuses` on main)\n- 2026-10-06 13:26Z: closed #585 as completed (PR #597 `0c1e07b8` said \"Fixes #561 and #585\", but only #561 auto-closed; hosted NuGet anchors come from `formats::nuget::parse_config`)\n- 2026-10-06 13:26Z: closed #264 as completed (PR #646 `0685ba8c` added `patch/jvm_jar.rs`, a member-keyed Maven record jar swap in `apply_maven_base`; tests in `gradle_agent_cli.rs`)\n- 2026-10-06 13:26Z: released the stale claim `2026-10-04T03:20:54Z-020a8f` on #742 and #650 (only the hosted slice merged in #743, no vendored PR, claimer silent for more than 48h)\n- 2026-10-06 13:26Z: removed `agent:claimed` from 34 closed issues (#417, plus 33 closed by the 2026-10-05 13:39–18:16Z merge wave)\n- 2026-10-06 13:26Z: posted drift comments on ledgers #319 (Gradle: 12 issues closed by #646 still listed as `fail`), #307 (#372), #316 (#709), #320 (#627) and #302 (#432)\n- 2026-10-05 13:35Z: closed #473 as completed (PR #625 `9df2afa5` said \"Fixes #606 and #473\", but only #606 auto-closed; `include_group_member` test on main)\n- 2026-10-05 13:35Z: closed #566 as completed (PR #611 `2465131e`; site config layer read in `pdm_global_site_packages_with`)\n- 2026-10-05 13:35Z: closed #603 as completed (PR #605 `46466931`; `verify_mode_requires_every_store_copy_patched` covers the Deno `_1` case)\n- 2026-10-05 13:35Z: posted a not-closing comment on #742 and #650 (PR #743 fixed only the hosted half; the vendored half is still open)\n- 2026-10-05 13:30Z: removed `agent:claimed` from 49 closed issues (46 closed by the 11:13–13:20Z merge wave, plus #473, #566 and #603 above)\n- 2026-10-05 13:35Z: posted drift comments on ledgers #306, #307, #308, #309, #310, #311, #312, #313, #314 and #316 (they cite issues closed today as `fail`)\n- 2026-10-05 13:35Z: posted a drift comment on #575 (its hatch gap note still calls the merged #743 and #680 open)\n- 2026-10-03 13:20Z: posted a drift comment on ledger #307 (it still watches #579, closed by a maintainer)\n- 2026-10-03 13:20Z: posted a drift comment on #575 (it still lists closed #579 as an open regression)\n- 2026-10-03 08:19Z: posted a drift comment on ledger #308 (its Deno CLI-tool matrix still cites closed #434 for Windows)\n- 2026-10-03 00:20Z: posted a drift comment on ledger #311 (its `scan -g` official-installer row is `fail` but points only at closed #415; no open issue tracks it)\n- 2026-10-02 22:20Z: posted a drift comment on ledger #311 (its matrix still lists closed #327 as `fail`)\n- 2026-10-02 20:25Z: removed `agent:claimed` from closed #570 (closed as completed by PR #581)\n- 2026-10-02 20:25Z: released the stale claim on #362 and removed `agent:claimed` (no PR for the remaining half, claimer silent for more than 48h)\n- 2026-10-02 19:20Z: removed `agent:claimed` from closed #328 (closed as completed, so the claim is finished)\n- 2026-10-02 19:20Z: removed `agent:claimed` from closed #563 (closed as completed, so the claim is finished)\n- 2026-10-02 19:20Z: removed `agent:claimed` from closed #482 (closed as completed, so the claim is finished)\n- 2026-10-02 19:20Z: removed `agent:claimed` from closed #548 (closed as completed, so the claim is finished)\n- 2026-10-02 19:20Z: posted a drift comment on ledger #305 (its matrix lists closed issues as `fail`)\n- 2026-10-02 19:20Z: posted a drift comment on ledger #309 (its matrix lists closed issues as `fail`)\n- 2026-10-02 19:20Z: posted a drift comment on ledger #311 (its matrix lists closed issues as `fail`)\n- 2026-10-02 19:20Z: posted a drift comment on ledger #313 (its matrix lists closed issues as `fail`)\n- 2026-10-02 19:20Z: posted a drift comment on ledger #314 (its matrix lists closed issues as `fail`)\n- 2026-10-02 19:20Z: posted a drift comment on ledger #316 (its matrix lists closed issues as `fail`)\n- 2026-10-02 18:28Z: removed `agent:claimed` from closed #366 (closed as completed, so the claim is finished)\n- 2026-10-02 18:28Z: removed `agent:claimed` from closed #369 (closed as completed, so the claim is finished)\n- 2026-10-02 18:28Z: removed `agent:claimed` from closed #373 (closed as completed, so the claim is finished)\n- 2026-10-02 18:28Z: removed `agent:claimed` from closed #403 (closed as completed, so the claim is finished)\n- 2026-10-02 18:28Z: removed `agent:claimed` from closed #404 (closed as completed, so the claim is finished)\n- 2026-10-02 18:28Z: removed `agent:claimed` from closed #405 (closed as completed, so the claim is finished)\n- 2026-10-02 18:28Z: removed `agent:claimed` from closed #468 (closed as completed, so the claim is finished)\n- 2026-10-02 18:28Z: removed `agent:claimed` from closed #495 (closed as completed, so the claim is finished)\n- 2026-10-02 18:28Z: removed `agent:claimed` from closed #516 (closed as completed, so the claim is finished)\n- 2026-10-02 18:28Z: posted a drift comment on ledger #302 (its matrix lists closed issues as `fail`)\n\n## Deferred / unsure\n- A maintainer closed #467, #515, #744, #941 and #944 as not planned between 13:15 and 13:19Z today, with no closing comment. #944 carried the pnpm07 claim (PR #1007). I didn't touch these; the ledger drift comments point the bug-hunt routines at them.\n- Fresh claims with an open PR (all under 48h or with a live PR): #1094 → #1095; #1086 → #1091; #1084 → #1085; #1079 → #1121; #1067 → #1106; #996, #867 → #997; #905 → #1117; #824 → #1124; #815 → #1108; #747 → #1126; #693 → #1110; #631 → #1103; pnpm07 batch → #1007; npm batch → #1008; bun batch → #1009; #580 → #1051; #615 → #1021; #648 → #1041; #704 → #1027; #792 → #1049; #808 → #1030; #966 → #1031; #973 → #1036.\n- #612: partly fixed by #1044. It stays open for the hosted→vendored takeover. Re-check when a PR names it.\n\n## Needs a human\n- Open `agent:needs-human` decisions: #1065 (unsigned SHA256SUMS), #1088 (command model), #1099 (hosted VEX evidence) and #1130 (hosted rollback originals sidecar).\n- #578 (bun/* ~+102–125% from #472) is still claimed under PR #1009. The bench (#575) still reports it as regressed.\n- Discussion #301 (\"Welcome to socket-patch Discussions!\") is closed. The janitor keeps it as is.\n- Ledgers #317 (Go) and #321 (Composer) have had no comments since 2026-10-03, and #308 (Deno) and #314 (Hatch) none since 2026-10-05. Check that those bug-hunt routines are still running.\n\n\n---\n_Generated by [Claude Code](https://claude.ai/code)_"
66+
}
67+
]

0 commit comments

Comments
 (0)