chore(skill): harden post-accept carbonize cleanup so the agent can't skip it

After an LLM-triggered session where the carbonize cleanup got skipped
entirely (the instruction was buried as a single bullet among four
cases in live.md, and `_acceptResult.handled: true` felt like a
"done" signal), add three redundant reinforcements:

1. live-accept.mjs now emits a `todo` array on the event payload when
   carbonize is true, listing all five cleanup steps plus a pointer to
   reference/live.md. The agent reads this as part of the event JSON.

2. live-poll.mjs prints a loud multi-line stderr banner on every
   carbonize=true event. Even agents that parse only stdout JSON see
   stderr output and can't treat the event as handled without action.

3. reference/live.md pulls the carbonize branch out of the "Handle
   accept" bullet list into a dedicated "Required after accept
   (carbonize)" section with a numbered five-step checklist, a
   rationale paragraph for why skipping is bad, and an explicit
   "do not poll again until the file is clean" instruction.

The three layers are deliberately redundant: a future LLM that ignores
the reference text should still be caught by the stderr banner or the
in-event todo, and vice versa.

.github/skills/impeccable/reference/live.md

@@ -233,16 +233,26 @@ Remove the wrapper you inserted in Step 2. Nothing else to do.
 Event: `{id, variantId, _acceptResult}`. The poll script already ran `live-accept.mjs` to handle the file operation deterministically; the browser DOM is already updated.
 
 - `_acceptResult.handled: true` and `carbonize: false` — nothing to do. Poll again.
-- `_acceptResult.handled: true` and `carbonize: true` — the accepted variant has an inline `<style>` block marked with `impeccable-carbonize-start` / `impeccable-carbonize-end` comments. The accepted content itself is wrapped in a `<div data-impeccable-variant="N" style="display: contents">` so the existing `@scope ([data-impeccable-variant="N"])` rules keep rendering correctly until carbonize runs — the user sees the accepted design immediately, no visual gap. Spawn a **background agent** to:
-  1. Find the carbonize markers in the file.
-  2. Move the CSS rules into the project's proper stylesheet(s).
-  3. Rewrite `@scope` selectors to use the element's real classes instead of `[data-impeccable-variant]`.
-  4. Remove the `<div data-impeccable-variant="N">` wrapper and any helper classes/attributes from the accepted HTML.
-  5. Delete the carbonize markers and inline `<style>` block.
-  Poll again immediately; don't wait for the background agent.
+- `_acceptResult.handled: true` and `carbonize: true` — **post-accept cleanup is required before the next poll.** See the "Required after accept (carbonize)" section below. The `event._acceptResult.todo` field and a stderr banner both list the steps explicitly; neither is decorative.
 - `_acceptResult.handled: false, mode: "fallback"` — the session lived in a generated file and the script refused to persist there. You've already written the accepted variant into true source during Handle fallback Step 3; just clean up the temporary wrapper in the served file if any, and poll again.
 - `_acceptResult.handled: false` without `mode` — manual cleanup: read file, find markers, edit.
 
