* feat(input): the arithmetic of controller statistics - classes, batteries, makers, one pad seen twice (D155-D163)
Nothing reads a device yet. Domain.Input says whether an XInput state or a DualSense report is a pad in use and what
its battery is, adds a battery's readings up, counts switches and decides when two entries are one pad;
Application.Input holds one session's slices and turns them into a reading a second; InputSessionBuilder turns a
session's readings into its totals, its controllers as JSON and its timeline. TelemetrySample can carry a reading.
Every byte and reading under test was written by hand: no report from a real controller has passed through this code.
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* feat(input): a session can store what it was played with - schema 0024, the .partial file's chunk 11, both tiers (D160)
Nine columns on sessions (the time in front and its four classes, the switches of method, the sources that answered,
the controllers as JSON) and three on games (what a store lists of controller support), ADD COLUMN only. The .partial
file gains chunk 11, so a session recovered after the Agent died keeps its readings. SessionFinalizer.Build stores
them before the tier branch: hooked, unhooked and recovered sessions alike. The input series are sensor_blobs rows
named input.*, which the sensors' read now leaves out and FindInputSensorsAsync returns.
Nothing produces a reading yet. A ledger this build has opened cannot be opened by 0.1.0-beta.49 or earlier.
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* feat(input): the input reader, which the Agent does not start yet - raw input for controllers, XInput, the time of the last input (D155, D158, D159)
Application.Input.InputReader takes a slice about ten times a second from Infrastructure.Input.Win32InputBackend, on
the thread of InputDeviceHub, which exists only while a session has a view of it. It opens no device, sends nothing
to one and registers for no keyboard or mouse. tools/input-readonly-check.ps1 holds its Windows calls to a list.
With no controller at hand, what the reader does with one connected is not established.
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* fix(input): an arm of XInputPad.Battery's switch said what the default says (Qodana, on #464 after it merged)
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* test(input): no using that makes the file's own qualified names redundant (InspectCode)
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* test(input): what InspectCode reported in the reader's tests - redundant casts, a hub disposed twice, a suppression not needed
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* wip(input): the Agent records what a session was played with - the switch, the terms, the legal texts
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* style(input): import order in the Agent's composition; no redundant qualifier in a test (InspectCode)
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* wip(input): what a store lists of controller support, the input libraries, the game page's three rows
* wip(input): the game page's details tests expect the three controller rows; the library names test without ToLowerInvariant
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* docs(guide): the settings page listed Controllers and input twice
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* feat(input): a session's summary says what it was played with - the shares, the controllers and their batteries, two charts, marks on the frame-time chart; Trend, Compare and the CSV export (D155-D163)
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* release: 0.1.0-beta.50 - what a session was played with: controllers and input, read from outside the game; owner-only item 48 (D155-D163; with D152, D154)
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* test(app): the bar's gap is named by the class that has it; one sentence for the frames session's own sensors
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* test(app): the fixture's constant is named as the format check wants
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* test(input): the last-input time is asked not to go back, not to match .NET's tick - the two differ by the time the PC slept; the finding in 21_INPUT_DEVICES and HANDOFF's traps
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* refactor(app): the notes of a session's input need its controllers' record, not its row
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* docs(handoff): auto-merge does not wait for Qodana - the trap, and what was fixed here
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
---------
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
* feat(input): the arithmetic of controller statistics - classes, batteries, makers, one pad seen twice (D155-D163)
Nothing reads a device yet. Domain.Input says whether an XInput state or a DualSense report is a pad in use and what
its battery is, adds a battery's readings up, counts switches and decides when two entries are one pad;
Application.Input holds one session's slices and turns them into a reading a second; InputSessionBuilder turns a
session's readings into its totals, its controllers as JSON and its timeline. TelemetrySample can carry a reading.
Every byte and reading under test was written by hand: no report from a real controller has passed through this code.
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* feat(input): a session can store what it was played with - schema 0024, the .partial file's chunk 11, both tiers (D160)
Nine columns on sessions (the time in front and its four classes, the switches of method, the sources that answered,
the controllers as JSON) and three on games (what a store lists of controller support), ADD COLUMN only. The .partial
file gains chunk 11, so a session recovered after the Agent died keeps its readings. SessionFinalizer.Build stores
them before the tier branch: hooked, unhooked and recovered sessions alike. The input series are sensor_blobs rows
named input.*, which the sensors' read now leaves out and FindInputSensorsAsync returns.
Nothing produces a reading yet. A ledger this build has opened cannot be opened by 0.1.0-beta.49 or earlier.
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* feat(input): the input reader, which the Agent does not start yet - raw input for controllers, XInput, the time of the last input (D155, D158, D159)
Application.Input.InputReader takes a slice about ten times a second from Infrastructure.Input.Win32InputBackend, on
the thread of InputDeviceHub, which exists only while a session has a view of it. It opens no device, sends nothing
to one and registers for no keyboard or mouse. tools/input-readonly-check.ps1 holds its Windows calls to a list.
With no controller at hand, what the reader does with one connected is not established.
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* fix(input): an arm of XInputPad.Battery's switch said what the default says (Qodana, on #464 after it merged)
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* test(input): no using that makes the file's own qualified names redundant (InspectCode)
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* test(input): what InspectCode reported in the reader's tests - redundant casts, a hub disposed twice, a suppression not needed
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* wip(input): the Agent records what a session was played with - the switch, the terms, the legal texts
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* style(input): import order in the Agent's composition; no redundant qualifier in a test (InspectCode)
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* wip(input): what a store lists of controller support, the input libraries, the game page's three rows
* wip(input): the game page's details tests expect the three controller rows; the library names test without ToLowerInvariant
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* docs(guide): the settings page listed Controllers and input twice
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* feat(input): a session's summary says what it was played with - the shares, the controllers and their batteries, two charts, marks on the frame-time chart; Trend, Compare and the CSV export (D155-D163)
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* test(app): the bar's gap is named by the class that has it; one sentence for the frames session's own sensors
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* test(app): the fixture's constant is named as the format check wants
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
---------
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
* feat(input): the arithmetic of controller statistics - classes, batteries, makers, one pad seen twice (D155-D163)
Nothing reads a device yet. Domain.Input says whether an XInput state or a DualSense report is a pad in use and what
its battery is, adds a battery's readings up, counts switches and decides when two entries are one pad;
Application.Input holds one session's slices and turns them into a reading a second; InputSessionBuilder turns a
session's readings into its totals, its controllers as JSON and its timeline. TelemetrySample can carry a reading.
Every byte and reading under test was written by hand: no report from a real controller has passed through this code.
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* feat(input): a session can store what it was played with - schema 0024, the .partial file's chunk 11, both tiers (D160)
Nine columns on sessions (the time in front and its four classes, the switches of method, the sources that answered,
the controllers as JSON) and three on games (what a store lists of controller support), ADD COLUMN only. The .partial
file gains chunk 11, so a session recovered after the Agent died keeps its readings. SessionFinalizer.Build stores
them before the tier branch: hooked, unhooked and recovered sessions alike. The input series are sensor_blobs rows
named input.*, which the sensors' read now leaves out and FindInputSensorsAsync returns.
Nothing produces a reading yet. A ledger this build has opened cannot be opened by 0.1.0-beta.49 or earlier.
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* feat(input): the input reader, which the Agent does not start yet - raw input for controllers, XInput, the time of the last input (D155, D158, D159)
Application.Input.InputReader takes a slice about ten times a second from Infrastructure.Input.Win32InputBackend, on
the thread of InputDeviceHub, which exists only while a session has a view of it. It opens no device, sends nothing
to one and registers for no keyboard or mouse. tools/input-readonly-check.ps1 holds its Windows calls to a list.
With no controller at hand, what the reader does with one connected is not established.
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* fix(input): an arm of XInputPad.Battery's switch said what the default says (Qodana, on #464 after it merged)
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* test(input): no using that makes the file's own qualified names redundant (InspectCode)
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* test(input): what InspectCode reported in the reader's tests - redundant casts, a hub disposed twice, a suppression not needed
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* wip(input): the Agent records what a session was played with - the switch, the terms, the legal texts
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* style(input): import order in the Agent's composition; no redundant qualifier in a test (InspectCode)
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* wip(input): what a store lists of controller support, the input libraries, the game page's three rows
* wip(input): the game page's details tests expect the three controller rows; the library names test without ToLowerInvariant
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* docs(guide): the settings page listed Controllers and input twice
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
---------
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
* feat(input): the arithmetic of controller statistics - classes, batteries, makers, one pad seen twice (D155-D163)
Nothing reads a device yet. Domain.Input says whether an XInput state or a DualSense report is a pad in use and what
its battery is, adds a battery's readings up, counts switches and decides when two entries are one pad;
Application.Input holds one session's slices and turns them into a reading a second; InputSessionBuilder turns a
session's readings into its totals, its controllers as JSON and its timeline. TelemetrySample can carry a reading.
Every byte and reading under test was written by hand: no report from a real controller has passed through this code.
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* feat(input): a session can store what it was played with - schema 0024, the .partial file's chunk 11, both tiers (D160)
Nine columns on sessions (the time in front and its four classes, the switches of method, the sources that answered,
the controllers as JSON) and three on games (what a store lists of controller support), ADD COLUMN only. The .partial
file gains chunk 11, so a session recovered after the Agent died keeps its readings. SessionFinalizer.Build stores
them before the tier branch: hooked, unhooked and recovered sessions alike. The input series are sensor_blobs rows
named input.*, which the sensors' read now leaves out and FindInputSensorsAsync returns.
Nothing produces a reading yet. A ledger this build has opened cannot be opened by 0.1.0-beta.49 or earlier.
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* feat(input): the input reader, which the Agent does not start yet - raw input for controllers, XInput, the time of the last input (D155, D158, D159)
Application.Input.InputReader takes a slice about ten times a second from Infrastructure.Input.Win32InputBackend, on
the thread of InputDeviceHub, which exists only while a session has a view of it. It opens no device, sends nothing
to one and registers for no keyboard or mouse. tools/input-readonly-check.ps1 holds its Windows calls to a list.
With no controller at hand, what the reader does with one connected is not established.
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* fix(input): an arm of XInputPad.Battery's switch said what the default says (Qodana, on #464 after it merged)
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* test(input): no using that makes the file's own qualified names redundant (InspectCode)
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* test(input): what InspectCode reported in the reader's tests - redundant casts, a hub disposed twice, a suppression not needed
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* wip(input): the Agent records what a session was played with - the switch, the terms, the legal texts
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* style(input): import order in the Agent's composition; no redundant qualifier in a test (InspectCode)
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
---------
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
* feat(input): the arithmetic of controller statistics - classes, batteries, makers, one pad seen twice (D155-D163)
Nothing reads a device yet. Domain.Input says whether an XInput state or a DualSense report is a pad in use and what
its battery is, adds a battery's readings up, counts switches and decides when two entries are one pad;
Application.Input holds one session's slices and turns them into a reading a second; InputSessionBuilder turns a
session's readings into its totals, its controllers as JSON and its timeline. TelemetrySample can carry a reading.
Every byte and reading under test was written by hand: no report from a real controller has passed through this code.
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* feat(input): a session can store what it was played with - schema 0024, the .partial file's chunk 11, both tiers (D160)
Nine columns on sessions (the time in front and its four classes, the switches of method, the sources that answered,
the controllers as JSON) and three on games (what a store lists of controller support), ADD COLUMN only. The .partial
file gains chunk 11, so a session recovered after the Agent died keeps its readings. SessionFinalizer.Build stores
them before the tier branch: hooked, unhooked and recovered sessions alike. The input series are sensor_blobs rows
named input.*, which the sensors' read now leaves out and FindInputSensorsAsync returns.
Nothing produces a reading yet. A ledger this build has opened cannot be opened by 0.1.0-beta.49 or earlier.
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* feat(input): the input reader, which the Agent does not start yet - raw input for controllers, XInput, the time of the last input (D155, D158, D159)
Application.Input.InputReader takes a slice about ten times a second from Infrastructure.Input.Win32InputBackend, on
the thread of InputDeviceHub, which exists only while a session has a view of it. It opens no device, sends nothing
to one and registers for no keyboard or mouse. tools/input-readonly-check.ps1 holds its Windows calls to a list.
With no controller at hand, what the reader does with one connected is not established.
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* fix(input): an arm of XInputPad.Battery's switch said what the default says (Qodana, on #464 after it merged)
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* test(input): no using that makes the file's own qualified names redundant (InspectCode)
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* test(input): what InspectCode reported in the reader's tests - redundant casts, a hub disposed twice, a suppression not needed
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
---------
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
* feat(input): the arithmetic of controller statistics - classes, batteries, makers, one pad seen twice (D155-D163)
Nothing reads a device yet. Domain.Input says whether an XInput state or a DualSense report is a pad in use and what
its battery is, adds a battery's readings up, counts switches and decides when two entries are one pad;
Application.Input holds one session's slices and turns them into a reading a second; InputSessionBuilder turns a
session's readings into its totals, its controllers as JSON and its timeline. TelemetrySample can carry a reading.
Every byte and reading under test was written by hand: no report from a real controller has passed through this code.
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* feat(input): a session can store what it was played with - schema 0024, the .partial file's chunk 11, both tiers (D160)
Nine columns on sessions (the time in front and its four classes, the switches of method, the sources that answered,
the controllers as JSON) and three on games (what a store lists of controller support), ADD COLUMN only. The .partial
file gains chunk 11, so a session recovered after the Agent died keeps its readings. SessionFinalizer.Build stores
them before the tier branch: hooked, unhooked and recovered sessions alike. The input series are sensor_blobs rows
named input.*, which the sensors' read now leaves out and FindInputSensorsAsync returns.
Nothing produces a reading yet. A ledger this build has opened cannot be opened by 0.1.0-beta.49 or earlier.
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* fix(input): an arm of XInputPad.Battery's switch said what the default says (Qodana, on #464 after it merged)
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* test(input): no using that makes the file's own qualified names redundant (InspectCode)
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
---------
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
* docs(roadmap): the owner's order of work after the controller train - time played, more from stored data, shader-compilation stutter, the in-game overlay, winget and the Microsoft Store
The owner was shown six directions on 2026-11-14 and chose four, and added distribution; the
Store upload and its listing are the owner's by hand. What must be verified before anything is
promised of the two channels is listed as leads, not findings. Documents only.
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* docs(roadmap): FrameLedger has no product in Partner Center yet - the one there is another program of the owner's
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
---------
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
Nothing reads a device yet. Domain.Input says whether an XInput state or a DualSense report is a pad in use and what
its battery is, adds a battery's readings up, counts switches and decides when two entries are one pad;
Application.Input holds one session's slices and turns them into a reading a second; InputSessionBuilder turns a
session's readings into its totals, its controllers as JSON and its timeline. TelemetrySample can carry a reading.
Every byte and reading under test was written by hand: no report from a real controller has passed through this code.
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
The owner was shown the catalog (140 entries, 110 read) and what the ten entries of reach
Spike hold, read from Streamline 2.14.16's own headers, with what reading them takes: none
is an export, a game gets each function through slGetFeatureFunction and keeps the pointer,
so seeing its calls means handing the game a function of ours in place of Streamline's
(rule 4) - and a game that fetched its functions before the attach never calls it. The
owner closed it.
The ten are RefusedRoute; that reach's sentence names the third refused route in English,
Vietnamese and Japanese; the guide no longer says a later release reads more; 18_GPU's
inventory, 20_OPEN_QUESTIONS M15 and HANDOFF say train D is not built. Nothing that was
read stops being read; no hook, layout, schema or stored value changes.
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
* docs: owner-only item 47 read (the Cyberpunk difference is the driver's; the holes are gone from steady play); Streamline's Reflex and DLSS-RR guides read against the code
Item 47, run by the owner on 0.1.0-beta.49 (sessions 236-245), read from a copy of the
ledger and the Overlay's logs: in Cyberpunk 2077 without frame generation the driver's
active GPU time is longer than its two marks are apart on 4 917 of 5 394 frames, and on
none of 129 900 frames in five other games; samples without a report are confined to a
game's start; off means off; D141's stop fired in a real game for the first time.
NVIDIA's Streamline guides for Reflex and DLSS Ray Reconstruction (2.14.16), read whole:
the guide's page on Advanced metrics now says what bUseGameSleep and bLowLatencyMode
mean; two design tables no longer promise PC latency (D147); spike-notes 30 has what the
guides add. Two comments (fl_shm.h, dllmain.cpp) said super resolution and ray
reconstruction run together - they do not; comments only, no object code changes.
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* docs(handoff): item 47 (f) and (g) in the owner's words - the NVIDIA App's Low Latency Mode is off, no hitch
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* docs(handoff): item 47 (f) as the owner showed it - the NVIDIA App's Low Latency Mode is off for Cyberpunk 2077, the game's own Reflex is on
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* fix(app): the two GPU labels say what each figure is, not which holds the other (D152)
"GPU active render (idle time excluded)" and "GPU render, start to end (idle time included)"
followed NVIDIA's header, which defines the active time as the span between the driver's two
GPU marks less its idle time. Item 47 counted it on 0.1.0-beta.49: in Cyberpunk 2077 without
frame generation the active time is the longer of the two on 4 917 of 5 394 frames. The owner
chose to reword the labels. They now read "GPU active render (the driver's own figure)" and
"GPU render (between the driver's start and end marks)", in English, Vietnamese and Japanese;
the guide says why. Strings only: the numbers and the means are unchanged.
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* docs(handoff): D153 - of Reflex it is enough to tell whether a game has it: Reflex and PCL leave train D, D141's stop is unchanged
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
---------
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
* docs: owner-only item 47 read (the Cyberpunk difference is the driver's; the holes are gone from steady play); Streamline's Reflex and DLSS-RR guides read against the code
Item 47, run by the owner on 0.1.0-beta.49 (sessions 236-245), read from a copy of the
ledger and the Overlay's logs: in Cyberpunk 2077 without frame generation the driver's
active GPU time is longer than its two marks are apart on 4 917 of 5 394 frames, and on
none of 129 900 frames in five other games; samples without a report are confined to a
game's start; off means off; D141's stop fired in a real game for the first time.
NVIDIA's Streamline guides for Reflex and DLSS Ray Reconstruction (2.14.16), read whole:
the guide's page on Advanced metrics now says what bUseGameSleep and bLowLatencyMode
mean; two design tables no longer promise PC latency (D147); spike-notes 30 has what the
guides add. Two comments (fl_shm.h, dllmain.cpp) said super resolution and ray
reconstruction run together - they do not; comments only, no object code changes.
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* docs(handoff): item 47 (f) and (g) in the owner's words - the NVIDIA App's Low Latency Mode is off, no hitch
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* docs(handoff): item 47 (f) as the owner showed it - the NVIDIA App's Low Latency Mode is off for Cyberpunk 2077, the game's own Reflex is on
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
---------
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
* feat(overlay): the frames of NVIDIA's latency report are counted for the native log - each by its GPU span and the driver's active time, in batches that belong to one state of the sleep status (D148, D151; nothing published, no new call, no further member; in no release yet)
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* test(guard): the log case's expected words are widened before they are multiplied (Qodana native: bugprone-implicit-widening-of-multiplication-result, two)
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* fix(overlay): the watchdog's periodic tick is on a grid of one second, and a tick the loader woke no longer takes the driver read or publishes region 5 - a read a second whatever a tick's work took (D150, the Overlay's half; in no release yet)
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* fix(agent): a reading that waits for a sample is no longer overwritten by the next one - two wait, the older is carried first; the guide says whose switches the latency table shows (D150, the Agent's half; D151)
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* release: 0.1.0-beta.49 - item 46 read; the latency report's frames counted for the log, Reflex and frame generation together; a read a second on a grid; the Agent keeps the reading that waits (D148-D151); owner-only item 47
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* test(guard): the measurement case prints the numbers it parsed, never a line of the log as it stands (SonarCloud cppsecurity:S5145)
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
---------
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
* feat(overlay): the frames of NVIDIA's latency report are counted for the native log - each by its GPU span and the driver's active time, in batches that belong to one state of the sleep status (D148, D151; nothing published, no new call, no further member; in no release yet)
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* test(guard): the log case's expected words are widened before they are multiplied (Qodana native: bugprone-implicit-widening-of-multiplication-result, two)
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* fix(overlay): the watchdog's periodic tick is on a grid of one second, and a tick the loader woke no longer takes the driver read or publishes region 5 - a read a second whatever a tick's work took (D150, the Overlay's half; in no release yet)
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* fix(agent): a reading that waits for a sample is no longer overwritten by the next one - two wait, the older is carried first; the guide says whose switches the latency table shows (D150, the Agent's half; D151)
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* test(guard): the measurement case prints the numbers it parsed, never a line of the log as it stands (SonarCloud cppsecurity:S5145)
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
---------
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
* feat(overlay): the frames of NVIDIA's latency report are counted for the native log - each by its GPU span and the driver's active time, in batches that belong to one state of the sleep status (D148, D151; nothing published, no new call, no further member; in no release yet)
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* test(guard): the log case's expected words are widened before they are multiplied (Qodana native: bugprone-implicit-widening-of-multiplication-result, two)
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* fix(overlay): the watchdog's periodic tick is on a grid of one second, and a tick the loader woke no longer takes the driver read or publishes region 5 - a read a second whatever a tick's work took (D150, the Overlay's half; in no release yet)
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* test(guard): the measurement case prints the numbers it parsed, never a line of the log as it stands (SonarCloud cppsecurity:S5145)
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
---------
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
* feat(overlay): the frames of NVIDIA's latency report are counted for the native log - each by its GPU span and the driver's active time, in batches that belong to one state of the sleep status (D148, D151; nothing published, no new call, no further member; in no release yet)
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* test(guard): the log case's expected words are widened before they are multiplied (Qodana native: bugprone-implicit-widening-of-multiplication-result, two)
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
---------
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
* docs(handoff): owner-only item 46 read - ten sessions on beta.48: samples a second apart, both games gave the driver's own GPU times, the multipliers listed, off means off; active render longer than the span in Cyberpunk 2077 without frame generation, not explained
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* docs(handoff): item 46 (g) - the owner's answer: no hitch with Advanced metrics on
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
---------
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
* feat(overlay): two more members of NVIDIA's latency report - the driver's active GPU time and its GPU frame time - and every frame-generation multiplier a session saw; four reserved words, layout still 5; a read left by the session before is dropped (D142, D144; in no release yet)
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* feat(advanced): the driver's active GPU time and GPU frame time as two lines of their own; the GPU render label says what it includes; the multiplier row lists every value seen; the texts say two real games were read - Privacy Policy 2.21, Disclaimer 2.17 (D142-D145; in no release yet)
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* fix(telemetry): the poller keeps its period - it waited the whole interval after a poll's work, and on the owner's PC a second was 1.32 s; sensor_blobs.hz is the rate the samples had, not the constant 1 (D146; in no release yet)
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* release: 0.1.0-beta.48 - two real games read; the driver's own GPU times beside a span that includes idle (D142, D143); every frame-generation multiplier a session saw (D144); samples a second apart (D146); Privacy Policy 2.21, Disclaimer 2.17 (D145); owner-only item 46
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
---------
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
* feat(overlay): two more members of NVIDIA's latency report - the driver's active GPU time and its GPU frame time - and every frame-generation multiplier a session saw; four reserved words, layout still 5; a read left by the session before is dropped (D142, D144; in no release yet)
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* feat(advanced): the driver's active GPU time and GPU frame time as two lines of their own; the GPU render label says what it includes; the multiplier row lists every value seen; the texts say two real games were read - Privacy Policy 2.21, Disclaimer 2.17 (D142-D145; in no release yet)
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* fix(telemetry): the poller keeps its period - it waited the whole interval after a poll's work, and on the owner's PC a second was 1.32 s; sensor_blobs.hz is the rate the samples had, not the constant 1 (D146; in no release yet)
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
---------
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
* feat(overlay): two more members of NVIDIA's latency report - the driver's active GPU time and its GPU frame time - and every frame-generation multiplier a session saw; four reserved words, layout still 5; a read left by the session before is dropped (D142, D144; in no release yet)
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* feat(advanced): the driver's active GPU time and GPU frame time as two lines of their own; the GPU render label says what it includes; the multiplier row lists every value seen; the texts say two real games were read - Privacy Policy 2.21, Disclaimer 2.17 (D142-D145; in no release yet)
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
---------
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
* feat(advanced): the driver's latency report in the Agent and the App - seven series and one table under Latency, what became of the read said in words; reaches GameDriver and RefusedRoute; Privacy Policy 2.20 and Disclaimer 2.16; owner-only item 45 (D132, D136, D138-D141; in no release yet)
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* docs: the owner kept the 2 ms latch at one call after the busy-PC run (D141)
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* test(app): no redundant qualifier and no redundant null suppression in the driver-read tests (Qodana)
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
---------
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
* feat(overlay): the driver's latency report, read while a session asks - two getters of an nvapi64.dll the game loaded, about once a second on the presenting thread, behind a gate of four states; a module beside the executable refused, a fault or a call of 2 ms the last one; the gates that hold it (D132, D136, D138-D141; in no release yet)
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* fix(overlay): the latency log line measures its path with a bound (cpp:S5813)
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* fix(overlay): the resolve switch names every outcome (Qodana native: clang-diagnostic-switch-enum)
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
---------
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
* spike(reflex): the leg with a sleep - the decision table, written before the run (D139)
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* spike(reflex): the getters while the game sleeps - a leg of the probe with a sleep mode, three runs, no stop condition (D139); the plan's four decisions (D138-D141) and the train's design in HANDOFF
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* feat(overlay): the PATCH_BATCH line says how a batch ended - install / restore for one apply, install singly / restore singly with the count in the high half of b (D137)
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* feat(shm): the Reflex latency words of region 5 - ten reserved words named, written by nobody; the layout stays 5 (D136, D138)
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
---------
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
* spike(reflex): the leg with a sleep - the decision table, written before the run (D139)
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* spike(reflex): the getters while the game sleeps - a leg of the probe with a sleep mode, three runs, no stop condition (D139); the plan's four decisions (D138-D141) and the train's design in HANDOFF
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* feat(overlay): the PATCH_BATCH line says how a batch ended - install / restore for one apply, install singly / restore singly with the count in the high half of b (D137)
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
---------
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
* spike(reflex): the leg with a sleep - the decision table, written before the run (D139)
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* spike(reflex): the getters while the game sleeps - a leg of the probe with a sleep mode, three runs, no stop condition (D139); the plan's four decisions (D138-D141) and the train's design in HANDOFF
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
---------
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
* docs(handoff): what the owner's five sessions on 0.1.0-beta.46 showed - eighteen install batches in five games, sixteen at 81-262 ms whatever they held, two not explained (Hogwarts Legacy 1.26 s, Cyberpunk 2077 0.61 s); the stop while a game runs was not exercised; item 44's sentence about a fallback corrected
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* docs: the owner's answers of 2026-11-13 - Reflex route D goes to a plan for one real title, Cyberpunk 2077 (D136); the PATCH_BATCH line says how a batch ended, with the next release (D137)
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
---------
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
On 2026-11-13 security software removed a freshly linked fl_guard_test.exe while a local gate ran: the process
ended early with exit code 0 and ctest printed "fl_guard ... Passed 0.66 sec" for a suite that takes three
minutes. Only the next test, which runs the same executable, made the gate red.
- src/native/CMakeLists.txt: fl_test_completes(<test> <regex>...) and fl_catch2_test_completes(<test>...) set the
line a test must print (Catch2: "All tests passed (", or its summary row with a skipped case, never a row that
names a failure); fl_require_every_test_completes() fails the configure when a test in tests/ or tools/ was
registered without one.
- All 35 tests go through one of the two, each on the last line it already printed; no program changed.
- Four canaries print what a Catch2 run would - nothing, its last line, a row with a skipped case, a row with a
failure beside "passed" - through the same helper; the two that must be red are WILL_FAIL.
- fl_nvapi_bridge, fl_process_stats, fl_nvapi_probe and fl_signer_probe passed on a line printed in the middle of
their run; they now need it and, after it, their last line. fl_nvapi_probe also passed whatever followed its
branch line - a pass expression makes ctest ignore the exit code.
Docs: 14_TESTING, HANDOFF, the changelog. No shipped code.
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
- Released 2026-11-13T11:10:28Z from the signed tag on 47f010a by run 43412434074; eight assets, seven digests
equal, the build id in four natives, the delta 634,023 bytes, the wiki run. SonarCloud's gate passed on the
release's commit with no issue open; Qodana's two reports are green on it.
- Security software on the development PC removed the freshly linked fl_guard_test.exe while a local gate ran, and
ctest reported the run that was cut short as Passed after 0.66 s (the suite takes 181 s); only the next test,
which runs the same executable, made the gate red. Recorded with a proposal; nothing changed.
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
* spike: Reflex route D on the harness - the driver's two getters called from an unshipped probe, against a stand-in nvapi64.dll and against the installed driver; a decision table written before the runs, and what they showed (spike-notes §31; D132)
No shipped code changes and no game was touched.
- tools/fl-probe-reflex: fl_reflex_candidate.h, the call sequence that would move into the Overlay (find
nvapi64.dll only if the process already holds it, resolve NvAPI_D3D_GetLatency and NvAPI_D3D_GetSleepStatus by
interface id, call them SEH-guarded); --stub against tools/vendor-stubs/stub_nvapi64.cpp (ctest
fl_reflex_probe_stub); --real against the installed driver with the probe playing the game's part - it sets
latency markers on its own device, in its own process.
- docs/spike-notes/31-reflex-route-d-harness.md: nine pre-committed measurements and their results. No fault
before initialisation, without markers, or beside a marker-setting thread (38 million reads); a call costs half
a microsecond; the Direct3D 12 device the Overlay holds is the object the driver takes; the report's unit is
microseconds. The call belongs on the presenting thread once a second, not on the watchdog. The newest frames
of a report are not final. Ends in the owner's go or no for one real title.
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* docs(spike): §31 in the index, §M14 and §30 point at what the harness spike showed; the probe and its stub in the build document and CLAUDE.md's tools list
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* docs(spike): HANDOFF says the route D spike is done and what a plan must keep from it; the changelog names the probe as a developer's tool
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* fix(probe): the Reflex probe's Measure takes its callable by const reference - a forwarding reference it never forwarded (Qodana native, cppcoreguidelines-missing-std-forward)
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* fix(probe): what SonarCloud reported on the Reflex probe - the counter read through the union member it was initialised with, a guard for an empty measurement, NvU32 printed as what it is, a variable no longer named module; and the note says what a fourth run measured (1.5 us a call, 70 us at worst)
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
---------
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
- docs/changelog/0.1.0-beta.46.md takes [Unreleased] as it stood, under an introduction that says what the
release is and is not; CHANGELOG.md keeps an empty [Unreleased] and gains the table row.
- docs/HANDOFF.md: the beta.45 section moves verbatim to docs/handoff/history/0.1.0-beta.45.md; a new START HERE -
what the release decided beyond D132-D135 (the refused first design and the rules that replaced it, the gate, the
engine's verdict, the fallback), the traps of the train, NEXT, what is left open.
- Owner-only item 44, with what each outcome means written before the run.
- The release lines: ACCESSIBILITY.md, LIMITATIONS.md, README.md, legal/ACCURACY.md, legal/DISCLAIMER.md.
Documents only; nothing under src/ changes.
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
* feat(overlay): patches go in and come out under one stop of the game's threads - MinHook's queue for the rows a tick finds and for the stop, behind a gate, with only patches that are still ours ever marked for a restore (beta.46 PR-1; D134)
MinHook stops every thread of the process to write a jump, and enabling or disabling one hook did that for one
jump: thirteen Streamline patches took 0.74 s to 2.8 s of a game's start in the owner's sessions of 2026-11-13,
and a stop restored its patches the same way.
- fl_patch_registry.h: fl::patch::Batch (Add: slot and create, nothing marked; Commit: enable them all, then the
re-read of the flag Install makes) and fl::patch::RestoreAll, the stop's walk. Install and Registry untouched.
- dllmain.cpp: InstallUpscalerHooks queues every row a tick finds something for and commits once, before the
families published "when whole"; InstallRtHooks batches its two; StopObserving calls RestoreAll. A patch's
HOOK_INSTALLED line, family bit and latch come in that order and only once it is in. A new log line an apply,
PATCH_BATCH install|restore (a = microseconds, b = patches). No hook body changed.
- MH_ApplyQueued applies every hook whose mark differs from its state, whoever marked it. So no mark is left
standing, only a patch that is still ours is marked for a restore and nothing is marked "all" (a draft that did
could put a patch back in after a stop; refused on review against hook.c), and mark, apply and commit happen
inside a gate - a slim lock on no hook body's path, never held across a symbol lookup, re-entered by its owner.
The verdict on an install is the engine's, not the bytes'. An apply stops at its first failure: the hooks
after it are enabled or restored one at a time.
Measured on hook-harness's Streamline target, three runs before and after: the nine Advanced-only patches,
0.60 / 0.70 / 0.60 s one by one, are one batch of 81 / 90 / 78 ms; the stop's eighteen, 1.37 / 1.56 / 1.37 s,
are one apply of 77 / 90 / 76 ms; unhook requested to UNHOOKED, 1.27-1.48 s, is 94-109 ms.
ctest fl_unhook_inline: six new cases, against real MinHook and against a model of its table. fl_guard's
Streamline [advanced] case asserts the batch lines. No real game has been run.
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* fix(overlay, tests): what SonarCloud reported on the batching pull request - the performance counter read through the union member it was initialised with, a test's strlen, and a model index that could be -1
- dllmain.cpp: QpcNow() names QuadPart in the LARGE_INTEGER's initialiser, so the member read back is the member
the union holds (cpp:S6232, four times on MicrosSince); MicrosSince takes the ticks.
- guard_test.cpp: the log-field helper takes a string_view instead of calling strlen (cpp:S5813).
- unhook_inline_test.cpp: the model's Set refuses an index outside its table and the test marks a foreign patch
through a method that looks the target up (cpp:S3519: enabled[-1] if Find had failed).
No behaviour changes. The batch timings on the fixture are as before (four in 70 ms, nine in 70 ms, eighteen
out in 76 ms).
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
---------
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
Read 2026-11-13 from a copy of the ledger (sessions 190-196), seven overlay logs, the Agent's log and Windows'
application log. Every session hooked, normal, no fault counted, no PATCH_FAILED. slIsFeatureSupported read in
every Streamline session; slIsFeatureLoaded in three games; slSetFeatureLoaded in two; slFreeResources and
slShutdown once in one game each; slAllocateResources in none. Hogwarts Legacy and Black Myth: Wukong fault
while closing at the offsets they had before. Thirteen interposer patches take 0.7 s to 2.8 s of a game's start.
Off means off and a stop while a game runs were not exercised. The pages that said "not confirmed" are corrected.
The owner's decisions the same day: D132 (route D goes to a spike on hook-harness and a stub; a driver's
read-only getter with the device of the hooked swap chain is inside rule 4 - CLAUDE.md carries the note, and
nothing shipped does it), D133 (route C refused, the ETW route stays closed), D134 (batch installs and restores
through MinHook's queue, released alone as 0.1.0-beta.46), D135 (slAllocateResources keeps its patch).
Documents only.
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
- docs/HANDOFF.md: released 2026-11-12T16:40:42Z from the signed tag on 550d830 by run 43257803723; eight assets,
seven digests equal, the build id in four natives, the delta 1,762,465 bytes, the wiki run, what Qodana said.
- SonarCloud's quality gate failed on 550d830 on duplicated lines on new code (3.7 % against 3 %), with no issue
open: the six new members of FlHookFamily and of its Domain mirror HookFamilies, which are the same on purpose
and held together by MetricEnumMirrorTests. SonarQube.Analysis.xml leaves the mirror out of the detection, with
the reason there and in docs/13_CI_CD.md.
Whether the gate is green again is for the analysis of this commit on main to say.
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
- docs/changelog/0.1.0-beta.45.md takes [Unreleased] as it stood, under an introduction that says what the
release is and is not; CHANGELOG.md keeps an empty [Unreleased] and gains the table row.
- docs/HANDOFF.md: the beta.44 section moves verbatim to docs/handoff/history/0.1.0-beta.44.md; a new START
HERE - what the release decided beyond D129-D131, the traps of the train, NEXT, what is left open, and one
finding not acted on: a stop restores its patches one after another, about 160 ms each.
- Owner-only item 43, with what each outcome means written before the run.
- The release lines: ACCESSIBILITY.md, LIMITATIONS.md, README.md, legal/ACCURACY.md, legal/DISCLAIMER.md.
Documents only; nothing under src/ changes.
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
Train C's spike as a document. Hooking NVAPI's latency functions is the refused class; hooking Streamline's
Reflex and PCL functions is train D's wrapper and would miss a game that fetched them before the attach;
the Overlay calling slReflexGetState breaks the vendor's stated thread contract. What remains is the
Overlay calling two driver getters with the game's device (no patch; the owner's ruling on rule 4 first)
and a no-injection ETW route that gives the game-side markers only. Every Streamline game the owner ran
asks about kFeatureReflex. nvapi64.dll exports two functions on the dev box, not one.
No shipped code changes.
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
The Agent and the App read what the six hooks of this release keep.
- InGameAdvancedSampler: sl.feature.support (<feature> · slIsFeatureSupported as NVIDIA's own sl::Result
name, a refusal included; <feature> · slIsFeatureLoaded on or off) and sl.feature.lifecycle
(<feature> · slSetFeatureLoaded on, off or both; slAllocateResources and slFreeResources as counts,
">= 15" where the four bits stopped; a row slShutdown). A feature with nothing to say has no row.
- AdvancedSources: one member a call (Read / NeverCalled / NotHooked), null in every row written before.
The page says the six in one sentence, each call by its name under what became of it.
- sl.init.preferences has reach BeforeAttach (D129): the game makes the call once, before FrameLedger is
inside it. No catalog entry waits for a hook any more.
- Privacy Policy 2.19 (wording approved with the plan): what is read for each feature, and two more
things never read - what identifies the graphics card a game hands over with its question, and the
content of a graphics resource. "Four further calls" is ten. The Disclaimer stays 2.15.
- Strings in en, vi, ja. LIMITATIONS, the guide, docs 06/08/18, the accuracy block (three copies),
CLAUDE.md, the changelog.
No native change, no layout change (5), no schema change (23). The Agent's end-to-end test on the
harness's Streamline target stores both facts and all six calls as Read; the FSR target stores NotHooked.
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
Three more patch sites on sl.interposer.dll (family bits 20-22), installed only in a process that was asked for
Advanced metrics. The feature's id is the only argument looked at; the command buffer and the viewport are forwarded
and never read. The two that sit on a game's way out note the call and then call the original, and run nothing after
it. Two four-bit counts in word 1 of the feature's slot, and slShutdowns in the first of three reserved words (layout
5 as it was) with FL_ADV_VALID_SL_SHUTDOWN; all three are a session's and a new request clears them.
Measured (the detours' bodies on the headers, the Overlay's flags, 20 M calls x 3): slAllocateResources +0.70/+0.72/
+0.80 ns not asked, +10.43/+10.53/+10.74 asked; slFreeResources +0.61/+0.84/+0.58, +10.33/+10.57/+10.44; slShutdown
within the bench's noise not asked, +3.39/+3.37/+3.52 asked.
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
* feat(overlay): hook slIsFeatureSupported, slIsFeatureLoaded and slSetFeatureLoaded - whether Streamline says a feature is supported and loaded, and the game switching it, read only once the Agent has asked; the adapter a game asks about is never read; slInit is not hooked (beta.45 PR-1; D129-D131)
Three new patch sites on sl.interposer.dll, a row and a family bit each (17-19), installed only in a process that
was asked for Advanced metrics (D111). Bare arguments and results, no vendor struct: the feature's id, the sl::Result
of slIsFeatureSupported (a refusal is the answer), the bool slIsFeatureLoaded wrote when it said OK, the bool the
game passed to slSetFeatureLoaded. sl::AdapterInfo is forwarded and never looked at, and the fields gate refuses the
names of its members in code loaded into a game (D131). Packed into word 1 of the feature's slot (layout 5 as it
was); the switch bits are a session's, the answers the process's.
Also: a stop restores a patch in about 160 ms, and the watchdog's wait for the stop's log lines was two seconds
whatever the number of patches - with fifteen the log lost its last UNHOOK_RESTORED lines. The wait is now a quarter
of a second for every patch the registry can hold.
Measured (the detours' bodies on the headers, the Overlay's flags, 20 M calls x 3): slIsFeatureSupported +1.50/+1.48/
+1.50 ns not asked, +11.97/+11.98/+12.08 asked; slIsFeatureLoaded +1.79/+1.77/+1.89, +12.35/+12.31/+12.33;
slSetFeatureLoaded +1.44/+1.47/+1.80, +11.28/+11.54/+11.45.
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* fix(harness): compute two feature-slot indices in size_t in the unit probe (Qodana native, bugprone-implicit-widening-of-multiplication-result)
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
---------
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
Read from a copy of the ledger, the Agent's log, eight overlay logs and Windows' application log. Both calls read
on five games; the degrees fix reads right on Cyberpunk 2077; a game with no Streamline says not hooked. Not
exercised: off means off. Not explained: Valor Mortis's crash at 51 s (also on beta.40), Black Myth: Wukong's fault
in Steam's crash handler at exit. HANDOFF's NEXT carries the owner's word on the next version (slInit,
slIsFeatureSupported and other parts, to be planned).
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
* feat(advanced): a session shows which version each Streamline feature is and what it requires - two catalog entries read inside the game, and for each of the two calls whether it was read, not hooked, or hooked and not asked again; Privacy Policy 2.18 (beta.44 PR-3)
The Agent turns region 5's feature slots into sl.feature.versions and sl.feature.requirements, rows named
<feature> - <member> in the vendor's words; AdvancedSources says for each call which of three things happened,
and the App words hooked-and-not-seen for a start-up call as what it is: the game did not ask again. The Agent's
end-to-end tests run a Streamline target for the first time. Privacy Policy 2.18 names what Streamline answers
about a feature and what of the answer is never read. No layout change (5), no schema change (23).
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* style(recorder): drop two namespace qualifiers the new using made redundant (Qodana managed, RedundantNameQualifier)
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
---------
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
* feat(overlay): hook slGetFeatureVersion and slGetFeatureRequirements - what Streamline answers when a game asks which version a feature is and what it requires, read after the original call and only once the Agent has asked; never the lists the answer points to (beta.44 PR-2)
Two new patch sites on sl.interposer.dll, a row and a family bit each (15, 16), installed only in a process that
was asked for Advanced metrics (D111) and the first two rows the watchdog patches. The answer is read only when
the original returned eOk and the struct carries its own GUID: two versions; the flags, three counts and four
versions of the requirements - every one a member of struct version 1 at each of sixteen upstream tags (D115).
requiredTags and the Vulkan members are never read; no pointer of the game's is followed. Twelve slots in region 5
(layout 5 as it was), kept across a new request.
Measured (the detours' bodies on the headers, the Overlay's flags, 20 M calls x 3): the version +0.58/+0.61/+0.58 ns
not asked, +14.82/+14.54/+14.47 ns asked; the requirements +0.58/+0.63/+0.61 ns not asked, +20.88/+21.01/+20.96 ns
asked.
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* fix(tests): compute the index of a feature slot in size_t - three products of two 32-bit values used as a pointer offset, in the injected test and the harness (Qodana native, bugprone-implicit-widening-of-multiplication-result)
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
---------
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
What the owner's nine sessions on 0.1.0-beta.43 found. The Overlay does not change.
- D128: a field of view over pi is the number as the game gave it, with a row that says it is not radians; never converted.
- D126: the consent grant sets hook_crash_count to 0 - it was never set back, so one early end was enough once a game had had two.
- D127: a fault while a game is closing, unseen by a hooked session, is written down and not changed.
- The accuracy statement and LIMITATIONS say what was read from real games and what was not.
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
Read from a copy of the ledger, the Agent's log, nine overlay logs and Windows' application log.
Not exercised: a configure through the FidelityFX 2.3 loader, a game with neither library.
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
docs/changelog/0.1.0-beta.43.md takes [Unreleased]; HANDOFF's beta.42 section moves verbatim to docs/handoff/history/0.1.0-beta.42.md and a new START HERE says what the release decided beyond D123-D125, the traps of the train and what is left open; owner-only item 41 is the first real games with the two new hooks, with what each outcome means written before the run.
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
The Agent and the App for the two hooks of #415 and #416. InGameAdvancedSampler makes sl.constants.jitter, .motion_vectors, .depth, .projection, .resets and ffx.framegen.config from members region 5 already had; the count is brought up to the last publication when the session ends. AdvancedSources gains StreamlineConstants and FsrFrameGeneration (AdvancedInGameCall), from the hook families the writer state published and what the publications carried; the session's sources line says it in en, vi, ja. Privacy Policy 2.17 names the two readings and says the two calls are intercepted only once a session with the option on has started in the game; the accuracy block, LIMITATIONS, the guide and docs 06, 08, 18 follow. No schema change (23), no layout change (5).
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
Four inventory rows, family FL_HOOK_FFX_CONFIGURE (bit 14), installed only in a process asked for Advanced metrics at least once and published when every loaded ffx-api module is patched. fl_adv_fields.h reads frameGenerationEnabled, allowAsyncWorkloads, flags, onlyPresentGenerated and generationRect of a frame-generation configuration into region 5's ffxFg group, counted at the first module that saw one; the rectangle is kept in one word so it cannot tear, and one that does not fit is four -1. Every configure type is kept for the log (FFX_CONFIGURE). tools/overlay-fields-check.ps1 gains the parameter g and five list entries.
Measured on the headers with the Overlay's flags: +1.7 ns not asked, +15.2 ns on the counted module, +2.7 ns on the forwarded copy.
The test's 'is this export patched' compares the target's bytes with the file's own.
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
A new inventory row, sl.interposer.dll!slSetConstants, family FL_HOOK_SL_CONSTANTS (bit 13). InstallByFamily returns before resolving the symbol in a process never asked for Advanced metrics (D111), so nothing is patched with the option off. The detour checks the request, MayObserve, the struct's GUID and version and the viewport handle's on every call; fl_adv_fields.h reads jitterOffset, mvecScale, cameraNear, cameraFar, cameraFOV, cameraAspectRatio and the seven Booleans into region 5's sl group, summarised for the first viewport seen. tools/overlay-fields-check.ps1 gains the parameter k and thirteen list entries; the camera's names are still refused everywhere.
Measured on the headers with the Overlay's flags: +0.6 ns not asked, +19.6 ns asked on the summarised viewport, +5.8 ns on another.
ctest fl_adv_fields and fl_guard [advanced]: never asked - the export's first 16 bytes in the target are the file's; asked - the first viewport's numbers and none of the second's; no longer asked - the region unchanged; stopped - the bytes restored.
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
g_ffxUpscaleOwner gates the count and the source word through fl::adv::Owns; the FSR 3.0 host is a source like the four leaves; the render size and the quality byte are not gated. Measured on Cyberpunk 2077's loader 2.3.0 for frame-generation dispatches; no title run so far upscales through such a loader, so it is a precaution, held by the stub loader bound through the leaves' exports (hook-harness --ffx-topology 2x-export): 60 presents read as 120 frames before, 60 after.
Measured on the header's Owns with the Overlay's flags: +0.02 to +0.03 ns on the counted module.
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
* fix(guard): a module list that changed while it was read is read again, at most three times, before the guard refuses - launches were being lost as a safety unhook with no frame recorded (owner decision D123)
Collected::kUnsettled for a module that was in the list and could not be named (until now kIncomplete, an immediate refusal). CheckModules re-reads the whole scan set from a fresh snapshot after kScanRetryPauseMs, up to kMaxUnsettledRereads (3) times; a list still unsettled on the last read refuses kModuleScanFailed with its own signal. A finding - also among the modules that were read from a half-read list - a protected process and a list too long for the buffer still refuse at once; D48's re-read stays one. The launch poll's runtime probe asks again on an unsettled list.
ctest fl_guard [D123]: ten sections against fakes, and the real source against a process that loads and frees a module in a loop (hook-harness --churn-module): about one read in four unsettled, none anything else.
HANDOFF: D123; the Cyberpunk FSR 3 session cannot be run (the game's only FSR upscaler is 2.1), D121 closed.
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* test(guard): the live D123 case counts its answers with an if-chain - Qodana's switch-enum on a switch that named two of five values
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
---------
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
* docs(handoff): what the owner's first four sessions on 0.1.0-beta.42 showed - Cyberpunk's upscale was FSR 2.1, built into the game (D121 answered); the 2.3 loader re-enters the leaf's export; the plane at infinity measured on two titles
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* docs(handoff): three more starts of Cyberpunk on beta.42 - the game was still on FSR 2 (the settings file says so), and the first start was lost to a module list read while the game was loading: five such ends in the Agent's logs since 2026-11-05, and a decision for the owner
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* docs(handoff): the owner's screenshot of Cyberpunk's Graphics menu confirms it - Resolution Scaling is FSR 2.1
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
---------
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
docs/changelog/0.1.0-beta.42.md takes [Unreleased]; HANDOFF's beta.41 section moves verbatim to docs/handoff/history/0.1.0-beta.41.md and a new START HERE says what the release decided, what to read in the Cyberpunk log and the design of beta.43's two hooks; owner-only item 40; the release lines in README, LIMITATIONS, ACCESSIBILITY and the accuracy block's copies. No legal version, schema, rules or layout change.
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
FL_ADV_FLOAT_INFINITE (0x7F800000) in ffxNearBits / ffxFarBits only; fl::adv::FfxDepthPlaneBits on the ffx route only; InGameAdvancedSampler shows the row as the infinity sign. No field moved, the layout version is unchanged. The layout's comments carry the release numbers of D118 and D122.
Measured on fl_adv_fields.h with the Overlay's flags, old header beside new: no difference beyond the run-to-run spread (+25.0 to +25.4 ns per UPSCALE dispatch with Advanced on, +25.2 to +25.8 before; off unchanged).
Qodana's native report: six false 'never used' on the registry test's stand-in engines switched off for that file with the reason; one vector reserve fixed.
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
The log held the first half second of a session unless the Agent asked for it or a stop ran, and a game that exits does neither. FlushLogIfNew on the watchdog's tick; the init flush moved before the watchdog exists. Install lines name module!symbol from the inventory row (fl::inventory::NameOfRow; the event's text is 72 characters). fl_ffx_types.h keeps each descriptor type a hooked ffx-api module was handed, per entry point, and the watchdog logs it once (FFX_DISPATCH / FFX_QUERY), with UPSCALE_ROUTE and RUNTIME_CENSUS from words the detours already kept. A diagnostic: the log file and nothing else.
Measured on the header with the Overlay's flags: +3.8 ns per dispatch for a frame's three types; +0.9 ns first slot, +8.4 ns eighth.
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
fl_patch_registry.h: slots Free -> Claimed -> Live -> Retired and one sequence, fl::patch::Install - claim, create, enable, commit, re-read the flag - against a stop that clears the flag and then walks the committed slots, both sequentially consistent. PatchTarget, the loader detour and the three DXGI patches go through it; a patch that did not go in is logged once (PATCH_FAILED); the capacity is asserted against the inventory's row count; READY is written only over INIT and init's failure path stores nothing, so neither overwrites a stop's reason. No hook body changed.
ctest fl_unhook_inline drives the shipped sequence against real MinHook patches (+3 cases).
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
A session that evaluated DLSS briefly and then ran FSR was stored as DLSS with FSR's quality byte and render size. Domain.Metrics.UpscalerChoice picks the modal named technology over the dominant stream; with more than one named, quality and size are read only from the samples that name it, a quality byte of the other family is withheld, and the session is marked settings-changed. One technology named keeps the whole stream, as before. The live card is unchanged.
HANDOFF and 18_GPU_VENDOR_APIS record D119-D122: train B's second step is beta.42 (no new patch site) and beta.43 (the two new hooks).
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
docs/changelog/0.1.0-beta.41.md holds the two [Unreleased] entries of #400 and #401. HANDOFF's START HERE for
0.1.0-beta.40 - with what the owner's first sessions showed - moved verbatim to
docs/handoff/history/0.1.0-beta.40.md; the new one records D118, NEXT and what is left open. Owner-only item 39:
the fix on the PC that showed the fault.
D118 (owner decision 2026-11-12): the fix takes the number D113 gave train B's second release; that one is
beta.42, the third beta.43, train C beta.44, train D beta.45.
The code loaded into a game is 0.1.0-beta.40's, line for line. Schema 23, rules 2026.11.2, Privacy Policy 2.16
and Disclaimer 2.15 unchanged.
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
Found in the owner's first sessions as administrator with PawnIO (0.1.0-beta.40): after seven of ten sessions the
Advanced reader's processor device threw NullReferenceException twice and was left alone, and once the reader's
Open threw ObjectDisposedException and the session stored 17 series instead of 212. The Agent holds up to three
Computers at once; the library keeps the driver it reads the processor through and its bus mutexes per process,
and Computer.Close() lets go of them whoever else is reading. Read from the log's timing, not reproduced: it needs
that elevation.
LhmLibrary (one per process; LhmComputerAdapter is its user): opens and closes never run at once, and a Computer
closed while another is in use is parked and handed to the next user of the same groups; the last user's close
closes them all, even when one throws. The reads are not serialised - the readers keep their own threads.
20_OPEN_QUESTIONS M13 records the first elevated run (119 processor, 14 memory, 21 motherboard series read; no
value compared with another tool) and stays open: whether the faults are gone is the owner's next sessions to
show. HANDOFF records what the same ledger says of beta.40's in-game readings.
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
HANDOFF records the release: 2026-11-11T19:30:13Z, the signed tag on 5268332, run 43085044822, eight assets, the
seven digests, FL_BUILD_ID v0.1.0-beta.40, the delta of 2,413,166 bytes, the wiki run, the rehearsal.
InGameAdvancedSampler told one value from a range with == on two doubles (csharpsquid:S1244, twice); it now
compares the stored bits. ParentDump's DangerousGetHandle is the call accepted in beta.24, raised anew because
#398 moved it; it is unchanged, its reason is on the line and in 13_CI_CD, and accepting it again is the owner's.
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
docs/changelog/0.1.0-beta.40.md holds the [Unreleased] entries of #395-#398 under the release's heading. HANDOFF's
START HERE for 0.1.0-beta.39 moved verbatim to docs/handoff/history/0.1.0-beta.39.md; the new one records what the
train decided that the plan had not, that nothing of beta.41 begins before the owner has run item 38, what is left
open and the traps. Owner-only item 38: this release on real games.
The code loaded into a game changed in this release (the Overlay reads more members of calls it already hooked,
only while the Agent asks; no new patch site; shared-memory layout 5). Schema 23 and rules 2026.11.2 unchanged.
Privacy Policy 2.16, Disclaimer 2.15.
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
ICaptureObserver.WantsInGameAdvanced: CaptureSession writes the control word either way as the ring is attached,
before its first guard result, and carries each publication of region 5 on CaptureProgress.InGameAdvanced as one
instance. A session that did not ask never reads the region.
Application.Capture.InGameAdvancedSampler turns a publication into session facts (reach Game: the DLSS output
size, presets, HDR input, auto-exposure, alpha upscaling, exposure; FSR's sharpening, largest jitter, exposure,
depth range, the RANGE of the field of view, flags) in the vendor's own words, and into two series
(adv.ffx.upscale.frame_time_delta, adv.ffx.memory_usage). Zero is "not read", never a value. No schema change:
facts_json, sensor_blobs and the .partial carry them. AdvancedSources.InGame says what became of them - read,
nothing seen, not hooked - and is absent in every row beta.39 wrote.
The App: the session's sources line and the Sources tab say it; fourteen strings and the Settings text in en, vi,
ja. Privacy Policy 2.16 (content approved with the plan), the accuracy statement, the guide, LIMITATIONS.
Also: SonarCloud's three findings on #397 (cpp:S6232 in the watchdog's QPC read, two cpp:S2259 in the new fl_guard
cases); ParentDump.WriteDump tries MiniDumpWriteDump up to three times - a running process changes under it
(ERROR_PARTIAL_COPY), which failed CrashDumpHelperTests under the gate's load for the third time in two days.
Verified end to end with the shipped Agent, the real Overlay and the harness: two sessions of one target, the
first (option off) storing no row and no adv. series, the second the exact values the target sends.
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
fl_adv_fields.h is the one place a vendor struct's extra members are read: sl::DLSSOptions at the struct version
that carries each member, ffxDispatchDescUpscale on the ffx-api route, the upscaler's memory query after the vendor
answered OK. The detours consult one process-local flag the watchdog copies from FlControlBlock.advancedRequested;
with it at 0 nothing more is read and region 5 is never written.
"On" is a request, not a 1: a value no session of the ring used before. The watchdog starts its summaries afresh at
a request it has not seen and names it in every publication (FlAdvancedState.request, the word that was reserved0);
ShmRingReader.AdvancedState returns only a publication that names its own. A second session of a game that kept
running no longer reads the first one's ranges and counts.
tools/overlay-fields-check.ps1 (build.ps1 gate): every member read is on tools/overlay-allowed-fields.txt and every
name there is read; no alias; no listed member read elsewhere in the Overlay or the Vulkan layer; a camera's
position, axes and matrices named nowhere, whatever the list says; sl::Constants and the frame-generation prepare
descriptor never copied or measured.
Measured (the header's functions, the Overlay's flags, 20 M calls x 3): +22.3-23.2 ns per ffx UPSCALE dispatch,
+9.5-11.7 ns per evaluation that chains DLSSOptions, +4.3-6.1 ns per memory query while asked; inside the bench's
noise when not asked.
ctest 33/33 (fl_adv_fields; fl_guard: every byte of region 5 zero until asked on a target that sends everything,
the exact values when asked, untouched after an off, a count that starts again at the next request).
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
fl_shm.h: FlAdvancedState (1472 bytes at 0x100; the ring moves to 0x6C0) and FlControlBlock.advancedRequested (took
reserved[0]). While the word is 0 the Overlay is to read and hook exactly what it does today, and the region stays
zero. One writer - the watchdog, once a second; a vendor Boolean or preset is stored plus one and a float as its
bits with a "none" pattern, so zero is "not read" and never a value. The members beta.41 and beta.42 fill are
declared now, so those releases bump no layout.
The Agent's side: ShmLayout (layout 5, the mirror), ShmRingReader.AdvancedState - null until published, then the
last consistent copy - and SetAdvancedRequested, which stores the word either way because the control block
outlives a session. ICaptureSink gains both with default bodies; nothing calls them yet. fl-layout-dump prints every
member and ShmLayoutMirrorTests checks each offset. No hook body changes.
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
Train B (what only a hooked game can say) is three releases: beta.40 more fields of calls already hooked and no new
patch site; beta.41 slSetConstants + ffxConfigure; beta.42 slGetFeatureVersion + slGetFeatureRequirements. Inside the
game too, off means nothing more is read. docs/17_HOOK_ENGINE.md gains which struct version carries which field,
compared across sixteen Streamline and ten FidelityFX tags. tools/agent-cost.ps1 measures the shipped Agent in a
session: 1.93 % of one core off, 2.04 % on; the owner amended NFR-2 to 2.5 %. HANDOFF records beta.39's release facts.
ShmDrainIntegrationTests waits Init out and prints the guard's verdict.
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
* release: 0.1.0-beta.39 - Advanced metrics, train A: its changelog file, HANDOFF's beta.39 section with what the train decided, the traps and the next work (ask M16, then train B's plan), owner-only item 37, the release lines (Advanced PR-8)
docs/changelog/0.1.0-beta.39.md holds [Unreleased] as it stood, under the release's summary: a setting, off by
default, and a page of its own; Privacy Policy 2.15 and Disclaimer 2.15 shown once; schema 23. docs/HANDOFF.md's START
HERE for beta.38 moves, verbatim, to docs/handoff/history/0.1.0-beta.38.md; the new one carries D109, what was
decided that the plan had not, what is left open - nothing was seen in the running App, and the first run as
administrator with PawnIO is still to come - and the traps this train paid for. Owner-only item 37 is what only the
owner's PC can show.
git diff v0.1.0-beta.38 -- src/native/FrameLedger.Overlay src/native/FrameLedger.VkLayer src/native/FrameLedger.Shm
src/native/FrameLedger.Injector is empty: the code loaded into a game is beta.38's, line for line.
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* test(app): the page-load fixture loads Settings' System card once and awaits it - two pages built a moment apart could differ by a row, and the theme-switch comparison was red once on a hosted runner (Advanced PR-8)
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
---------
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
Pages/AdvancedPage over ViewModels/AdvancedViewModel. This PC is what the Agent reads now, asked only while the page
is on screen and never stored: the facts under the catalog's groups, every series with the time it was read at, and
one entry's last five minutes. Session is what a session recorded with the option on stored: the PC as it was, the
session's own facts, the statistics, and the entry's series over the session. Sources is every catalog entry with
whether it is read, or why not.
The navigation item is the menu's last and is bound to Services.AdvancedOption.IsOn - set at start and by the
Settings switch - and Ctrl+6 opens the page only while it is on; Ctrl+1..5 keep their pages. A session's summary has
"Advanced metrics..." where the session stored them. A viewer opens on Session and asks no Agent.
245 strings in en, vi and ja (ja marked for review): the English label of an entry is its summary in the catalog. A
family of more than eight series is drawn as its lowest, average and highest. ISessionRepository.ListAdvancedAsync;
SessionSeriesLoader.LoadAdvancedAsync. The guide gains a page; ACCESSIBILITY.md, LIMITATIONS.md, 08_UI §Advanced, the
accuracy block and Privacy Policy 2.15 follow. Nothing in src/native changes.
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
* feat(ipc): GetAdvancedMachine - what the Agent's advanced reader last read, answered without touching a sensor, each request the page's hold on that reader; and the App's feed that asks while a page watches (Advanced PR-6, D101/D107)
Application.Ipc.AdvancedMachineResponder answers from IAdvancedHardware.Latest alone: the pipe's read loop awaits its
handler, so a driver call there would hold up Ping and StopSession. The first request acquires the shared reader and
each renews a five-second lease; a lease after the last one the hold is let go - a page that closes, an App that
exits and a pipe that drops all look the same. With telemetry.advanced off the answer is Error AdvancedOff and
nothing is held. The facts travel once, by their hash; a reading that is not a number is left out. Additive,
protocol 2.
App.Services.AdvancedMachineFeed asks once a second while a page holds Watch(), and keeps the facts, the last value
of every series with the tick it was read on, five minutes of each for the live charts and the sources' states.
It stores nothing, and no page watches it yet. Nothing in src/native changes.
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* test(display): the monitor a game's window is on, asked by a named window as Observe is - and tested against the harness's window (Advanced PR-6; SonarCloud's coverage of PR-5's new code)
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
---------
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
telemetry.advanced becomes RecorderOptions.AdvancedMetrics at each session's start. The Agent registers one
AdvancedHardwareHub; SessionRecorder holds it for a session's length only when the option is on, and the session's
TelemetryPoller gets it on the same condition. A session's facts are read once, off the capture loop, fifteen seconds
after the game's process is known or at the session's end; which display is the game's comes from Windows
(WindowGeometryProbe.MonitorDeviceOf). Off: not held, not asked, no chunk 9 or 10, no session_advanced row.
Settings gains the row (off in a viewer), strings in en/vi/ja, the guide's settings page. Privacy Policy 2.15 names
what is read and stored only while the option is on, and what never is. Disclaimer 2.15 (the owner's answer of
2026-11-11, D109): PawnIO and the admin mode are no longer "for the CPU temperature" alone; the admin mode's
disclosure follows (agent-admin-dialog/2), with Settings, the first run, the guide and LIMITATIONS.md. The accuracy
block gains an item. Nothing in src/native changes.
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
Produced by nothing yet: no Agent code composes the advanced reader, so no
session stores any of it and nothing a user sees or records changes.
- Schema 0023, the first CREATE TABLE since 0001: machine_profiles (the
PC's facts, one row per distinct set, by the SHA-256 of their JSON) and
session_advanced (one row per session recorded with the option on - its
facts, each source's state, its series' statistics and directory). No
column on sessions: every read of that row, the JSON export and the bug
bundle carry all of it. A session recorded with the option off has no
row, and that absence is how the App will say so.
- The advanced series are rows of sensor_blobs under names that start with
adv., with NaN - not -1 - for a tick with no reading: a -12 V rail is
negative, and the sensor library is read every fifth tick. A second
encoder, ISeriesCodec.EncodeSparseFloat32, allows NaN and still refuses
an infinity; EncodeFloat32 still throws on a NaN. FindSensorsAsync, which
every summary, chart and export reads, leaves the adv. rows out;
FindAdvancedSensorsAsync and FindAdvancedAsync read them.
- Application.Advanced.AdvancedJson: the one stored form. Writing is
strict, reading is tolerant, and only a fact whose catalog entry is read
may be written (D104 held at the door of the ledger).
- AdvancedSessionBuilder, both tiers: one series per advanced reading,
aligned to t_ms; at most 256 a session, the rest counted. With no reading
and no context it builds nothing, and a session is byte for byte what it
was.
- TelemetrySample.Advanced, and the poller's optional IAdvancedHardware:
held from Start to Dispose, each of its ticks attached to one sample and
never repeated on the next.
- The .partial: chunk 9 (the readings of the sensor chunk before it, with
their own names) and chunk 10 (the session's context), written only when
there is something to write; a recovered session keeps both. D106: a
chunk of a type the reader does not know, whose length and checksum are
right, is skipped where it ended the read - so a build one release older
no longer loses everything after the first new chunk.
- LedgerDatabaseTests' rewind helper undoes a script's CREATE TABLE and
CREATE INDEX as well as its ADD COLUMN: 0023 would otherwise have failed
every test that rewinds a ledger.
- Measured: one hour of 58 series shaped like the dev box's reader is 816
KiB raw and 189 KiB stored (NFR-5 allows 3 MB an hour).
- docs: 06_DATA_MODEL (schema 0023, the NaN rule, chunks 9 and 10, D106),
18_GPU_VENDOR_APIS, CLAUDE.md, CHANGELOG.
Hook overhead: not applicable - nothing in code loaded into a game
changes.
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
Nothing calls it yet: no Agent code composes the reader, so nothing a user
sees or records changes.
- Application.Advanced: the port IAdvancedHardware (Acquire, Latest,
ReadSessionFacts), AdvancedSnapshot, AdvancedSources and the status of
each source - Reading, NotPresent, NotElevated, PawnIoMissing, Faulted.
A source that is not there is a state, never an exception and never a
value in its place.
- Infrastructure: AdvancedHardwareHub - one reader for the whole Agent on
a thread of its own (fl-advanced), started by the first holder and
closed a linger after the last lets go (D107), so a PC idling with
FrameLedger in the tray reads nothing for this. AdvancedHardwareReader -
one tick of NVAPI and of LibreHardwareMonitor. LhmAdvancedReader over a
Computer of its own: every sensor of the graphics card, and as
administrator with PawnIO the processor, memory and motherboard groups
(D103). LhmGroups has a member for those four and no other.
- Storage is not opened (D103's outcome, written before any run):
LibreHardwareMonitor 0.9.6's StorageGroup lists every drive through
DiskInfoToolkit with no filter by bus and follows drives plugged in
later. lhm.storage.* is Deferred in the catalog; a drive's temperature
will read N/A with that reason.
- A device that throws twice is left alone and the others go on; NVAPI
answering with no field twice running, after it had answered, is
released and initialised again once (20_OPEN_QUESTIONS M12).
- FrameLedger.CaptureHost probe-advanced (unshipped): runs that reader on
the caller's own rights and prints what it read and what it cost. On the
dev box (RTX 5080, unelevated): 35 facts, 58 readings a tick; one NVAPI
live read 0.4 ms of processor time; one refresh of the sensor library's
graphics-card group 14 ms (62 ms elapsed) - 1.4% of one core at one a
second, above NFR-2. So NVAPI is read every tick and the sensor library
every fifth (0.28%), with no value repeated between.
- The same refresh is what the L2 telemetry layer does once a second in
every session. That cost is not this train's: recorded as
20_OPEN_QUESTIONS M16, with the owner's choices.
- PrivilegeFootprintTests: opening every group this project can name
enables no powerful privilege (the real thing on the elevated CI runner).
- docs: 18_GPU_VENDOR_APIS (the reader, D103 as found, L2's line),
20_OPEN_QUESTIONS (M13 half answered, M16 new), HANDOFF, CLAUDE.md,
CHANGELOG.
Hook overhead: not applicable - nothing in code loaded into a game
changes.
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
FrameLedger.NvapiBridge.dll - loaded by the Agent into its own process,
never into a game - gains five reads. Nothing composes them yet: no Agent
code calls the reader, so no behaviour changes.
- Native (fl_nvapi_bridge.h/.cpp, ABI 3, additive): FlNvReadFacts (the
card's type, bus, PCI ids, VBIOS, architecture, core counts, base and
boost clocks, memory sizes, the driver's package, the chipset),
FlNvReadLive (free video memory with evictions and promotions, the
frame-buffer / video / bus utilisation, video clock, P-state, board and
power-supply temperatures, the throttle word, encoder statistics),
FlNvReadDisplays (HDR formats and luminances, variable refresh,
adaptive sync per connected display), FlNvSessionDisplay (one display's
variable-refresh state and one process's colour space) and
FlNvProfileSettings (every setting of the global profile, or what a
game's own profile sets). Each struct carries its size and a present
mask; a clear bit is N/A, never 0. No ABI 2 struct changed size, and
FL_NV_FIELD_VRAM stays clear, so which layer fills vram_adapter does
not change.
- No identifier has an entry point (D104): no board serial, unique id,
EDID, or list of encoding programs. A display is passed on by its place
in the list, never by NVAPI's handle.
- tools/nvapi-readonly-check.ps1 (D108), wired into build.ps1: every
NvAPI_* call of the bridge's source is on tools/nvapi-allowed-calls.txt
and every name there is called - forty-four - and a name that sets,
saves, restores, registers or controls, or returns an identifier, is red
even when the list names it. Seventeen self-test cases, both directions;
the self-test caught two holes in the rule as first written.
- Managed: mirrors of the five structs, INvapiAdvancedBridge (a port of
its own; a DLL that predates ABI 3 answers Unavailable, never throws),
NvapiAdvancedReader (the structs become the catalog's facts and
readings - every nvapi. entry of the Agent's reach and no other, held
in both directions) and Application.Advanced's value model: a fact is a
number, the vendor's words, our own tokens the App will translate, or
rows; one that was not read is absent.
- Measured the day it was written (ctest fl_nvapi_bridge, AVAILABLE
branch, RTX 5080): all twenty facts answer; eight of ten live groups -
the card has no board or power-supply temperature sensor; the display
answers its four groups; the global profile lists 24 settings.
20_OPEN_QUESTIONS M12 is half answered, with what is still open.
- The vendored nvapi.h misspells NV_ENCODER_STATISTICS_VER; the bridge
names NV_ENCODER_STATISTICS_VER1.
- Fixed from #387: Qodana's one result, a redundant "!" in
AdvancedMetricCatalogTests.
- docs: 18_GPU_VENDOR_APIS (ABI 3, the gate), 12_BUILD (gate 14e),
CLAUDE.md, CHANGELOG.
Hook overhead: not applicable - nothing in code loaded into a game
changes (Overlay, VkLayer, Shm, Injector untouched).
Gate on the dev box: all passed in 301 s (native 32/32).
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
The owner asked for a setting, "Thông số nâng cao", with a navigation item
of its own that shows as much as the NVAPI and Streamline headers and PawnIO
make available, each value under what it belongs to: one game session, or
the PC. Planned 2026-11-11 with the owner's decisions asked while planning;
four trains, A (0.1.0-beta.39, the Agent's reads only) to D. This is the
first pull request of train A and changes no behaviour.
- FrameLedger.Application.Advanced: AdvancedMetricCatalog, 137 entries -
86 the Agent will read (60 NVAPI, 10 LibreHardwareMonitor unelevated, 16
through PawnIO as administrator) and 51 that are not read, each with its
reason: a call already hooked, a hook not built, a route a spike decides,
an identifier (D104), the player's own state (rule 4), a licence, a
function the public headers do not declare. One list for the reader, the
recorder, the page and the documents.
- docs/18_GPU_VENDOR_APIS.md section Advanced metrics: the decisions, what
belongs to what, the four trains, what is left out by name, and the
inventory as a table. AdvancedMetricCatalogTests fails when the table and
the catalog differ in either direction (proven red on one changed row).
- docs/18: the Memory row said the vendored NVAPI headers do not declare
NvAPI_GPU_GetMemoryInfoEx. They do (nvapi_lite_common.h:600, included by
nvapi.h); the search had looked in nvapi.h alone. Corrected.
- docs/HANDOFF.md: the plan's order and the owner's four answers, D101-D108
in the decisions index, and 0.1.0-beta.38's release facts, which its own
release could not carry.
- docs/20_OPEN_QUESTIONS.md: M12-M15, each with its outcome written before
the measurement - the NVAPI rows on real hardware, LibreHardwareMonitor's
other groups elevated, a route to Reflex latency, the refused
slGetFeatureFunction route re-examined.
- docs/02_SPEC.md: FR-5.6, and NFR-2's limits stated to hold with the
option on (unmeasured). CLAUDE.md: the Application layer's new folder.
Gate on the dev box: all passed in 300 s.
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
The documents of 0.1.0-beta.38, cut from [Unreleased] as it stood:
- docs/changelog/0.1.0-beta.38.md: what the release is for its user - one hardening, the link opener refusing
anything but http, https and mailto, and nothing else seen, recorded or measured changing - then the entries of
#384 and #385, moved verbatim. CHANGELOG.md's [Unreleased] is empty and the table has its row.
- The release lines: README, legal/ACCURACY.md and its two copies, LIMITATIONS.md, ACCESSIBILITY.md.
- docs/HANDOFF.md: START HERE is beta.38's. It opens with the NEXT work, in the owner's own words (2026-11-11, sent
while this session was running): a setting "Thông số nâng cao" with a navigation item of its own, showing all the
Streamline, NVAPI and PawnIO headers can give - recorded, not designed: it starts with a plan. Then what this
session left open: LogNoteW (dead code in the Overlay, the owner's call), this release's own facts, the Qodana
licence, C# 15's constructs, the resting alpha line. Owner-only item 36.
- docs/handoff/history/0.1.0-beta.37.md: the START HERE it replaces, moved whole - the plan's three parts, D94-D100.
No code changes. The legal texts keep their versions; the ledger stays at schema 22 and the rules at 2026.11.2. No
alpha follows: the alpha line rests (D98).
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
The second of two pull requests. Qodana for .NET - whose C++ is ReSharper C++ - is the only linter of JetBrains' that
can read this code: it is MSVC-only, and qodana-cpp and qodana-clang are Linux images. It reads C++ through a Visual
Studio solution, and src/native is a CMake tree, so the job has CMake write one.
The job
- src/native/CMakePresets.json: the preset x64-vs-analysis (generator "Visual Studio 18 2026", tests and tools on).
Nothing ships from it, and the gate and the release never use it.
- qodana-native.yaml: the solution, RelWithDebInfo and x64; the build tree, third_party, the vendor stubs and a
compiled shader left out by path; a gate of zero.
- qodana.yml: the job `native` - configure, build the one target whose output is a header (the blocklist floor), then
the action with --config qodana-native.yaml. Its own results folder, cache keys, artifact (qodana-report-native)
and Qodana Cloud project (frameledger-cpp, QODANA_TOKEN_NATIVE). No comment and no annotations: the pull request's
are the managed job's. Advisory.
What its first run reported, and what was done (docs/13_CI_CD.md, section Qodana)
- 4,695 problems, 4,040 of them hints (off, as on the managed side). Of the 655 left, 494 are distinct: a file
compiled into three targets is reported three times.
- Off in .editorconfig, each with its reason - every clang-tidy check and clang diagnostic the engine runs has a key
of ReSharper's, so no .clang-tidy file is added:
278 a choice this code made (struct padding, MSVC's keywords, a function pointer got by name cast to its type,
"can be const / constexpr / static", an #include of what the file uses);
53 a newer idiom proposed for working code;
25 the engine misreading std::atomic_ref, zero-initialised API structures and tests of constexpr functions;
25 fields nothing names in structures Windows defines (four files);
19 %lu with NvU32 in one probe - unsigned int only under clang, the linter's compiler;
78 what a probe or a test does on purpose (tools and tests);
7 in code loaded into a game, kept as it is.
- Fixed, 11, none changing what a shipped binary does: std::size for four hand-written array lengths; two
multiplications done in a narrower type than their result (a constant in the guard's sources, a test); two unused
member functions, an unused type alias and two unused includes in the tests and the probes.
Code loaded into a game - the Overlay, the Vulkan layer, the shared-memory headers, the guard's rule matcher - is not
changed (D100: there only a defect is fixed, and the report found none). One thing there is not as it should be and
is RECORDED, not removed: dllmain.cpp's LogNoteW, which nothing calls. .editorconfig leaves that one file unread for
an unused function, in a section that says to remove it with the function; whether it goes is the owner's call
(HANDOFF).
"Zero" proved to mean "analysed": a branch that put back three of the things fixed here was reported with exactly
those three, by the inspections that had found them (run 42942390715).
Runs on this branch: 42942068024 (one problem left: LogNoteW), 42943094415 (none).
Docs: 13_CI_CD (the native report), 12_BUILD (the preset), CLAUDE.md (the layout, the C++ conventions), HANDOFF,
wiki/Releasing, CHANGELOG.
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
The owner took an Ultimate licence for the Qodana Cloud organisation and asked for Qodana over every language. This is
the first of two pull requests: the existing job moves to Qodana for .NET (Rider's engine) and what it reports over the
managed code is settled. The C++ is the next one's, as a second report.
The job
- qodana.yaml: linter qodana-dotnet, withinDocker false (native mode on the job's Windows runner, the SDK from
global.json; no container, no EnableWindowsTargeting, no bootstrap line). Everything a run needs is in the file.
- qodana.yml: the job is `managed` (Qodana (managed)), on windows-latest - checkout, setup-dotnet, the NuGet cache
restored, dotnet build -c Release, then the action pinned by commit. Still advisory, still a gate of zero.
What its first run reported, and what was done (docs/13_CI_CD.md, section Qodana, has each)
- 3,953 problems, 3,607 of them hints - the level an editor offers without underlining anything; the Community linter
never reported them. Hints are off as a severity (one group in qodana.yaml). 347 left.
- 271: a vi or ja value equal to the English one - off in .editorconfig for .resx (names, units, format strings).
- 23 + 10: two Markdown inspections (table padding; anchors computed otherwise than GitHub does) off in qodana.yaml;
the application manifest's XML ignored for XmlHighlighting.
- 6 in PrimaryDisplay.cs are the linter's own fault (an internal assertion, in its log); two inspections are excluded
for that file, and the file is as it was.
- 1 fixed: a test expression that carried a clause its first half implied.
- 36 from JetBrains' security rules: 35 process starts and 1 SQL text. Each was read - what it starts, where the path
and the arguments come from (a table in the docs). None takes a value from outside the PC, except the game the user
added. One place was hardened: ShellUrlOpener now refuses any address that is not http, https or mailto itself,
where it trusted each caller to have checked (ShellUrlOpenerTests).
The rules stay on. A rule's own id is honoured nowhere - a profile entry's `ignore`, an `exclude` path and
`enabled: false` were each tried in a run of its own and every result stood: the OpenGrep plugin reports every rule
through one inspection, OpenGrepInspection, and hands its server every rule file whatever the profile says. That
inspection does take a path, so the eleven files of src the results were read in, and tests, are listed under its
name in qodana.yaml: a new file that starts a process is reported.
- ProcessStartSitesTests, in the gate, is the same tripwire where a merge is blocked: it sweeps src for every way a
process is started here - Process.Start, a ProcessStartInfo, CreateProcessWithTokenW, the logon task's
registration - and fails on a file that has not been read and listed.
Also: ShmDrainIntegrationTests' drain under supervision supervises at least twice whatever the first drain holds. On
a busy machine the first scan was slow enough for fifty presents to be waiting, the loop ended after one evaluation,
and the test failed its own "supervised more than once" (once, in a local gate of this change).
Where an inspection is switched off (D100, amending D93's "never in qodana.yaml"): in the place the engine that raised
it reads - one of ReSharper's in .editorconfig, what has no key there in qodana.yaml.
Docs: 13_CI_CD (section Qodana rewritten above D93's account, which is kept as history), CLAUDE.md (the rule, the
layout), HANDOFF (D99, D100, this part's section, and the facts of the two releases of 2026-11-11: v0.1.0-beta.37 and
v0.1.0-alpha.4), wiki/Releasing, CHANGELOG.
Shipped code: ShellUrlOpener.cs alone. No link the App could open before stops opening.
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
- docs/changelog/0.1.0-alpha.4.md: the experimental-build warning, why
this alpha exists (to bring an installed alpha off the release
candidate by an update), that the alphas pause after it, and what a
paused alpha costs - no update, the anti-cheat list included; ten
betas later an older alpha no longer finds it. Install the beta.
- CHANGELOG.md: its row.
- HANDOFF: the alpha.4 part of START HERE - every switch file conflicts
this time and main's side is taken for each, leaving RELEASE_LINE -
and owner-only item 35.
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
- docs/changelog/0.1.0-beta.37.md: the [Unreleased] entries, under what
a user should know before updating - the processor, Windows 10, the
size of the download, the terms window (EULA 1.7, Disclaimer 2.14).
- HANDOFF: START HERE for beta.37 (the decisions asked while planning,
the choices, what was measured, the traps); beta.36's section moved
verbatim to docs/handoff/history/0.1.0-beta.36.md with its index row;
owner-only item 34.
- The release lines: README, the accuracy statement and its copies,
LIMITATIONS, ACCESSIBILITY.
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
The owner asked for C# 15 in the release that moved the main line to
.NET 11. The rule approved with the plan: a construct is used only
where the build, CodeQL and Qodana all read it. Each of the four was
written once, in a file of its own, and shown to each tool (draft pull
request #377, closed unmerged; spike-notes section 29):
- The compiler and every analyzer take collection expression arguments,
closed hierarchies and labeled jumps; a union draws CA1815 from the
SDK's own rules.
- ReSharper's engine - InspectCode 2026.2.3.1, which Qodana 2026.2
runs, and 2026.3.0 - reads none: `closed` and `union` are not parsed,
the other two are called preview features. On a gate of zero every
file using one would be an error.
- What CodeQL extracts of them is not established: a pull request's C#
analysis is an overlay on main's database and prints no per-file
result.
So beta.37 takes API, not syntax:
- sixteen char searches name their comparison through
string.StartsWith/EndsWith/LastIndexOf(char, StringComparison), where
they went through a span to satisfy .NET 10 and 11 alike;
- AgentLauncher finds the Agent it started with
Process.TryGetProcessById instead of a caught ArgumentException.
Nothing changes in what the software does.
codeql.yml takes workflow_dispatch, so a branch can have a full
analysis. 13_CI_CD (C# 15 and the analyses), 20_OPEN_QUESTIONS (a new
row, with what answers it), CLAUDE.md, the decisions index.
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
Until 0.1.0-alpha.3 an alpha was "a beta's source built on a prerelease
.NET" and every text said so. 0.1.0-alpha.4 runs on .NET 11's release -
the betas' own from beta.37 - and the alpha line rests after it.
- EULA 1.7 (section 2B), Disclaimer 2.14 (section 0, which also gains
the paragraph on Windows and the processor), Alpha notice 1.1 (what an
alpha is, the hardware, the pause), the accuracy statement's line and
its two copies. The texts were approved with the plan of 2026-11-11.
- Shared.AlphaLine: IsPrerelease(the runtime's description) and Rests,
stamped from Directory.Build.props' FlAlphaLineRests (true on main
since beta.37; set to false on the alpha branch when it tries a newer
.NET). App/Services/AlphaTexts picks the banner and About's line from
the two facts; a prerelease runtime is said whatever the stamp says.
- Strings in en, vi and ja: the banner and About's line no longer say
"a prerelease .NET" unconditionally; three new keys.
- guide (the alphas are paused: install the beta; a paused alpha's
anti-cheat list is not updated; ten betas after alpha.4 hide it from
older alphas), LIMITATIONS, 11_UPDATER, 12_BUILD, 08_UI, the wiki.
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
* build: the main line on .NET 11 - SDK 11.0.100, net11.0, the three runtime-serviced packages at 11.0.0; Windows 10 stated as untested and unsupported (D94, D95) (beta.37 PR-1)
The owner moved the main line to .NET 11 the day after it shipped (D94),
setting aside condition (a) of 20_OPEN_QUESTIONS section G's table - two
alphas on the released runtime. This is the alpha branch's switch applied
to main at released versions, and what follows from it.
- global.json 11.0.100 (allowPrerelease false), TFM
net11.0-windows10.0.22621.0, Microsoft.Extensions.Hosting,
Microsoft.Data.Sqlite and System.Diagnostics.EventLog 11.0.0;
legal/licenses/nuget regenerated (78 packages -> 69).
- Two CA1307 sites the released SDK raised in tests written after the
last alpha was cut take the (char, StringComparison) overload.
- IHost.RunAsync rethrows a failed BackgroundService on .NET 11: the
Agent's --serve leaves through its crash report where it exited 0.
Accepted, not wrapped; HostBackgroundFailureTests holds the runtime's
behaviour, which nothing had observed.
- release.yml installs a .NET 10 runtime for vpk 1.2.161; Qodana's
container installs the .NET 11 SDK first (interim, until the Ultimate
linter); Dependabot's and the workflows' comments follow.
- Windows 10 22H2 is not blocked, and is stated as untested and
unsupported (D95): NFR-8, LIMITATIONS, README, the guide, the wiki.
A processor needs SSE4.2 and POPCNT.
- docs: 12_BUILD (the main line's .NET; the alpha line rests after
alpha.4, D98), 13_CI_CD, 20_OPEN_QUESTIONS row closed, 10_LOGGING,
spike-notes section 28, CLAUDE.md, the decisions index (D94-D96, D98).
Gate on the dev box: all passed in 338 s on SDK 11.0.100 (native 32/32,
2,561 tests, coverage floors held).
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* build: what this pull request's runs measured on .NET 11 - CodeQL reads net11.0 whole, the delta from beta.36, Qodana's one finding fixed
- HostBackgroundFailureTests: the message is kept rather than the
exception, so no `!` is needed - the one problem Qodana's interim run
reported (run 42916491047, InspectCode 2026.2.3.1 on SDK 11.0.100).
- 13_CI_CD: what analyze (csharp, none) read of net11.0 (CodeQL 2.27.4,
"scanned 1220 out of 1220 C# files", 363 references resolved, none
unresolved), and the rule for C# 15 constructs (D96); the interim's
first run.
- spike-notes section 28: the table of this pull request's runs - check,
CodeQL, SonarCloud, Qodana, and the release rehearsal with the first
delta across two runtime majors (72.6 MB, 372 of 443 files patched).
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
---------
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
The tag's run built with SDK 10.0.404, so the package carries runtime 10.0.15
where beta.35's carried 10.0.14 - 343 of 456 files patched in the delta. The
notes at the tag did not say so; the changelog file gains a marked paragraph.
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
Nothing a user sees changes: the fixes of #373 are in the shipped assemblies,
and the version says which code is installed. No alpha (D92 stands).
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
* ci: Qodana - a workflow of its own from JetBrains' template, Qodana Community for .NET over FrameLedger.slnx (D93)
The first run: the linter in its Linux container, EnableWindowsTargeting passed
to it, no quality gate yet - what it builds and what it reports decides the rest.
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* ci: Qodana's gate is zero problems, and the inspections this project argues with are off in .editorconfig, each with its reason (D93)
Pushed before the fixes on purpose: the run this starts has the settings and
none of the fixes, so it shows the gate failing on what is left.
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
* fix: what Qodana's first run reported, settled - about 400 fixes in 181 files, none changing behaviour; the documents (D93)
Redundant qualifiers, casts, using directives, nullable suppressions and unsafe
modifiers removed from the report's own positions; var for built-in types and
one-line block bodies brought to .editorconfig's style by dotnet format; every
XAML item template names its DataType and a binding that reached its page through
DataContext.ViewModel names the page's type; two unread fields, two overwritten
initialisers and an unused parameter removed; SpokenTextAutomationPeer no longer
assumes the base peer's name is a string.
docs/13_CI_CD.md §Qodana, CLAUDE.md, the wiki's workflow table, HANDOFF's
decisions index (D93) and the changelog entry.
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
---------
Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
docs/changelog/0.1.0-beta.35.md takes [Unreleased] as it stood (#366-#371) under a
summary and the update paragraph: the legal texts keep their versions, schema 22
and rules 2026.11.2 unchanged. HANDOFF's beta.34 START HERE (with its alpha.3
lines) moves verbatim to docs/handoff/history/0.1.0-beta.34.md with its row; the
new START HERE carries D88-D92, the choices, what was measured and the traps (a
ContentDialog test needs the dispatcher's context, a static event hears every
test's, WPF UI's throwing brushes fall back to the Fluent fills inside the App, a
resource reference's callback runs on an equal value, a forward StaticResource
fails only when used, Python's "\b", RenderTargetBitmap's offset); owner-only item
32 is beta.35 on real hardware; D88-D92's rows, and D82's and D87's rows now point
at the history files they moved to. README, ACCURACY, the Disclaimer's accuracy
block and LIMITATIONS name 0.1.0-beta.35; ACCESSIBILITY.md's checks paragraph
rewrapped.
No alpha with this release (D92): alpha.4 moves the alpha line to .NET 11's
release as a task of its own.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* feat: focus and motion - Ctrl+1 to 5 put the keyboard in the page they open and say its title, a message box is owned by the window it opens over, and pages slide in only while Windows animates (beta.35 PR-6)
PageFocus: after a page shortcut the page shown takes the focus once laid out (its first
control) and its first-level heading is announced; the shell tells it each page shown
from NavigationView.Navigated. PageMotion: the NavigationView's Transition is None while
SystemParameters.ClientAreaAnimation is off, followed as it changes (WPF UI 4.3.0 played
FadeInWithSlide whatever it was). MessageBoxes: WPF UI's MessageBox sets no owner
(measured: null before and after it is shown), so every box is owned by the App's
active window - six call sites, and a scan holds it.
Measured, and left alone: a ContentDialog already gives the focus back to its opener
(WPF UI's ContentDialogHostController stores and restores it); a test pins it. A first
measurement said otherwise because it ran with no dispatcher context, where the
dialog's own finally never resumed.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* test(native): the tiny ring's case retries until one attempt both overlapped the writer and was lapped by it - CI's single attempt kept up with all 200000 records (beta.35 PR-6)
ci.yml's check on #371 failed in fl_ring, "a tiny ring, so the writer laps the
reader constantly": attempts 1, most overlapped drains 167058, dropped 0. The loop
repeated an attempt only when it had not overlapped the writer (#308); an attempt
that overlapped and was never lapped ended it, and CHECK(dropped > 0) failed. Both
now hold in the same attempt, the last, repeated up to kMaxAttempts (8): a reader
that never counts a drop still fails every attempt. 40 local runs of the case and
the native suite (32/32) pass; nothing outside the test changes.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* feat: Windows contrast themes followed - every colour the theme's own, by role from WPF UI's four contrast files, the accent its highlight and the highlight's text, the charts in its colours, the Remove button its own button, on and off at once (D91) (beta.35 PR-5)
While SystemParameters.HighContrast is on, the light or the dark Fluent theme (as the
contrast theme is) lies under Services/ContrastOverlay: every key of WPF UI 4.3.0's HC1,
HC2, HCBlack and HCWhite in the user's own SystemColors colour for its role
(Services/ContrastRoles: the colour a key has in all four, opaque colours only; ties and
placeholders by name), the transparent keys transparent, the 21 accent keys as the
highlight and the text on the accent as the highlight's text. No Mica, no
SystemThemeWatcher (it would apply WPF UI's files: 84 of 97 colours a red placeholder,
17 brushes that throw). A switch, an edit or turning it off is followed at once.
What the App draws itself reads ContrastTheme.Active: ChartPalette.ForContrast,
ChartTheme.TextOn, the artwork band, the Import list, the update footer. The Remove
button takes the DangerButton style (WPF UI's Danger is a fixed #F44336). Settings >
Theme says a contrast theme is in use.
Red first: the sweep under four default and two edited themes found the chips at
1.26-1.78:1, the Remove button at 3.06-4.42:1, the badges' black, and the pressed
menu item white on white.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: what no sweep rendered reads - the agent's pill on the theme's own fills, every snackbar in the theme's colours, a Danger button's dark text on its red and the theme's own button under a contrast theme (beta.35 PR-5)
Measured 2026-11-09 against WPF UI 4.3.0's styles, outside any surface the sweeps render:
the title bar's agent pill was a ui:Badge with a bound palette appearance (light theme
2.78, 2.63, 2.16 and 3.68:1), the Success and Caution snackbars white on fixed green and
orange (2.78 and 2.16:1 in both themes), and a Danger button white on #F44336 in the dark
theme (3.68:1), out of any contrast theme's reach.
AgentPill (a Pill on the theme's success, caution and critical fills), the strip's
messages all Secondary, and an implicit ui:Button style: a Danger button's text is
TextFillColorDarkPrimaryBrush (5.3 and 5.7:1), and the theme's own button while a
contrast theme is on, message boxes included. The DangerButton style of the first
commit is gone; a bound badge appearance and the other five button appearances are
refused.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>