Evidence
Main commit 6e24bcb, Debian run https://github.com/LucaLin233/Linux/actions/runs/34237080747: partial batch (good1 bad1 good2) entered lifecycle failure before good2 was scheduled. The next all-failure batch was blocked by the retained barrier; expected 2 failure records, got 0. Old assert_fail accepted any nonzero status and hid the first contract violation.
Current status
Root cause remains unknown. #51 merged as dc58996 strengthens exact status/flags/accounting assertions and eight consecutive rounds, without production wrappers or barrier resets. Its pre-merge full CI 34249483414 passed both environments. #52 addresses independently reproduced HUP substitution parsing failures, not a proven cause of this batch failure. Green runs do not prove resolution.
The user explicitly accepted deferring this unresolved anomaly. Do not treat it as fixed, or rerun unchanged jobs to hide a recurrence.
Next investigation
Capture the first internal failing boundary and lifecycle state before teardown. Preserve PID/start identity checks, cleanup grace, registration/session ownership validation and fail-closed barriers. No speculative production changes. Keep probes bounded and use CI, not production-host behavior tests.
Acceptance
Explain the causal failure path; add a deterministic regression or adequately justified targeted reproducer; verify both Ubuntu 24.04 and Debian 13 full suites without weakening assertions. See docs/push-batch-investigation.md and PR #51 review notes.
Evidence
Main commit 6e24bcb, Debian run https://github.com/LucaLin233/Linux/actions/runs/34237080747: partial batch (good1 bad1 good2) entered lifecycle failure before good2 was scheduled. The next all-failure batch was blocked by the retained barrier; expected 2 failure records, got 0. Old assert_fail accepted any nonzero status and hid the first contract violation.
Current status
Root cause remains unknown. #51 merged as dc58996 strengthens exact status/flags/accounting assertions and eight consecutive rounds, without production wrappers or barrier resets. Its pre-merge full CI 34249483414 passed both environments. #52 addresses independently reproduced HUP substitution parsing failures, not a proven cause of this batch failure. Green runs do not prove resolution.
The user explicitly accepted deferring this unresolved anomaly. Do not treat it as fixed, or rerun unchanged jobs to hide a recurrence.
Next investigation
Capture the first internal failing boundary and lifecycle state before teardown. Preserve PID/start identity checks, cleanup grace, registration/session ownership validation and fail-closed barriers. No speculative production changes. Keep probes bounded and use CI, not production-host behavior tests.
Acceptance
Explain the causal failure path; add a deterministic regression or adequately justified targeted reproducer; verify both Ubuntu 24.04 and Debian 13 full suites without weakening assertions. See docs/push-batch-investigation.md and PR #51 review notes.