wei-wuwei 0.6.0 → 0.6.1

package/CHANGELOG.md

@@ -4,6 +4,10 @@ One section per published version, newest first. `wuwei update` prints the
 sections between the installed version and the new one before it asks;
 `wuwei check` fails when package.json's version has no section here.
 
+## 0.6.1
+
+- fix(retro): review rounds — prose sweep, later-phase artifacts, escalation by section (#106)
+
 ## 0.6.0
 
 - feat(brief): wuwei brief — the personal dashboard (stream personal-dashboard) (#75)

package/agents/wuwei-implementer/agent.md

@@ -21,6 +21,11 @@ the phase context, the ladder (climb it before writing), and step 4's floor.
 `wuwei-tdd` governs the task; commit as `wuwei-commit-hygiene` says — one
 concern per commit, the why in the body.
 
+**A task or a fix ends with the prose sweep** (step 2): grep every name,
+path, number and fact your change removed, renamed or changed — `wuwei sites
+<term>…` over docs, comments, SPEC, ACCEPTANCE and phase files — and fix each
+hit in the same commit.
+
 ## Out of scope
 
 - Another task, or the phase's next step — hand back instead.
@@ -31,4 +36,5 @@ concern per commit, the why in the body.
 ## Output contract
 
 What landed (commit shas, one line each), the tests that ran and their
-result, and anything you stopped short of — with why.
+result, the sweep's terms and any hit left unfixed, and anything you stopped
+short of — with why.

package/agents/wuwei-review-claims/agent.md

@@ -169,6 +169,9 @@ to `review:claims`. Categories: `wrong-claim` | `unsupported` | `stale`.
   said, `PLAUSIBLE` when you reasoned it — or when you constructed it on your
   machine and the claim is about the author's or CI's. **Nothing PLAUSIBLE is
   rated HIGH.**
+- **A failure that fires only once a later phase's artifact exists is LOW at
+  most**; its `Action` is a requirement for that phase's file, not more
+  procedure here.
 
 Quote the line, name what it contradicts, cite that. **And read past the line
 that confirms you** — a later section of the same file can reverse it, and
@@ -179,12 +182,14 @@ proposing how to correct a stale claim, grep the repo for how the same kind
 of staleness was resolved elsewhere — a sibling document's frontmatter field,
 a prior correction to the same kind of record. A repo with an existing
 convention for this already answered the question; inventing a new shape is
-itself an unsupported claim. **The anchor must survive the repo's merge
-settings**: a commit SHA dies under `allow_squash_merge` (`gh api
+itself an unsupported claim. **The anchor must survive the merge**: a commit
+SHA dies when this target is squash-merged — the merge method it records
+(sign-off, PR body) before `allow_squash_merge` (`gh api
 repos/<owner>/<repo> --jq .allow_squash_merge`); anchor to a tracked path, a
 heading, or a symbol that still exists. **A record is corrected, not
 rewritten**: for a plan, a summary or a decision log, the fix is a dated
-correction beside the original sentence.
+correction beside the original sentence; a self-declared snapshot (dated
+banner, executed phase's summary, generated codebase map) is not stale.
 
 **The `Action` cell carries `wuwei-review` §7's bar** — a fix is a claim about
 a mechanism and is verified like one, or the cell says it is untested.

package/agents/wuwei-review-drift/agent.md

@@ -155,6 +155,9 @@ to `review:drift`. Categories: `stale` | `wrong-claim` | `contradiction`.
   two quotes that disagree without that is `PLAUSIBLE`, because "which is
   wrong" is the finding; so is a side observed on your machine when the
   claim is about the author's or CI's. **Nothing PLAUSIBLE is rated HIGH.**
+- **A failure that fires only once a later phase's artifact exists is LOW at
+  most**; its `Action` is a requirement for that phase's file, not more
+  procedure here.
 
 **Read past the line that confirms you.** A quote from one section is not
 evidence until the rest of the file has been checked for the line that
@@ -167,11 +170,14 @@ corrected before — a sibling `REVIEW.md`'s convention for a status field, a
 prior fix to the same kind of stale record. Match that shape; do not invent
 one the repo has already answered differently. **A record is corrected, not
 rewritten**: for a plan, a summary or a decision log, the fix is a dated
-correction beside the original sentence — the record is also evidence of what
-was believed when.
-
-**The anchor must survive the repo's merge settings.** A commit SHA dies
-under `allow_squash_merge` (`gh api repos/<owner>/<repo> --jq
+correction beside the original sentence. **A document that declares itself
+a snapshot** — a dated banner, an executed phase's summary, a generated
+codebase map — **is not stale**: one dated banner at most, never a row per
+line.
+
+**The anchor must survive the merge.** A commit SHA dies when this target is
+squash-merged: the merge method it records (sign-off, PR body) before
+`allow_squash_merge` (`gh api repos/<owner>/<repo> --jq
 .allow_squash_merge`); anchor to a tracked path, a heading, or a symbol that
 still exists.
 

package/agents/wuwei-review-structure/agent.md

@@ -82,6 +82,9 @@ to `review:structure`. Categories: `missing` | `unfindable` |
   following §8 stops at step 1 believing nothing can deploy" is.
 - **Ev** — `CONFIRMED` when you followed the document's own order and hit it,
   `PLAUSIBLE` when you inferred it. **Nothing PLAUSIBLE is rated HIGH.**
+- **A failure that fires only once a later phase's artifact exists is LOW at
+  most**; its `Action` is a requirement for that phase's file, not more
+  procedure here.
 
 **Name the intended reader in the report's opening line, and where you got
 it** — what the document declares, what dispatch said, or that you asked. A

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "wei-wuwei",
-  "version": "0.6.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": {

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

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/skill.md

@@ -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.