squad watch --execute: spawned session does not receive specialist charter (only generic Ralph prompt) #1081

When squad watch --execute picks up an issue labeled squad:{member}, does it actually delegate to that specialist (with their charter, history, decisions) — or does it just spawn a generic Copilot session that does the work itself?

What I''m seeing: PRs from watch mode don''t follow the assigned member''s charter conventions, which makes me think the charter never reaches the model. Is that intentional?

Relevant code in dist/cli/commands/watch/capabilities/execute.js — buildAgentPrompt() fallback when .squad/ralph-instructions.md is absent:

function buildAgentPrompt(issues, teamRoot) {
    const ralphInstructionsPath = path.join(teamRoot, ".squad", "ralph-instructions.md");
    if (existsSync(ralphInstructionsPath)) {
        // ...defers to .squad/ralph-instructions.md
    }
    // Generic fallback — no charter, no squad:{member} role mapping
    return `You are Ralph, the autonomous work executor for this squad.
Pick up the following issue(s) and complete them:
${issueList}
...`;
}

The squad:{member} label is only used as a filter in findExecutableIssues — it''s never threaded into the spawn prompt as a role assignment.