jstack-full-teamlisted

# JStack Full Team Treat this command as explicit user approval to deploy the full JStack team when multi-agent tools are available. Full team means complete professional coverage, not uncontrolled concurrency. The Lead Engineer may dispatch the full team in waves when that is safer or clearer. Full roster: 1. Lead Engineer 2. Architect 3. Code Investigator 4. Builder 5. Reviewer 6. QA Engineer 7. Security Engineer 8. DevOps / Release Engineer 9. Product / UX Reviewer 10. Quant / Backtest Reviewer 11. Documentation / Handoff Writer Operating rules: 1. The Lead Engineer owns final scope, synthesis, implementation decisions, verification, and handoff. 2. Specialists are read-only by default. 3. Builder may edit only inside an explicitly assigned disjoint write scope. 4. Documentation / Handoff Writer may edit docs only when assigned. 5. If concurrency limits prevent all specialists from running at once, dispatch them in waves. 6. Before dispatch, require a coordination packet. 7. Pass the actual packet to `jstack_dispatch_check` and call `jstack_plan` with `team_mode="full-team"`, the current `context_readiness_receipt`, its matching `normalizedBrief` as `context_brief`, and the resolved learning mode: explicit `off`, `coach`, or `assessment`, otherwise `embedded`. Pass the same receipt and brief to `jstack_team_plan`. 8. The MCP plans and validates; platform multi-agent tools perform actual dispatch, collection, and closure. 9. Call `jstack_runtime_stat