chore(specgit): refresh delivery harness

.opencode/command/specgit-issue.md

@@ -13,17 +13,18 @@ AGENTS.md SpecGit block; this command only launches it.
 
 1. Collect the argument: `$ARGUMENTS` is either an issue title (create) or a
    pure number (reuse). Multiple arguments = N issues in one delivery.
-2. Run from the repo root:
+2. Run from the repo root — keep `$ARGUMENTS` UNQUOTED so each quoted title
+   arrives as its own argument:
 
    ```bash
-   specgit issue "$ARGUMENTS" --json
+   specgit issue $ARGUMENTS --json
    ```
 
 3. On success report the brief: issue URL(s), PR URL (draft), branch name —
    then fill each issue body it created (Why / Scope / Approach /
    Acceptance) from the discussion with `gh issue edit <n>`, then
    implement. Fill in the draft PR's scaffold (Why / What changed /
-   Evidence) as you deliver; its placeholders are advisory, never gates,
-   and the closing references stay intact.
+   Evidence / Checklist) as you deliver; its placeholders are advisory,
+   never gates, and the closing references stay intact.
 4. Switch to the delivery branch and begin the TDD loop.
 5. On error, read `errors[].fix` and follow it — never bypass the record.

.opencode/hooks/specgit-merge-guard.sh

@@ -26,7 +26,7 @@ esac
 command=$(printf '%s' "$payload" | node -e "let s='';process.stdin.on('data',d=>s+=d).on('end',()=>{try{const j=JSON.parse(s);process.stdout.write((j.tool_input&&j.tool_input.command)||'')}catch{process.stdout.write('')}})")
 
 case "$command" in
-  gh\ pr\ merge*)
+  gh\ pr\ merge*|glab\ mr\ merge*)
     exec node -e '
       const { spawn } = require("child_process");
       const fs = require("fs");

.specgit.yaml

@@ -1,11 +1,11 @@
 version: 1
-delivery: tui-crashes-on
+delivery: refresh-specgit-harness
 context:
   kind: branch
-  branch: fix/465-tui-crashes-on
+  branch: chore/refresh-specgit-harness
 issues:
-  - 465
+  - 488
 issueKinds:
-  - issue: 465
-    kind: kind::fix
-pr: 466
+  - issue: 488
+    kind: kind::chore
+pr: 489