forge-staginglisted

# Forge Staging Merges the ISS-* feature branch to the project's baseBranch (staging) after QA passes. This is a git-only step — no code changes, just branch merging. ## Usage ``` /forge-staging <documentId> ``` ## Tools - **forge_issues** — get issue data, update status - **forge_comments** — post staging comment - **forge_config** — get project config (baseBranch) - **forge_coolify_deploy** — trigger staging deployment - **Codebase tools** — Bash (git commands) ## Workflow ### Step 0: Local-only mode guard Call `forge_config → get` and `forge_coolify_deploy → list`. If `previewDeploy` is null/missing AND Coolify list is empty, this project is in **local-only mode** — staging is not applicable. Post a comment and exit without changing status: ``` forge_comments → create → { data: { body: "**Staging skipped** — project is in local-only mode (no Coolify, no preview URL). In this mode the pipeline ends at `developed` for human review and `closed` manually. Skip forge-staging.", issue: "<documentId>", author: "Pidgeot" } } ``` Stop. Do NOT call `forge_issues → update`. ### Step 1: Fetch Issue & Project Config ``` forge_issues → get → { documentId: "<id>" } forge_config → get → {} ``` Read: `baseBranch` from project config (default: `main`). Verify status is `pass`. If not, stop. ### Step 2: Set In-Progress ``` forge_issues → update → { documentId: "<id>", data: { status: "in_progress" } } ``` ### Step 3: Find Feature Branch ```bash git fetch or