@imgly/codesign-mcp 0.2.0 → 0.2.1-next.20260820151648.ge42664a

package/assets/docs/handbook/SKILL.md

@@ -28,7 +28,7 @@ You MUST follow these steps in order for ANY canvas change:
 3. **Run `edit({ parent, code, note? })`** — execute the JS body. The response's first text part is JSON `{ revision, parent }` — save `revision`; it's your `parent` for the next edit.
 4. **Visually verify.** Call `preview({ blockIds: [<pageId>], revision })` — `revision` is REQUIRED; omit `blockIds` for every page. Never tell the user something "looks good" without seeing it yourself.
 
-5. **Judge & remediate before reporting done.** When the design is a candidate for "done", run the build → judge → remediate loop from the `judge` skill: score all 8 design axes against your actual `preview` renders, dry-run the applicable §6 Pass checklists (§6.1.11, §6.5.2 — in this skill's design-rules.md), and remediate any applicable axis below 8 via further `edit`s — then re-preview and re-judge. Never report an unjudged design as done.
+5. **Judge & remediate before reporting done.** When the design is a candidate for "done", run the `judge` loop: score the 8 axes against your actual `preview` renders, dry-run the §6.1.11 + §6.5.2 checklists (design-rules.md), remediate any applicable axis below 8 via further `edit`s, re-preview, re-judge. On pass, record `scorecard({ revision, verdict: 'pass' })`; later content `edit`s re-arm this step. Never report an unjudged design as done.
 
 Steps 1, 2, 4, and 5 are NOT optional. Step 3's `note` is encouraged: a one-liner describing what you accomplished, so you can re-ground later.
 

package/assets/docs/judge/SKILL.md

@@ -87,6 +87,7 @@ A variant that is clean on its own but diverges from the source on any of these
 
 4. **Remediate** — apply the fixes via `edit` on the latest revision. Remediation is surgical: fix the flagged blocks in place (handbook §5 "Prefer surgical fixes"); respect the reshape trap (line-height/font changes → reshape → re-apply every color/style range, §6.1.3). Never rebuild the scene to fix a spacing violation.
 5. **Re-preview → re-judge** — repeat from step 1 until the gate passes, but re-capture only what you changed: `preview({ blockIds: [<the pages you fixed>], revision })`. Re-rendering untouched pages puts near-identical copies of the same design at different revisions into the conversation, which makes it harder, not easier, to see what moved. Then report done, with the final scorecard.
+6. **Record the verdict** — `scorecard({ revision: <the revision the passing renders came from>, verdict: 'pass' })`. This closes the loop: `export` checks the latest recorded scorecard and reminds you when a delivered revision carries changes it does not cover. If the loop is being cut short with an axis still below 8 (e.g. the user says ship anyway), record `verdict: 'fail'` — the failure belongs on record, not silently dropped. **The record is a claim about work done**: never record a verdict for renders you did not score, and after any further content `edit` the gate re-arms — judge again, record again.
 
 ## Judging discipline