wei-wuwei 0.5.0 → 0.6.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "wei-wuwei",
-  "version": "0.5.0",
+  "version": "0.6.1",
   "description": "為無為，則無不治 — a source-of-truth skills & agents framework that compiles to Claude Code and Codex (Cursor and Gemini CLI planned). Write once, run in every agent, govern without forcing.",
   "type": "module",
   "bin": {
@@ -19,7 +19,7 @@
   "scripts": {
     "build": "node bin/wuwei.js build",
     "check": "node bin/wuwei.js check",
-    "test": "sh test/smoke.sh",
+    "test": "sh test/smoke.sh && sh test/brief.sh",
     "install:targets": "node bin/wuwei.js install"
   },
   "engines": {

package/skills/wuwei-execute-phase/skill.md

@@ -207,16 +207,19 @@ get.
    | 6 | can it be one line? | `shrink:` |
    | 7 | only then: the minimum code that works | — |
 
-   Rung 2 is the one that has to be caught here rather than later: `stdlib:`
-   and `native:` are visible to anyone reading the diff, while a helper three
-   files over is invisible unless you already looked. `review:defects` looks
-   too — **both sides gate** — and **a `reuse:` finding from either is a rung
-   that was skipped**, so it counts in the round's convergence like any other.
+   Rung 2 is caught here first; `review:defects` looks too — **both sides
+   gate** — and **a `reuse:` finding from either is a rung that was skipped**,
+   so it counts in the round's convergence like any other.
 
    **The ladder shortens the solution, never the reading.** Trace every file
    the change touches and the flow it really takes first, then climb — the
    smallest change in the wrong place is not lazy, it is a second bug.
 
+   **A task ends with its prose sweep.** Before hand-back, grep every name,
+   path, number and fact the task removed, renamed or changed (`wuwei sites
+   <term>…`) across docs, comments, SPEC, ACCEPTANCE and phase files; fix each
+   hit in the same commit, and list the terms in the hand-back.
+
    **A fix goes at the proven cause, and when the cause is in a shared
    function, one guard there beats one per caller** — smaller diff, and the
    siblings stop being broken too. Find the call sites the way `## Invariants`
@@ -287,10 +290,8 @@ get.
    asked for. A `yagni:` on "config nobody sets" is exactly how one of these
    leaves.
 
-   The linter clause is deliberate: wuwei does not carry its own opinion on
-   what a project must check for — `review:code` already runs whatever the
-   project configured. A category with no configured check and no name in
-   `## Sign-off`'s threats is not this step's floor to enforce alone.
+   A category with no configured check and no name in `## Sign-off`'s threats
+   is not this step's floor to enforce alone.
 
    **Two ways the same size → the one that is correct on edge cases.** Fewer
    lines, never a flimsier algorithm.
@@ -347,8 +348,7 @@ get.
    and `contested` findings, **its `unread:` scopes**, and the phase's full
    range as something a lens may widen to. The unread scopes have to be passed
    explicitly and **read before the delta**: they are unchanged code by
-   definition, so nothing else in a delta round would bring them back. Rounds 2 and 3 otherwise pay four lenses to re-read code four
-   lenses already read.
+   definition, so nothing else in a delta round would bring them back.
 
    **Full scope comes back whenever the delta cannot be trusted**, and
    `wuwei-review` §6 lists when: the sync above actually moved the base, or the
@@ -372,6 +372,10 @@ get.
    find nothing, so nothing is given up — except one seam, named with the
    skip: a code-only fix can falsify prose it never touched, and until the
    stream audit only `review:defects`' prose-inside-code rule watches it.
+   **The mirror**: a delta with no code (§1 classifies by content) and no open
+   code-panel finding dispatches only `review:defects` from the code panel;
+   `review:code` still sits in the document panel. Each panel is sent only
+   its own files.
    Round 1 is untouched by this — it runs full scope, where §1's
    classification already decides which panels exist at all. Inside a phase the panel has two obligations it does not
    have standalone:
@@ -414,7 +418,8 @@ get.
    coordinate is where the defect became visible; the cause can sit in a file
    it never opened. Locate it first, and where it is not already proven that
    is `wuwei-debug-root-cause` — the skill is not only for red tests, and a
-   finding whose cause is a guess is the same situation.
+   finding whose cause is a guess is the same situation. **A fix that changes
+   a stated fact runs step 2's prose sweep** before its commit.
 
    **The finding disappearing is not the test; the cause being gone is.** One
    closed by widening a type, wrapping the call in a `try`, deleting the
@@ -474,7 +479,8 @@ get.
    | 1 or 2 | otherwise | next round |
    | ≥ 3 | no HIGH, no MED | **exit the loop** |
    | ≥ 3 | converging, HIGH or MED still open | next round |
-   | ≥ 2 | **`HIGH + MED` did not fall** | **stop and escalate**, recorded in the phase file |
+   | ≥ 2 | **`HIGH + MED` did not fall** — new findings replacing fixed ones is not falling | **stop and escalate**, recorded in the phase file |
+   | ≥ 2 | **one section raised MED or above two rounds running** | **stop and escalate**, offering to cut or defer that section |
 
    The round-1 exit is the only way out before three — **every lens that ran**,
    zero findings, not a size guess about the diff, and a mixed phase runs two
@@ -569,6 +575,18 @@ get.
    tree and no other), and states whether the composed result still matches
    `## Target architecture`.
 
+   **Work decided after the stream audit or a UAT, before the stream PR
+   merges, is a new phase — never a hand-cut branch:** cut on the stream
+   branch as `wuwei-plan-phases` step 4 cuts one (its `## Intended design`,
+   its ACCEPTANCE items, `review:`, `depends-on` what it actually depends on
+   — not "the last"), the scope change in SPEC's `## Sign-off`, `STATE.md`'s
+   total raised, `wuwei plan-check <stream>` green; then `wuwei claim <stream>
+   <NN>` cuts `wuwei/<stream>/NN-<name>`. A hand-cut branch has no phase
+   file: nothing `brief` or the next session sees. **Its exit:** a phase that
+   only fixes the audit's findings closes when the collator re-checks each
+   AUDIT.md row against its fix — no new panel; one that adds scope (a UAT's
+   new feature) gets the stream panel again, as a delta (`wuwei-review` §4).
+
    **Tracker**, subject to step 1's write rule:
 
    | granularity | on PR open | on merge |

package/skills/wuwei-plan-phases/skill.md

@@ -121,11 +121,12 @@ tags: [planning, workflow]
      in the reverted phase, no screen claiming what is no longer so;
    - a task checklist inside the file, each task carrying **`depends-on`**
      when it has one (omit when it has none, so an absent field means
-     independent, never forgotten). One task ≈ one commit;
+     independent, never forgotten). One task ≈ one commit. **A task documents
+     only what exists when its phase ends**: how to operate something a later
+     phase builds is a requirement list in that phase's file, not a runbook
+     here;
    - **a task dependency diagram** — mermaid, in the phase file, from the
