v0.35.0 — Tokens that reach the page

An eleventh pass, eight items, driven a screenshot at a time. Its spine is that a control should mean what it says: a checkbox should belong to something, a label should describe what is true, and a switch should change something.

The largest finding was not in the list it came from. Asked why the typography tokens did nothing, the answer was that they had never done anything, on any site.

Fixed

• The typography tokens never reached the page. Ticking a role declared --heading-font-family and stopped, leaving the rule that uses it to Automatic.css, which only writes one once its Typography section is configured, and which is not there at all on a site without ACSS. Measured on a live install: nothing read either token, so Use for headings was a switch that changed no pixels. The block now carries the rule as well, on the same selectors ACSS uses, so a configured ACSS site gets two rules that agree and every other site gets one that works.
• The Automatic.css bridge never fired. The token block was attached to ACSS's own stylesheet handle at priority 99 and bailed when that handle was not registered yet, leaving an empty <style id="automaticcss-core-inline-css"> on the page. That ordering matters now the block carries a body rule, because ACSS sets body { font-family: system-ui } directly. It uses a handle of its own, enqueued last, so it no longer depends on another plugin's timing.
• Files in the trash claimed to be in use. "In use" was true of any file a family mapped, including a family that is trashed or disabled and therefore emits no @font-face at all. Three states now: in use, not loaded, unused. What counts as safe to delete is unchanged, because restoring a trashed family still needs its files.
• A select-all in one file table answered for the others. It compared how many files were selected against how many the table held, so choosing two files anywhere made a two-file table read as fully selected, and unticking any header cleared the selection in all three.
• Apply to no longer writes a selector its own role already covers. Both would have set font-family on the same element, leaving source order to decide.
• Tested up to said 6.8 while the plugin runs on 7.0.

Added

• A search field and format chips on Font files. The screen lists the whole shared fonts folder and has no ceiling, so it gained the toolbar its sibling screens already had.
• A select-all in each file table's head, scoped to that group, beside the one in the bulk bar that answers for every group at once.
• A notice when Etch is not active. The panel opens from the Etch Settings Bar and nowhere else, so without Etch the plugin activated, kept serving its fonts, and offered no way in.

Changed

• The select-all checkbox that floated above the grid is gone. It sat outside the cards it selected, with no label and nothing to head. Select all is a word in the bulk bar now, and it counts what a filter left on screen.
• Taking a typography token from another family says so, under the toggle rather than in a toast: it is unsaved state, so it behaves like unsaved state and Discard is what puts it back.

---

Full detail in CHANGELOG.md.