Parked from DPLAN-0206 (memory config relocation).
custom_config/ is the de-facto home for operator-editable runtime config (e.g. hooks_json/custom_config/cadence_config.json, and now memory_json/custom_config/memory.config.json) — it separates human-tunable settings from auto-generated logs/data at the _json/ root. But it is NOT codified: the json_structure standard says "{branch}_json/ root, one directory, no splits" and the checker does not recognize the subdir.
Proposal: bless custom_config/ as the standard location for human-editable config under {branch}_json/. Update json_structure_content.py + the checker + docs so it stops being an undocumented @hooks convention.
Low priority — park for whenever. Ref: DPLAN-0206, seedgo consult msg 948ae990.
Parked from DPLAN-0206 (memory config relocation).
custom_config/ is the de-facto home for operator-editable runtime config (e.g. hooks_json/custom_config/cadence_config.json, and now memory_json/custom_config/memory.config.json) — it separates human-tunable settings from auto-generated logs/data at the _json/ root. But it is NOT codified: the json_structure standard says "{branch}_json/ root, one directory, no splits" and the checker does not recognize the subdir.
Proposal: bless custom_config/ as the standard location for human-editable config under {branch}_json/. Update json_structure_content.py + the checker + docs so it stops being an undocumented @hooks convention.
Low priority — park for whenever. Ref: DPLAN-0206, seedgo consult msg 948ae990.