kata-setup

# kata-setup ## Operating Brief When this skill is invoked, help the user make Kata usable in the current harness and repository. If the skill is already installed, use the local wrapper for setup and health checks. Explain only the concrete next fix when setup is blocked. This skill does not initialize project state. It only verifies that the runtime, skill installation, and backend configuration are ready for the requested Kata workflow. ## Success Criteria - The user knows whether Kata is ready in this harness. - Runtime health has been checked with `node ./scripts/kata-call.mjs health.check` when the wrapper is available. - Any blocking setup issue is stated with the exact next action. - No project, milestone, slice, task, or artifact state is created. ## Do Not - Do not create or modify project artifacts. - Do not continue into planning or execution if setup is blocked. - Do not inspect helper scripts unless the helper command itself fails. - Do not invent backend-specific setup steps outside the CLI contract. ## Process 1. Read `references/workflow.md` before taking action. Execute that workflow end-to-end. 2. Preserve every workflow gate: required checks, user confirmations, durable writes, status updates, and next-step routing. 3. Before any backend IO, read `references/runtime-contract.md` and use only the operations listed there. 4. When the workflow tells you to create or read an artifact, use `references/artifact-contract.md` and the named template files...