Create single source of truth for smoke test environment configuration: **tools/smokes/v2/lib/env.sh** (new, 183 lines): - Centralize 16 environment variables across 6 categories - JoinIR development (NYASH_JOINIR_DEV, HAKO_JOINIR_STRICT) - LLVM features (NYASH_LLVM_USE_HARNESS, NYASH_LLVM_BACKEND, etc.) - Tmpdir EXDEV mitigation (TARGET_TMPDIR) - Plugin loader strategy (NYASH_LOAD_NY_PLUGINS, NYASH_DISABLE_PLUGINS) - Parser features (NYASH_FEATURES, using system variables) - Debug features (NYASH_CLI_VERBOSE, etc.) **Mode Presets**: - dev: Verbose logging, unlimited fuel, JoinIR dev enabled - integration: Moderate settings, JoinIR dev enabled - quick: Minimal logging, fast execution **Helper Functions**: - setup_smoke_env [mode]: Configure environment for test profiles - validate_env_setup: Validate configuration - show_smoke_env: Display current configuration **Documentation**: - ENV_README.md: Comprehensive usage guide - ENV_QUICK_START.md: Quick reference for script authors - p1.5-task5-env-ssot.md: Implementation details and testing Benefits: - SSOT: Single file for all environment variables - Sparrow prevention: No duplicate settings - Clarity: Well-documented configuration - Backward compatibility: Existing scripts work unchanged Test Results: - All environment presets work correctly - Phase 131 smoke tests PASS - Syntax validation for all shell files PASS Related: Phase 131 smoke test infrastructure improvement 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
Phase ドキュメント
このフォルダは、実装フェーズ(Phase 131, Phase 33 等)ごとの詳細記録を保管します。
現在の Phase
- Phase 132: Exit Values Parity (VM == LLVM)
- Phase 133: Promoted carrier join_id(Trim)修正
- Phase 134: Plugin loader best-effort loading
- Phase 135: ConditionLoweringBox allocator SSOT(ValueId 衝突の根治)
- Phase 136: MirBuilder Context SSOT 化(+ ValueId allocator 掃討)
- Phase 137–141: Loop Canonicalizer(前処理 SSOT)導入(Phase 137 フォルダに統合して記録)
- Phase 91–92: Selfhost depth‑2 coverage(P5b escape recognition → lowering)
- Phase 94–100: P5b escape E2E / Trim policy / pinned + accumulator(VM/LLVM EXE parity)
- Phase 102: real-app read_quoted loop regression(VM + LLVM EXE)
- Phase 103: if-only regression baseline(VM + LLVM EXE / plan)
- Phase 113: if-only partial assign parity(片側代入の保持 merge)
- Phase 107–109: real-app depth-scan / policy router SSOT / error hint SSOT
- Phase 110–112: ControlTree / StepTree(構造SSOT, dev-only)※設計SSOTは
../design/control-tree.md
Phase フォルダ構成(推奨)
phases/phase-131/
├── README.md (Phase 全体概要)
├── 131-03-llvm-lowering-inventory.md (LLVM 部分のテスト・検証)
├── 131-11-case-c-summary.md (Case C 実装サマリー)
└── phase131-11-case-c-root-cause-analysis.md (根本原因分析)
参照方法
- 現在の Phase を知りたい → ../10-Now.md
- 該当 Phase を詳しく知りたい → フォルダを開く
- 設計背景を知りたい → ../design/
- 調査ログを見たい → ../investigations/
Phase 命名規則
- ファイル名:
phase-<N>-<title>/(例:phase-131/) - 文書名:
<N>-<NN>-<topic>.md(例:131-11-case-c-summary.md)- Phase 番号で自然にソート可能
- 同一 Phase 内で段階的に追跡可能
作成ルール(SSOT)
詳しくは ../DOCS_LAYOUT.md を参照。
- ✅ 置き場所:
phases/phase-<N>/配下のみ - ✅ 内容: Phase の実装記録・進捗・チェックリスト・検証結果
- ❌ 避けるべき: 複数 Phase で参照される設計・アーキテクチャ(→ design/ へ)
最終更新: 2025-12-18