Source-patch disposition

Seven live-tree diffs were replayed and sorted instead of being silently carried forever.

Result

All seven Phase 0 patches apply cleanly to the Bunsen fork head and current upstream main. Reverse checks fail for all seven, so none is already integrated.

Promote as a cohesive candidate

The TTS/footer behavior spans three source files and three tests. Its targeted gateway tests pass 42/42. Keep it as one reviewable change.

Hold and repair

The cron prompt-scanning toggle patch calls removed get_config(). A companion repair changes it to load_config(); the cron target set passes 23/23. The corrected form should be squashed into one patch before review.

Broad-suite evidence

The combined worktree run recorded 19,005 passed and 22 failed. Two changed cron tests pass in isolation, while the broad run exhibits module-isolation instability; 20 other failures are outside the changed files. This is evidence, not a waiver: neither candidate is merge-ready until a clean promotion worktree satisfies the repository’s full gate.

Boundary

No patch was applied to Herman. No MR was opened. This lane produced a disposition ledger and promotion candidates only.

Falsifier

Reclassify any patch if a clean upstream tree shows it already landed, a forward apply check fails, or the relevant full-suite failures reproduce as regressions caused by the patch bundle.