docs(10.1): create gap closure plans (06-07)

.planning/ROADMAP.md

@@ -51,7 +51,7 @@ Plans:
 
 **Requirements:** MOD-03 (new)
 
-**Plans:** 6 plans
+**Plans:** 7 plans
 
 Plans:
 - [x] 10.1-01-PLAN.md — Rename sub-workflows, analyze domain boundaries, get user approval
@@ -59,18 +59,17 @@ Plans:
 - [x] 10.1-03-PLAN.md — Extract Container Status sub-workflow (~10-15 nodes)
 - [x] 10.1-04-PLAN.md — Extract Confirmation sub-workflow (~15-20 nodes)
 - [x] 10.1-05-PLAN.md — Integration verification and UAT
-- [ ] 10.1-06-PLAN.md — Gap closure: document contracts, analyze Code nodes, decide on remaining gaps
+- [ ] 10.1-06-PLAN.md — Gap closure: Extract Matching/Disambiguation sub-workflow
+- [ ] 10.1-07-PLAN.md — Gap closure: Code node classification + contract documentation
 
 **Success Criteria:**
 1. Main workflow contains only: trigger, auth, keyword routing, sub-workflow dispatch
 2. UX/Keyboard sub-workflow handles all batch selection UI and pagination
 3. Container Status sub-workflow handles list and status display
 4. Confirmation sub-workflow handles all confirmation dialogs
-5. Main workflow reduced to ~50-80 nodes (from 192) — *Revised: 115-125 realistic target*
+5. Main workflow reduced to ~50-80 nodes (from 192)
 6. All sub-workflows have clean input/output contracts
 
-**Note:** Original 50-80 target was unrealistic (58 Telegram response nodes locked to main). Revised target 115-125. Current: 168 nodes after 3 domain extractions. Gap closure plan addresses remaining verification gaps.
-
 ---
 
 ### Phase 10.2: Better Logging and Log Management (INSERTED)
@@ -172,4 +171,4 @@ Plans:
 **v1.2 Coverage:** 12+ requirements mapped across 7 phases
 
 ---
-*Updated: 2026-02-05 — Phase 10.1 gap closure plan added (10.1-06)*
+*Updated: 2026-02-08 — Phase 10.1 gap closure plans added (plans 06-07)*