business-analyst persona: register in canary-rings.json + promote past draft (incubator prereq)

[don-petry]

Part of the fleet-promotion delivery (Epic #781) — the business-analyst persona prerequisites so it can reach incubator by riding the persona-mention router (BA has no dedicated reusable). These are gaps found while mapping the Epic; they do NOT need persona-mention's rings, but BA can't route in incubator until BOTH these AND the persona-mention sweep (#785) land.

Gaps (verified)

• personas/business-analyst/persona.yml declares canary.agent: business-analyst, but business-analyst is NOT in petry-projects/.github standards/canary-rings.json (dangling reference).
• The persona is status: draft. Its evals/business-analyst/{dev,holdout} and the org team business-analyst (closed, notifications disabled) already EXIST.

Steps

1. Register business-analyst in standards/canary-rings.json (petry-projects/.github) — mirror the shape of another advisory/persona agent; edit as TEXT, not a JSON round-trip (mixed encoding, insertion order). Its runtime is the shared persona-mention router, so ring membership follows persona-mention.
2. Promote personas/business-analyst/persona.yml past draft once validate-personas.py passes with evals present and the team gating is satisfied.
3. Confirm validate-personas.py and any canary-rings validator stay green.

Acceptance criteria

• business-analyst resolves in canary-rings.json (no dangling canary.agent).
• persona.yml status advanced past draft; validators green.
• No behavioral change to the router; BA remains advisory/mention-triggered.

[don-petry]

Tracked under fleet-promotion Epic #781 (business-analyst → incubator prereqs; BA rides the persona-mention router, so incubator routing also needs the #785 sweep).

[don-petry]

Dev-Lead: implementation deferred — automation PR queue is full

No pull request was opened for issue #814. The org-wide
open-automation-PR queue is currently at its signed-off cap (see
standards/pr-limits.json in petry-projects/.github).

This issue stays labeled dev-lead and will be re-attempted automatically once
the queue drains — no action is required.