Fire haandhaevelseslag for [CURABIS-STATE]-tilstandssporet

Michael: "lad os bygge alle 4" - rangeret efter styrke fra sidste samtale.

1. Smiley v6: close-gaten laeser nu det faktiske [CURABIS-STATE]-spor
   tilbage FOER merge, i stedet for at stole paa sessionens egen hukommelse.
   Mangler et tidligere checkpoint, blokerer merge - selv hvis testen er
   groen og reviewet lige sagde APPROVE nu.
2. al-review v3: "state trail complete?" er nu et Titus-tjekpunkt der giver
   BLOCK, ikke bare en note - et ufuldstaendigt spor er i sig selv et
   vedligeholdelsesfund.
3. Ny .github/workflows/curabis-task-state-check.yml: reelt deterministisk
   haandhaevelse for AppSource (parser PR-body'ens tjekliste, fejler hvis en
   senere fase er tjekket mens en tidligere ikke er). Testet mod fire cases
   (gyldig raekkefolge, ugyldig, ingen sektion, tom sektion) - alle korrekte.
   Kraever et manuelt engangs-trin (branch protection required check) som
   filudrulningen ikke selv kan saette.
4. Roemer v6: ny station 13, retrospektiv - stikprover de sidste ~10
   afsluttede BC-opgaver/mergede PR'er for spor-fuldstaendighed, fanger
   drift ingen enkelt opgaves egen gate fangede. Kun opgaver lukket efter
   2026-08-03 flages - reglen fandtes ikke foer.

curabis-standard.agent.md: ny artefakt-raekke + Mode A step 4h (deploy
workflow-filen, mind om branch protection-trinet) + Mode B repo-tabel-raekke.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

custom/agents/smiley.agent.md

@@ -1,7 +1,7 @@
 ---
 kind: watchdog
 id: curabis-smiley
-version: 5
+version: 6
 title: Smiley — Session Watchdog
 description: >
   Always-active session observer. Shapes Claude's behavior from within.
@@ -170,6 +170,17 @@ all of them mean AL code is about to change.
   BLOCK verdict from the independent review is the same kind of hard stop
   as a red test — green tests prove the requirement is met, not that the
   change is well-built.
+- **2026-08-03 — self-verify before merging, don't just trust the session's
+  own memory.** Read back the actual `[CURABIS-STATE]` trail (BC comments
+  for PTE, the PR checklist for AppSource) before allowing the merge — not
+  from what this session remembers doing, from what's actually recorded.
+  If `TASK_STARTED` → `RED_CONFIRMED` → `GREEN_CONFIRMED` → `REVIEW: <verdict>`
+  aren't all present in order, the merge does not proceed, even if the
+  current test run is green and the current review just said APPROVE — a
+  missing earlier checkpoint means the trail itself can't be trusted, which
+  is the entire reason it exists. This is the one advantage a queryable
+  state trail has over a plain instruction: it can be checked, not just
+  followed.
 - At release (track branch → main, tag, AppSource submission): app.json
   version consciously bumped before the merge.