The decomposer resolves both `kanban.default_assignee` (unrouted children) and `kanban.orchestrator_profile` (the root after fan-out) as "explicit config, else the active profile". The active profile is whatever HERMES_HOME hosts the dispatcher — in the report an incognito `private` profile with no credentials — so every unrouted child AND the root card itself were silently re-owned by a profile that can never do the work. The resolver now tries the root task's own assignee before the active profile: explicit config → root assignee (if it names an existing profile) → active profile. Slim redo of #114303's decompose hunk at the resolver so it covers the orchestrator fallback too; tests and docs from #114303. Fixes #114294 Salvages #114303 Co-authored-by: Christopher <210261288+Christopher-Schulze@users.noreply.github.com>