docs(phase287): Add P9 closeout instructions
This commit is contained in:
@ -1,6 +1,6 @@
|
||||
# Self Current Task — Now (main)
|
||||
|
||||
## Current Focus: Phase 287 P8(Rewriter README/guard)
|
||||
## Current Focus: Phase 287 P9(Phase closeout)
|
||||
|
||||
**2025-12-27: Phase 188.3 完了** ✅
|
||||
- Pattern6(NestedLoopMinimal): `apps/tests/phase1883_nested_minimal.hako` が RC=9
|
||||
@ -58,6 +58,12 @@
|
||||
- 入口: `docs/development/current/main/phases/phase-287/P7-REWRITER-BOX-SCAFFOLDING-CLEANUP-INSTRUCTIONS.md`
|
||||
- 次の指示書(P8): `docs/development/current/main/phases/phase-287/P8-REWRITER-README-GUARD-INSTRUCTIONS.md`
|
||||
|
||||
**2025-12-27: Phase 287 P8 完了** ✅
|
||||
- `rewriter/README.md` を追加し、責務境界と SSOT(Plan→Apply)を明文化(docs-only)
|
||||
- 検証: cargo check / quick PASS
|
||||
- 入口: `src/mir/builder/control_flow/joinir/merge/rewriter/README.md`
|
||||
- 次の指示書(P9): `docs/development/current/main/phases/phase-287/P9-PHASE-CLOSEOUT-INSTRUCTIONS.md`
|
||||
|
||||
**2025-12-27: Phase 188.2 完了** ✅
|
||||
- StepTreeの `max_loop_depth` を SSOT に採用(Option A)
|
||||
- strict mode で depth > 2 を明示エラー化(Fail-Fast)
|
||||
@ -149,8 +155,8 @@
|
||||
- quick smoke 154/154 PASS 維持、Pattern1/4 PoC 両方 PASS
|
||||
|
||||
**次のステップ**:
|
||||
1. **Phase 287(P8)**: Rewriter README/guard(docs-first)
|
||||
- 指示書: `docs/development/current/main/phases/phase-287/P8-REWRITER-README-GUARD-INSTRUCTIONS.md`
|
||||
1. **Phase 287(P9)**: Phase closeout(docs-only)
|
||||
- 指示書: `docs/development/current/main/phases/phase-287/P9-PHASE-CLOSEOUT-INSTRUCTIONS.md`
|
||||
2. (post self-host / docs-first)**Phase 29y**: MIR lifecycle vocab freeze(RC/weak/ABI)
|
||||
- 相談パケット: `docs/development/current/main/investigations/phase-29y-mir-lifecycle-vocab-consult.md`
|
||||
3. (future design, separate phase)Plan 生成の正規化(相談パケット)
|
||||
|
||||
@ -13,11 +13,10 @@ Related:
|
||||
- SSOT: `docs/reference/language/repl.md`
|
||||
- 次: Phase 288.2+(任意): REPL UX improvements(history / multiline / load 等)
|
||||
|
||||
- **Phase 287(active): Big Files Refactoring follow-ups(意味論不変)**
|
||||
- 状況: P0/P1/P2/P3/P4/P5/P6/P7 ✅ 完了(merge modularize / ast_feature_extractor facade / contract_checks facade / rewriter stages split / plan stage split / stages facade / remove scan stage / box scaffolding cleanup)
|
||||
- 次(P8): rewriter README/guard を追加して責務境界を明文化
|
||||
- 入口: `docs/development/current/main/phases/phase-287/README.md`
|
||||
- 指示書: `docs/development/current/main/phases/phase-287/P8-REWRITER-README-GUARD-INSTRUCTIONS.md`
|
||||
- **Phase 287(closeout): Developer Hygiene(意味論不変)**
|
||||
- 状況: P0–P8 ✅ 完了(big files / facade / SSOT / docs guard)
|
||||
- 次(P9): Phase closeout(docs-only)
|
||||
- 指示書: `docs/development/current/main/phases/phase-287/P9-PHASE-CLOSEOUT-INSTRUCTIONS.md`
|
||||
|
||||
- **Phase 284(✅ COMPLETE): Return as ExitKind SSOT(patternに散らさない)**
|
||||
- 目的: `return` を “pattern最適化の個別実装” にせず、`ExitKind` と `compose::*` / `emit_frag()` に収束させる
|
||||
|
||||
@ -0,0 +1,41 @@
|
||||
# Phase 287 P9: Closeout(docs-only, 意味論不変)
|
||||
|
||||
**Date**: 2025-12-27
|
||||
**Status**: Ready(next)
|
||||
**Scope**: Phase 287 の完了状態を docs と index で確定し、次フェーズへ迷わず移れるように入口を締める(コード変更なし)。
|
||||
**Non-goals**: コード変更、テスト追加、CI/スモーク構成変更
|
||||
|
||||
---
|
||||
|
||||
## 目的
|
||||
|
||||
- Phase 287 の “Done” を SSOT に反映し、Now/Backlog の参照先を次へ切り替える。
|
||||
- 入口文書が古い “Next (P4/P5...)” を指さない状態にする。
|
||||
|
||||
---
|
||||
|
||||
## 手順
|
||||
|
||||
1. `docs/development/current/main/phases/phase-287/README.md`
|
||||
- `**Status**: Complete`(または `Completed`)へ変更
|
||||
- P0–P8 を “Done” として列挙し、Next を撤去(または “Next: none”)
|
||||
2. `docs/development/current/main/10-Now.md`
|
||||
- Current Focus を次フェーズ(または次タスク)へ更新
|
||||
3. `docs/development/current/main/30-Backlog.md`
|
||||
- Phase 287 を “completed” へ移す(active から外す)
|
||||
|
||||
---
|
||||
|
||||
## 検証
|
||||
|
||||
docs-only なので、最低限:
|
||||
|
||||
```bash
|
||||
git status --porcelain=v1
|
||||
```
|
||||
|
||||
(任意)手元の安心:
|
||||
```bash
|
||||
cargo check -p nyash-rust --lib
|
||||
./tools/smokes/v2/run.sh --profile quick
|
||||
```
|
||||
Reference in New Issue
Block a user