Foerste eval-runde nogensinde (korpus: Jernpladsen @ b7656b1, 36 pages,
77 testprocedurer) fandt to regler med uskarpe graenser:
- pages-must-not-contain-business-logic: undtagelse 3 tilfoejet -
singleton-init-idiomet paa Cue/Activities-pages (if not Get then
Init+Insert i OnOpenPage) er praesentations-bootstrap, ikke
forretningslogik. Basisappen bruger samme moenster paa alle cue-pages.
Evidens: reglen flagede ScrapDealerActivities; adjudikeret FP.
Precision som skrevet: 0,67 (2 TP / 1 FP) - de to TP'er staar ved magt.
- test-one-when-per-test: flow-test-graensen defineret. Multi-WHEN er
tilladt naar navnet deklarerer flowet, hver WHEN er en runde af EET
scenarie, og THEN asserter den akkumulerede sluttilstand. Unit-tests
beholder streng een-WHEN. Evidens: 5 bevidst runde-maerkede
procedurer i SVPartialFlowTests, som reglen ikke kunne doemme.
Scorecards i PR-beskrivelsen. Rute: Edison -> Francis (Type A) ->
Immanuel -> Michael, jf. edison.agent.md Step 6.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Normalisering af alle 39 custom knowledge-filer til READ-kontraktens
skema (validate_frontmatter.py + Test-KnowledgeIndex.ps1 begge groenne):
- R01/R02: 28 filer manglede frontmatter eller brugte aeldre skemaer
(title/category/severity/rule-id m.fl.) - alle har nu praecis de 6
kraevede noegler; keywords haandskrevet pr. fil da de driver
worklist-selektionen i INDEX/knowledge-index
- R09: manglende Description-sektion - regel-agtige foersteoverskrifter
(Core Rule/Rule/Regel/Core Principle) omdoebt, eller sektion indsat
efter titlen hvor intro-tekst fandtes
- R10: fenced code blocks konverteret til 4-space indrykkede blokke
i alle filer (indhold uaendret)
- R11: 4 filer over 100 linjer fortaettet redaktionelt uden semantisk
tab (ai-eval-scores 143->100, git-lifecycle 121->97,
permission-sets 113->99, test-feature-scenario-tags 105->91)
- R05: AL0197->al0197, add_repo->add-repo; keyword-lister trimmet
til maks 10
Ingen regler er fjernet eller aendret i betydning - kun form.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
- All 7 existing Tier 1/2 knowledge files now include a BCApps Reference
section with concrete source links and observed patterns
- New: bcpt-scenarios-must-be-app-specific — PerformanceTest apps must
include app-domain BCPT scenarios, not only Microsoft generic samples
- New: permission-sets-must-follow-least-privilege — View/Edit/Admin
hierarchy with IncludedPermissionSets, mirroring BCApps BusFound pattern
- api-page-key-fields-must-be-editable-on-insert clarified: SystemId as
ODataKeyField + Editable=false is valid (auto-generated); rule applies
to consumer-provided key fields only
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
- test-one-when-per-test: one WHEN per test, split if multiple actions
- ui-test-codeunit-naming: _UT suffix for TestPage-based codeunits
- test-feature-scenario-tags: [FEATURE]/[SCENARIO] comment structure
Based on patterns from Automatiserede tests med Business Central (Dieringer).
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
