The capture write's --found-at refusals exit 1 though they are the caller's input with nothing written: internal/core/capture/foundat.go checkFoundAt returns plain errors for a path that leaves the checkout or does not exist in it, so abcd capture --found-at ../outside and --found-at does/not/exist.go exit 1, while commands/capture.md and brief 06-capture say a flag value outside its shape or naming nothing exits 2 on the capture write alike. They should unwrap to capture.ErrRequestRefused; a path that could not be checked for another reason is a fault reading the checkout and stays exit 1.

The capture write's --found-at refusals exit 1 though they are the caller's input with nothing written: internal/core/capture/foundat.go checkFoundAt returns plain errors for a path that leaves the checkout or does not exist in it, so abcd capture --found-at ../outside and --found-at does/not/exist.go exit 1, while commands/capture.md and brief 06-capture say a flag value outside its shape or naming nothing exits 2 on the capture write alike. They should unwrap to capture.ErrRequestRefused; a path that could not be checked for another reason is a fault reading the checkout and stays exit 1.

Grounds

• pursued: capture --found-at naming a path outside or absent from the checkout exits 2 and writes nothing; either exiting 1, or an unsearchable directory on the way exiting 2, would show it wrong