Align hiring flow and routing templates with squad health validation #2234

Steps

1. delete old squad from repo
2. squad init
3. ask for new team, let it run
4. run squad health, fail
5. ask squad to fix it, many times

Friction report

I asked for a Squad health check and for the team-hiring process to be fixed. The first response changed the default naming guidance but did not make the resulting team pass squad health. After I separately asked to run the check, it failed on routing references. The next response added a health gate to the init instructions but still left the current health failure unresolved, so I had to ask twice for the correction. I also had to separately ask for squad health to be run.

The eventual fix aligned routing targets with registry IDs and removed built-in support agents from routing destinations. squad health then passed.

Root cause

The hiring/routing guidance and health validator disagreed: routing examples used display names (for example, Nick Fury), while the validator resolves registry IDs (for example, nick-fury). Built-in support agents such as Rai and Fact Checker are not cast registry agents and should not be routing targets. The hiring flow also lacked a required health check before declaring a team ready.

Expected behavior

• Init and add-member guidance generates routing entries using the canonical agent IDs the health check accepts.
• Support agents that are not valid routing targets are not added to the routing table.
• Hiring is not reported complete until squad health passes; failures are diagnosed and fixed rather than merely reported.

Related: #1605 (squad health readiness check command).