Does Tailwind get its own writer

[stueydubs]

Question

Does Tailwind get its own writer, and what is a Patch when the change is a class?

webtweak's entire model is write a CSS rule for this element. On a Tailwind page there is no rule to write. The change is p-4 becoming p-6 in the HTML class attribute, in a different file, with a different failure mode.

This is not a variation on the CSS writer. It is a second writer with a different target.

Resolve:

• Whether Tailwind is a second back end behind the same edits file, a separate mode, or ruled out of scope with a recorded reason.
• What a Patch means when the change is a class swap rather than a declaration. The Patch currently carries property/value pairs and a media map - neither maps cleanly onto utility classes, and Tailwind expresses breakpoints as class prefixes (md:p-6) rather than as @media blocks.
• Whether the Fingerprint still works when the class list is the thing being mutated. Classes are one of its identity signals, so editing them changes the fingerprint of the element being edited.
• What happens to a value Tailwind has no class for. Round to the nearest step, write arbitrary-value syntax (p-[17px]), or refuse.
• Whether the Overlay's controls change shape - a font-size slider means something different when the target is a scale of tokens rather than a continuous value.

Blocked on the writer's uncertainty policy, so the second writer is not designed before the first one exists.