Yeachan-Heo f91d156f85 Keep poisoned test locks from cascading across unrelated regressions ...

The repo-local backlog was effectively exhausted, so this sweep promoted the
newly observed test-lock poisoning pain point into ROADMAP #74 and fixed it in
place. Test-only env/cwd lock acquisition now recovers poisoned mutexes in the
remaining strict call sites, and each affected surface has a regression that
proves a panic no longer permanently poisons later tests.

Constraint: Keep the fix test-only and avoid widening runtime behavior changes
Rejected: Refactor shared helper signatures across broader call paths | unnecessary churn beyond the remaining strict test sites
Confidence: high
Scope-risk: narrow
Reversibility: clean
Directive: These guards only recover the mutex; tests that mutate env or cwd still must restore process-global state explicitly
Tested: cargo fmt --all --check
Tested: cargo clippy --workspace --all-targets -- -D warnings
Tested: cargo test --workspace
Tested: Architect review (APPROVE)
Not-tested: Additional fault-injection around partially restored env/cwd state after panic
Related: ROADMAP #74

2026-04-12 13:52:41 +00:00

..

bundled

wip: plugins progress

2026-04-01 07:09:06 +00:00

src

Keep poisoned test locks from cascading across unrelated regressions

2026-04-12 13:52:41 +00:00

Cargo.toml

fix: resolve all post-merge compile errors

2026-04-01 18:59:55 +09:00