-     `depends-on` fields. Order in a list cannot distinguish "this must come
-     second" from "I wrote it second"; the field carries the intent and the
-     diagram makes it readable at a glance. Omit only for a single-task
+     `depends-on` fields. Omit only for a single-task
      phase, and say so in one line;
    - an `## Intended design` section — the target structure as a mermaid
      diagram: the modules/interfaces this phase adds or changes and how they

package/skills/wuwei-review/references/lens-rules.md

@@ -39,4 +39,5 @@ changed in one is changed in the other.
 | drift | **a cross-branch or cross-version comparison uses §6's three-dot form** (`<a>...<b>`), not `<a> <b>` — tip-to-tip answers "do these differ", not "did `<b>` change what `<a>` changed", and is wrong exactly when `<a>` moved since the merge base. Three-dot fails closed (errors with no common ancestor); state which form you used |
 | drift | **a claim about an external platform's live configuration is checked against that platform, not the repo's copy of it** — on GitHub check both `.../branches/<branch>/protection` (classic, 404s under rulesets) and `.../rules/branches/<branch>` (rulesets); GET only, `per_page=100`, every page — a list endpoint's first page is a pattern with a reach. **A platform fact the dispatcher supplied (§1) is that check**; re-query only to dispute it. Can't query it → `PLAUSIBLE`, name what went unqueried, never fall back to the repo's copy as settling it |
 | drift | **a hit on a removed name is a finding only if its clause still asserts the name as current** — a clause recording the removal is not one. Quote the clause |
