Say why the stable route proof failed #6

Merged

eureka merged 2 commits from routing-proof-reason into main

2026-11-14 01:34:35 +00:00

eureka commented

2026-11-13 18:58:05 +00:00

Owner

Follow-up idunn-deploy-provenance:follow_up:chat-mind-20261113T162719900Z-t62 (live web deploy tx-216475c6 failed only with 'the Routing phase passed its deadline').

advance_routing journals each failed prove_stable_route once per distinct reason (existing report_once/ReportOnce, cleared on recovery): silent (nothing answered), refused (HTTP status line, etc.), presence not active, authority disagreement, challenge-binding failures. Texts name states and codes only.
The phase-deadline cause now appends the step's last_error ("; its last attempt failed: ..."), so the abort record and idunn status --command show the reason instead of only the clock. status already rendered last_error as 'waiting on' while the phase is live.
No persisted type, schema or new abstraction: two small helpers and one call site pair.

Tests: unit tests for each failure class text, report-once and clear, and the deadline abort carrying the proof failure. 44 route_proof-filtered tests fail identically on main and this branch under uid 985 (environment); not caused by this change.

🤖 Generated with Claude Code

Follow-up idunn-deploy-provenance:follow_up:chat-mind-20261113T162719900Z-t62 (live web deploy tx-216475c6 failed only with 'the Routing phase passed its deadline'). - `advance_routing` journals each failed `prove_stable_route` once per distinct reason (existing `report_once`/`ReportOnce`, cleared on recovery): silent (nothing answered), refused (HTTP status line, etc.), presence not active, authority disagreement, challenge-binding failures. Texts name states and codes only. - The phase-deadline cause now appends the step's `last_error` ("; its last attempt failed: ..."), so the abort record and `idunn status --command` show the reason instead of only the clock. `status` already rendered `last_error` as 'waiting on' while the phase is live. - No persisted type, schema or new abstraction: two small helpers and one call site pair. Tests: unit tests for each failure class text, report-once and clear, and the deadline abort carrying the proof failure. 44 route_proof-filtered tests fail identically on main and this branch under uid 985 (environment); not caused by this change. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

eureka added 1 commit

2026-11-13 18:58:05 +00:00

Say why the stable route proof failed: journal each distinct reason, keep it in the deadline abort a484a7ec17

advance_routing now logs the proof failure (silent, refused with the HTTP
status line, presence not active, authority disagreement) once per distinct
reason, and the Routing deadline abort carries the step's last failure
instead of only the clock. No persisted type or schema changes.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

eureka added 1 commit

2026-11-14 01:23:51 +00:00

Test the route-proof report through advance_routing: reported once per reason, cleared on recovery; deadline abort carries the proof's own failure text 88e2f24cc6

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

eureka commented

2026-11-14 01:34:34 +00:00

Author

Owner

Soul (two passes, a484a7e and 88e2f24): pass with findings, tests-only fix verified, mutations M1/M5/M7 now killed. Open, accepted: the continuity test pins text stability, not print count, so a mutant that prints every tick while keeping the text stable survives (M6c); dedup is the existing report_once owner, tested at its other call sites. Also noted: installs/driver errors in advance_routing are not journalled (status shows them), dedup is same-as-last not per-distinct-reason, and the reason text prints twice (ChallengeFailure Display plus source, predates this PR). Merging as steward; these go to a follow-up.

Soul (two passes, a484a7e and 88e2f24): pass with findings, tests-only fix verified, mutations M1/M5/M7 now killed. Open, accepted: the continuity test pins text stability, not print count, so a mutant that prints every tick while keeping the text stable survives (M6c); dedup is the existing report_once owner, tested at its other call sites. Also noted: installs/driver errors in advance_routing are not journalled (status shows them), dedup is same-as-last not per-distinct-reason, and the reason text prints twice (ChallengeFailure Display plus source, predates this PR). Merging as steward; these go to a follow-up.

eureka merged commit 7eae1c4ee1 into main

2026-11-14 01:34:35 +00:00

eureka referenced this pull request from a commit

2026-11-14 01:34:36 +00:00

Say why the stable route proof failed (#6)

No reviewers

No labels

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

GameCult/Idunn!6

No description provided.

Rows
Columns