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

coverage/README.md

@@ -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

coverage/development-capabilities.json

@@ -1,5 +1,6 @@
 {
   "version": 1,
+  "minimumFixtureCoverage": 0.5,
   "capabilities": [
     {
       "id": "setup-and-master-data",
@@ -82,13 +83,15 @@
     {
       "id": "install-and-upgrade",
       "title": "Installation and data upgrade",
-      "status": "planned",
+      "status": "fixture",
       "domains": [
         "breaking-changes",
         "testing",
         "upgrade"
       ],
-      "fixtureIds": []
+      "fixtureIds": [
+        "versioned-data-upgrade"
+      ]
     },
     {
       "id": "external-services",