Follow-up from #60.
config.example.json has a _comments block and config.user.example.json has _purpose and _notes. These flow through the jq -s 'reduce .[] as $x ({}; . * $x)' merge into the final REMEMBER_CONFIG. Today they're harmless — nothing iterates all keys — but this could trip up future config validation, schema checks, or anything that flags unknown keys.
Proposal: during config merge in scripts/lib-memory-dir.sh, filter out keys prefixed with _ before producing the final merged config. Convention: _* keys are user-facing documentation, never runtime data.
jq -s 'reduce .[] as $x ({}; . * $x) | with_entries(select(.key | startswith("_") | not))'
Follow-up from #60.
config.example.jsonhas a_commentsblock andconfig.user.example.jsonhas_purposeand_notes. These flow through thejq -s 'reduce .[] as $x ({}; . * $x)'merge into the finalREMEMBER_CONFIG. Today they're harmless — nothing iterates all keys — but this could trip up future config validation, schema checks, or anything that flags unknown keys.Proposal: during config merge in
scripts/lib-memory-dir.sh, filter out keys prefixed with_before producing the final merged config. Convention:_*keys are user-facing documentation, never runtime data.jq -s 'reduce .[] as $x ({}; . * $x) | with_entries(select(.key | startswith("_") | not))'