igneum-labs 6ada573e0c Ember Tune: the core-clock knob's display (knob-24, 0.3.24; the hash lane's engine tip 2caf39c1 on release-0.3.24, the shipper's line of 7 October 2026): the card row and the Ember panel read the card's lock_* fields. The row's tune line carries the lock against the unlocked row at the same cap ("the lock: 112 W less for 1.3% of rate, knee at 1200 MHz"; "no rate lost" when nothing was lost; "clock unlocked, the knee came at 2472 MHz" when the first lock step was already past it) and, while the clock ladder runs, the search step inside the tune's ("locking clocks: step 4 of 9 · about 7 min left"). The panel adds a lock line (the measured point, the unlocked row, the knee in words: the rate fell, a hash mismatch with the clocks reset, or the floor with no knee), the rule the knob keeps (Ember never locks the clock below the knee by itself; going lower is the user's choice) and the knee as a dashed point on the curve with its sentence in the note; "no lever" names a card without a clock lock; a build without the fields shows nothing new. View.lockWords, kneeWords and LOCK_RULE in the pure block; the rows re-render when the lock fields change (sig). The mock gains scenario=knob (the 5090 locked at 1,300 MHz with the knee at 1,200, the 4070 in the clock search) and knob-search; ?tune=tuned and ?tune=running carry the fields. view.test.mjs: the lock, the knee words, the search step, no lever, the untouched older shape (known-failed first on build-2: "V.lockWords is not a function"; then 69 green). Display only: the knob and its fields stay the engine's. ... Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>		2026-10-08 08:32:19 +00:00
..
igneum-app	Ember Tune: the core-clock knob's display (knob-24, 0.3.24; the hash lane's engine tip 2caf39c1 on release-0.3.24, the shipper's line of 7 October 2026): the card row and the Ember panel read the card's lock_* fields. The row's tune line carries the lock against the unlocked row at the same cap ("the lock: 112 W less for 1.3% of rate, knee at 1200 MHz"; "no rate lost" when nothing was lost; "clock unlocked, the knee came at 2472 MHz" when the first lock step was already past it) and, while the clock ladder runs, the search step inside the tune's ("locking clocks: step 4 of 9 · about 7 min left"). The panel adds a lock line (the measured point, the unlocked row, the knee in words: the rate fell, a hash mismatch with the clocks reset, or the floor with no knee), the rule the knob keeps (Ember never locks the clock below the knee by itself; going lower is the user's choice) and the knee as a dashed point on the curve with its sentence in the note; "no lever" names a card without a clock lock; a build without the fields shows nothing new. View.lockWords, kneeWords and LOCK_RULE in the pure block; the rows re-render when the lock fields change (sig). The mock gains scenario=knob (the 5090 locked at 1,300 MHz with the knee at 1,200, the 4070 in the clock search) and knob-search; ?tune=tuned and ?tune=running carry the fields. view.test.mjs: the lock, the knee words, the search step, no lever, the untouched older shape (known-failed first on build-2: "V.lockWords is not a function"; then 69 green). Display only: the knob and its fields stay the engine's.	2026-10-08 08:32:19 +00:00
mac	The opening window size, one rule for both hosts (window-22, 7 October 2026, the project lead on PC 2: "why did the app open super wide?"): scaling-21's 80 percent of the work area scaled above 1920 wide opened 2752 by 1152 on a 3440-wide area and 3072 by 864 on a two-monitor span, and a remembered WindowW/WindowH could carry that into later starts; now app/windows/opening_size.h: the PRIMARY monitor's work area (MonitorFromPoint primary, never the virtual desktop), width 80 percent capped at 1440 up to a 1920-wide display and 1920 beyond, height from the width at 16:10 bounded by the work area, never wider than 1.6 times the height, never under 900 by 600, never over the work area; a remembered frame kept only when it fits the work area, the minimum and the aspect cap, and never saved when it would not; the Mac window mirrors the rule on NSScreen.screens.first and discards an autosave frame that fails it; opening_size_test.c compiles on the gate with cc (known-failed first: it could not compile before the header, and 0.3.21's rule fails the 3440 by 1440 and the 3840 by 1080 cases); host.cpp touched (the shipper's named line)	2026-10-07 18:34:47 +00:00
windows	0.3.24: version strings first (rule 15; the six places), the tree after 0.3.23's cut: class v5 by height on Devnet 3, the chain id at the v5 floor, the dashboard width caps, the pool daemon's reconnect and counters	2026-10-07 21:37:44 +00:00