docs(authorization-obligations): approve design; generate tasks

Six task groups in the design's migration order: closed facts and
obligation shapes; operations, siblings, declared policy, dominance
protocol and the checker; MAP wiring, reports, ranking and hunter intent;
corpus harvest mode, labels, leave-one-out and relabeling; the
obligations lever; validation. All 44 acceptance criteria covered; no
task waits on the unimplemented upstream specs (path-aware evaluation
enters through the Dominance protocol and an optional PathRecord input).

Co-Authored-By: Claude Fable 5.1 <[email protected]>
Claude-Session: https://claude.ai/code/session_01T7XD7x5KonMdmGRkp63EQG

.kiro/specs/authorization-obligations/spec.json

@@ -1,7 +1,7 @@
 {
   "feature_name": "authorization-obligations",
   "created_at": "2026-09-05T17:00:00Z",
-  "updated_at": "2026-09-05T18:00:00Z",
+  "updated_at": "2026-09-05T18:30:00Z",
   "language": "en",
   "phase": "design-generated",
   "approvals": {
@@ -11,7 +11,7 @@
     },
     "design": {
       "generated": true,
-      "approved": false
+      "approved": true
     },
     "tasks": {
       "generated": false,
@@ -24,5 +24,5 @@
     "guard-dominance-regime",
     "corpus-seeded-mechanisms"
   ],
-  "approval_note": "2026-09-05 requirements approved by the maintainer in session ('approve the requirements and run the design phase')"
+  "approval_note": "2026-09-05 requirements and design approved by the maintainer in session"
 }