shoney/writeonce
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 1

docs: state why web-framework merges before iteration 17 starts

Browse source 
- 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) <noreply@anthropic.com>
This commit is contained in:
shoney.arickathil 2026-08-20 02:10:32 +02:00
parent b32e8a5073
commit b2aed69cb8
1 changed files with 6 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

7
docs/00-status.md
View file

@ -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 <dir>` on a
library runs the FULL pipeline as a check — parse, typecheck, borrow