release 0.3.22 section 21: the core-clock knob cherry-picked onto release-0.3.24 (the union with the efficient-point ceiling), the measured Ember line from PC 1

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

docs/plans/release-0.3.22.md

@@ -192,3 +192,9 @@ Main's word on route (A) or (B) did not come (asked 01:41, 01:50, 01:53, 01:56 B
 **build-1's seed, the reading and the repair (03:0x BST):** /home/build/dn3seed.log ends at 02:09:05 BST at DAA 29,732 mid-stream with no stop, shutdown or panic line (an igneumd stop writes "igneumd has stopped"), so it was killed abruptly; it ran under nohup from a shell, so no journal names the killer, and the OOM record needs sudo (the morning's build-server lane reads it); the datadir intact (13 GB). The node lane's DAA reads 25,169 (00:52:38) and 28,906 (01:55:09 BST) came from it while it lived; the chain read 32,659 at 02:57:50 BST from node1-dn3's JSON on 28670 (the observer 32,660), past 32,400 at about 02:53 as computed. Restarted on the shipper's word at 03:00:09 BST on the kept datadir with the 2720d8d2 hands pair (igneumd f2cf6a87; the same flags; setsid nohup with stdout appended behind a dated banner, the stop line in its own log; the restart script at /tmp/dn3seed-restart.sh for the morning's move): digest ba75bf6f, object version 7, the N15 lines (resumed from the exec snapshot at tip 11,901, the records continuous), DAA 32,905 in step with node1-dn3, 22 peers at 03:02 (20 inbound, the fleet's dials returning; 38 before the kill). A repair of the hub the fleet dials, not a release change; the DAA reads come from 27632 again. dn3-floor-cut.sh (the fourth re-cut from a named minute: the DAA from 28670, the floor = the publish DAA plus 7,200 to the next 3,600, the commit, both mirrors, the gate set, about 20 minutes plus the fast-time pair's 14; the latest minute before the heights move is about 12:50 BST) stands ready for main's minute.
 
 **The attack-pass record lines on the frozen class v5 1c420786 (pairing e5a4ac5978462156), both PASS on the full 10^5:** F9 exhaustion (the last chunk 03:34:54 BST): 100,000 of 100,000 seeds through the chain path, 0 exhausted, 0 panics, 0 past attempt 31, max attempt 30, first-draw acceptance 0.3145, mean attempt index 2.185 (3.185 draws per seed); F1 redundancy (census.csv 05:20 BST): 100,000 of 100,000 programs, saved max 4.688 percent (0 over 5, 0 over 10), differential mismatches 0, verifier mismatches 0, 0 panics. Nothing from the attack lane holds the 0.3.24 move; the interim at 01:55 BST was the gate as main set it. **PC 1 overnight (the hash lane, 03:4x to 05:1x BST):** the 5090 floor2 pass ended by its 45 min cap with the rows to 400 MHz (every fingerprint matched; the card left at the 400 lock until the restore job at 03:46 BST brought it back to 2,880 MHz); the CA4 sparse runs read base rows (the research lane's second exe ran base on every variant, its third failed NVRTC on the card, "identifier d is undefined"; the finding with that lane); the microbench exe exited at once (rerun as -b after the packs); the packs job fell on a read-only $pid (fixed, rerun as -b from 05:12 BST); the 5080 Ember tune, the 9070 XT tune pass and the hot table follow; PC 2 held all night for main's word ("PC 2 clear" never given, take 3 never ran).
+
+## 21. The core-clock knob in 0.3.24 and the measured Ember line (07:1x BST, 8 October)
+
+**The knob:** the hash lane's 74585c91 (main's order of 7 October: the Ember clock ladder continues below 45 percent in 100 MHz steps to a 20 percent floor; the search stops at the knee, the first row more than the tolerance under the cap point's rate, or on a faulted row, the fingerprint check; the best MH per watt within tolerance is the point; lock_result and the card's lock_* fields for the UI; tests known-failed first on a fake helper) sat on the mirror's master, not on the release line; cherry-picked onto release-0.3.24 as e181f497 with ember.rs resolved as the union (the knob's floor and fine step beside the efficient-point ceiling of 7 October: EFFICIENT_W, DEFAULT_CAP_PCT, power_ceiling), the plan-count test updated to the knob's ladder on the 5090 (1 + 6 + 7; b6e2845f); app gate GREEN on build-1 (294 + 35 + 8), pre-push 60; the DMG re-cut under the lock on b6e2845f; the UI lane's drawing of the lock fields asked onto that tip. The rule: the knob never sets a lock below the knee without the user's own choice.
+
+**The measured Ember line (the Counter lane, read on PC 1 overnight):** the installed app's stock power-limit climb on the RTX 5080 lands at 60.3 MH/s at 123 W (0.489 MH/W, clock_cap 2,936; run-ca3-pc1-ember-5080-20261007 at 07:05 BST, the app's own tune complete before the script's cast fault), while the clock-lock grid on the same card gives 71.1 MH/s at 103.7 W at the 1,000 MHz lock (0.686 MH/W) and 71.2 at 146.6 W at 1,100 on class v4 (0.486) (run-ca3-pc1-v4-eff-5080-20261007-d at 02:54 BST), so the core-clock lock is worth about 40 percent more per watt and 18 percent more rate than the climb alone on the 5080; on the 5090 the knob's reference rows are class v4 at 1,200 MHz (133.8 MH/s at 305 W, 0.439) and class v3 at 1,300 (134.6 at 223 W, 0.603), the knee at 1,300 on both, measured four times (docs/bench-log.md, the 7 to 8 October entry). The 9070 XT tune row follows. Nothing else changes in the cut: the pin dfbd1e10 and the kit e6c088bb stand; the move on main's morning minute.