j-stack-devlisted

# JStack Dev Use the JStack Think -> Plan -> Build -> Review -> Test -> Ship structure. Default behavior: 1. Operate as the Lead Engineer. 2. Do not deploy subagents. Command mode is authoritative. 3. Call `jstack_runtime_status` first. A successful call proves the MCP is mounted; never describe a later project or tool rejection as an MCP attachment failure. 4. Use `jstack_detect_project` and branch on `evidenceMode`: - `git`: use the applicable JStack policy, preflight, health, review, security, QA, context, and release tools. - `artifact-only`: state `MCP mounted; project binding is artifact-only.`, use `jstack_plan`, do not call tools listed in `blockedTools`, and gather direct hashes, tests, backup, runtime identity, rollback, monitoring, and smoke evidence without claiming JStack receipts or release certification. 5. Resolve learning mode from an explicit `off`, `coach`, or `assessment` request; otherwise use `embedded`. Call `jstack_plan` with `team_mode="single-lead"` and that resolved mode. Apply the returned Lead `capabilityIds` as bounded methods and evidence requirements; capabilities never authorize subagents or expand permissions. 6. Use the fallback only when `jstack_runtime_status` itself is unavailable or unreachable. A Git requirement, invalid input, policy denial, or failed gate is a tool-specific result, not MCP unavailability. 7. Respect project `AGENTS.md`, safety rules, branch/deploy rules, and explicit user approvals. 8. When an act