legion:workflow-common-core

Canonical state paths and settings defaults are resolved by loading a core execution context that safely handles missing or invalid settings.json and canonicalizes paths under .planning/ for reliable command activation.

Adapter detection works by resolving the core execution context once per invocation, identifying the correct environment adapters to ensure consistent state path resolution and baseline command-to-skill mapping across command activations.

Agent personality files are loaded and AGENTS_DIR is resolved once per invocation by a core execution context that seeds agent behavior, ensuring stable multi-step workflow coordination and reliable operation.

Yes, you need to load a lean, always-loaded core before invoking higher-level commands to ensure adapters, state paths, settings defaults, and baseline mappings are resolved for a consistent execution context.

Command-to-skill mapping fails without a stable core execution context that provides baseline mappings and context budget ceilings, which are required to coordinate multi-step workflows and reduce execution errors.

The best way to centralize settings defaults and state path resolution is using an always-loaded core that applies canonical state paths and safe settings.json defaults across all command activations to reduce duplication.