record_schema's nested-store-root exemption is derived from every value in the record_stores config map, including keys naming no store the scanner knows, so a committed config line such as an unknown prefix pointing at .abcd/work/issues/anything hides that directory from the undeclared-bucket blocker without anything scanning it; the file's own comment says a config that could add a bucket could also hide one and that the list is code, not config. Build the nested set from the code-side recordStores looked up in the config, and refuse unknown record_stores keys at parse.

Frontmatter

.abcd/work/issues/resolved/iss-2608300227224016-record-stores-config-can-hide-a.md
open on GitHub ↗ · commit history ↗

mentions2

• iss-2608300320001985The nested-store-root exemption still blinds record_schema through a known prefix: a committed record_stores line pointing rdi (or dsp, or itd) at another store's declared bucket — .abcd/work/issues/open, or a readings run directory — passes validateRecordStores, marks that bucket a nested root so the parent store skips it, and the misdirected store ignores every file not matching its own filename grammar, so a malformed issue record with five missing required fields yields zero findings; reopens the class iss-2608300227224016 records as closed, whose resolution text is not true as written. Refuse a configured store root that equals or sits inside a declared bucket of any other store, refuse two prefixes resolving to one path, and grant the exemption only when the child is not a bucket the parent declares.
• itd-179The reasoning behind what was pursued no longer evaporates at the gate — readiness and triage record grounds for the conjecture, not only the decision