phase29ap(p0): reduce legacy extractors (pattern1/3)

This commit is contained in:
2025-12-30 22:13:24 +09:00
parent 49f6457619
commit ab81747d6a
8 changed files with 49 additions and 199 deletions

View File

@ -2,8 +2,8 @@
## Current Focus
- Phase: `docs/development/current/main/phases/phase-29ao/README.md` (closeout)
- Next: Phase 29ap (planned; see `docs/development/current/main/phases/phase-29ao/README.md`)
- Phase: `docs/development/current/main/phases/phase-29ap/README.md`
- Next: Phase 29ap P1 (planned; see `docs/development/current/main/phases/phase-29ap/README.md`)
## Gate (SSOT)

View File

@ -5,7 +5,7 @@ Scope: 「次にやる候補」を短く列挙するメモ。入口は `docs/dev
## Active
- Phase 29ap (planned): legacy削減の段階計画extractor/router+ composer SSOT
- Phase 29ap: `docs/development/current/main/phases/phase-29ap/README.md` (Next: P1 planned)
- JoinIR regression gate SSOT: `docs/development/current/main/phases/phase-29ae/README.md`
- CorePlan hardening (docs-first): `docs/development/current/main/phases/phase-29al/README.md`

View File

@ -33,8 +33,8 @@ Related:
## 1.1 Current (active)
- Active phase: `docs/development/current/main/phases/phase-29ao/README.md`
- Next step: Phase 29ap (planned; P55 done)
- Active phase: `docs/development/current/main/phases/phase-29ap/README.md`
- Next step: Phase 29ap P1 (planned)
## 2. すでに固めた SSOT再発防止の土台

View File

@ -0,0 +1,32 @@
---
Status: Active
Scope: Legacy extractor reduction (planner+composer SSOT)
Related:
- docs/development/current/main/design/coreplan-migration-roadmap-ssot.md
- docs/development/current/main/design/coreplan-migration-done-criteria-ssot.md
- docs/development/current/main/design/coreloop-composer-v0-v1-boundary-ssot.md
- docs/development/current/main/phases/phase-29ae/README.md
---
# Phase 29ap: Legacy extractor reduction (Step-E)
Goal: Reduce legacy extractor fallbacks while keeping planner+composer as the SSOT path.
Gate (SSOT):
- `./tools/smokes/v2/profiles/integration/joinir/phase29ae_regression_pack_vm.sh`
## P0: Reduce legacy extractors (Pattern1/3) ✅
- Scope:
- Remove Pattern1/3 extractor fallbacks in `single_planner`.
- Remove Pattern3 JoinIR router entry so plan line is the only path.
- Pattern1 JoinIR entry is retained for now (stdlib loops still rely on it).
- Guardrails:
- Outcome remains `Ok(None)` for non-matching cases.
- No new logs or error strings.
## Next (planned)
- P1: Pattern6/7 JoinIR wrapper → composer entry only
- P2: Router pattern-name branching reduction (planner outcome + composer SSOT)
- P3: Facts/Feature expansion if needed