Merge remote-tracking branch 'origin/main' into garrytan/chrome-extension-ctrl

Resolved conflicts:
- VERSION/package.json: keep 0.12.0.0 (our version bump)
- CHANGELOG: our v0.12.0 entry on top, main's v0.11.21/v0.11.20 below
- gen-skill-docs.ts: use main's clean approach (no local RESOLVERS redeclaration)
- SKILL.md files: regenerated from merged templates
- Removed stale ship gate test (main removed the "run /review first" gate)
- Added review-dashboard-via tier entry (new test from main)

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

TODOS.md

@@ -213,6 +213,18 @@ Linux cookie import shipped in v0.11.11.0 (Wave 3). Supports Chrome, Chromium, B
 
 ## Ship
 
+### GitLab support for /land-and-deploy
+
+**What:** Add GitLab MR merge + CI polling support to `/land-and-deploy` skill. Currently uses `gh pr view`, `gh pr checks`, `gh pr merge`, and `gh run list/view` in 15+ places — each needs a GitLab conditional path using `glab ci status`, `glab mr merge`, etc.
+
+**Why:** Without this, GitLab users can `/ship` (create MR) but can't `/land-and-deploy` (merge + verify). Completes the GitLab story end-to-end.
+
+**Context:** `/retro`, `/ship`, and `/document-release` now support GitLab via the multi-platform `BASE_BRANCH_DETECT` resolver. `/land-and-deploy` has deeper GitHub-specific semantics (merge queues, required checks via `gh pr checks`, deploy workflow polling) that have different shapes on GitLab. The `glab` CLI (v1.90.0) supports `glab mr merge`, `glab ci status`, `glab ci view` but with different output formats and no merge queue concept.
+
+**Effort:** L
+**Priority:** P2
+**Depends on:** None (BASE_BRANCH_DETECT multi-platform resolver is already done)
+
 ### Ship log — persistent record of /ship runs
 
 **What:** Append structured JSON entry to `.gstack/ship-log.json` at end of every /ship run (version, date, branch, PR URL, review findings, Greptile stats, todos completed, test results).