Local check routes an incomplete generated-cache inventory to human review during concurrent tests

[pengfei-threemoonslab]

Problem

During #557 validation, shipgate check --agent codex --format agent-boundary-json ran while the full pytest suite was active. It returned human_review_required, all permissions false, with Directory inventory could not complete at tests/__pycache__. No release declarations or protected workflow edits were involved. The repository was then left unchanged until tests exited; a fresh read-only verifier completed and current control returned passed / complete.

This is an observed local workflow interruption. Concurrent cache creation is a plausible cause, but the present diagnostic does not establish whether the directory changed during capture, hit a bound, or encountered another reader failure. Do not label that cause proven from the path alone.

Proposed direction

Use the actual identity-reader failure origin to distinguish a recoverable unstable input snapshot from a semantic/human-owned decision. Where sound, provide a bounded retry after the writer is quiescent, preserving captured-input identity and real trust-root review. Examine whether generated cache inventory is needed for recognized host coverage before changing traversal; do not blindly skip paths or turn incomplete reads into success.

Acceptance

• A deterministic fixture reproduces the relevant generated-directory inventory failure during a local check.
• The diagnostic identifies its typed cause and an exact safe next step without relying on exception-text inference.
• A quiescent rerun obtains new evidence; no cached denial or cached completion overrides it.
• Genuine missing, unreadable or protected capability inputs remain fail-closed and human-owned decisions retain their existing route.

Sequencing

Deferred from #557, which validates after tests are quiescent. Related #547 delivered bounded recovery metadata; #588 owns deeper typed shared-reader provenance. This issue owns the concurrent local test/check workflow and appropriate recovery routing.