phase29ap(p12): remove joinir legacy loop table
This commit is contained in:
@ -6,7 +6,7 @@ This document defines when the CorePlan migration can be considered done.
|
||||
|
||||
- Release adopt gate patterns execute via CorePlan without strict/dev flags.
|
||||
- Gate smokes cover the release paths and remain green.
|
||||
- The legacy path remains only as a fallback for non-gate cases.
|
||||
- JoinIR legacy loop table is removed; routing is plan/composer only.
|
||||
|
||||
## Stage-3 Done (composer v0/v1)
|
||||
|
||||
@ -17,5 +17,5 @@ This document defines when the CorePlan migration can be considered done.
|
||||
## Still allowed to remain
|
||||
|
||||
- `DomainPlan` can remain as an intent layer for normalization/compatibility.
|
||||
- Legacy extractors and router branches remain until Phase 29ap removes them.
|
||||
|
||||
- Legacy extractors may remain in the plan layer as long as they do not reintroduce
|
||||
JoinIR-side routing tables.
|
||||
|
||||
@ -34,7 +34,7 @@ Related:
|
||||
## 1.1 Current (active)
|
||||
|
||||
- Active phase: `docs/development/current/main/phases/phase-29ap/README.md`
|
||||
- Next step: Phase 29ap P12 (planned)
|
||||
- Next step: Phase 29ap P13 (planned)
|
||||
|
||||
## 2. すでに固めた SSOT(再発防止の土台)
|
||||
|
||||
|
||||
Reference in New Issue
Block a user