Interface Assertion Sweep
Assertions at the Interface
A sweep that kept tests on observable contracts rather than rendered sentences.
2 milestones 9 tasks 32 agents
3 plan 9 execute 13 review
200k peak context
135k median execute
2h 38m total 13m 30s per task
4m 34s plan 54m 44s execute 36m 20s review
69 edits 846 commands
codex harness
This run removed prose-sensitive assertions from the Rust and Rails test suites without changing product copy. It kept assertions for typed values, interface tokens, fixture echo, structure, residue, and external output shape, then recorded the second pass and archived the source plan.
How this walkthrough is structured
Feature
What did the run build and ship?
The current tree keeps tests on values and interface presence while the archived plan and accounting retain the rule and its scope.
Build
How did Gantry structure the work?
The cut separated the Rust-side rule from the Rails sweep and closeout, leaving each milestone a bounded assertion audit.
Milestone 1
Rust Assertion Sweep
6 tasks 17 agents 1h 30m wall time 200k peak context
The Rust tests now retain timeout state, interface keys, paths, and enabled-state facts instead of pinning explanatory text. Command verification checks the timeout value and captured output without asserting the appended timeout sentence. Reference-dataset and TUI tests likewise check named entries or the presence of a disabled reason rather than its rendered wording.
The milestone carried the Rust, tool, and screencast assertion census, while leaving Rails work and closeout to the following milestone. Its brief gave the agent a concrete rule for separating stable observables from sentences produced by the code. The ledger records the milestone as green, and the run facts record no recovery or re-plan for the run.
Milestone 2
Web Second Pass Closeout
3 tasks 11 agents 50m 26s wall time 175k peak context
The Rails accounting document states that surviving text assertions are limited to observable interfaces and records the second pass. The replay public-pages test now checks that Gantry branding is present rather than matching full authored phrases. The source plan is archived, and its execution note points readers to the assertion analysis that records the completed sweep.
The remaining milestone combined the Rails assertion sweep with the cross-tree second pass, accounting, and plan closeout. That boundary let the Rust-side rule become an input to a separate audit of selectors and longer string expectations. The ledger records this milestone as green; the run facts record no retry, recovery, or re-plan.