skip to content
Replays

Restoring a Silently Reverted TUI Layout

Re-applying dropped layout commits by hand, then pinning them with a test the gate never had.

Gantry sprints

0 milestones 2 sprints

Re-applying dropped layout commits by hand, then pinning them with a test the gate never had.

21m 34s total 7m 30s per sprint

5.3M tokens in 58.8k tokens out

$7.69 nominal cost

Gantry's terminal monitor had gained a left rail made from stacked about and sprint cards, with the activity feed beside it. A later menu-makeover integration dropped those hand-written layout commits when its conflict resolver kept the branch side, and the test suite did not describe the missing shape.

This job restored the visible TUI behavior on top of code that had moved, then added render assertions so the intended structure became something the gate could check.

How this walkthrough is structured

Feature

What did the run build and ship?

The tree still carries the stacked sidebar-card structure and tests that inspect the drawn layout, while later layout work replaced the restored equal split with adaptive sizing and a draggable divider.

Build

How did Gantry structure the work?

The cut separated hand reconciliation from test coverage: first a narrow agent reapplied known TUI diffs onto changed context, then another converted the missing visual contract into render assertions.

Restore Layout Structure

0 agents 6m 37s wall time 18.2k tokens out $2.97 nominal cost

The current renderer still has a dedicated sidebar-card helper and a sidebar that stacks an about card over the sprints or milestones card. The standalone activity label remains absent from the rail, and the follow state is still rendered on the section header. The exact equal-column sizing this sprint restored can no longer be isolated: current drawing uses a capped, centered default and a user-set proportional branch, with mouse routing based on the recorded divider column rather than the old fixed sidebar width.

This sprint carried the risky reconciliation. Its brief gave the agent the dropped commits, the handover document, and the exact places where the menu makeover had shifted surrounding code, so the job was not an open-ended TUI redesign. The boundary was small enough for a fresh agent because it touched the render and input surfaces only, preserving the current sidebar visibility wrapper while restoring the named layout behavior. The run facts show that boundary held: the sprint passed without a retry, fix pass, or re-plan.

Add Layout Snapshot Test

0 agents 8m 23s wall time 28.2k tokens out $3.08 nominal cost

The render tests now exercise the real draw path and inspect structural signals from the frame instead of relying on a full-screen fixture alone. Later layout work changed the sizing assertions to cover capped default placement, narrow-window fill, and user-owned proportional splits, but the stacked-card test still checks the about card above the sprint card and the absence of the old activity row. The original equal-width assertion has been superseded; the durable contribution is layout-specific test coverage around the TUI shape.

After the layout was back, this sprint had a narrower job: make the lost visual contract executable. The brief pointed the agent at the existing render-test harness and asked for assertions that would fail against the reverted fixed rail and single-panel sidebar. Because production behavior had already landed, the unit could stay in test code and test helpers. It also stayed green, with no recovery or review-driven change to the plan.