`abcd <iss-N>` answers that the record is not found in the issue ledger when the record's file is there but was skipped on read, for example because it still carries a retired property such as `promoted_to`. describeIssue in internal/core/record/record.go reads only the parsed issues and never the skipped roster, so an adopter with an unmigrated ledger gets a false 'not found' with no hint to run `abcd capture migrate --apply`, while `abcd capture list` beside it names the remedy. The shape predates the related-links rename; the rename widens it to every unmigrated record.

abcd <iss-N> answers that the record is not found in the issue ledger when the record's file is there but was skipped on read, for example because it still carries a retired property such as promoted_to. describeIssue in internal/core/record/record.go reads only the parsed issues and never the skipped roster, so an adopter with an unmigrated ledger gets a false 'not found' with no hint to run abcd capture migrate --apply, while abcd capture list beside it names the remedy. The shape predates the related-links rename; the rename widens it to every unmigrated record.

Grounds

• pursued: we expect an adopter with an unmigrated ledger to be told where the record is and how to repair it; shown wrong if abcd <iss-N> answers not found for a file present in the ledger, or omits the remedy that capture list prints beside it