Repository navigation
Disposable Git fixtures can outlive synchronous commits through detached maintenance #203
Description
OAuth PR #202 final Comprehensive run 40589229879 failed on Node 22.18 with ENOTEMPTY during strict cleanup of two disposable Git fixtures (.git and .git/objects). Both invalid-option assertions completed; failures were teardown hooks.
CI used Git 2.55.0. The CLI exits before provenance collection for these invalid arguments. Independent same-version probing found detached maintenance after every fixture commit (12/12); repository-local maintenance.auto=false suppressed it (12/12). Ten baseline traces recorded descendant activity after the synchronous parent exited. The exact ENOTEMPTY was not reproduced locally; maintenance as the particular CI writer remains an evidence-backed inference, while its process-lifetime hazard is confirmed.
Acceptance: disable automatic maintenance only in owned disposable repositories before their first commit; retain strict removal without retries; add a real Git trace regression that fails old setup and proves no maintenance launch; pass CLI/harness and final supported-Node CI. No global or developer-repository Git settings should change.
I am implementing this in fix/fixture-git-maintenance-20261027 from reviewed Router head 8c4a21b, separately from OAuth logic.
Activity
mvalancy commentedon Oct 28, 2026
The owned-repository Git maintenance correction (#204) and real Git trace regression are integrated. Final Node 22.18 and Node 24 Comprehensive suites pass strict fixture cleanup. Earlier ENOTEMPTY and the first post-integration LOD failure remain retained; the latter was corrected through #207 and is now green in the final integrated branch. No global or developer-repository Git settings changed.
Verified integrated
devhead:780a7599d1d7949d5e0fac56091f0b07bb0e6e0d, complete treecffa8b8a7903b9609603f1c42978511d900678f6, identical to independently reviewed and tested source525ca4e5aa5bd4a918ad85165d0f2a0e8caf59ac.Final integrated CI and Comprehensive Tests passed every applicable job. Downloaded strict reports contain smoke 6, new-user 42, LOD 2, routes 7, mobile 27 and performance 3 passing cases, with zero failures, warnings, skipped cases, evidence errors, timeouts or nonzero exits. Both supported Node versions, real Neo4j, all three runtime images, effects and showcase passed. The main/nightly-only production job was inapplicable to this dev run; it is not credited as a pass. Earlier failures and cancelled intermediate runs remain retained.
Integration used the owner's standing dev-only native admin authorization after independent exact-head review; that is not a non-author GitHub approval. Main remains
775362eace0723c57b7ba3c7936645c9d0d36cb4. No release, deployment or protection change occurred. Closing this bounded implementation issue after final branch acceptance, not claiming hosted or deployed-site clearance.