wdi-method 0.6.5 → 0.6.7

package/kit/.constitution/method/constitution.md

@@ -24,8 +24,8 @@ The repo layout is governed by `corpus-guide.md` and mapped by
 | `.what/` | What is promised |
 | `.how/` | How it is built |
 | `.what-rendered/` · `.how-rendered/` | The two above, assembled for a human to read — one page per gate, at the mirror path. Regenerated by `validate.py`, never edited, never read by a skill |
-| `_bmad-output/` | Run workspace; committed, not curated |
-| `.work/` | Scratch; committed, emptied when a task closes |
+| `_bmad-output/` | Run workspace; MUST be in git, not curated |
+| `.work/` | Scratch; MUST be in git, emptied when a task closes |
 | *(application roots)* | Application code — named and mapped in `.control/structure-codebase.md` |
 
 The method does not use a `docs/` layer for corpus or rules. A leftover `docs/`

package/kit/.constitution/method/repo-guide.md

@@ -48,6 +48,11 @@ drafts, exploratory output, a working paper for a change spanning several sessio
 It is **committed**, so that a session picked up on another machine finds it, and so a reviewer can
 see what a change was actually reasoning about.
 
+`.work/` MUST NOT be excluded from git, and neither MUST `_bmad-output/` or any corpus layer.
+`corpus-in-git` reports it and names the file and line. A pattern that excludes one noisy artifact
+INSIDE `.work/` — a vendored checkout, a tool's raw dumps, logs — is allowed and stays green; a
+pattern that drops the folder is not, because it leaves the material on one machine and in no clone.
+
 It is **ephemeral**, and the two together are what make its rules matter:
 
 - Any durable outcome MUST be moved out before the task closes — to the corpus if it is truth, to