abb5b747 fixed the expansion gap for plugin_dir/module_dir/skills_dir and #1143 recorded the four plugin-settings dirs as deliberately free-form. Not yet examined for the same two questions: eda_playbook_dir, playbook_dirs, workflow_routing_file, workflow_labels_file and the MCP work_dir (all found unvalidated during that lane). The specific question is whether config.example.toml advertises a ~ path for any of them while applyGeneralDefaults expands only SecretEngineDir/WorkDir/StateDir/Chat.Workspace - i.e. whether the example tells an operator to write a path that resolves nowhere. Per AGENTS.md this is the 'a field that parses is not a field that works' shape; check the example against applyGeneralDefaults rather than adding validators.
Imported from beads archie-core-v7gw · GitHub #1382 · type task · priority P3 · created 2026-09-30
abb5b747 fixed the expansion gap for plugin_dir/module_dir/skills_dir and #1143 recorded the four plugin-settings dirs as deliberately free-form. Not yet examined for the same two questions: eda_playbook_dir, playbook_dirs, workflow_routing_file, workflow_labels_file and the MCP work_dir (all found unvalidated during that lane). The specific question is whether config.example.toml advertises a ~ path for any of them while applyGeneralDefaults expands only SecretEngineDir/WorkDir/StateDir/Chat.Workspace - i.e. whether the example tells an operator to write a path that resolves nowhere. Per AGENTS.md this is the 'a field that parses is not a field that works' shape; check the example against applyGeneralDefaults rather than adding validators.
---
_Imported from beads `archie-core-v7gw` · GitHub #1382 · type task · priority P3 · created 2026-09-30_
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
abb5b747fixed the expansion gap for plugin_dir/module_dir/skills_dir and #1143 recorded the four plugin-settings dirs as deliberately free-form. Not yet examined for the same two questions: eda_playbook_dir, playbook_dirs, workflow_routing_file, workflow_labels_file and the MCP work_dir (all found unvalidated during that lane). The specific question is whether config.example.toml advertises a ~ path for any of them while applyGeneralDefaults expands only SecretEngineDir/WorkDir/StateDir/Chat.Workspace - i.e. whether the example tells an operator to write a path that resolves nowhere. Per AGENTS.md this is the 'a field that parses is not a field that works' shape; check the example against applyGeneralDefaults rather than adding validators.Imported from beads
archie-core-v7gw· GitHub #1382 · type task · priority P3 · created 2026-09-30