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. Inspect project instructions, stack, relevant files, and durable context, then call `jstack_context_readiness` with `workflow_mode="j-stack-dev"`. Supply source-attributed facts, separate assumptions, and only material open questions. If it returns questions, ask no more than three in normal chat, explain why each matters, and show its recommended default. Clear prompts ask nothing. Reuse answers, never repeat unchanged questions, and never request a token or terminal paste. Low-risk recommended defaults may proceed as disclosed assumptions; high-risk material defaults require explicit conversational confirmation. Confirm onl