Close AL development contract gaps

Bound post-implementation review rounds, expose output kinds in Entry
dispatch, enforce capability coverage, map BCFIX-HANDOFF v1, clarify
no-knowledge behavior, and reject repository-escaping skill paths.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 638b66d2-9f06-4f60-8781-808709e1485c
This commit is contained in:
Jesper Schulz-Wedde 2026-09-04 13:36:49 +02:00
parent 56b80e6dcf
commit f6fca1d56d
15 changed files with 356 additions and 52 deletions

View file

@ -14,6 +14,10 @@ one-for-one.
- `development-capabilities.json` tracks whether representative Business
Central development capabilities have implementation fixtures.
The capability manifest declares `minimumFixtureCoverage`. CI fails when the
share of `fixture` or `validated` capabilities falls below that floor, so a
new planned capability cannot silently dilute generation coverage.
Each tracked unit has a `reviewStatus`:
- `in-progress` — at least one concern has been identified, but editorial