capture resolve --commit wants the sha of the commit that fixed the record, so the resolution is a second commit by construction: the lane commits the fix, runs capture resolve --commit <that sha>, and commits the ledger move with the Resolves: trailer on the second commit. Every one of the pilot run's four lanes produced this pair, and AGENTS.md's rule that a fix resolves its record in the same change is met only by the pair, never by one commit. Wanted: either resolve accepts a placeholder the post-commit stamp fills (the reachability gates RS002/RS003 already verify the sha after the fact), or the surface page states the two-commit shape as the documented protocol so an implementer stops trying to make it one.

capture resolve --commit wants the sha of the commit that fixed the record, so the resolution is a second commit by construction: the lane commits the fix, runs capture resolve --commit <that sha>, and commits the ledger move with the Resolves: trailer on the second commit. Every one of the pilot run's four lanes produced this pair, and AGENTS.md's rule that a fix resolves its record in the same change is met only by the pair, never by one commit. Wanted: either resolve accepts a placeholder the post-commit stamp fills (the reachability gates RS002/RS003 already verify the sha after the fact), or the surface page states the two-commit shape as the documented protocol so an implementer stops trying to make it one.

Grounds

• pursued: implementers follow the documented pair instead of trying to make it one commit; a lane again forcing fix and resolution into one commit would show it wrong