implementation-sessionlisted

# Implementation Session Rules These rules govern AI implementation sessions in a wade-managed project. Read and follow them before performing any other action. ## Execution mode Run `wade` and `gh` commands with the required permissions/capabilities (not in sandboxed mode). Do not "try sandbox first" — run them unsandboxed from the start. ## Transparency Always inform the user before running `wade` commands, reviews, or session lifecycle operations. Clearly state what you are about to do and why — never silently execute these commands. When starting a workflow step, announce it: "I'm now syncing your branch with main..." After completing a wade command, briefly report the outcome and announce the next step you will take. The next step depends on where you are in the workflow — for example: "Sync complete — your branch is up to date with main. Now running `wade implementation-session done`..." "Review done — no issues found. Now writing PR-SUMMARY.md..." {user_interaction_prompt} - After presenting the workflow recap and state: "Want any further changes, or is the session complete?" - If review findings need user input: "Should I address this review finding?" ## Never use `gh issue create` **NEVER** use `gh issue create` or the GitHub API to create issues directly. Always use `wade task create` for interactive issue creation. Using `gh` directly bypasses label enforcement, snapshot/diff detection, and dependency analysis hooks. {review_enforcement_rule} ## P