findRecordFile treats any os.ReadDir failure as an empty bucket, so an unreadable (not absent) intent/spec bucket — mode 000, or a symlinked bucket dir — makes capture promote --intent and capture resolve --intent/--spec report 'not found in the store' instead of the actual I/O error; the old intent.Load path in promote link mode reported the read error and refused symlinked buckets. Still fail-closed (nothing written), but the diagnostic lies about the cause.

findRecordFile treats any os.ReadDir failure as an empty bucket, so an unreadable (not absent) intent/spec bucket — mode 000, or a symlinked bucket dir — makes capture promote --intent and capture resolve --intent/--spec report 'not found in the store' instead of the actual I/O error; the old intent.Load path in promote link mode reported the read error and refused symlinked buckets. Still fail-closed (nothing written), but the diagnostic lies about the cause.

Grounds

• pursued: an operator told a linked record is missing can trust that it is missing; a symlinked bucket still answered as not found or followed would show it wrong