* 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>