From b2aed69cb87723a3d86a5345b13af754c056de88 Mon Sep 17 00:00:00 2001 From: "shoney.arickathil" Date: Thu, 20 Aug 2026 02:10:32 +0200 Subject: [PATCH] docs: state why web-framework merges before iteration 17 starts - NEXT PLAN step 1 now carries the reason: 17's edit targets (framework sources, [deps] resolution in main.ml, just web-app gate) exist only on the web-framework branch; unmerged start = branch stacked on unreviewed branch Co-Authored-By: Claude Opus 5 (1M context) --- docs/00-status.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/docs/00-status.md b/docs/00-status.md index c103354..c5d28c0 100644 --- a/docs/00-status.md +++ b/docs/00-status.md @@ -29,7 +29,12 @@ driving workload is now `docs/examples/writeonce-framework` consumed by what remains, in order: 1. Merge the `web-framework` branch to master (iterations 15–17 docs + code, - local only). + local only). Why first: everything iteration 17 edits exists ONLY on that + branch — the framework and web-app sources, the `[deps]` resolution code + in `compiler/bin/main.ml` (17's `internal/` rule lands in that exact + code), and the `just web-app` regression gate. Starting 17 unmerged means + stacking a branch on an unreviewed branch; merged, 17 is a small clean + diff off master. 2. Spec + plan from the settled decisions (prose only, per convention). 3. `kind = "library"` in `wo.toml` (default `"program"`): `woc ` on a library runs the FULL pipeline as a check — parse, typecheck, borrow