docs(skills): fix what an eval of the audio preset docs found

Ran three realistic mixing tasks against the skill and against its state
before the preset docs landed, six runs in all, and audited every claim in
`presets.md` against the shipped catalogue.

Four things came back.

**Nodes need a `label`, and the skill never said so.** Zero of six runs
wrote one — including the run that otherwise nailed the task, placing the
exact shipped Tame Boominess and Reduce Boxiness settings. The rack shows
that chain as two identical `peaking` rows, which is the precise problem
the named jobs exist to dissolve. The doc taught the numbers and lost the
naming, which was the point. `label` now appears in `attributes.md` with
the reason, and the jobs section shows a labelled node.

**Single-quoted attributes are invisible to `carve.mjs`.** Three of six
runs wrote `data-fx-chain='{...}'`. The browser reads through
`getAttribute` and does not care; the script finds attributes with a
`name="..."` regex, so the carve sees no existing chain and overwrites
work it cannot find. The convention was never written down.

**"18 presets" — 19 ship.** The list was complete; only the numeral was
wrong. Dropped rather than corrected, since nothing keeps it honest.

**Every job also ships inside a preset at identical settings**, so
`voice-clean` plus a Reduce Mud job cuts 250 Hz twice. The doc listed both
vocabularies without connecting them.

Also: "Not covered" said what not to do without saying what to do, and it
cost real behaviour — asked to add a de-esser, the run with the doc changed
nothing while the run without it shipped a narrow 7 kHz cut with the
trade-off stated. The section now names the honest fallback per gap and
says to apply it.

Verified clean: the five job frequencies, all five profile curves and the
parameters each derives, the level-matching claim, append-and-replace
semantics, the leveller's 80th percentile, `presetAmount` and
`fx.preset.<id>`.

Author: vanceingalls

skills/hyperframes-audio/SKILL.md

@@ -35,7 +35,7 @@ Exact JSON for each, and the rules a lane must satisfy: `references/attributes.m
 Every effect with its parameters, ranges and units: `references/fx-registry.md`.
 **Presets, named jobs and one-knob profiles, plus a symptom-to-fix table:
 `references/presets.md`** — read that before hand-building a chain, because one
-of the 18 presets or 5 jobs usually already names the problem.
+of the presets or named jobs usually already names the problem.
 
 ## How it fits together
 

skills/hyperframes-audio/references/attributes.md

@@ -12,13 +12,20 @@ that sounds plausible and is wrong.
 {
   "version": 1,
   "nodes": [
-    { "type": "highpass", "id": "n1", "params": { "frequency": 120, "q": 0.707, "poles": "2" } },
+    { "type": "highpass", "id": "n1", "label": "Remove Rumble", "params": { "frequency": 120, "q": 0.707, "poles": "2" } },
     { "type": "peaking", "id": "n2", "fromCarve": true, "params": { "frequency": 1600, "gain": -6, "q": 1.4 } },
     { "type": "limiter", "id": "n3", "enabled": false, "params": { "limit": -1, "attack": 5, "release": 50, "level_out": 0 } }
   ]
 }
 ```
 
+**Write these attributes double-quoted, with the JSON's own quotes as `"`.**
+The browser reads them through `getAttribute` and does not care, but
+`scripts/carve.mjs` finds them with a `name="..."` regex, so a single-quoted
+attribute is invisible to it — the carve reports no existing chain and quietly
+overwrites work it could not see. `&` becomes `&`; nothing else needs
+escaping.
+
 - **Order is signal order.** Each node processes what the one before produced.
 - `type` is an effect id from the registry. `params` are in the units a person
   thinks in — dB, ms, Hz — and out-of-range values are clamped on read, so a
@@ -28,6 +35,11 @@ that sounds plausible and is wrong.
   with no id loads fine but cannot be automated. Writing a chain by hand, any
   unique string works; Studio hands out the first free `n1`, `n2`, … so matching
   that convention keeps a hand-written chain and an edited one looking alike.
+- `label` is what the rack calls this node, replacing the effect's own name.
+  Write one whenever the node is doing a named job — a chain with two `peaking`
+  nodes otherwise shows the same row twice and the author cannot tell which is
+  the mud cut and which is the clarity lift. Presets and jobs always set it; a
+  hand-written node should too. See `presets.md` for the names they use.
 - `enabled: false` is bypass — the node stays in the chain, out of the signal
   path. Absent means enabled.
 - `fromCarve: true` marks a node the carve analysis generated. Re-running the

skills/hyperframes-audio/references/presets.md

@@ -64,7 +64,7 @@ Diagnose in this order, because each step changes what the next one hears:
 
 ## Presets
 
-18, in four families. Apply one and it **appends** — stacking a character preset
+Four families, listed in full below. Apply one and it **appends** — stacking a character preset
 onto an already-cleaned voice is a real thing to want. Re-applying one that is
 already present replaces its own nodes in place, because position in the chain
 is signal order.
@@ -135,6 +135,20 @@ Each is an ordinary `peaking` node underneath — the frequency is a starting
 point, not a cage. Prefer a job to a bare `peaking` when one matches: it arrives
 already aimed, and the rack names it for the work rather than the mechanism.
 
+Writing one by hand, **carry the name in `label`** — `{"type":"peaking","id":"n2",
+"label":"Reduce Mud","params":{"frequency":250,"gain":-3,"q":1.2}}`. The
+parameters alone are not the job. A chain with three unlabelled `peaking` nodes
+shows the author three identical rows, which is the exact problem jobs exist to
+dissolve.
+
+**Every job also ships inside a preset, at identical settings** — that is where
+the five came from. `boom-tame` *is* Tame Boominess; `harsh-tame` *is* Soften
+Harshness; `voice-clean` contains Reduce Mud and Add Clarity; `voice-broadcast`
+contains Reduce Boxiness. So check what a preset already contains before adding
+a job on top of it, or the cut lands twice — `voice-clean` plus a Reduce Mud job
+is −6 dB at 250 Hz where −3 was meant. The rack shows the contained nodes by
+name once the preset is expanded, which is the fastest way to see it.
+
 ---
 
 ## One-knob profiles
@@ -184,11 +198,19 @@ Two things measure the audio before they act, so they cannot be a fixed chain:
 
 ## Not covered by anything shipped
 
-Say so rather than reaching for the nearest preset:
-
-- **De-essing.** `harsh-tame` is a broad always-on cut, not a de-esser. A real
-  one needs a detector faster than the analysis hop available here.
-- **Tone matching** one track to another. The Tone EQ does the job predictably
-  by hand instead.
+Name the gap rather than reaching for the nearest preset and calling it the
+thing — but then **ship the honest fallback anyway**, with its cost stated. An
+author who asked for a fix and got only an explanation has been told something
+true and handed nothing. Say what it is, say what it costs, apply it.
+
+- **De-essing.** `harsh-tame` is a broad always-on cut centred a band too low,
+  not a de-esser. A real one needs a detector faster than the analysis hop
+  available here. *Fallback:* a narrow `peaking` cut in the Edge band — sweep
+  5–9 kHz to find where this voice actually spits, Q 3–4, −3 to −5 dB. It is
+  always on, so it costs a little air on every word; that trade is usually worth
+  it and is the author's to reject.
+- **Tone matching** one track to another. *Fallback:* the Tone EQ by hand, which
+  is predictable in a way a match curve derived from two takes would not be.
 - **Noise removal.** `room-gate` closes the gaps; the noise under speech is
-  untouched. A source with audible hiss under the voice needs a better source.
+  untouched. There is no fallback for hiss beneath the words — a source with
+  audible hiss needs a better source, and saying so is the whole answer.