forge-shiplisted

# forge-ship The review approved. Two things left: land it, and account for it. ## Merge Into the base branch you checked out from. That is yours and needs no permission. Resolve the target from the project's own configuration, not from the plan text and not from habit — a project whose base branch changed will have stale branch names written into older issue descriptions, and following them merges into the wrong place silently. Merging anywhere else needs a human. Ask, do not assume. If the merge conflicts, that is phase 3 again, not a failure: re-declare `code`, resolve, and come back through review if the resolution changed behaviour. ## Deploy gate `projectFacts.deploy-policy` says whether a deploy happens on this project and what gates it. You request it; the cloud allows it or does not. A refusal is not an error to work around — if deploy is gated, the gate is the answer. If a deploy runs and does not come up, do not close the issue. Comment with what you saw and set `needs_info`. A green merge with a dead deploy is the exact state that looks finished and is not. ## Account for it One comment. It is the only record a human will read, so it carries everything that is not in the diff: | Section | Content | |---|---| | What changed | one paragraph, in terms of the reported problem, not the files | | Extra fixes | defects you fixed that were not in the acceptance criteria | | Left unresolved | anything you found and did not fix, and why | | Verification | what y