Pawprint dispatch · one consequential repair
The schedule went read-only.
The action should have too.
ADS caught the contradiction, disabled the write action, kept Retry available, and proved every unrelated state stayed untouched.
- Contradiction
- 1 caught
- Changed captures
- 2 of 8
- Preserved action
- Retry
“Read-only schedule” appeared beside an active New walk action.
The contradiction
See the exact state boundary.
At a readable size.
The evidence leads. Baseline, repaired, and diff modes keep the changed control in context; full-resolution originals remain one step away.
×The page says read-only while the write action still looks available.
✓The mutation is natively disabled. Retry remains the active recovery path.
How ADS got there
One case through the existing
five-stage workshop.
No new story system. This repair moves through the same assembly line the homepage teaches.
- 01Intent
Keep dispatch usable when the connection drops.
- 02Baseline
Load Pawprint’s states, actions, and existing UI.
- 03Rubric
Check every nearby action against the state contract.
- 04Evidence
Compare changed captures and preserve the originals.
- 05Release
Separate grader, frozen run, auditable packet.
The result
One action changed.
Six captures did not.
The repair is narrow enough to explain and complete enough to trust. The page shows both.
Error state only, desktop and mobile.
Supporting evidence
The proof packet stays available.
It does not lead the story.
- Screenshots
- 8 / 8
- Serious axe violations
- 0
- Horizontal overflow
- None
- Targets under 44px
- 0
- Maximum CLS
- 0.00000
- Fresh rerun delta
- 0%
OutcomeWhat success meantBuilderWhat changedGraderWhat was verifiedExpand packet +
Use the same loop