the binary declares two per-repo config paths the tree never instantiates: rule_privacy reads .abcd/config/pii.json and the launch includes-closure reads .abcd/config/scripts-closure.json, but .abcd/config/ holds neither and no doc mentions them. Both read as optional overrides, so nothing is broken — but code-declared record paths and tree-instantiated ones have no reconciliation check in either direction. Document the two optional files where the config/ members get their index entry, and consider a parity sweep between code path literals and the documented namespace.

the binary declares two per-repo config paths the tree never instantiates: rule_privacy reads .abcd/config/pii.json and the launch includes-closure reads .abcd/config/scripts-closure.json, but .abcd/config/ holds neither and no doc mentions them. Both read as optional overrides, so nothing is broken — but code-declared record paths and tree-instantiated ones have no reconciliation check in either direction. Document the two optional files where the config/ members get their index entry, and consider a parity sweep between code path literals and the documented namespace.

Grounds

• pursued: every path the binary reads under .abcd/ config is named in the namespace index; a code-declared .abcd/config path absent from the index would show it wrong