[danspark]

Problem

Release run 41323134582 for v0.1.4-nightly.20261027.3796 (source PR #62, merged as 23aa96769) failed three checks. None of them come from the T2 overlay; all three are in upstream code at the pinned commit b88da913 and passed PR CI on 2026-10-28. No release was published.

• Test Server 1: UsageService "reports saved usage of a removed directory only for windows it reaches" reads the wall clock. By 2026-11-01 its 2026-08-01 usage had aged out of retention, so the expected bucket was pruned.
• Test Server 2: the runner image moved to Git 2.56.0. When a worktree's .git file points at a deleted gitdir, Git now says "gitfile does not point to a valid repository" instead of "not a git repository". Storage cleanup therefore reported that worktree as failed rather than kept. Nothing was deleted either way.
• Linux x64 launch check: the fixture threads, last active 2026-10-27, aged past the default auto-settle window. The server settled them on startup and the sidebar hid them in the collapsed Settled shelf, so the check timed out looking for "Release launch check". Its screenshot shows an empty thread list with "Settled 2".

Change

Three overlay rules, one commit each:

• Backport upstream's test fix test(server): pin clock in saved-usage window test pingdotgg/t3code#28603 (1280ccd0d) unchanged, pinning TestClock near the write.
• Storage cleanup also recognizes Git 2.56's invalid-gitfile message. Upstream has not changed this check yet.
• The desktop launch check writes settings.json with sidebarAutoSettleAfterDays: null before launching. Upstream fixed the same failure by editing the binary fixture (ae521d1d7). The overlay patches text, so carrying a copy of that fixture would silently override later upstream fixture changes. This text rule fails loudly if the script changes.

Scope and approval

This is a release-CI compatibility repair within the authorized nightly release task in the linked T3 thread. Privacy protections, analytics overlay rules, dependency versions, lockfiles, update destinations and the Linux x64/ARM64 outputs are unchanged. The pinned upstream tag stays v0.1.4-nightly.20261027.3796.

Verification

• The usage test failed locally on the pinned source. With the backport, which matches upstream's commit line for line, all 40 UsageService tests pass.
• The storage cleanup test failed locally under Git 2.56.0 with the CI error. With the change, all 122 storage cleanup tests pass.
• I ran the candidate server against a copy of the launch fixture. Without the setting, a startup sweep settled both threads. With it, a complete sweep settled neither, and the server kept the setting when it rewrote settings.json. PR CI does not run the packaged launch check, so the release workflow's x64 launch step is the final proof.
• node .github/t2code/overlay.mjs verify passes, all 37 release-control tests pass, and vp run check:changed passes format, lint, Knip, typecheck of 36 packages and the adjacent tests.
• The failed release run stays unpublished. A new release run is needed after this merges.

Model: Claude Opus 5.5. Harness: Claude Code in T3 Code.

🤖 Generated with Claude Code