Reviewing a wskill (human ⇄ agent loop)

§ 1Purpose

Run the review loop: a human pins comments on the rendered book; an agent collects, fixes, and resolves them.

§ 2Prerequisites

• The wskill renders (just wskill-check passes).

§ 3Flowchart

§ 4Steps

$ wcl wdoc serve wdoc/book/main.wcl --comment

The dev server injects a review client: click any block on a rendered page, type a note, save. Comments land in a comments.wcl sidecar beside wskill.wcl — no rebuild, they re-appear on reload.

$ wcl wdoc review .        # blocks until the reviewer clicks "Send to agent"

When an agent has just made changes and wants review, it runs wcl wdoc review <root> — this registers it as waiting and blocks. The reviewer's toolbar shows a banner: rebuild, look at the changes, leave comments, then click Send to agent. The command unblocks and prints the comments.

$ wcl wdoc comments . --format json     # list (id, page, target, body)
$ wcl wdoc comments . resolve <id>      # delete one once addressed

Address each comment in the data files, resolve it by id, and rebuild. Comments pin to a page + block locator, so open the named page to see exactly what the note refers to.

More comments after the next Send? Fix and resolve again. The loop ends when wcl wdoc comments . lists nothing unresolved.