claw/docs/superpowers/reports/2026-04-19-timeout-rerun-hygiene-integration-report.md

Timeout Rerun Hygiene Integration Report

Date: 2026-04-19 Plan: docs/superpowers/plans/2026-04-19-timeout-rerun-hygiene-integration-plan.md Follow-up input: tests/fixtures/generated_scene/structured_fail_closed_improvement_followup_2026-04-19.json Hygiene input: tests/fixtures/generated_scene/timeout_budget_rerun_hygiene_2026-04-19.json

Scope

This integration only changes the reporting and reconciliation interpretation layer.

It does not:

1. change analyzer or generator code
2. rerun the 102 sweep
3. update scene_execution_board_2026-04-18.json
4. promote scenes
5. start timeout implementation fixes

Raw Follow-Up Timeout Summary

The raw follow-up sweep still reports:

Raw status	Count
source-unreadable	3

Hygiene-Aware Timeout Interpretation

After applying the timeout rerun hygiene overlay, the same three records become:

Hygiene interpretation	Count
timeout-as-pass-candidate	2
timeout-as-fail-closed-candidate	1
timeout-still-unreadable	0
timeout-rerun-error	0

Overlay Records

Scene id	Scene	Raw status	Hygiene status	Hygiene interpretation
sweep-015-scene	????	source-unreadable	rerun-resolved-pass	timeout-as-pass-candidate
sweep-025-scene	??????????	source-unreadable	rerun-resolved-pass	timeout-as-pass-candidate
sweep-040-scene	?????	source-unreadable	rerun-resolved-fail-closed	timeout-as-fail-closed-candidate

Interpretation

1. The raw follow-up timeout count remains preserved as 3.
2. The hygiene-aware layer shows that none of these three records should remain grouped as hard unreadable sources.
3. Two timeout records are better understood as budget-sensitive pass candidates.
4. sweep-040-scene is better understood as a budget-sensitive fail-closed candidate, not as a persistent unreadable source.
5. Future reconciliation and coverage reporting should use both views together:
   • raw timeout count
   • hygiene-aware timeout interpretation

Conclusion

Timeout rerun hygiene is now integrated into a reconciliation-friendly reporting layer.

This integration is reporting-only. It does not update scene status, execution board state, or promotion state.

The next use of this integration should be inside future sweep/reconciliation reporting so raw source-unreadable and hygiene-aware timeout interpretation are published together.