feat: add planning boundary guardrails to ticket plan command

[danielsuguimoto]

Ticket

SKIPPED

Overview

This PR tightens the ticket/plan command so planning stays strictly analysis-only. It adds explicit guardrails that prevent a completed plan from being treated as permission to start implementation work.

Changes

• Added a dedicated Respect Planning Boundary section to the ticket/plan command definition.
• Explicitly states that the command must not implement the plan, edit files, run implementation workflows, or start coding unless the user asks for implementation separately.
• Clarifies that repository inspection during planning is only for reconnaissance to improve the plan, and that the workflow must stop after syncing and presenting the plan.
• Reinforced the same restriction in Additional Context so the non-implementation rule remains part of the command’s standing guidance.
• Regenerated the OpenCode command output so the shipped adapter copy stays aligned with the source command definition.

[dbpolito]

wondering if this is the right place to add, rather than the planner agent... in theory we already don't allow edits:

https://github.com/kompassdev/kompass/blob/main/packages/opencode/.opencode/agents/planner.md?plain=1#L4

@danielsuguimoto what happened? can you give more details of the session / what the agent did wrong?

[dbpolito]

should be fixed with #56