-| claims, drift | **a suggested fix is checked against precedent, not invented** — grep the repo for how the same kind of staleness was corrected before, and match that shape. A repo with an existing convention already answered the question. **And the anchor must survive the repo's merge settings** — a commit SHA dies under `allow_squash_merge`; anchor to the file tree. **A record (a plan, a summary, a decision log) is corrected beside the sentence, dated, not rewritten** — it is also evidence of what was believed |
+| claims, drift | **a suggested fix is checked against precedent, not invented** — grep the repo for how the same kind of staleness was corrected before, and match that shape. A repo with an existing convention already answered the question. **And the anchor must survive the merge** — a commit SHA dies when the target is squash-merged (recorded merge method first); anchor to the file tree. **A record (a plan, a summary, a decision log) is corrected beside the sentence, dated, not rewritten**; a self-declared snapshot (dated banner, executed phase's summary, generated codebase map) is not stale |
+| claims, structure, drift | **a failure that fires only once a later phase's artifact exists is LOW at most**, its `Action` a requirement in that phase's file |

package/skills/wuwei-review/references/stream.md

@@ -1,6 +1,11 @@
 # Stream panel (`wuwei-review` §4)
 
-Runs once, when every phase has merged and before the stream PR reaches main.
+Runs when every phase has merged and before the stream PR reaches main —
+and again, as a delta from the audited sha (the digest records both shas),
+after a phase that **adds scope** after the audit merges (a UAT's new
+feature). A phase that only fixes the audit's own findings gets no panel: the
+collator re-checks each AUDIT.md row against its fix, as the audit's first
+fixes were closed, and records the sha it checked at.
 Its subject is not a diff — it is **a delivery against the contract that
 authorised it**, a question no phase review is positioned to ask.
 

package/skills/wuwei-review/skill.md

@@ -124,7 +124,7 @@ wuwei's own; lenses report in its columns.
 Four fresh subagents in one dispatch, **not one reviewer**: a reviewer holding
 the implementer's context re-reads its own work with every justification
 already in mind. Each is an agent file, so its tier and its read-only tools
-are what dispatch actually reads — not a claim made here.
+are what dispatch reads — not a claim made here.
 
 | Reporter | Agent | Asks |
 |---|---|---|
@@ -149,10 +149,10 @@ but most carry `Bash`, and **`Bash` is bounded by instruction, not by the tool
 list**: a suite run rewrites snapshots, a build writes artifacts. **A control
 that needs a write — a mutation, a suite run against it — is taken in the
 lens's own throwaway worktree of the reviewed sha** (`wuwei worktree <lens>
-<sha>`, a path no other lens can pick; `--prune` after), never the
-dispatched tree and never another lens's: a
-mutation another lens reverts under you reads as "green after mutation", the
-second cause below. No worktree → `PLAUSIBLE`, naming the control. Base sync
+<sha>`, a path no other lens can pick; the dispatcher's `--prune <sha>`
+after the panel), never the dispatched tree and never another lens's: a
+mutation another lens reverts under you reads as "green after mutation". No
+worktree → `PLAUSIBLE`, naming the control. Base sync
 happens before dispatch, by the session dispatching — a reviewer that can move
 HEAD can change what it was sent to review.
 
@@ -235,8 +235,7 @@ mismatch between them is visible.
 Reviewing a document with no diff (`/wuwei-review <path>`) leaves the facts
 empty: say so, and `review:drift` falls back to the document's own assertions
 as the things to grep the repo for. **Tell each lens what the others
-cover**, the same as §2 — four identical prompts duplicate, four pointed at
-each other's gaps complement. **Running a gate is `review:claims`' job**:
+cover**, as in §2. **Running a gate is `review:claims`' job**:
 another lens that meets one names it for `claims` instead of running it,
 unless it already ran it for a finding of its own.
 
@@ -273,10 +272,14 @@ Give the derivation or do not give the number.
 
 ## 4. Stream panel
 
-Runs once, when every phase has merged and before the stream PR reaches main
-— `--stream`, or asked for in words. **Read `references/stream.md` before
-dispatching**: its five audits plus §2 over the composed diff, the coverage
-chain, and the `wuwei:` ledger.
+Runs when every phase has merged and before the stream PR reaches main.
+**Read `references/stream.md` before dispatching**: its five audits plus §2
+over the composed diff, the coverage chain, and the `wuwei:` ledger.
+
+**Work the audit or a UAT decides on is a new phase, never a hand-cut
+branch** (`wuwei-execute-phase` step 7). A phase fixing the audit's own
+findings: the collator re-checks each AUDIT.md row, no panel. New scope: the
+panel again, a delta from the audited sha.
 
 ## 5. Tools
 

package/wuwei.config.json

@@ -24,7 +24,7 @@
     "skills/wuwei-brainstorm/skill.md": 500,
     "skills/wuwei-commit-hygiene/skill.md": 200,
     "skills/wuwei-debug-root-cause/skill.md": 300,
-    "skills/wuwei-execute-phase/skill.md": 5400,
+    "skills/wuwei-execute-phase/skill.md": 5600,
     "skills/wuwei-grill/skill.md": 600,
     "skills/wuwei-legible-output/skill.md": 200,
     "skills/wuwei-map-codebase/skill.md": 1600,