apm-review-panel

# APM Review Panel - Fan-Out Advisory Review The panel is FAN-OUT + SYNTHESIZER. Each persona runs in its own agent thread (via the `task` tool) and returns JSON matching `assets/panelist-return-schema.json`. The orchestrator schema-validates each return, hands all returns to the apm-ceo synthesizer (also a task thread, returns JSON matching `assets/ceo-return-schema.json`), then renders ONE recommendation comment from `assets/recommendation-template.md`. This skill is ADVISORY by design. It does not compute a binary verdict, it does not apply verdict labels, and it does not gate merge. The panel surfaces findings; the maintainer and the PR author decide ship. ## Architecture invariants - **Advisory regime, not gate regime.** There is no `APPROVE` / `REJECT`, no `panel-approved` / `panel-rejected` label, no deterministic verdict computation. The CEO returns a `ship_recommendation.stance` (`ship_now` / `ship_with_followups` / `needs_discussion` / `needs_rework`); this is prose for the human reviewer, never auto-applied as a label or status check. This is the architectural fix for the previous regime's over-strictness: removing the binary gate removes the incentive for panelists to inflate `required[]` defensively. - **Three severity buckets, none of them gate.** Findings carry `severity: blocking | recommended | nit`. `blocking` is the highest signal a panelist can send and renders prominently in the comment; it still does not block merge. `recommended`...