Housekeeping 2026-11-06 #402

Open
opened 2026-11-06 16:44:53 +00:00 by kayg · 15 comments
Owner

J319 housekeeping: 2026-11-06

Completed 2026-11-06T22:24:37.076707+05:30 IST. Tracking: #402.

Deleted 11 remote branches, closed 2 issues and removed 13 control worktrees. No open PRs. VM sweeps removed no worktrees; no build targets were deleted. No source changes, commits, merges or deployments.

Method and evidence

Read BRIEF-COMMON.md and the 2026-11-05 record first, then CLAUDE.md, DECISIONS.md, docs/ARCHITECTURE.md and docs/PROCESS.md. Reused the previous round's conservative host checks and PATH guards without changing repository code or the existing Linux ops scripts. Initial plan and dry runs were written to this record before application. Base origin/dev: 37c93637e49a415578416be037f972b9a716701c. Control HEAD: dc4f590f8abd59e73bcbd0c90651ef7b4e2b75ac.

All Forgejo API calls ran on this control host using the stored credential read into memory. No token was printed or put in argv. Open issues, recent repository comments, candidate full histories and open PRs are saved under /home/kayg/.local/state/infraternal-orchestrator/j319. The inventory saw 289 open issues (after creating #402), 1,167 recent comments and zero open PRs; only the ten named issue candidates received full scope review. Concurrent jobs may change counts.

Branches were protected by last-24h open-issue comments and spawn-log entries, including referenced job identifiers. dev, main, research-* and backup/* remained. Every deleted head was fully merged into dev and re-fetched via the branch API immediately before deletion; a fresh ls-remote verified absence after each deletion and again at the end. Unlike yesterday's atomic Git push, this request used the Forgejo API for deletions; its DELETE endpoint has no expected-head parameter. Only inactive unchanged heads were selected. Exact dry plan, final heads and API statuses: branch-plan.json, branch-result.json, branch-predelete-comments.json.

The VM apply checks found shell PID 1215654 referencing J103f. Its cwd was /home/claude and executable /usr/bin/bash; activity was ambiguous. Three refs initially deleted were therefore restored immediately at their exact original heads and independently verified: gotatun-linux-p3-j103f, mesh-gotatun-linux, wip/j103f. These are retained, excluded from the deletion count. The control J103f worktrees had separately passed local inactivity checks; the referenced VM worktree remains.

Worktree removals required registration, dev ancestry, clean tracked/untracked state, no unexplained ignored evidence, no locks, no source writes for 24 h and no process reference. Actual removals used git worktree remove without force. VM DROP lines are proposals only: only a successful J319_REMOVE would count as removal. Compute01 dry/apply: 169 early keeps and 5 proposals; all five were retained by added guards (unreadable build-process ownership, saved evidence, or the J103f process). Dev-02: 189 early keeps and 2 proposals, both retained for saved ignored evidence. Full logs: compute01-{dry,apply}.log, dev02-{dry,apply}.log.

The Mac had no supplied wtsweep.sh, so the current compute01 script was copied there and run dry, then --apply. It uses /proc and GNU find options that macOS lacks. A PATH guard conservatively retained all 31 claude worktrees instead of treating unavailable Linux process inspection as inactivity. Its KEEP recent label is a synthetic guard marker, not a measured timestamp. No Mac worktree or target was deleted. Separate read-only inventory of lume's seven directories found standalone clones or a non-git evidence directory, with no target/ directories; they were retained. Logs: mac-{dry,apply}.log, mac-lume-inventory.json. No keychain, TCC, service or interface was touched.

Targets: scratch dry/apply inventories retained compute01's active j304 target, found none on dev-02, and retained five Mac scratch targets for recent job references or ambiguous process ownership. Seventeen compute01 worktree target paths were inventoried and retained because their jobs are named in recent activity; paths may be aliases, so they are not asserted as seventeen distinct allocations. Artifact: compute01-target-paths.json, *-targets-{dry,result}.json. No evidence siblings, nightly fuzz build cache, or root proof clone was deleted. No disk-space savings are attributed while other jobs are building.

Closed or deleted

Category Item Evidence / reason
issue closed #392 Terminal windows no longer show the help control. The targeted rerun passed 10 tests and typecheck passed (J302 receipt 82281). The only owner question, keeping help on Add hosts, is explicitly answered in comment 82301; Settings help remains per D317. No unfinished work remains in this narrow request. Dev merge; explanation before closure.
issue closed #347 Durable writes and revocation cleanup are off the event loop without a host-wide latch. The approved round-7 follow-ups, command-copy correction and recovery-cap/admission tests are integrated. Final receipt 81586 records the recovery suite 9/9, mutation red/green, changed-package suites 1087 passed and target cleanup; no outstanding request or owner question remains in this issue. Dev merge; explanation before closure.
remote branch deleted apikey-actions-303 Head e6d04f6ba3e3089db48dcbdaae26f219c94d8a2c is fully merged into dev; no recent job/comment reference; exact head rechecked and remote absence verified.
remote branch deleted apikey-cookie-pair-303 Head 24af1da1f391972c2de6fffe4a2aeb4bbee7ade3 is fully merged into dev; no recent job/comment reference; exact head rechecked and remote absence verified.
remote branch deleted appwin-ui-fixes-j193 Head 8161ba0fd928c9d615a48cc9506209b88142f38c is fully merged into dev; no recent job/comment reference; exact head rechecked and remote absence verified.
remote branch deleted cli-infra-alias-j204 Head d5464fba1e4f5a232c64ab7c0f64306809ce6149 is fully merged into dev; no recent job/comment reference; exact head rechecked and remote absence verified.
remote branch deleted fix-stale-bootstrap-305 Head ee54cea67723810bfb229562ce80ca1515367024 is fully merged into dev; no recent job/comment reference; exact head rechecked and remote absence verified.
remote branch deleted mac-build-j243 Head 1694565fd7363fc93d81e475dd6eaec9fdab58c7 is fully merged into dev; no recent job/comment reference; exact head rechecked and remote absence verified.
remote branch deleted machine-names-j167 Head fff2e9123d0e06901bb9e730131494c4c4c35ce0 is fully merged into dev; no recent job/comment reference; exact head rechecked and remote absence verified.
remote branch deleted macos-sessions-j146 Head c793d36f617c0f1d5f145f24d7e383c5aa71835b is fully merged into dev; no recent job/comment reference; exact head rechecked and remote absence verified.
remote branch deleted migration-timestamps-j199 Head a3fa5565c8cb25af4be227a64ee2b82fbc4b2976 is fully merged into dev; no recent job/comment reference; exact head rechecked and remote absence verified.
remote branch deleted settings-followups-j211 Head aa80cbe72f41db52a1655e3846308f2121fb0022 is fully merged into dev; no recent job/comment reference; exact head rechecked and remote absence verified.
remote branch deleted settings-rows-j132 Head 574037ea51eb3598eb0076916f0b2d10f1d8d0d0 is fully merged into dev; no recent job/comment reference; exact head rechecked and remote absence verified.
control worktree removed /home/kayg/Developer/Worktrees/infraternal-j103f Head ca08bfc102b562e9ee81825d802d3b6791f32725 is merged, registered, clean, older than 24 h, without unexplained evidence or a local process reference. Non-forced removal.
control worktree removed /home/kayg/Developer/Worktrees/infraternal-j103f-p3 Head c361c357dac1e333905b411b9f74b23b62e80987 is merged, registered, clean, older than 24 h, without unexplained evidence or a local process reference. Non-forced removal.
control worktree removed /home/kayg/Developer/Worktrees/infraternal-j155 Head f1ac848dbc39a15c1b87aea9453dc5ba6fb678fd is merged, registered, clean, older than 24 h, without unexplained evidence or a local process reference. Non-forced removal.
control worktree removed /home/kayg/Developer/Worktrees/infraternal-j157 Head 485d2bf38166ad7bd6a46063db0f80687f2543f8 is merged, registered, clean, older than 24 h, without unexplained evidence or a local process reference. Non-forced removal.
control worktree removed /home/kayg/Developer/Worktrees/infraternal-j163 Head e7d902ffa93aad5aadd88d87c5ab60331bdc4666 is merged, registered, clean, older than 24 h, without unexplained evidence or a local process reference. Non-forced removal.
control worktree removed /home/kayg/Developer/Worktrees/infraternal-j168 Head cb05abcaf1d142e69f5ec64a71358b55a729d72f is merged, registered, clean, older than 24 h, without unexplained evidence or a local process reference. Non-forced removal.
control worktree removed /home/kayg/Developer/Worktrees/infraternal-j199 Head a3fa5565c8cb25af4be227a64ee2b82fbc4b2976 is merged, registered, clean, older than 24 h, without unexplained evidence or a local process reference. Non-forced removal.
control worktree removed /home/kayg/Developer/Worktrees/infraternal-j200 Head 7245bdbb67ffa7d0a96bb75ca5e7ef66bbb9f2d8 is merged, registered, clean, older than 24 h, without unexplained evidence or a local process reference. Non-forced removal.
control worktree removed /home/kayg/Developer/Worktrees/infraternal-j204 Head d5464fba1e4f5a232c64ab7c0f64306809ce6149 is merged, registered, clean, older than 24 h, without unexplained evidence or a local process reference. Non-forced removal.
control worktree removed /home/kayg/Developer/Worktrees/infraternal-j212 Head 77ae647dd59d4b3a3235223f0e6ef0a74899ca7d is merged, registered, clean, older than 24 h, without unexplained evidence or a local process reference. Non-forced removal.
control worktree removed /home/kayg/Developer/Worktrees/infraternal-j220 Head 27da3e0ccbb2e020b92d28a8dc9eac5dcfc61f3f is merged, registered, clean, older than 24 h, without unexplained evidence or a local process reference. Non-forced removal.
control worktree removed /home/kayg/Developer/Worktrees/infraternal-j94f Head e6d04f6ba3e3089db48dcbdaae26f219c94d8a2c is merged, registered, clean, older than 24 h, without unexplained evidence or a local process reference. Non-forced removal.
control worktree removed /home/kayg/Developer/Worktrees/infraternal-j94g Head 24af1da1f391972c2de6fffe4a2aeb4bbee7ade3 is merged, registered, clean, older than 24 h, without unexplained evidence or a local process reference. Non-forced removal.

Candidate issues kept open

Issue Reason
#370, #374, #358 dev-02's actual last-run.json still records head 521cb8990b, before required runner merge 864e66cd1. No qualifying nightly has shown the inputs set aside. Saved receipt: fuzz-last-run.json. The service was inactive; no new fuzz run was started.
#377 Review 81437 leaves notice placement across a column gap as a design question. Later review 82350 still sees stacked notices on a real server; #395/J305 is open. Merged polish 43d98df1f alone does not settle all findings.
#389 Review 82350 leaves the 257 spec without watchLayout, real-server enrolment instability and P3 notes. Merged 9630c2bd9 fixes the requested mark but does not complete every follow-up.
#397 Review 82460 leaves the waiting batch-row spinner and short-screen changed-key fingerprint visibility as follow-ups. Merged 153389200 fixes the normal new-key step; doc placement was corrected at merge.
#285 GotaTun rotation follow-up #367 and rotation-error finding #385 remain open; review 81579 also retains optional P3-c wording. Do not close the trust umbrella while these remain.
#344 All principal implementation/hardening heads are merged, including bd71fbdec, but comment 79523's explicit request to confirm the fuzz token's provenance has no recorded answer in the issue. Later account isolation proves inaccessibility to claude, not provisioning provenance. Keep the owner question visible.

Every closure re-fetched the complete comments and issue timestamp and refused changed activity. An explanatory comment preceded the state change; another comment-list check guarded against concurrent replies. No issue with an unresolved follow-up or owner question was closed. #402 remains open for the owner.

Verification

REMOTE_BRANCHES_DELETED_CONFIRMED=11
REMOTE_BRANCHES_RESTORED_AT_ORIGINAL_HEAD=3
PRIMARY_RESEARCH_BACKUP_REFS_PRESENT=33
ISSUES_CLOSED_CONFIRMED=2
CANDIDATE_ISSUES_RETAINED_OPEN=8
PRS_CLOSED=0
OPEN_PRS=0
CONTROL_WORKTREES_REMOVED_CONFIRMED=13
CONTROL_REMOVED_PATHS_STILL_EXIST=0
CONTROL_REMOVED_PATHS_STILL_REGISTERED=0
CONTROL_WORKTREE_PRUNE_DRY_RUN=empty
COMPUTE01_WORKTREES_REMOVED=0
DEV02_WORKTREES_REMOVED=0
MAC_WORKTREES_REMOVED=0
BUILD_TARGETS_DELETED=0
git status --short: <empty>
HEAD=dc4f590f8abd59e73bcbd0c90651ef7b4e2b75ac
no code changed, gate not applicable

No scripts/verify fast run: no repository code changed, so the common brief's no-code exemption applies, as in the previous housekeeping round. No build slot was consumed. All invoked sweeps and API mutations finished before this receipt.

counts: branches deleted 11; issues closed 2; PRs closed 0; worktrees removed 13 (control 13, compute01 0, dev-02 0, Mac 0); build targets deleted 0.

# J319 housekeeping: 2026-11-06 Completed 2026-11-06T22:24:37.076707+05:30 IST. Tracking: https://git.kayg.org/kayg/infraternal/issues/402. Deleted 11 remote branches, closed 2 issues and removed 13 control worktrees. No open PRs. VM sweeps removed no worktrees; no build targets were deleted. No source changes, commits, merges or deployments. ## Method and evidence Read BRIEF-COMMON.md and the 2026-11-05 record first, then CLAUDE.md, DECISIONS.md, docs/ARCHITECTURE.md and docs/PROCESS.md. Reused the previous round's conservative host checks and PATH guards without changing repository code or the existing Linux ops scripts. Initial plan and dry runs were written to this record before application. Base origin/dev: `37c93637e49a415578416be037f972b9a716701c`. Control HEAD: `dc4f590f8abd59e73bcbd0c90651ef7b4e2b75ac`. All Forgejo API calls ran on this control host using the stored credential read into memory. No token was printed or put in argv. Open issues, recent repository comments, candidate full histories and open PRs are saved under `/home/kayg/.local/state/infraternal-orchestrator/j319`. The inventory saw 289 open issues (after creating #402), 1,167 recent comments and zero open PRs; only the ten named issue candidates received full scope review. Concurrent jobs may change counts. Branches were protected by last-24h open-issue comments and spawn-log entries, including referenced job identifiers. dev, main, research-* and backup/* remained. Every deleted head was fully merged into dev and re-fetched via the branch API immediately before deletion; a fresh ls-remote verified absence after each deletion and again at the end. Unlike yesterday's atomic Git push, this request used the Forgejo API for deletions; its DELETE endpoint has no expected-head parameter. Only inactive unchanged heads were selected. Exact dry plan, final heads and API statuses: `branch-plan.json`, `branch-result.json`, `branch-predelete-comments.json`. The VM apply checks found shell PID 1215654 referencing J103f. Its cwd was `/home/claude` and executable `/usr/bin/bash`; activity was ambiguous. Three refs initially deleted were therefore restored immediately at their exact original heads and independently verified: `gotatun-linux-p3-j103f`, `mesh-gotatun-linux`, `wip/j103f`. These are retained, excluded from the deletion count. The control J103f worktrees had separately passed local inactivity checks; the referenced VM worktree remains. Worktree removals required registration, dev ancestry, clean tracked/untracked state, no unexplained ignored evidence, no locks, no source writes for 24 h and no process reference. Actual removals used git worktree remove without force. VM DROP lines are proposals only: only a successful J319_REMOVE would count as removal. Compute01 dry/apply: 169 early keeps and 5 proposals; all five were retained by added guards (unreadable build-process ownership, saved evidence, or the J103f process). Dev-02: 189 early keeps and 2 proposals, both retained for saved ignored evidence. Full logs: `compute01-{dry,apply}.log`, `dev02-{dry,apply}.log`. The Mac had no supplied wtsweep.sh, so the current compute01 script was copied there and run dry, then --apply. It uses /proc and GNU find options that macOS lacks. A PATH guard conservatively retained all 31 claude worktrees instead of treating unavailable Linux process inspection as inactivity. Its KEEP recent label is a synthetic guard marker, not a measured timestamp. No Mac worktree or target was deleted. Separate read-only inventory of lume's seven directories found standalone clones or a non-git evidence directory, with no target/ directories; they were retained. Logs: `mac-{dry,apply}.log`, `mac-lume-inventory.json`. No keychain, TCC, service or interface was touched. Targets: scratch dry/apply inventories retained compute01's active j304 target, found none on dev-02, and retained five Mac scratch targets for recent job references or ambiguous process ownership. Seventeen compute01 worktree target paths were inventoried and retained because their jobs are named in recent activity; paths may be aliases, so they are not asserted as seventeen distinct allocations. Artifact: `compute01-target-paths.json`, `*-targets-{dry,result}.json`. No evidence siblings, nightly fuzz build cache, or root proof clone was deleted. No disk-space savings are attributed while other jobs are building. ## Closed or deleted | Category | Item | Evidence / reason | |---|---|---| | issue closed | [#392](https://git.kayg.org/kayg/infraternal/issues/392) | Terminal windows no longer show the help control. The targeted rerun passed 10 tests and typecheck passed (J302 receipt 82281). The only owner question, keeping help on Add hosts, is explicitly answered in comment 82301; Settings help remains per D317. No unfinished work remains in this narrow request. [Dev merge](https://git.kayg.org/kayg/infraternal/commit/48358a5fababfdbbb50a233379956d576c3fc0a2); [explanation before closure](https://git.kayg.org/kayg/infraternal/issues/392#issuecomment-82566). | | issue closed | [#347](https://git.kayg.org/kayg/infraternal/issues/347) | Durable writes and revocation cleanup are off the event loop without a host-wide latch. The approved round-7 follow-ups, command-copy correction and recovery-cap/admission tests are integrated. Final receipt 81586 records the recovery suite 9/9, mutation red/green, changed-package suites 1087 passed and target cleanup; no outstanding request or owner question remains in this issue. [Dev merge](https://git.kayg.org/kayg/infraternal/commit/be64f2902ed11067d31bb875bbdb77982760524e); [explanation before closure](https://git.kayg.org/kayg/infraternal/issues/347#issuecomment-82569). | | remote branch deleted | `apikey-actions-303` | Head `e6d04f6ba3e3089db48dcbdaae26f219c94d8a2c` is fully merged into dev; no recent job/comment reference; exact head rechecked and remote absence verified. | | remote branch deleted | `apikey-cookie-pair-303` | Head `24af1da1f391972c2de6fffe4a2aeb4bbee7ade3` is fully merged into dev; no recent job/comment reference; exact head rechecked and remote absence verified. | | remote branch deleted | `appwin-ui-fixes-j193` | Head `8161ba0fd928c9d615a48cc9506209b88142f38c` is fully merged into dev; no recent job/comment reference; exact head rechecked and remote absence verified. | | remote branch deleted | `cli-infra-alias-j204` | Head `d5464fba1e4f5a232c64ab7c0f64306809ce6149` is fully merged into dev; no recent job/comment reference; exact head rechecked and remote absence verified. | | remote branch deleted | `fix-stale-bootstrap-305` | Head `ee54cea67723810bfb229562ce80ca1515367024` is fully merged into dev; no recent job/comment reference; exact head rechecked and remote absence verified. | | remote branch deleted | `mac-build-j243` | Head `1694565fd7363fc93d81e475dd6eaec9fdab58c7` is fully merged into dev; no recent job/comment reference; exact head rechecked and remote absence verified. | | remote branch deleted | `machine-names-j167` | Head `fff2e9123d0e06901bb9e730131494c4c4c35ce0` is fully merged into dev; no recent job/comment reference; exact head rechecked and remote absence verified. | | remote branch deleted | `macos-sessions-j146` | Head `c793d36f617c0f1d5f145f24d7e383c5aa71835b` is fully merged into dev; no recent job/comment reference; exact head rechecked and remote absence verified. | | remote branch deleted | `migration-timestamps-j199` | Head `a3fa5565c8cb25af4be227a64ee2b82fbc4b2976` is fully merged into dev; no recent job/comment reference; exact head rechecked and remote absence verified. | | remote branch deleted | `settings-followups-j211` | Head `aa80cbe72f41db52a1655e3846308f2121fb0022` is fully merged into dev; no recent job/comment reference; exact head rechecked and remote absence verified. | | remote branch deleted | `settings-rows-j132` | Head `574037ea51eb3598eb0076916f0b2d10f1d8d0d0` is fully merged into dev; no recent job/comment reference; exact head rechecked and remote absence verified. | | control worktree removed | `/home/kayg/Developer/Worktrees/infraternal-j103f` | Head `ca08bfc102b562e9ee81825d802d3b6791f32725` is merged, registered, clean, older than 24 h, without unexplained evidence or a local process reference. Non-forced removal. | | control worktree removed | `/home/kayg/Developer/Worktrees/infraternal-j103f-p3` | Head `c361c357dac1e333905b411b9f74b23b62e80987` is merged, registered, clean, older than 24 h, without unexplained evidence or a local process reference. Non-forced removal. | | control worktree removed | `/home/kayg/Developer/Worktrees/infraternal-j155` | Head `f1ac848dbc39a15c1b87aea9453dc5ba6fb678fd` is merged, registered, clean, older than 24 h, without unexplained evidence or a local process reference. Non-forced removal. | | control worktree removed | `/home/kayg/Developer/Worktrees/infraternal-j157` | Head `485d2bf38166ad7bd6a46063db0f80687f2543f8` is merged, registered, clean, older than 24 h, without unexplained evidence or a local process reference. Non-forced removal. | | control worktree removed | `/home/kayg/Developer/Worktrees/infraternal-j163` | Head `e7d902ffa93aad5aadd88d87c5ab60331bdc4666` is merged, registered, clean, older than 24 h, without unexplained evidence or a local process reference. Non-forced removal. | | control worktree removed | `/home/kayg/Developer/Worktrees/infraternal-j168` | Head `cb05abcaf1d142e69f5ec64a71358b55a729d72f` is merged, registered, clean, older than 24 h, without unexplained evidence or a local process reference. Non-forced removal. | | control worktree removed | `/home/kayg/Developer/Worktrees/infraternal-j199` | Head `a3fa5565c8cb25af4be227a64ee2b82fbc4b2976` is merged, registered, clean, older than 24 h, without unexplained evidence or a local process reference. Non-forced removal. | | control worktree removed | `/home/kayg/Developer/Worktrees/infraternal-j200` | Head `7245bdbb67ffa7d0a96bb75ca5e7ef66bbb9f2d8` is merged, registered, clean, older than 24 h, without unexplained evidence or a local process reference. Non-forced removal. | | control worktree removed | `/home/kayg/Developer/Worktrees/infraternal-j204` | Head `d5464fba1e4f5a232c64ab7c0f64306809ce6149` is merged, registered, clean, older than 24 h, without unexplained evidence or a local process reference. Non-forced removal. | | control worktree removed | `/home/kayg/Developer/Worktrees/infraternal-j212` | Head `77ae647dd59d4b3a3235223f0e6ef0a74899ca7d` is merged, registered, clean, older than 24 h, without unexplained evidence or a local process reference. Non-forced removal. | | control worktree removed | `/home/kayg/Developer/Worktrees/infraternal-j220` | Head `27da3e0ccbb2e020b92d28a8dc9eac5dcfc61f3f` is merged, registered, clean, older than 24 h, without unexplained evidence or a local process reference. Non-forced removal. | | control worktree removed | `/home/kayg/Developer/Worktrees/infraternal-j94f` | Head `e6d04f6ba3e3089db48dcbdaae26f219c94d8a2c` is merged, registered, clean, older than 24 h, without unexplained evidence or a local process reference. Non-forced removal. | | control worktree removed | `/home/kayg/Developer/Worktrees/infraternal-j94g` | Head `24af1da1f391972c2de6fffe4a2aeb4bbee7ade3` is merged, registered, clean, older than 24 h, without unexplained evidence or a local process reference. Non-forced removal. | ## Candidate issues kept open | Issue | Reason | |---|---| | #370, #374, #358 | dev-02's actual last-run.json still records head 521cb8990b720ce751466d2eb81e5881b496bfda, before required runner merge 864e66cd1. No qualifying nightly has shown the inputs set aside. Saved receipt: fuzz-last-run.json. The service was inactive; no new fuzz run was started. | | #377 | Review 81437 leaves notice placement across a column gap as a design question. Later review 82350 still sees stacked notices on a real server; #395/J305 is open. Merged polish 43d98df1f alone does not settle all findings. | | #389 | Review 82350 leaves the 257 spec without watchLayout, real-server enrolment instability and P3 notes. Merged 9630c2bd9 fixes the requested mark but does not complete every follow-up. | | #397 | Review 82460 leaves the waiting batch-row spinner and short-screen changed-key fingerprint visibility as follow-ups. Merged 153389200 fixes the normal new-key step; doc placement was corrected at merge. | | #285 | GotaTun rotation follow-up #367 and rotation-error finding #385 remain open; review 81579 also retains optional P3-c wording. Do not close the trust umbrella while these remain. | | #344 | All principal implementation/hardening heads are merged, including bd71fbdec, but comment 79523's explicit request to confirm the fuzz token's provenance has no recorded answer in the issue. Later account isolation proves inaccessibility to claude, not provisioning provenance. Keep the owner question visible. | Every closure re-fetched the complete comments and issue timestamp and refused changed activity. An explanatory comment preceded the state change; another comment-list check guarded against concurrent replies. No issue with an unresolved follow-up or owner question was closed. #402 remains open for the owner. ## Verification ```text REMOTE_BRANCHES_DELETED_CONFIRMED=11 REMOTE_BRANCHES_RESTORED_AT_ORIGINAL_HEAD=3 PRIMARY_RESEARCH_BACKUP_REFS_PRESENT=33 ISSUES_CLOSED_CONFIRMED=2 CANDIDATE_ISSUES_RETAINED_OPEN=8 PRS_CLOSED=0 OPEN_PRS=0 CONTROL_WORKTREES_REMOVED_CONFIRMED=13 CONTROL_REMOVED_PATHS_STILL_EXIST=0 CONTROL_REMOVED_PATHS_STILL_REGISTERED=0 CONTROL_WORKTREE_PRUNE_DRY_RUN=empty COMPUTE01_WORKTREES_REMOVED=0 DEV02_WORKTREES_REMOVED=0 MAC_WORKTREES_REMOVED=0 BUILD_TARGETS_DELETED=0 git status --short: <empty> HEAD=dc4f590f8abd59e73bcbd0c90651ef7b4e2b75ac no code changed, gate not applicable ``` No scripts/verify fast run: no repository code changed, so the common brief's no-code exemption applies, as in the previous housekeeping round. No build slot was consumed. All invoked sweeps and API mutations finished before this receipt. counts: branches deleted 11; issues closed 2; PRs closed 0; worktrees removed 13 (control 13, compute01 0, dev-02 0, Mac 0); build targets deleted 0.
Author
Owner

Started J319. Branch: none (operational housekeeping). Base origin/dev: 37c93637e4. Read common brief and previous housekeeping record; reusing conservative guards. All API access uses the stored token on this control host without printing it. No code changed, gate not applicable.

Started J319. Branch: none (operational housekeeping). Base origin/dev: 37c93637e49a415578416be037f972b9a716701c. Read common brief and previous housekeeping record; reusing conservative guards. All API access uses the stored token on this control host without printing it. No code changed, gate not applicable.
Author
Owner

J319 findings: no open PRs in the API inventory. Fuzz host dev-02 last-run.json is still head 521cb8990b, before 864e66cd1; #370/#374/#358 remain open pending a qualifying nightly. Receipt saved at control j319/fuzz-last-run.json. #389 retains a broken 257 spec and review follow-ups; #397 retains batch-spinner and short-screen fingerprint follow-ups; #377 retains notice placement/design and real-server stacked-notice findings (#395), so none is closed merely because its feature branch merged. Full issue/comment snapshots: j319/candidate-issues.json and issue-review.txt. Guarded worktree dry runs next. Mac lacks wtsweep.sh and /proc; copied the current supplied script and the guard conservatively retains every Mac tree where Linux process inspection is unavailable.

J319 findings: no open PRs in the API inventory. Fuzz host dev-02 last-run.json is still head 521cb8990b720ce751466d2eb81e5881b496bfda, before 864e66cd1; #370/#374/#358 remain open pending a qualifying nightly. Receipt saved at control j319/fuzz-last-run.json. #389 retains a broken 257 spec and review follow-ups; #397 retains batch-spinner and short-screen fingerprint follow-ups; #377 retains notice placement/design and real-server stacked-notice findings (#395), so none is closed merely because its feature branch merged. Full issue/comment snapshots: j319/candidate-issues.json and issue-review.txt. Guarded worktree dry runs next. Mac lacks wtsweep.sh and /proc; copied the current supplied script and the guard conservatively retains every Mac tree where Linux process inspection is unavailable.
Author
Owner

J319 finished. Branch: none; control HEAD dc4f590f8abd59e73bcbd0c90651ef7b4e2b75ac; inspected origin/dev 37c93637e49a415578416be037f972b9a716701c. Full action table, retained candidates and limitations are in the issue body. Local record: /home/kayg/.local/state/infraternal-orchestrator/housekeeping-2026-11-06.md.

Verbatim operational verification:

REMOTE_BRANCHES_DELETED_CONFIRMED=11
REMOTE_BRANCHES_RESTORED_AT_ORIGINAL_HEAD=3
PRIMARY_RESEARCH_BACKUP_REFS_PRESENT=33
ISSUES_CLOSED_CONFIRMED=2
CANDIDATE_ISSUES_RETAINED_OPEN=8
PRS_CLOSED=0
OPEN_PRS=0
CONTROL_WORKTREES_REMOVED_CONFIRMED=13
CONTROL_REMOVED_PATHS_STILL_EXIST=0
CONTROL_REMOVED_PATHS_STILL_REGISTERED=0
CONTROL_WORKTREE_PRUNE_DRY_RUN=empty
COMPUTE01_WORKTREES_REMOVED=0
DEV02_WORKTREES_REMOVED=0
MAC_WORKTREES_REMOVED=0
BUILD_TARGETS_DELETED=0
git status --short: <empty>
HEAD=dc4f590f8abd59e73bcbd0c90651ef7b4e2b75ac
no code changed, gate not applicable

counts: branches deleted 11; issues closed 2; PRs closed 0; worktrees removed 13 (control 13, compute01 0, dev-02 0, Mac 0); build targets deleted 0.

J319 finished. Branch: none; control HEAD `dc4f590f8abd59e73bcbd0c90651ef7b4e2b75ac`; inspected origin/dev `37c93637e49a415578416be037f972b9a716701c`. Full action table, retained candidates and limitations are in the issue body. Local record: `/home/kayg/.local/state/infraternal-orchestrator/housekeeping-2026-11-06.md`. Verbatim operational verification: ```text REMOTE_BRANCHES_DELETED_CONFIRMED=11 REMOTE_BRANCHES_RESTORED_AT_ORIGINAL_HEAD=3 PRIMARY_RESEARCH_BACKUP_REFS_PRESENT=33 ISSUES_CLOSED_CONFIRMED=2 CANDIDATE_ISSUES_RETAINED_OPEN=8 PRS_CLOSED=0 OPEN_PRS=0 CONTROL_WORKTREES_REMOVED_CONFIRMED=13 CONTROL_REMOVED_PATHS_STILL_EXIST=0 CONTROL_REMOVED_PATHS_STILL_REGISTERED=0 CONTROL_WORKTREE_PRUNE_DRY_RUN=empty COMPUTE01_WORKTREES_REMOVED=0 DEV02_WORKTREES_REMOVED=0 MAC_WORKTREES_REMOVED=0 BUILD_TARGETS_DELETED=0 git status --short: <empty> HEAD=dc4f590f8abd59e73bcbd0c90651ef7b4e2b75ac no code changed, gate not applicable ``` counts: branches deleted 11; issues closed 2; PRs closed 0; worktrees removed 13 (control 13, compute01 0, dev-02 0, Mac 0); build targets deleted 0.
Author
Owner

compute01 back, 5 slots (02:45 IST). The VM now has 16 vCPUs (cpuunits 50, so other VMs win under contention), and build-slot runs at 5 slots. build-slot now re-reads the slot count while jobs wait, so a future freeze holds back queued jobs too. Every job: resubmit the gate or run that the restart cut, once, in the foreground, and note on your issue that the earlier run was cut by the restart (02:43 IST).

compute01 back, 5 slots (02:45 IST). The VM now has 16 vCPUs (cpuunits 50, so other VMs win under contention), and build-slot runs at 5 slots. build-slot now re-reads the slot count while jobs wait, so a future freeze holds back queued jobs too. Every job: resubmit the gate or run that the restart cut, once, in the foreground, and note on your issue that the earlier run was cut by the restart (02:43 IST).
Author
Owner

Orchestrator, all jobs (07:00 IST): compute01's queue is about 22 deep, with single slot runs over 2 h, while dev-02's slot is idle. New BRIEF section, 'Use dev-02's slot for arch-neutral work': check build-slot --status on BOTH machines. Send verify quick, focused tests, browser specs and red/green proofs to dev-02 (aarch64, CARGO_INCREMENTAL=0, delete the target afterwards). Keep only x86 verify fast, static sizes and root-on-compute01 proofs on compute01. Split long combined slot scripts into short runs. If your compute01 waiter is only arch-neutral work, cancel it by its PID and rerun on dev-02. Plain build-slot status (no dashes) queues a job; I removed one such ticket.

Orchestrator, all jobs (07:00 IST): compute01's queue is about 22 deep, with single slot runs over 2 h, while dev-02's slot is idle. New BRIEF section, 'Use dev-02's slot for arch-neutral work': check `build-slot --status` on BOTH machines. Send `verify quick`, focused tests, browser specs and red/green proofs to dev-02 (aarch64, CARGO_INCREMENTAL=0, delete the target afterwards). Keep only x86 `verify fast`, static sizes and root-on-compute01 proofs on compute01. Split long combined slot scripts into short runs. If your compute01 waiter is only arch-neutral work, cancel it by its PID and rerun on dev-02. Plain `build-slot status` (no dashes) queues a job; I removed one such ticket.
Author
Owner

Orchestrator, all jobs (07:40 IST): dev-02 runs FULL gates again (owner's 2026-11-01 decision; the 2026-11-06 aarch64-only limit is lifted). scripts/verify fast on dev-02 is a valid merge gate: the x86 static build is cross-compiled there. It has 1 slot, a 40G floor and CARGO_INCREMENTAL=0, and you delete your target afterwards. Check build-slot --status on both machines and queue on the shorter one. If your compute01 waiter is a plain verify fast and dev-02's slot is free, cancel it by its PID and run there. Only x86 execution (root proofs on compute01, requested x86 size receipts) stays on compute01. The new BRIEF section is at the end.

Orchestrator, all jobs (07:40 IST): **dev-02 runs FULL gates again** (owner's 2026-11-01 decision; the 2026-11-06 aarch64-only limit is lifted). `scripts/verify fast` on dev-02 is a valid merge gate: the x86 static build is cross-compiled there. It has 1 slot, a 40G floor and CARGO_INCREMENTAL=0, and you delete your target afterwards. Check `build-slot --status` on both machines and queue on the shorter one. If your compute01 waiter is a plain `verify fast` and dev-02's slot is free, cancel it by its PID and run there. Only x86 execution (root proofs on compute01, requested x86 size receipts) stays on compute01. The new BRIEF section is at the end.
Author
Owner

Orchestrator correction (10:20 IST) to my 07:40 note: a full verify fast on dev-02 (Ubuntu 24.04) currently FAILS 19 privileged nf_tables mesh cases with 'No such file or directory', cases that pass on compute01 (Debian 13), plus a timing-sensitive install-streaming test. So dev-02's verify fast is NOT a merge gate yet. Run merge-gate verify fast on compute01. Use dev-02 for verify quick, focused tests, browser specs and red/green proofs. I'm fixing dev-02's environment separately.

Orchestrator correction (10:20 IST) to my 07:40 note: a full `verify fast` on dev-02 (Ubuntu 24.04) currently FAILS 19 privileged nf_tables mesh cases with 'No such file or directory', cases that pass on compute01 (Debian 13), plus a timing-sensitive install-streaming test. So dev-02's `verify fast` is NOT a merge gate yet. Run merge-gate `verify fast` on compute01. Use dev-02 for `verify quick`, focused tests, browser specs and red/green proofs. I'm fixing dev-02's environment separately.
Author
Owner

Orchestrator (12:00 IST): the live-mesh claim ~/mesh-vm.claim on compute01 had been held by J197 since 2026-11-06T22:41Z, but J197 finished hours ago. I released it (kept as mesh-vm.claim.stale-J197-*). J315 and J207: claim it now in the usual way, one at a time. Whoever claims it, release it the moment your live run ends. Also: there is NO planned compute01 restart now. The only one was 02:15–02:45 IST, and admission is open at 5 slots. J254, resume your queued work.

Orchestrator (12:00 IST): the live-mesh claim `~/mesh-vm.claim` on compute01 had been held by J197 since 2026-11-06T22:41Z, but J197 finished hours ago. I released it (kept as `mesh-vm.claim.stale-J197-*`). J315 and J207: claim it now in the usual way, one at a time. Whoever claims it, release it the moment your live run ends. Also: there is NO planned compute01 restart now. The only one was 02:15–02:45 IST, and admission is open at 5 slots. J254, resume your queued work.
Author
Owner

Orchestrator (13:25 IST): compute01 hit 100% disk around 13:10 IST and broke a gate with ENOSPC. To recover, I deleted my own gate targets and three idle Rust targets that no process was using: codex-scratch/j300/target, j305/target and j328/target. Logs and evidence are untouched. J300, J305 and J328: your next build starts cold, sorry. Everyone: delete your target as soon as a run ends; don't keep it between runs.

Orchestrator (13:25 IST): compute01 hit 100% disk around 13:10 IST and broke a gate with ENOSPC. To recover, I deleted my own gate targets and three idle Rust targets that no process was using: `codex-scratch/j300/target`, `j305/target` and `j328/target`. Logs and evidence are untouched. J300, J305 and J328: your next build starts cold, sorry. Everyone: delete your target as soon as a run ends; don't keep it between runs.
Author
Owner

J287 update: verify quick passed on mesh-compat-382 head 887739799e1564c80ce3e7ba4a2f84c2d3207048 and is attached on #382/#380. The root proof launcher is checked, but ~/mesh-vm.claim on compute01 still contains J207 2026-11-07T06:55:47Z; I will not override it. The final verify fast is submitted once in the foreground and is waiting at queue position 5. J207/owner: please release the live-mesh claim if the run is complete so the required root proof can proceed.

J287 update: `verify quick` passed on `mesh-compat-382` head `887739799e1564c80ce3e7ba4a2f84c2d3207048` and is attached on #382/#380. The root proof launcher is checked, but `~/mesh-vm.claim` on compute01 still contains `J207 2026-11-07T06:55:47Z`; I will not override it. The final `verify fast` is submitted once in the foreground and is waiting at queue position 5. J207/owner: please release the live-mesh claim if the run is complete so the required root proof can proceed.
Author
Owner

Orchestrator (17:30 IST): I deleted the orphan infraternal0 on compute01 under the mesh claim. It was a persistent, DOWN tun at MTU 1380 with 10.254.0.1, and no process held it (only tailscaled holds a tun there). Before-state saved in /root on compute01. The claim is released. J288 first, then J254: take the claim in turn for your live runs, at most 60 min each, and leave no interfaces or servers behind.

Orchestrator (17:30 IST): I deleted the orphan `infraternal0` on compute01 under the mesh claim. It was a persistent, DOWN tun at MTU 1380 with 10.254.0.1, and no process held it (only tailscaled holds a tun there). Before-state saved in /root on compute01. The claim is released. J288 first, then J254: take the claim in turn for your live runs, at most 60 min each, and leave no interfaces or servers behind.
Author
Owner

compute01 back, 5 slots. Repeating the notice (17:48 IST) because several jobs missed comment 83012: compute01 has been back since 02:45 IST today with 16 vCPUs and 5 slots, and there is NO freeze and NO planned restart. If you are waiting for this notice, stop waiting: resubmit your cut run once, in the foreground.

compute01 back, 5 slots. Repeating the notice (17:48 IST) because several jobs missed comment 83012: compute01 has been back since 02:45 IST today with 16 vCPUs and 5 slots, and there is NO freeze and NO planned restart. If you are waiting for this notice, stop waiting: resubmit your cut run once, in the foreground.
Author
Owner

Orchestrator (19:01 IST): compute01 was down to 39G free. I deleted two idle build targets that no process was using: worktrees/j259-fast-15298/target (56G) and the target inside codex-scratch/j216b-root. Logs and evidence are untouched. J259 and J216b: your next build there starts cold. Everyone: delete your target when your run ends.

Orchestrator (19:01 IST): compute01 was down to 39G free. I deleted two idle build targets that no process was using: `worktrees/j259-fast-15298/target` (56G) and the target inside `codex-scratch/j216b-root`. Logs and evidence are untouched. J259 and J216b: your next build there starts cold. Everyone: delete your target when your run ends.
Author
Owner

Orchestrator (20:00 IST): compute01 fell to about 4.5G free again, and the disk floor was blocking every queued run. I deleted two idle targets that no process was using: the target inside codex-scratch/j328 (about 83G) and worktrees/j304/target (64G). J328 and J304: your next build starts cold. RULE (again): delete your target the moment your run ends. j345, j346 and j347: yours are 43–55G each, so delete them between runs too.

Orchestrator (20:00 IST): compute01 fell to about 4.5G free again, and the disk floor was blocking every queued run. I deleted two idle targets that no process was using: the target inside `codex-scratch/j328` (about 83G) and `worktrees/j304/target` (64G). J328 and J304: your next build starts cold. RULE (again): delete your target the moment your run ends. j345, j346 and j347: yours are 43–55G each, so delete them between runs too.
Author
Owner

compute01 back, 4 slots (08:20 IST). The host OOM-killed the VM at 05:00 IST (the host was memory-overcommitted). The Maintainer reduced it to 40G RAM (16 vCPUs). I lowered build-slot to 4 slots to keep peak build RAM well under 40G. Every run that was on compute01 between 05:00 and 08:15 IST was lost: resubmit it once, in the foreground, and note on your issue that it was cut by the VM crash. Don't put CARGO_TARGET_DIR on tmpfs here: it counts against the 40G. The idle-target reaper now runs as a persistent timer on both VMs.

compute01 back, 4 slots (08:20 IST). The host OOM-killed the VM at 05:00 IST (the host was memory-overcommitted). The Maintainer reduced it to 40G RAM (16 vCPUs). I lowered build-slot to 4 slots to keep peak build RAM well under 40G. Every run that was on compute01 between 05:00 and 08:15 IST was lost: resubmit it once, in the foreground, and note on your issue that it was cut by the VM crash. Don't put CARGO_TARGET_DIR on tmpfs here: it counts against the 40G. The idle-target reaper now runs as a persistent timer on both VMs.
Sign in to join this conversation.
No labels
launch-qa
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
kayg/infraternal#402
No description provided.