work-onlisted

# Forge Repo Adapter: work-on Use `commands/work-on.md` as the authoritative state-machine source, but apply the Forge repo overrides below when running from Codex in this repository. ## Repo Resolution Override Inside the Forge repo, resolve issue targets like this unless the user explicitly prefixes another project: | Input | Repo | |---|---| | `123`, `#123`, `next`, empty | `RapierCraftStudios/forgedock` | | `forge:123` | `RapierCraftStudios/forgedock` | Satellite prefixes (e.g. `mcp:5`, `sdk:12`) are project-specific and defined in `forge.yaml → repos.satellites`. See `commands/work-on.md` Phase 0B for multi-repo routing. For Forge repo issues, set: - `GH_REPO=RapierCraftStudios/forgedock` - `GH_FLAG=--repo RapierCraftStudios/forgedock` - `REPO_PATH=/home/mrdubey/projects/forgedock` - `STAGING_BRANCH=staging` - `DEFAULT_BRANCH=main` ## Codex Runtime Overrides - Treat any `.claude/worktrees/...` example path in the shared command spec as `.codex/worktrees/...` for Codex execution in this repo. - Create and reuse worktrees under `/home/mrdubey/projects/forgedock/.codex/worktrees`. - Prefer `gh api repos/{GH_REPO}/issues/{NUMBER}/comments` for comment reads instead of `gh issue view --comments`. - Treat GitHub Project-board sync as best-effort only for Forge issues. Do not block the pipeline if Forge-specific board/component mappings are absent. - Create missing `workflow:*` labels on demand if the Forge repo does not already have them. ## Forge Repo File Scope Whe