mirror of
https://github.com/microsoft/BCQuality.git
synced 2026-10-05 22:56:55 +01:00
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>
This commit is contained in:
parent
bfc2c59cc9
commit
bcbc4acced
5 changed files with 137 additions and 3 deletions
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
kind: action-skill
|
||||
id: curabis-standards-inspector
|
||||
version: 5
|
||||
version: 6
|
||||
title: Rømer — Standards Inspector
|
||||
description: >
|
||||
Owns the uniformity inspection across CURABIS repos: walks one full
|
||||
|
|
@ -103,6 +103,19 @@ Walk ALL stations, every time. A partial round creates false confidence
|
|||
entry — it is a CURABIS artifact; no VS Code command generates it.
|
||||
Evidence for this station: a session wrote AL code it could not compile
|
||||
and only surfaced the gap when asked (Conzept, 2026-07-02).
|
||||
13. **Task-state trail completeness** (2026-08-03, retrospective, not
|
||||
structural). Sample the last ~10 closed BC tasks (`taskComments` where
|
||||
`Status = Done`) and the last ~10 merged PRs with a `## CURABIS Task
|
||||
State` section. For each: read the `[CURABIS-STATE]` comments / checklist
|
||||
and confirm `TASK_STARTED` → `RED_CONFIRMED` → `GREEN_CONFIRMED` →
|
||||
`REVIEW: <verdict>` → `MERGED` are all present, in order — the same
|
||||
check the close gate and al-review already do per-task, run here
|
||||
across a sample to catch drift no single task's own gate caught (e.g.
|
||||
an older task from before this rule existed, or a session that bypassed
|
||||
the gates entirely). A missing trail on a task closed AFTER 2026-08-03
|
||||
is a divergence finding → Ferencz. A missing trail on a task closed
|
||||
BEFORE that date is expected (the rule didn't exist yet) — note it, do
|
||||
not flag it as drift (rule `[[task-state-lives-in-the-mandatory-artifact]]`).
|
||||
|
||||
## Safety rules
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue