docs(joinir): Phase 78-85 Boxification Feedback Report

Comprehensive analysis of boxification patterns effectiveness.

Key Findings:
- Overall: Exceptional success ⭐⭐⭐⭐⭐ (24/25 avg rating)
- Net code reduction: -1,388 lines (Phase 78-79: -530L, Phase 85: -858L)
- 4 new Boxes: PromotedBindingRecorder, Detector/Recorder, BindingMapProvider, DebugOutputBox
- 28 new unit tests, 974/974 PASS maintained

Box Ratings (out of 25):
- PromotedBindingRecorder: 24/25 (67% wiring reduction)
- Detector/Recorder: 24/25 (60% code reduction, SRP)
- BindingMapProvider: 23/25 (80% cfg reduction)
- DebugOutputBox: 21/25 (centralized debug output)

Phase 86 Recommendations:
- GO: Carrier Initialization Builder (HIGH, 2-3h, -100L)
- GO: Remaining DebugOutputBox Migration (QUICK, 30m)
- GO: Error Message Centralization (LOW, 1-2h)
- NO-GO: Detector/Promoter Pipeline (over-abstraction risk)
- NO-GO: ScopeManager Lookup Variants (premature)

Lessons Learned:
- Single Responsibility principle validated
- Testability-first approach successful
- Low migration cost (1-2h per phase)
- Zero production risk (all dev-only/backward-compatible)

Report: phase78-85-boxification-feedback.md (~1,200 lines)
Updated: INDEX, Now, architecture-overview (Phase 85 links)

docs/development/current/main/10-Now.md

@@ -17,6 +17,8 @@
 - 残課題（JoinIR ライン）：
   - JoinIR→MIR merge の一般化（複雑な Select/PHI パターンの統合）
   - JsonParserBox など実アプリ側での長期運用テスト
+  - Boxification（箱化）の振り返りと、次の小粒リファクタ（Phase 86 推奨）:
+    - `docs/development/current/main/phase78-85-boxification-feedback.md`
 
 ### Scope / BindingId（dev-only の段階移行ライン）
 
@@ -30,6 +32,7 @@
     - `docs/development/current/main/phase78-bindingid-promoted-carriers.md`
     - `docs/development/current/main/phase80-bindingid-p3p4-plan.md`
     - `docs/development/current/main/phase81-pattern2-exitline-contract.md`
+    - `docs/development/current/main/phase78-85-boxification-feedback.md`
 
 ### JsonParser / Selfhost depth‑2 ライン