+### Required after accept (carbonize)
+
+When `_acceptResult.carbonize === true`, the accepted variant was stitched into source with helper markers and inline CSS so the browser can render it immediately with no visual gap. That stitch-in is **temporary**. The agent must rewrite it into permanent form before doing anything else. Skipping this leaves dead `@scope` rules for unaccepted variants, a pointless `data-impeccable-variant` wrapper, and `impeccable-carbonize-start/end` comment noise in the source file — all of which accumulate across sessions.
+
+Do these five steps in the current thread, synchronously, before the next poll. Do not poll again until the file is clean.
+
+1. **Locate the carbonize block** in the source file (`_acceptResult.file`). It's bracketed by `<!-- impeccable-carbonize-start SESSION_ID -->` and `<!-- impeccable-carbonize-end SESSION_ID -->` and contains a `<style data-impeccable-css="SESSION_ID">` element.
+2. **Move the CSS rules** into the project's real stylesheet. Which stylesheet depends on the project (e.g. `public/css/workflow.css` for this repo, or the component's co-located CSS file for a Vite/Next project — pick whichever already owns styling for the surrounding element).
+3. **Rewrite `@scope ([data-impeccable-variant="N"])` selectors** to target real, semantic classes on the accepted HTML. Example: `@scope ([data-impeccable-variant="2"]) { .v2-label { … } }` becomes `.why-visual--v2 .v2-label { … }` if the accepted element already carries `.why-visual--v2`, or pick/add a suitable class if it doesn't.
+4. **Unwrap the accepted content.** Delete the `<div data-impeccable-variant="N" style="display: contents">` that wraps it.
+5. **Delete the inline `<style>` block and both `<!-- impeccable-carbonize-start/end -->` markers.** Also drop any `@scope` rules for variants other than the accepted one — those are dead code now.
+
+Then poll again.
+
+A background agent may be used for the rewrite, but the current thread is responsible for verifying the five steps are complete before issuing the next poll. In practice, inline is usually faster and less error-prone.
+
 ## Handle `discard`
 
 Event: `{id, _acceptResult}`. The poll script already restored the original and removed all variant markers. Nothing to do. Poll again.

.github/skills/impeccable/scripts/live-accept.mjs

@@ -79,6 +79,21 @@ Output (JSON):
     console.log(JSON.stringify({ handled: true, file: relFile, carbonize: false, ...result }));
   } else {
     const result = handleAccept(id, variantNum, lines, targetFile);
+    // When carbonize is needed, emit an explicit todo in the payload so the
+    // agent can't miss it. The five steps are mirrored from reference/live.md
+    // "Required after accept" and are intentionally verbose: past runs skipped
+    // cleanup when the instruction was a single bullet.
+    if (result.carbonize) {
+      result.todo = [
+        'REQUIRED before next poll: post-accept carbonize cleanup.',
+        '1. Move the inline <style data-impeccable-css="' + id + '"> rules into the project stylesheet.',
+        '2. Rewrite @scope ([data-impeccable-variant="N"]) selectors to use the element\'s real classes.',
+        '3. Drop the <div data-impeccable-variant="N" style="display: contents"> wrapper around the accepted content.',
+        '4. Delete the <!-- impeccable-carbonize-start/end --> marker comments and the inline <style> block.',
+        '5. Remove any @scope blocks for variants other than the accepted one (dead code).',
+        'See reference/live.md "Required after accept" for the full checklist.',
+      ];
+    }
     console.log(JSON.stringify({ handled: true, file: relFile, ...result }));
   }
 }

.github/skills/impeccable/scripts/live-poll.mjs

@@ -156,6 +156,26 @@ Options:
       }
     }
 
+    // Loud stderr banner so the agent sees the cleanup requirement even if
+    // it parses stdout JSON and ignores nested fields. carbonize: true means
+    // the accepted variant was stitched in with helper markers + inline CSS
+    // that must be cleaned up before the next poll — see reference/live.md
+    // "Required after accept".
+    if (event._acceptResult?.carbonize === true) {
+      process.stderr.write(
+        '\n' +
+        '========================================================================\n' +
+        '  REQUIRED: post-accept carbonize cleanup before the next poll.\n' +
+        '  1. Move inline <style> rules into the project stylesheet.\n' +
+        '  2. Rewrite @scope ([data-impeccable-variant]) to real classes.\n' +
+        '  3. Drop the <div data-impeccable-variant> wrapper.\n' +
+        '  4. Delete impeccable-carbonize-start/end marker comments.\n' +
+        '  5. Drop @scope blocks for unaccepted variants.\n' +
+        '  Full checklist: reference/live.md, "Required after accept".\n' +
+        '========================================================================\n\n'
+      );
+    }
+
     // Print the event as JSON — the agent reads this from stdout
     console.log(JSON.stringify(event));
   } catch (err) {