Hotfix 0.1.2

Fill the processor time other apps leave free, at full speed

The CPU half heated far less than the GPU half. Two causes, both fixed:

• The rule stood the CPU half down entirely once other apps used 35 per
  cent of the processor. With 8 cores of normal-priority work on a
  20-thread PC, 0.1.1 burned nothing while 10.9 logical processors sat
  idle. The CPU half now fills the share other apps leave free, less a
  reserve of two logical processors for their bursts: in the same test
  0.1.2 burns 8.2 and leaves 1.5 idle. The GPU half keeps its rule.
• Windows gives idle-priority threads EcoQoS, which on the Core Ultra 7
  265K held 20 burner threads to 10.7 logical processors. Opting each
  thread out of execution-speed throttling keeps the idle priority and
  reached 18.8; opting out the process alone did not help (8.8).

The page's Task Manager demo now runs the new rule, so "the same rules
Hotfix follows" stays true, and "fill half the cores and Hotfix warms
with the other half" becomes "most of the other half", which is what it
does. The README describes both.

The landing page also gets a pass for phones and narrow windows. The
pinned hero could outgrow a short screen and slide its eyebrow under the
header; on phones and windows under 760 px tall it now flows. The Task
Manager mock keeps only the columns the demo is about, the research
results table stacks into one card per candidate, the number line scrolls
at a legible size, code wraps, the chat button shrinks to its icon, and
the floating purchase pill shows only from 1300 px, where it cannot
cover a heading.

Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com

Hotfix 0.1.1

Compute 2^-125 instead of infinity, and publish the research behind it

The product page now has a Den Frie Vilje Research post on what Hotfix
computes. For it to be true, the calculation had to change: 0.1.0's CPU
chains settled on 0.58886087, and its GPU shader fed the sum of its eight
chains back into itself, so every value overflowed to infinity after 43
passes, about a seventh of a second of heating.

Both halves now compute x * 1/2 + 2^-126, which settles on 2^-125 and
stays there, so every multiply-add returns the number it was given. With
a positive multiplier and every value a normal float, nothing of this
shape settles lower: at the answer x = m*x + c, both terms are at least
2^-126. Smaller, subnormal numbers would put CPUs on a slow path and be
flushed to zero on GPUs, and both would make less heat. The GPU buffer
starts on the answer, and the shader writes back the mean of its chains,
which is the answer again.

Heat did not suffer. Flat out on all 20 cores, the CPU calculation draws
126 to 130 W of package power against 121 to 122 W for the old one; the
GPU draws about 170 W either way, at 21.5 trillion multiply-adds a second
on an RTX 5070 Ti.

tests/AnswerCheck references the shipped assembly and holds it to the
claim: the constants, a CPU multiply-add returning its input, and every
GPU thread returning exactly 2^-125. CI runs it; on the GPU-less runner
it covers the CPU half. The README gains a roadmap pointing at #1
(climate science) and #2 (cheap, clean grid hours), and the version
moves to 0.1.1.

Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com

Hotfix 0.1.0

Add Hotfix, a tray app that warms the room with idle CPU and GPU time

The office is cold and the PCs in it are idle most of the day; every watt a
PC draws ends up as heat in the room. Hotfix keeps the processor and the
graphics card busy with register-only arithmetic, and is Den Frie Vilje's
first Windows release.

It must not slow down the work on the same PC, so it yields twice over,
separately for the CPU and the GPU:

• By priority: burner threads run at THREAD_PRIORITY_IDLE and the process
  asks the WDDM scheduler for the idle priority class, so other work is
  scheduled first.
• By turning down: measurements showed priority alone still cost an
  all-core job 25 per cent and a GPU job 12 per cent after a minute of
  heating, because a hot chip clocks lower and spends its turbo budget.
  A watcher reads other processes' CPU time and GPU engine counters twice a
  second, and each half's heat follows the room left on that part: full
  below 10 per cent CPU or 5 per cent GPU use by others, none above 35 and
  40 per cent. Heat drops at once and climbs back over ten seconds.

The UI is a native Win32 popup menu on a notification-area icon that works
as a heat gauge. Settings live under HKCU; Start with Windows is a Run key
that the uninstaller removes. Velopack builds a per-user Setup.exe and a
portable zip on each v* tag.

tests/YieldCheck times single-thread, all-core and GPU jobs at normal
priority with Hotfix off and on, and fails above a 10 per cent slowdown.
docs/ is the product page, a parody of Microsoft's flagship page register.

Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com