Strukturflag: BCQuality-implementering rejser flagene selv

Michaels krav: AI skal rejse flagene, naar BCQuality implementeres paa
et repo - ikke naar nogen tilfaeldigvis spoerger. Portefoeje-inventar
2026-07-02 (29 repos): 3 flade repos blokeret for testcases, 11 uden
test-app (een CreateTestApp-koersel hver, ikke migration).

- Ny regel al-go-template-layout-with-test-app-required: template-
  layout + test-app-companion er paakraevet; strukturfund er report-
  only (migration er aldrig stille korrektion); setup maa fortsaette
  paa non-compliant repo, men aldrig tavst
- roemer.agent.md v3: station 10 (AL-Go template-layout) og 11
  (test-app pr. main app)
- curabis-standard.agent.md v13: Mode A Step 1b koerer Roemers
  strukturstationer FOER konfiguration og kraever at udvikleren
  anerkender flagene inden Step 2

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

custom/setup/curabis-standard.agent.md

@@ -1,7 +1,7 @@
 ---
 kind: action-skill
 id: curabis-standard-setup
-version: 12
+version: 13
 title: CURABIS Standard — Project Setup
 description: >
   Configures a new or existing repository to the CURABIS Standard development
@@ -96,6 +96,27 @@ Check whether these paths exist:
 If `CLAUDE.md` already exists, ask: "CLAUDE.md eksisterer allerede. Overskrive? (ja/nej)"
 Stop if the developer answers no.
 
+### Step 1b — Structural readiness: raise the flags (Rømer)
+
+Before configuring anything, run Rømer's structural stations (10-11 in
+`roemer.agent.md` — rule `al-go-template-layout-with-test-app-required`):
+
+1. AL-Go template layout: apps folder with per-app project subfolders + `.AL-Go/`
+2. Test app companion for every main app
+
+Report every finding immediately and prominently:
+
+```
+⚠️ Strukturflag ved BCQuality-implementering:
+
+  - <fladt layout: tests kan ikke oprettes før migrering til AL-Go template>
+  - <manglende test-app for <App>: kør CreateTestApp-workflowet>
+```
+
+Setup MAY continue on a non-compliant repo — but the flags go in the setup
+report, and the developer must acknowledge them before Step 2. Never
+restructure silently; migration is a deliberate, planned change.
+
 ### Step 2 — Ask exactly three questions
 
 Do not proceed until all three are answered.