Compare commits

...
Author SHA1 Message Date
poli0981 134115bfd5 Merge pull request #383 from poli0981/alpha4/pr2-sync-main
sync: main at 0.1.0-alpha.4's notes into alpha - v0.1.0-beta.37 on .NET 11.0.0; every switch file takes main's side and the branch now differs from main in RELEASE_LINE alone (D98) (alpha.4 PR-2)
2026-11-11 07:43:33 +07:00
poli0981andClaude Fable 5.2 da2cb93fa9 sync: main at 0.1.0-alpha.4's notes into alpha - v0.1.0-beta.37 on .NET 11.0.0; every switch file takes main's side and the branch now differs from main in RELEASE_LINE alone (D98) (alpha.4 PR-2)
main moved to .NET 11 with 0.1.0-beta.37 (D94), so what the alpha
branch held as its switch - global.json, the TFM, the three
runtime-serviced packages, legal/licenses/nuget, the Transitive row of
THIRD_PARTY_NOTICES - main now holds at released versions. All 27
conflicts were in those files and each takes main's side: the branch's
release-candidate lines go. RELEASE_LINE stays `alpha`, and
`git diff --name-only origin/main` on this tree prints that one name.

The alpha line rests after 0.1.0-alpha.4 (docs/12_BUILD.md, The alpha
line): no further sync follows a beta until a newer .NET is tried.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
2026-11-11 07:30:48 +07:00
poli0981andClaude Fable 5.2 428b723bb3 docs: 0.1.0-alpha.4's notes - 0.1.0-beta.37 on .NET 11.0.0, the last alpha for now; how its sync differs, owner-only item 35 (alpha.4 PR-1) (#382)
- 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>
2026-11-11 00:29:52 +00:00
poli0981andClaude Fable 5.2 1a7fbf3ce7 release: 0.1.0-beta.37 - its changelog file (the main line on .NET 11, what an alpha is now, .NET 11's API and no C# 15 yet), HANDOFF's beta.37 section (D94-D98), owner-only item 34, the release lines (beta.37 PR-4) (#381)
- 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>
2026-11-11 00:18:00 +00:00
poli0981andClaude Fable 5.2 94eec7831c refactor: .NET 11's API where it reads better, and why no C# 15 construct is used yet - the canary, the table, the dispatch trigger for CodeQL (D96) (beta.37 PR-3) (#380)
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>
2026-11-11 00:04:05 +00:00
poli0981andClaude Fable 5.2 1c60c87b92 legal: what an alpha is once .NET 11 has shipped - EULA 1.7, Disclaimer 2.14, Alpha notice 1.1; a resting alpha says so and names a prerelease only where it runs on one (D97, D98) (beta.37 PR-2) (#379)
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>
2026-11-10 23:28:40 +00:00
poli0981andClaude Fable 5.2 49d7bd8e51 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) (#376)
* 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>
2026-11-10 23:13:00 +00:00
poli0981andClaude Fable 5.2 8767d30c7e docs: 0.1.0-beta.36's notes name the .NET runtime it carries (10.0.15), and HANDOFF records the release (#375)
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>
2026-11-10 17:13:25 +00:00
poli0981andClaude Fable 5.2 deaa8f30df release: 0.1.0-beta.36 - its changelog file (Qodana in CI, what its first run reported settled), HANDOFF's beta.36 section (D93), owner-only item 33, the release lines (#374)
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>
2026-11-10 16:34:10 +00:00
poli0981andClaude Fable 5.2 1342979353 ci: Qodana - JetBrains' code analysis from a workflow of its own, and what its first run reported settled (D93) (#373)
* 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>
2026-11-10 16:13:04 +00:00
poli0981andClaude Opus 5.5 7e6ff64b3a release: 0.1.0-beta.35 - its changelog file (accessibility: the statement, a screen reader's names and announcements, headings and charts, contrast themes, focus), HANDOFF's beta.35 section (D88-D92), owner-only item 32, the release lines (beta.35 PR-7) (#372)
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>
2026-11-09 06:30:00 +00:00
poli0981andClaude Opus 5.5 731f6d3082 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) (#371)
* 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>
2026-11-09 06:11:02 +00:00
poli0981andClaude Opus 5.5 cea7d87ff8 feat: Windows contrast themes followed - every colour the theme's own, the accent its highlight, the charts in its colours; and the title bar, the snackbars and a Danger button read (D91) (beta.35 PR-5) (#370)
* 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>
2026-11-09 05:46:12 +00:00
poli0981andClaude Opus 5.5 54a2c08601 feat: headings and charts a screen reader can use - page and section headings, every chart named with where its numbers are, its keys kept, a double-click that shows all of it, no series told apart by colour alone (D90) (beta.35 PR-4) (#369)
Every Title is AutomationProperties.HeadingLevel Level1 and every section Subtitle Level2; a Subtitle that shows
a value says None. AccessibilityTests holds every Title and Subtitle to a declared level, PagesLoadTests every
page to one first-level heading.

Every plot is Charts/ChartPlot, ScottPlot's WpfPlot with a peer: an Image of the localized type "chart", named
and with help text saying where its numbers are and which keys move it, focus drawn with WPF UI's focus style.
Charts/ChartKeys keeps the arrows and A with the chart after ScottPlot has acted (the page used to scroll or move
the focus on); a double-click shows all of the chart, as the guide said, instead of ScottPlot's benchmark overlay.
Charts/ChartPatterns gives every series a line pattern, marker or hatch by its index - Compare's five sessions,
the GPU temperature and hot spot, the two stutters, the two lows, the two limits - and
NoChartTellsTwoSeriesApartByColourAlone reads every chart's legend for two entries that differ by colour only.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-09 04:52:30 +00:00
poli0981andClaude Opus 5.5 926580c0f2 feat: a screen reader is told what appears - safety notices, the agent's and the update's banners, every short message, a game page's notice and each maintenance result, through UI Automation's notification (D89) (beta.35 PR-3) (#368)
Services/IAnnouncer over Services/UiaAnnouncer, the one place the App raises UI Automation's notification event:
only on its active window (a game that has the screen is never interrupted) and only when a screen reader listens.
An Alert (every one read): a safety notice as it arrives, a warning in the strip, the agent going offline, a game
page's refusal. A Status (a newer one replacing one not yet read): the strip's info and success, the agent back, an
update's step, a page's success, every Database maintenance result.

Every transient message goes through IMessageStrip now - MainWindowViewModel's six direct ISnackbarService calls
moved to it - and SnackbarStrip says what it shows. Services/ShellAnnouncements says only a change: the first state
is read with the window, a download's percent ticks are one step, a rebuilt window says nothing. The maintenance
line's LiveSetting, which announced nothing, is gone; no XAML may set one.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-09 04:36:48 +00:00
poli0981andClaude Opus 5.5 0b485d1293 feat: what a screen reader is given - every item, cell and row button named by what it shows, the display-only controls with a voice, the notices' text reachable, no silent Tab stop (D88) (beta.35 PR-2) (#367)
PagesLoadTests.Automation sweeps the UI Automation tree WPF builds for every page, window, dialog and control,
every tab shown: no Tab stop without a peer, no item named by its type, every focusable control named, no shown
text hidden in a template, no two buttons in a list sharing a name. All five went red on main first.

Fixes: every list item type speaks through ToString (Services/SpokenText) - Choice its label, a notice its title
and text, a document page its title, a session row its date, length and tier; FpsReadout, TriStateChip and
ChangeBadge get SpokenTextAutomationPeer (a Text element, no children) and leave the tab order, and the readout
says rule 6 aloud (Native, displayed and the factor together); a template column names its cells through
Controls/CellName over WPF UI's DefaultDataGridCellStyle, an empty cell read as "empty"; a row's button names its
row; the App's InfoBar template draws title and message through ContentPresenters; implicit styles take
ItemsControl, ui:Image and ui:CardControl out of the tab order; a CardExpander's expand button is named after its
header (Controls/ExpanderToggleName); the dialog hosts are no Tab stops. ScreenReaderNamesTests holds each piece.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-09 04:16:02 +00:00
poli0981andClaude Opus 5.5 fad7b84075 feat: the accessibility statement - ACCESSIBILITY.md under Help > Accessibility and on the wiki, the Accessibility problem form and its label, the documents corrected (D88) (beta.35 PR-1) (#366)
ACCESSIBILITY.md states WCAG 2.2 AA through WCAG2ICT as a goal and never a claim, what works with the keyboard
alone, a screen reader, a contrast theme or Magnifier, how it is checked (the owner's pass of 2026-11-09 on
beta.34 and alpha.3), the known limits with what to do instead, and how a barrier is reported and handled - by
severity, no promised times. Embedded and shown under Help > Accessibility and after Limitations in the guide's
window; a wiki page of its own.

The Accessibility problem issue form, a user-interface section in the PR template, and the labels accessibility,
safety and priority-high - the last two named by the Safety gap form since 2026-08-02 and never existing.

Documents corrected: charts take focus and ScottPlot's keys (ChartKeyboardTests measures it; 08_UI said
neither); the database-maintenance live region announces nothing; the Narrator gap is the owner's pass now;
20_OPEN_QUESTIONS G's accessibility row closed; NFR-9 widened (D88-D91); LIMITATIONS gains an Accessibility
section and loses its one struck sentence, which a screen reader reads as current.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-09 03:51:44 +00:00
dependabot[bot] 4cc4c3e9c2 Bump the minor-and-patch group with 1 update (#365)
Bumps Meziantou.Analyzer from 3.0.317 to 3.0.319

---
updated-dependencies:
- dependency-name: Meziantou.Analyzer
  dependency-version: 3.0.319
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: minor-and-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2026-11-09 07:03:16 +07:00
poli0981andClaude Opus 5.5 eb1c375b87 sync: main at 0.1.0-alpha.3's notes into alpha - v0.1.0-beta.34 and the notes, by a merge commit (D87) (alpha.3 PR-2) (#364)
alpha takes main at 0.1.0-alpha.3's notes (27f537a, #363) - v0.1.0-beta.34 and the notes, no other change - by a merge commit (13_CI_CD §The alpha line). One file the switch holds moved on main, legal/THIRD_PARTY_NOTICES.md (#358's Streamline row), on a line the switch does not touch, so the merge took both without a conflict; main's package set is unchanged and the switch is alpha.1's (SDK 11.0.100-rc.3.26522.148, the three packages at 11.0.0-rc.3.26522.148, the same NuGet licence texts). Its gate passed on the 11 SDK (run 42198454631, net11.0), as the local trial of the same tree had.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-06 17:11:35 +07:00
poli0981andClaude Opus 5.5 27f537a2d7 docs: 0.1.0-alpha.3's notes - its changelog file opening with the experimental-build warning, its row, HANDOFF's alpha.3 lines, owner-only item 31 (D87) (alpha.3 PR-1) (#363)
The third alpha is the source of 0.1.0-beta.34 on .NET 11 RC3 (D87: right after
beta.34, on RC3 because the train reached it before .NET 11's release on
2026-11-10). Its notes are on main as every release's are; the alpha branch takes
them with the sync that follows this pull request (13_CI_CD §The alpha line).

- docs/changelog/0.1.0-alpha.3.md: the experimental-build warning, the update
  from alpha.2 (the ledger copy, the Disclaimer 2.13 and the Privacy Policy 2.14
  once, the Alpha notice's box again, schema 22 - which an alpha.2 cannot open),
  installing over a beta and going back, and what differs from the beta - the
  same as alpha.1 from beta.32.
- CHANGELOG.md: its row in the Releases table.
- docs/HANDOFF.md: START HERE's "0.1.0-alpha.3" lines (the sync by a merge
  commit, the switch unchanged, the first alpha whose ledger moves) and
  owner-only item 31, the third alpha on real hardware.

No release line moves (README, ACCURACY, the Disclaimer's copy and LIMITATIONS
keep naming the newest beta).

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-06 09:51:02 +00:00
poli0981andClaude Opus 5.5 44c031faca release: 0.1.0-beta.34 - its changelog file (DLSS 5 and DLSS 4.5 from evidence, filters, Games at once), HANDOFF's beta.34 section (D83-D87), owner-only item 30, the release lines (beta.34 PR-7) (#362)
docs/changelog/0.1.0-beta.34.md takes [Unreleased] as it stood (#356-#361)
under a summary and the update paragraph: the Disclaimer 2.13 and the
Privacy Policy 2.14 once, schema 22 (a beta.33 cannot open it), rules
2026.11.2. HANDOFF's beta.33 START HERE (with its alpha.2 lines) moves
verbatim to docs/handoff/history/0.1.0-beta.33.md with its row; the new START
HERE carries D83-D87, the choices, what was measured and the traps
(notice-check reads the index, the native token test's exact mask, WPF UI's
navigation cache and pane template, Microsoft.Data.Sqlite's synchronous
async); owner-only item 30 is beta.34 on real hardware; D87's row. README,
ACCURACY, the Disclaimer's accuracy block and LIMITATIONS name
0.1.0-beta.34.

One wording fix found while writing the notes, before the release: D83's
evidence is DLSS Frame Generation IDENTIFIED in the session (fg_mode =
dlssg), as DlssText reads it - its factor need not have been counted - and
five places written in #357 said "counted" (05_DETECTION twice, spike-notes
§26, the changelog entry, HANDOFF's D83 row), with DlssText's and the test's
comments. DlssTextTests now pins it: Dynamic applied with DLSS Frame
Generation identified and the count refused (non_uniform) reads DLSS 4.5.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-06 09:34:30 +00:00
poli0981andClaude Opus 5.5 f66d98eb78 docs: the tested-games list from a copy of the ledger of 2026-11-06 (D35) - fifteen more games measured, the first Xbox titles; the docs sweep across the train (beta.34 PR-6) (#361)
Owner request 2026-11-06, item 5: review, update and sync the documents and the
tested-games list, from the database.

- docs/LIST_GAME_TESTED.md: refreshed from a copy of the owner's ledger taken
  2026-11-06 (read-only; 131 sessions of 27 games, the same as the live ledger
  when the commit was made), as drafted in the plan the owner approved: fifteen
  more Tier-1 rows (Phantom Blade Zero under Dynamic, Hogwarts Legacy loading
  DLSS 5's runtime, Valor Mortis and inKONBINI from the Xbox app, ...), seven
  rows updated, the Tier-2 sessions and the guard's refusals since 2026-09-27,
  the driver range and the engine versions read since.
- docs/08_UI.md: the DLSS line's two new rows (D83, D84); Compare over every
  session.
- docs/HANDOFF.md: item 28's tested-list step done.
- docs/open-questions/closed-s.md: S30 notes the fifth Streamline id decoded,
  from the vendor's header rather than by guess (row O4's warning).
- guide/08-settings.md: a language change stays on Settings.
- CHANGELOG.md: the entry.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-06 09:17:49 +00:00
poli0981andClaude Opus 5.5 efaf585928 feat: filters on Games and Compare; the Compare page's layout; the selected pane item keeps its label (D85, D86) (beta.34 PR-5) (#360)
Owner request 2026-11-06, items 3 and 4, with a screenshot of Compare.

- Games (D85): Store, Engine, State, Installed and Played beside the search
  and sort, with Clear filters; the title counts what is shown of all while a
  filter or the search narrows it. Kept while the App runs, not saved.
- Compare (D85): every session (it was the newest 200, one game lookup each;
  now one read of the names, off the UI thread), filtered by game, tier and
  frame generation, with a count; a ticked session stays listed.
- Compare layout: the selection bar on the left above the list with Clear
  selection; columns sized to what they hold and one filler column; the date
  sorts by when; the settings-changed cell says so or shows a dash; the
  result table's labels sit over their columns (MetricHeader bound).
- The pane (D86): our copy of WPF UI 4.3.0's LeftFluent item template
  without the IsActive collapse, so the selected page keeps its label.
- Strings en/vi/ja (ja review); 08_UI, guide/07-screens, CHANGELOG, HANDOFF.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-06 09:05:13 +00:00
poli0981andClaude Opus 5.5 a78d7bd359 feat: Games opens at once from any page - the window keeps the library page, cards before the executable checks; a language change keeps the page on screen (beta.34 PR-4) (#359)
The owner, 2026-11-06: switching to Games stalls 0.5-1.5 s; and changing the language in Settings
brings back the last game page instead of Settings.

- Measured first (spike-notes 27, a scratch test, not committed; 65 games, the first executable
  check held 800 ms for a USB drive waking): first cards 822-830 ms -> 10-15 ms; a revisit
  181-215 ms -> 15-16 ms; the first build unchanged (the non-virtualizing grid, by decision).
- WindowPageCache: the window's own page provider keeps the GamesPage it built (set after
  SetNavigationControl, which hands the NavigationView the container's provider; WPF UI's
  NavigationCacheMode is never read when a page provider is set). One per window, so a language
  change's new window builds its own.
- GamesViewModel: the library read on the thread pool; the cards listed before the executable
  checks, each getting its Not installed pill when its check answers; a read keeps every card that
  would look the same (GameCardViewModel.LooksLike, Sync - never Clear); the page reads the library
  again each time it is shown (Attach). The list view is bounded (MaxHeight 640).
- ShellHost notes every page the live window shows (pane clicks included), so a rebuild opens on
  the page on screen - Settings after a change made there.
- Tests: GamesViewModelTests (cards before the checks, a page shown again, Sync), WindowPageCacheTests
  (kept per window; the shell remembers the page on screen).
- Docs: 16_WPFUI_SYNTAX, wiki App-UI-development, 08_UI, 09_I18N, spike-notes 27, CHANGELOG.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-06 08:49:55 +00:00
poli0981andClaude Opus 5.5 c9b0aab862 feat: DLSS 5 is named where the game ran its neural rendering (schema 0022, rules 2026.11.2, Privacy 2.14); Streamline headers re-vendored at v2.14.16 (D84) (beta.34 PR-3) (#358)
The owner, 2026-11-06: Hogwarts Legacy with Neural Rendering on loaded DLSS 5's runtime
(nvngx_dlssnr.dll 310.9.16.0, from the game's folder) and the session could say only "DLSS 5
runtime loaded". Then: check what changed in recent Streamline versions, fix it if needed.

- Streamline: the vendored closure was v2.12.0 byte for byte; v2.14.16 changes three of its
  eleven files (kFeatureDLSS_NR = 1004, the uplift buffer types 70-72, kStructVersion7, the
  version). Re-vendored byte for byte; README provenance, THIRD_PARTY_NOTICES row.
- Overlay (hook path): the slEvaluateFeature detour decodes kFeatureDLSS_NR into its own bit;
  RecordPresent sets FL_FEAT_SL_NEURAL_RENDERING (feature byte bit 7, an enumerator - no layout
  change) under the condition every Streamline fact shares; the evaluate row's family also claims
  FL_HOOK_SL_NEURAL_RENDERING (bit 12), published with the detour. Overhead: decode unchanged
  within noise (4.7 ns a call), +0.14..0.19 ns a present.
- Agent: Domain.Metrics.NeuralRendering.SharePct; sessions.dlss_nr_pct (schema 0022) only from a
  writer that published the family - an older Overlay's silence is never a measured 0 %.
  CensusNames records sl.dlss_nr.dll.
- Rules 2026.11.2: capability dlss_nr -> "Supports DLSS 5 Neural Rendering".
- App (D84): DLSS 5 heads the DLSS line where it ran ("DLSS 5 (neural rendering on 97.3% of
  rendered frames)"); its library listed with version and source; measured 0 -> "runtime loaded,
  not seen running"; nothing to tell -> "runtime loaded" as before. CSV basis/pct.
- CaptureHost dev census: a kFeatureDLSS_NR bucket.
- Privacy Policy 2.14 (neural-rendering libraries); the accuracy block's DLSS 5 sentence.
- Tests: native guard_test (the new harness mode through an injected Overlay; 0xF00D lights no NR
  fact; the token case's exact mask gains the family), NeuralRenderingTests, SessionAggregatorTests,
  DlssGenerationTests, DlssTextTests (a row shaped from session 132), LedgerDatabaseTests (0022),
  the repository round trip, the rules fixture, RuntimeModuleSourcesTests, SlCensusTests.
- Docs: 05_DETECTION, 06_DATA_MODEL, 17_HOOK_ENGINE, LIMITATIONS, guide/03, guide/10, the accuracy
  block, spike-notes 26 (+ owner-only item 30(a)'s decision table), HANDOFF (D84), CHANGELOG.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-06 08:39:42 +00:00
poli0981andClaude Opus 5.5 569bacac95 feat: a session under the NVIDIA App's Dynamic frame generation reads DLSS 4.5; Disclaimer 2.13 (D83) (beta.34 PR-2) (#357)
The owner, 2026-11-06: Phantom Blade Zero under the NVIDIA App's Dynamic multi frame generation,
up to x3, read "DLSS 4" - but Dynamic (and x6) exist only in DLSS 4.5. The DLSS line named a
generation from the measured multiplier alone, and "up to x3" never passes x3.0.

- Domain: DlssEvidence.DynamicFrameGeneration, DlssBasis.DynamicFrameGeneration; the rule's new
  row sits below a measured x5 and above every DLSS 4 row.
- App: DlssText reads Dynamic as DLSS Frame Generation counted AND the game's driver profile
  setting NGX_DLSSG_MODE to 4 (NvidiaDriverSettings.DlssgModeDynamic, NVIDIA's own name) AND the
  driver's FG word reporting the mode override applied (FG_MODE). The driver's own mode number
  (3 Dynamic / 1 Fixed on all sixteen stored sessions) is recorded, not keyed on. Label "DLSS 4.5
  (Dynamic multi frame generation, set in the NVIDIA App)", CSV basis=dynamic_frame_generation.
  A Fixed multiplier names nothing by itself (Witcher 3 under Fixed x6 still presented x2.0).
- Dlss_Basis_Dynamic in en/vi/ja (ja review).
- Docs: 05_DETECTION (row + amendment), 03_METRICS (the ceiling decode confirmed), LIMITATIONS,
  guide/03, guide/10, the accuracy block re-dated 2026-11-06 + Disclaimer 2.13, spike-notes 26
  (new), HANDOFF decisions index (D83), CHANGELOG.
- Tests: DlssGenerationTests, DlssTextTests (a row shaped from the owner's session 129 and four
  negatives).

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-06 08:15:42 +00:00
poli0981andClaude Opus 5.5 f7bfe1e8f1 fix: an Xbox game's picture name that names a file's stream is passed over, not thrown on; the guard's note on GuardedInjectImpl sits above it again (beta.34 PR-1) (#356)
Two things a self-review of #351 and #352 found after their gates were green.

- XboxArtCache.Image: a ShellVisuals name in MicrosoftGame.config that points at a
  stream of a file, named like a drive ("Resources\a:b.png"), made the scale
  search's pattern "a:b.scale-*.png", and EnumerateFiles throws ArgumentException
  on a rooted pattern ("Second path fragment must not be a drive or UNC name") -
  which XboxArtCache.Find does not catch. GameArt.ForAsync's task then faulted:
  the game page showed no picture and logged an unobserved task, and a command
  that awaits the page's reload would reach the dispatcher's crash report. A name
  whose leaf holds ':' is now no picture, like a name outside the package. Red
  without the fix (the exact ArgumentException), green with it; no install of
  the owner's eleven titles has such a name (spike-notes §25).
- fl_guard.cpp: #352 put BlockingMitigation and TargetIsolationVerdict between
  GuardedInjectImpl and the comment that describes it ("A refusal returns here
  ... runs only for a target the full evaluation allowed"), so it read as the
  first line of BlockingMitigation's. It moves back above GuardedInjectImpl and
  names the target's isolation among what runs after the evaluation. No code
  change there.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-03 08:09:29 +00:00
poli0981andClaude Opus 5.5 4a0d5b482d sync: main at 0.1.0-alpha.2's notes into alpha - v0.1.0-beta.33 and the notes, by a merge commit (D82) (alpha.2 PR-3) (#355)
alpha takes main at 0.1.0-alpha.2's notes (4054492, #354) - v0.1.0-beta.33 and the notes, no other change - by a merge commit (13_CI_CD §The alpha line). No file the switch holds moved on main and its package set is unchanged, so nothing conflicted and the switch is alpha.1's (SDK 11.0.100-rc.3.26522.148, the three packages at 11.0.0-rc.3.26522.148, the same NuGet licence texts). Its gate passed on the 11 SDK (run 41597957507, net11.0).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-03 14:57:26 +07:00
poli0981andClaude Opus 5.5 405449283b docs: 0.1.0-alpha.2's notes - its changelog file opening with the experimental-build warning, its row, HANDOFF's alpha.2 lines, owner-only item 29 (D82) (alpha.2 PR-2) (#354)
The second alpha is the source of 0.1.0-beta.33 on .NET 11 RC3 (D82: right after
beta.33, on RC3 because the train reached it before .NET 11's release on
2026-11-10). Its notes are on main as every release's are; the alpha branch takes
them with the sync that follows this pull request (13_CI_CD §The alpha line).

- docs/changelog/0.1.0-alpha.2.md: the experimental-build warning, the update
  from alpha.1 (the ledger copy, the Privacy Policy 2.13 once, the Alpha notice's
  box again), installing over a beta and going back, and what differs from the
  beta - the same as alpha.1 from beta.32.
- CHANGELOG.md: its row in the Releases table.
- docs/HANDOFF.md: START HERE's "0.1.0-alpha.2" lines (the sync by a merge commit,
  the switch unchanged, the first delta an alpha's release has to find - #350's
  lookup) and owner-only item 29, the second alpha on real hardware.

No release line moves (README, ACCURACY, the Disclaimer's copy and LIMITATIONS
keep naming the newest beta).

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-03 07:37:51 +00:00
poli0981andClaude Opus 5.5 249c02be56 release: 0.1.0-beta.33 - its changelog file (games from the Xbox app and the Microsoft Store), HANDOFF's beta.33 section (D77-D82), owner-only item 28, the release lines (beta.33 PR-3) (#353)
docs/changelog/0.1.0-beta.33.md takes [Unreleased] as it stood (#351, #352)
under a summary and the update paragraph: Privacy Policy 2.13 once, schema
21, rules 2026.11.1. HANDOFF's beta.32 START HERE moves verbatim to
docs/handoff/history/0.1.0-beta.32.md with its row; the new START HERE
carries D77-D82, the choices, what was measured and the traps (the
Malwarebytes quarantine of fl_guard_test.exe, the ARM64 clang-format,
SonarCloud read after a merge); owner-only item 28 is the Xbox titles on
real hardware. README, ACCURACY, the Disclaimer's accuracy block and
LIMITATIONS name 0.1.0-beta.33.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-03 07:23:45 +00:00
poli0981andClaude Opus 5.5 042fdd631c feat: Xbox games start through Windows and are recorded once they appear; the guard refuses an app container and a game under code protection by their own reasons; one exe-path reader for the capture path (D78, D80) (beta.33 PR-2) (#352)
* feat: Xbox games start through Windows and are recorded once they appear; the guard refuses an app container and a game under code protection by their own reasons; one exe-path reader for the capture path (D78, D80) (beta.33 PR-2)

Play on a game the Xbox app or the Microsoft Store installed runs
`explorer.exe shell:AppsFolder\<AUMID>` in either Play mode and from an
elevated App: the user's shell activates the package as its Start-menu
tile does. Started by its path a GDK game is never the game in its
package (spike-notes §25), so the agent answers LaunchGame for an
executable whose install root is a GDK package root with `PackagedGame`
and starts nothing; the watcher records the game when it appears.

The guard asks one last question before the primitive, from the target's
own token and mitigation policies: kTargetAppContainer (a UWP app, D78)
and kTargetMitigation (signed-only images, no dynamic code, a strict or
non-CET-blocking user shadow stack, strict CFG). Neither is a finding;
both are Tier 2 with the reason. Each ended before as a failed
injection, a hook that installed nothing, or a risk of ending the game.
"Could not tell" refuses as kProcessUnreadable. Catch2 holds each
refusal through the seam, and two against Windows itself (a child
started under ProhibitDynamicCode + MicrosoftSignedOnly).

TargetResolver re-finds a game by the kernel's image name, as the
watcher keys it (ProcessImagePath), instead of the loader's
(MainModule), still opening candidates with the guard's rights so a
process an anti-cheat driver closes stays TargetUnreadable (D21).

Also: SonarCloud's two findings on PR-1 - the wcslen in
IsGdkPackageRoot (cpp:S5813) and new-code coverage under 80 %.

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

* test: a PC with no games folder names none - the hosted runner has no .GamingRoot, and FluentAssertions' OnlyContain fails an empty list (beta.33 PR-2)

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

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-03 06:14:56 +00:00
poli0981andClaude Opus 5.5 6ba6a41cea feat: games from the Xbox app and the Microsoft Store - the GDK library, a package root as an install-root boundary, the xbox platform rule, the game's own art; Privacy 2.13 (D77-D81) (beta.33 PR-1) (#351)
* docs(spike-notes): §25 - the Xbox/GDK titles' layout, read-only, and the launch probe's decision table, written before the run (D77) (beta.33 PR-1)

The owner's 11 GDK packages under C:\XboxGames and D:\xbox, read without launching anything: the .GamingRoot files,
MicrosoftGame.config / appxmanifest.xml, the WindowsApps junction chain, and the executables refusing FILE_READ_DATA
and FILE_EXECUTE to every process outside their package. Then the probe's method and the table that decides what each
outcome changes - committed before the probe runs, as the house rule asks.

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

* docs(spike-notes): §25's run - six GDK titles activated through their packages; the image paths, the chains, the tokens, the mitigations, and what a start by path really does (D77, D80) (beta.33 PR-1)

The image path and the loader's main-module path are both the Content spelling on every process of every chain; no
chain member the guard's rights cannot open; no fuzzy-fragment module; full trust, not an AppContainer, medium
integrity; none of the four mitigations. And CreateProcess by path is not error 5, as assumed: the package's launch
executable is replaced by an unpackaged gamelaunchhelper.exe that activates the package (the game is never the
caller's process nor its descendant), and an Unreal shipping executable runs outside its package. D80 stands on those
two measured grounds; the read-only claim is struck and dated in place.

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

* feat: games from the Xbox app and the Microsoft Store - the GDK library, a package root as an install-root boundary for the guard and detection, the xbox platform rule (root_file, rules 2026.11.1), the game's own art; Privacy 2.13 (D77-D81) (beta.33 PR-1)

The import gains a fifth store, `xbox`: each ready drive's .GamingRoot names the games folders, each
<Game>\Content\ holding MicrosoftGame.config beside appxmanifest.xml is a GDK package (read with DTDs prohibited),
and Windows' appmodel calls (PackageFamilyNameFromId, GetPackagesByPackageFamily) say whether it is installed for
this user. The record: the family name as the store id, Content as the install folder (the spelling the game's own
process reports, spike-notes section 25), the AUMID as the launch key; ExecutableLocator picks the process that
draws, never gamelaunchhelper.exe.

Safety: no install-root boundary matched the Xbox layout, so check 4 walked only an Unreal title's
Binaries\WinGDK. A GDK package root is now a boundary for InstallRoot and the native ResolveInstallRoot alike, asked
only where no store boundary matched (it can only widen the walk); GamesInstalled joins the native list; one case
list, tests/fixtures/install-roots/cases.txt, is read by Catch2 and xUnit both.

Detection: an `xbox` platform first in the array (a GDK FINAL FANTASY ships steam_api64.dll), decided by a new
root_file signal from the install root's own listing, so a deep walk that ran short cannot make it Unknown. Art: the
square logo and the splash image the package names, from inside the package root only. games.platform's vocabulary
gains xbox; the importer's fake repository now validates as the real one does. Privacy Policy 2.13 with the wording
approved with the plan; TRADEMARKS, 02_SPEC, 15_ROADMAP, 05/06/08/19/20, README, LIMITATIONS and the guide follow.

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

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-03 05:10:52 +00:00
poli0981andClaude Opus 5.5 7b3dec2b96 fix(release): find the delta by the name the pack listed - Velopack puts a non-default channel in its package names, which would have failed the second alpha (D73) (alpha.2 PR-1) (#350)
The 0.1.0-alpha.1 rehearsal (run 41220645263) packed FrameLedger.App-0.1.0-alpha.1-alpha-full.nupkg:
on a non-default channel Velopack names the packages with it. release.yml built the delta's name
for the default channel (FrameLedger.App-<v>-delta.nupkg), so the first alpha with a previous
alpha to diff against would have thrown "vpk produced no delta". The check now takes the one
*-delta.nupkg that assets.<channel>.json lists; a beta's names and checks are what they were.

13_CI_CD §release.yml (the alpha line) names the packages; CHANGELOG [Unreleased].

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-31 17:09:28 +00:00
poli0981andClaude Opus 5.5 a13206f220 build: the alpha line's switch - .NET 11 RC3 SDK and runtime, C# 15, the three runtime-serviced packages at 11.0.0-rc.3, the NuGet licence texts of that package set (D73, D76) (alpha.1 PR-1) (#349)
What the alpha branch differs from main by, and nothing else (docs/12_BUILD.md §The alpha line):
- RELEASE_LINE: alpha - release.yml tags this line vX.Y.Z-alpha.N only and packs it on Velopack's
  alpha channel; the App and the Agent act on it (the Alpha notice, its tick box, the Agent's
  wait, the badge and banner, the locked channel, the ledger copy).
- global.json: SDK 11.0.100-rc.3.26522.148, allowPrerelease (setup-dotnet installs exactly it).
- Directory.Build.props: TFM net11.0-windows10.0.22621.0; SupportedOSPlatformVersion stays 19045.
- Directory.Packages.props: Microsoft.Extensions.Hosting, Microsoft.Data.Sqlite and
  System.Diagnostics.EventLog 11.0.0-rc.3.26522.148 (Data.Sqlite 11 declares SQLitePCLRaw 3.0.5,
  SQLite 3.53.4).
- legal/licenses/nuget/: regenerated by tools/license-gather.ps1 - 69 packages (the nine
  Microsoft.Extensions abstractions are in the .NET 11 runtime; SQLitePCLRaw 3.0.5 and
  SourceGear's SQLite package); THIRD_PARTY_NOTICES says so.

./build.ps1 check on SDK 11.0.100-rc.3: ALL GATES PASSED - App 730, Application 553,
Infrastructure 536 of 538 (the two that need an administrator token), Domain 422, CaptureHost
137, Agent 32; coverage and licence OK. No source change: what .NET 11's SDK asked of the source
is on main (#345, spike-notes §24).

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-31 23:38:04 +07:00
poli0981andClaude Opus 5.5 11eaf14517 docs: 0.1.0-alpha.1's notes - its changelog file opening with the experimental-build warning, its row, HANDOFF's alpha.1 lines, owner-only item 27 (D73-D76) (alpha.1 PR-2) (#348)
* docs: 0.1.0-alpha.1's notes - its changelog file opening with the experimental-build warning, its row, HANDOFF's alpha.1 lines, owner-only item 27 (D73-D76) (alpha.1 PR-2)

The first alpha's notes, on main as every release's are; the alpha branch takes them with its
sync, and release.yml reads them for the tag v0.1.0-alpha.1 on alpha.

- docs/changelog/0.1.0-alpha.1.md: the warning first (an alpha of beta.32 on .NET 11 RC3, own
  risk, the Alpha notice with its tick box), installing it over the beta, going back, Windows and
  the processor, what differs from beta.32 (runtime, C# 15, three packages, SQLite 3.53.4, .NET
  11's IHost rethrow, the R2R target).
- CHANGELOG.md: its row in the Releases table. No release line moves (README, ACCURACY,
  LIMITATIONS keep naming the beta).
- HANDOFF: the alpha.1 lines under beta.32's START HERE (the next alpha follows the next beta;
  .NET 11 GA on 2026-11-10 moves the switch even without a beta); owner-only item 27.

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

* docs: where the alpha branch was cut - main at the notes, one docs commit after v0.1.0-beta.32 (alpha.1 PR-2)

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

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-31 16:23:35 +00:00
poli0981andClaude Opus 5.5 ac8bfda3d3 release: 0.1.0-beta.32 - its changelog file (the alpha line's groundwork), HANDOFF's beta.32 section (D73-D76), owner-only item 26, the release lines (beta.32 PR-4) (#347)
- docs/changelog/0.1.0-beta.32.md: the [Unreleased] entries of #344, #345 and #346, with what a
  user sees on updating (EULA 1.6 and Disclaimer 2.12 once; schema 21 and rules 2026.10.4 as
  they were; a beta never becomes an alpha).
- HANDOFF: beta.31's START HERE to docs/handoff/history/0.1.0-beta.31.md (and its row); the
  beta.32 START HERE - the owner's request, D73-D76, the evaluation, choices, the probe, traps;
  D73-D76 in the decisions index; owner-only item 26.
- The release lines: README's accuracy block and install line, legal/ACCURACY.md and the
  Disclaimer's copy, LIMITATIONS - "the latest beta is 0.1.0-beta.32", alphas published apart.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-31 16:07:25 +00:00
poli0981andClaude Opus 5.5 49b9084c1c feat: an alpha says what it is and asks first - Alpha notice + tick box, the alpha Agent's wait, ALPHA badge/banner, ledger copy; EULA 1.6, Disclaimer 2.12 (D73-D75) (beta.32 PR-2) (#346)
* feat: an alpha says what it is and asks first - the Alpha notice with its own tick box, the alpha Agent's wait, ALPHA badge and banner, the ledger copy before an alpha opens it; EULA 1.6, Disclaimer 2.12 (D73-D75) (beta.32 PR-2)

The owner's decisions of 2026-10-31, asked while planning: the alpha replaces the beta and shares
its data folder, copying the ledger before it first opens it (D73); a versioned Alpha notice with
its own tick box in the Legal Gate, the alpha's Agent waiting for it, a badge and a banner (D74);
the EULA and the Disclaimer made true about alphas (D75). Nothing of it shows in a beta.

- legal/ALPHA_NOTICE.md 1.0 (the approved text), embedded; Shared.AlphaNotice holds its key and
  version for both processes. LegalDocuments.Load(BuildLine) adds it after the four on the alpha
  line; About lists it on every line, for information.
- First run: on an alpha's gate a second warning box with the tick box; Accept is disabled until
  it is ticked. While the notice is outstanding the App holds the Agent's start - a hold of its
  own beside the updater's, set before the host starts (the connection's first round runs under
  the first-run window) - and Accept releases it and starts the Agent at once.
- Agent: an alpha's --serve reads legal_acceptance after opening the ledger and exits 8 until the
  notice is accepted at this build's version (the logon task can start it first); maintenance
  verbs are not held. Its log names the release line and the runtime.
- The shell: ALPHA badge beside the Agent pill (tooltip: the runtime), window title "FrameLedger
  Alpha", a Warning InfoBar at every start, closable for the run, opening the notice. About and
  --diag name the runtime; Settings locks the update channel on an alpha and says why.
- The ledger: LedgerDatabase.OpenAsync(backupFirst:) - an alpha copies the ledger with SQLite's
  online backup into backups\ledger-before-<version>.db before anything opens it for writing, once
  per version, under a lock of its own (the migration lock's 30 s would time a slow copy out); the
  newest three are kept and the copy just made is never pruned; a copy that cannot be made refuses
  the open (App: start-failure dialog; Agent: exit 7). Never for a viewer.
- EULA 1.6 (§2B) and Disclaimer 2.12 (§0): "pre-release builds - betas, and alphas". 12 strings in
  en/vi/ja (ja marked review).
- Docs: 08_UI, 06_DATA_MODEL §Migrations, 01_ARCHITECTURE §Lifecycle and §Data directory,
  11_UPDATER, 12_BUILD, LIMITATIONS §Alpha builds, guide/11-alpha-builds.md (+ contents, sidebar,
  the App's page list), guide/01-install, terms-in-plain-words, wiki/Releasing, CHANGELOG.
- Tests: FirstRunViewModel (tick, hold release), LegalDocuments (both lines; the constant equals
  the document's version), AgentConnection (the notice hold survives the updater's release),
  SettingsViewModel (locked picker), LedgerBackup (once per version, rows copied, keep three, the
  copy just made survives a skewed clock, a copy that cannot be made refuses the open, no request
  copies nothing), AlphaNoticeGate.

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

* fix: the ALPHA badge in the accent appearance, the picker's alpha lock on a container, About's legal list in its test (beta.32 PR-2)

The local gate's three reds on the previous commit, each a design test doing its job:
- ContrastTests: a badge's literal Appearance may not be a palette one (Danger paints outside the
  theme dictionaries, 08_UI §Contrast) - the ALPHA badge is Primary, the accent with its own text.
- ViewerModeTests: the update-channel picker keeps the viewer switch on the control itself; the
  alpha line's lock is a Grid around it bound to CanChooseUpdateChannel.
- DocumentWindowsTests: About's legal list now names legal/ALPHA_NOTICE.md (on every line, D74).

App.Tests 725/725.

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

* test: the alpha's start logic out of App.xaml.cs into AlphaStart, tested; the notice window, the exception, the no-op holds (beta.32 PR-2)

SonarCloud's quality gate on #346: new-code coverage 69.3 % against 80 %. The uncovered new lines
were the App's start helpers, DocumentWindows.ShowAlphaNotice, MainWindowViewModel's alpha
properties, LedgerBackupException's constructors and two default interface members.

- Services/AlphaStart: BackupFor (the copy only for an alpha over its own folder) and
  HoldTheAgentForTheNoticeAsync (the hold only while the notice is outstanding), which App.xaml.cs
  now calls; AlphaStartTests covers both and the viewer's and a window set's no-op members.
- DocumentWindowsTests: the alpha banner's button opens the notice in one window and asking again
  reveals it. LedgerBackupTests: the exception's three constructors.

App.Tests 730/730; dotnet format clean.

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

* docs: one Changed heading under [Unreleased] after main came in (beta.32 PR-2)

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

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-31 15:50:05 +00:00
poli0981andClaude Opus 5.5 8ac4c00e4b fix: what .NET 11's SDK asks of the source, in forms .NET 10 also compiles - span LastIndexOf/StartsWith/EndsWith, comparers for string sets, JsonElement.Parse; the probe in spike-notes §24 (D73-D76) (beta.32 PR-3) (#345)
The whole gate was run on .NET 11 RC3 (SDK 11.0.100-rc.3.26522.148) in a throwaway worktree
before the alpha line's switch was written. Native 32/32, every test suite green with no change
of answer, coverage and format clean; the managed build was red at 21 sites in 14 files, all
rewritten here so both SDKs compile them and they answer as before:

- CA1307 (13): .NET 11 adds LastIndexOf/StartsWith/EndsWith(char, StringComparison); the span
  forms (MemoryExtensions, also in .NET 10) are ordinal like the char forms. One site in a
  FluentAssertions expression tree, where a span cannot appear, compares the last char.
- MA0002 (7): C# 15 can give a collection expression a comparer, so Meziantou now flags
  HashSet<string>/Dictionary<string,...> built by []; the constructor with StringComparer.Ordinal
  (what [] used) compiles on C# 14 too.
- CA2026 (1, new in the 11 SDK): JsonElement.Parse instead of JsonDocument.Parse(...).RootElement
  in a test.

license-check was red on .NET 11 only because legal/licenses/nuget/ is the beta's package set;
the alpha branch regenerates it. docs/spike-notes/24-dotnet11-probe.md: the decision table
written before the run and what it found.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-31 15:19:19 +00:00
poli0981andClaude Opus 5.5 648e9c28b1 build: the alpha line - RELEASE_LINE stamped into every assembly, release.yml's line-vs-tag rule and Velopack alpha channel, CI on the alpha branch, no wiki for an alpha (D73) (beta.32 PR-1) (#344)
The owner, 2026-10-31: an alpha build where new .NET versions are tried, .NET 11 RC3 / C# 15 first,
with an experimental-build warning (owner decisions D73-D76, asked while planning). This is the
plumbing on main; it changes nothing in a beta.

- RELEASE_LINE (main | alpha), read like VERSION by Directory.Build.props, stamped as the
  FrameLedger.ReleaseLine assembly metadata; any other value is a build error. Shared.BuildLine
  reads it back for composition (BuildLineTests, AssemblyIdentityTests).
- release.yml: the version gate reads RELEASE_LINE - the alpha line takes vX.Y.Z-alpha.N and
  nothing else, no other line may carry an -alpha. tag; an alpha's vpk download and pack take
  --channel alpha (feed releases.alpha.json, asset names from assets.<channel>.json); the main
  line's pack command is unchanged. An alpha's release is titled "(experimental alpha)".
- ci.yml: also on pushes to alpha; no sonarcloud job and no Changelog step for pull requests into
  alpha. wiki.yml: no publish after an -alpha. tag.
- tools/fps-impact-runbook.ps1: the Agent path no longer names a TFM.
- Docs: 12_BUILD §The alpha line, 13_CI_CD §The alpha line (+ ci/release/wiki sections, branch
  policy), 11_UPDATER §Channels corrected in place (the alpha line uses Velopack channels;
  GithubSource reads the newest ten releases, hence one alpha per beta), 20_OPEN_QUESTIONS §G
  "The main line's .NET" with its decision table written first, CLAUDE.md, CHANGELOG.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-31 14:58:38 +00:00
poli0981andClaude Opus 5.5 2752fe9a2d release: 0.1.0-beta.31 - its changelog file (the remaining library updates), HANDOFF's beta.31 section (D72), the release lines (beta.31 PR-2) (#343)
- docs/changelog/0.1.0-beta.31.md: [Unreleased] moved under its heading, with the opening and how to update from
  beta.30 (nothing shown again - Disclaimer 2.11, Privacy Policy 2.12; schema 21; rules 2026.10.4; the first update
  beta.30's Velopack 1.2.161 installs). Its row in CHANGELOG.md's Releases table.
- docs/HANDOFF.md: beta.30's START HERE moved verbatim to docs/handoff/history/0.1.0-beta.30.md (its row in the split
  table); beta.31's START HERE - D72, the choices made, what was measured, the trap; Decisions index row D72; no new
  owner-only item (item 25(c) is this update).
- The release lines: README, the accuracy block (legal/ACCURACY.md and its copies), LIMITATIONS.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-26 11:09:31 +00:00
poli0981andClaude Opus 5.5 6b9330cb67 deps: the .NET 10.0.14 servicing packages and the updates beta.30 left - Markdig 1.5.0, CsWin32 0.3.367, Meziantou 3.0.317, coverlet.collector 10.1.0, Catch2 3.16.1 (D72) (beta.31 PR-1) (#342)
The owner, after beta.30: "làm thêm bản beta 31 với các deps còn lại (.net 10.0.14) và 1 số thư viện khác" - inside
Dependabot's seven-day cooldown on purpose (owner decision D72).

- Microsoft.Extensions.Hosting, Microsoft.Data.Sqlite, System.Diagnostics.EventLog 10.0.14 (Microsoft.Data.Sqlite
  10.0.14 still declares SQLitePCLRaw 2.1.13).
- Markdig 1.5.0: license.txt at the packaged commit 9900e46e is byte-identical; the override's header names it.
- CsWin32 0.3.367 and Meziantou.Analyzer 3.0.317: the build is warning-free as it was, nothing to change.
- coverlet.collector 10.1.0: NoSecondMatcherTests leaves out the Coverlet.* types the collector injects into each
  instrumented assembly (a constant reflection cannot read; not ours) - the reason it stayed at 10.0.1 in beta.29.
  Passes with coverage collected as CI collects it.
- Catch2 3.16.1 (native tests): clean under /W4 /WX with the /EHsc fix kept; 32 of 32 suites pass.
- legal/licenses/nuget regenerated; 13_CI_CD §Dependabot, CLAUDE.md, 08_UI.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-26 10:56:29 +00:00
poli0981andClaude Opus 5.5 4eb81c467b release: 0.1.0-beta.30 - its changelog file (and the .NET 10.0.14 runtime it carries), HANDOFF's beta.30 section (D69-D71), owner-only item 25, the release lines; ConsentPrompt.ShowAsync tested (beta.30 PR-4) (#341)
- docs/changelog/0.1.0-beta.30.md: [Unreleased] moved under its heading, with the opening and how to update from
  beta.29 (nothing shown again - Disclaimer 2.11, Privacy Policy 2.12; schema 21; rules 2026.10.4; a delta of about
  5 MB, installed by beta.29's updater), and a Security entry: the runtime is .NET 10.0.14, the out-of-band release of
  2026-10-25 - the rehearsal (run 40303218479) installed SDK 10.0.403, and the package's deps.json names the 10.0.14
  runtime packs. Its row in CHANGELOG.md's Releases table.
- docs/HANDOFF.md: beta.29's START HERE moved verbatim to docs/handoff/history/0.1.0-beta.29.md (its row in the split
  table); beta.30's START HERE - D69, D70, D71, the choices made, what was measured (WPF's re-transfer, WPF UI's
  template, ScottPlot's label, the SQLite engines, the rehearsal), the traps; Decisions index rows D69-D71; item 24(d)
  updated; owner-only item 25.
- The release lines: README, the accuracy block (legal/ACCURACY.md and its copies), LIMITATIONS.
- ConsentDialogKeysTests.OnlyThePrimaryButtonWithThePhraseTypedEnables: ConsentPrompt.ShowAsync through a fake
  IContentDialogService (Primary + phrase -> on; Primary alone, or the phrase and a close -> off) - the four lines
  SonarCloud found uncovered in #338.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-26 10:34:13 +00:00
poli0981andClaude Opus 5.5 517ef136f8 deps: Velopack and vpk 1.2.161 (D71), Markdig 1.4.2, and the SQLitePCLRaw pin dropped - Microsoft.Data.Sqlite's own 2.1.13 again; what was not taken and why (beta.30 PR-3) (#340)
- Velopack 1.2.0 -> 1.2.161 (Directory.Packages.props) with vpk 1.2.161 (release.yml) - the owner's decision D71, item
  24(d)'s Velopack half; never 1.2.158 (NuGet-deprecated). The five private fields VelopackHooksTests reads are there.
- Markdig 1.4.0 -> 1.4.2 (parser fixes); license.txt at the packaged commit 6a410393 is byte-identical to 1.4.0's, the
  reviewed override's header names the new commit.
- SQLitePCLRaw.bundle_e_sqlite3 3.0.5 transitive pin dropped: its own comment said to drop it once
  Microsoft.Data.Sqlite resolved a patched version (10.0.13 declares 2.1.13), and it had put a package built against
  the 2.x line on SQLitePCLRaw 3.x - a cross-major resolution NuGet does not report. The engine is SQLite 3.53.3
  (3.53.4 under the pin; read from the native libraries), above every floor the ledger needs.
- legal/licenses/nuget regenerated by license-gather (78 packages); THIRD_PARTY_NOTICES names the engine's package.
- Not taken, with reasons (13_CI_CD §Dependabot): the 10.0.14 servicing packages (a day old; the Brotli fix is the
  runtime's), Markdig 1.5.0, CsWin32 0.3.366/0.3.367, coverlet.collector 10.1.0, FluentAssertions 8.
- Docs: CLAUDE.md, 08_UI, 11_UPDATER, 13_CI_CD, CHANGELOG.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-26 10:18:23 +00:00
poli0981andClaude Opus 5.5 5608c71d59 fix(app): the hardware-change markers on a game's charts - a numbered badge per changed day in a band above the chart, the list under it, a tooltip (D70) (beta.30 PR-2) (#339)
The owner's screenshot (2026-10-26): "Driver GPU: 32.0.16.1742 -> 32.0.16.2101" with its top cut off at the chart's edge.
ScottPlot's VerticalLine label grows up from the data area into the top-axis panel, which an unused axis measures at
15 px; a day's further lines were lost; white on the orange read 1.78:1 / 2.63:1. Owner decision D70: numbers + a list.

- TrendSeriesBuilder.Markers (replaces MergedByDay): one ChangeMarker per changed day, numbered oldest first, each
  change once; the view model hands the same list to both charts and both lists.
- ChangeMarkerPlottable (IPlottable + IRenderLast): the dashed lines clipped to the data area; the badges after the
  axes in a band kept with Axes.Top.MinimumSize, joined to their lines, coloured from ChartTheme.Current at every render
  with ChartTheme.TextOn's black or white (black on both oranges, 11.79:1 / 8.00:1).
- ChangeBadgeLayout: inside the data width, never over another; too close -> aside in order; beyond ~one badge from
  their lines or no room -> one badge for the run ("3-5").
- ChangeMarkerList + Controls/ChangeBadge under both charts; Formats.Day; Trend_Changes_Header and
  Trend_Change_Heading_Format in en/vi/ja (ja drafts marked review).
- TrendChart: tooltip near a line or over a badge; the pointer read through the element's DPI now
  (GetPlotPixelPosition) - DisplayScale is read once, before the control has a window - for the overview's click too.
- ChartPalette.ForBackground shared by FgMixBar and ChangeBadge.
- Tests: ChangeBadgeLayoutTests (cases + a 20-2000 px sweep), PagesLoadTests.Changes (real renders at 640x320, 640x220,
  tight limits, 300x220, thirty days in a row; the tooltip's hit test), ChartMathTests (the badge text in both
  palettes), TrendSeriesBuilderTests, GameDetailViewModelTests; the shared page fixture has a driver change so the
  readable and theme-switch sweeps measure the list and its chip.
- Docs: 08_UI (Trend, the numbered markers, Contrast, DPI, Known gaps), 16_WPFUI_SYNTAX (Theming, Custom controls,
  ScottPlot, two Gotchas), 02_SPEC FR-6.3, guide 03 and 07, CHANGELOG.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-26 10:02:40 +00:00
poli0981andClaude Opus 5.5 1485341284 fix(app): Enter enables once the consent phrase is typed exactly (D69); the game page's switches read their row again after every click (beta.30 PR-1) (#338)
- ConsentPrompt: the primary button (Enable hooking) is the dialog's default, built by Build() so a test can render it.
  WPF UI 4.3.0's template sends Enter to the default button, and DefaultButton = Close made Enter in the phrase box
  decline without a word (the owner's report, 2026-10-26).
- ConsentDialogContent: while the phrase does not match, the content keeps Enter (SwallowsEnter) - the template makes
  Close the default while the primary is disabled; an IME's ImeProcessed is never taken for Enter.
- GameDetailViewModel: the Hooking and Recording commands raise the switch's property whatever happened
  (ThenShowStoredAsync). The switches are OneWay with a Command, a click flips IsChecked through SetCurrentValue, and a
  command that changed nothing (declined, refused, no Agent) left the switch on beside "off".
- Tests: ConsentDialogKeysTests (the real template and switch on the STA thread), GameDetailViewModelTests (every
  outcome raises the property; red without the fix).
- Docs: 19_SAFETY §User-facing consent (the D69 amendment), 08_UI (§Keyboard, the two switches, WPF UI's key routing
  corrected), 16_WPFUI_SYNTAX §Gotchas, the wiki's App-UI-development, guide 07-screens, DialogKeyboard's comment,
  CHANGELOG.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-26 09:39:31 +00:00
poli0981andClaude Opus 5.5 dc4727f846 release: 0.1.0-beta.29 - its changelog file, HANDOFF's beta.29 section (SonarCloud from CI, the libraries Dependabot never updated), owner-only item 24, the release lines; the patch check's NOSONAR on the line SonarCloud names (beta.29 PR-4) (#337)
- docs/changelog/0.1.0-beta.29.md: [Unreleased] moved under its heading, with the opening and how to update from
  beta.28 (nothing shown again - Disclaimer 2.11, Privacy Policy 2.12; schema 21; rules 2026.10.4; what is shown and
  recorded is beta.28's, the libraries under it newer); its row in CHANGELOG.md's Releases table.
- docs/HANDOFF.md: beta.28's START HERE moved verbatim to docs/handoff/history/0.1.0-beta.28.md (its row in the split
  table); beta.29's START HERE - D68, the choices made, what the analyses measured, the traps; owner-only item 24
  (optional settings: SonarCloud for Dependabot's pull requests, the branch a refused dispatch left, required checks,
  the two updates not taken).
- The release lines: README, the accuracy block (legal/ACCURACY.md and its copies), LIMITATIONS.
- A correction from main's analyses after #336: the 34 issues were dated by blame, two of them new code (the gate's
  C); the first analysis with a version kept the old new-code start and the next went green with nothing fixed; the
  merge of #336 closed 33, and cpp:S3519's NOSONAR moves from `p -= 5` to the read SonarCloud reports on the next line
  (a comment; the Overlay's code unchanged). 13_CI_CD, the beta.29 changelog and HANDOFF (two traps) say so.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-25 13:48:14 +07:00
poli0981andClaude Opus 5.5 3c89a76f71 fix(native): the 34 C++ issues of main's first SonarCloud analysis from CI - hook-harness asks for its D3D11 objects first, NvU32 as %lu, LARGE_INTEGER initialised through QuadPart, read bounds tested, five NOSONAR with reasons; the triage in 13_CI_CD (beta.29 PR-3) (#336)
main's first SonarCloud analysis from CI (run 40160302893) failed its gate on a C reliability rating: 34 C++ issues,
all on lines older than the release and all counted as new code, which the compilation database's real MSVC flags let
CFamily see for the first time.

- hook-harness: --vulkan and --opengl create no D3D11 objects, and --opengl alone (the default probes) or either flag
  beside a D3D11 mode called through a null swapchain - exit 0xC0000005 on main, measured. Every mode that drives the
  D3D11 swapchain asks HaveD3D11 first (exit 1 with a message); the dispatch's duplicate mode flags are the pre-pass's.
- fl-probe-nvapi: %lu for NvU32 (an unsigned long); the machine line CaptureHost parses prints the same digits.
- guard_test: 64-bit arithmetic on FILETIME's halves instead of a ULARGE_INTEGER; strnlen with the value's bound.
- A LARGE_INTEGER read through QuadPart after `{}` had made its first member, the LowPart/HighPart struct, the active
  one: the Overlay's log clock epoch and the Vulkan layer's enable-list read (where the PR's first two pushes drew the
  same S6232 on their own lines) are initialised through QuadPart now.
- VkLayer (that once-per-process read) and fl-baseline-probe: the read's bound tested before the terminator is
  written.
- NOSONAR with the reason above it, five: the ring's Publish (the path runs past a failed REQUIRE in ring_test), the
  patch check's hot-patch read, three console printf of a test and a probe.

The Overlay built from main and from this change, in one folder with one FL_BUILD_ID, has a byte-identical .text
(722,153 bytes); the layer's .text differs in one 613-byte range inside ThisProcessIsEnabled. docs/13_CI_CD.md carries
the triage, corrects its claim that issues on older lines are dated by blame, says why a local SonarAnalyzer's C#
findings are not the gate's, and quotes Dependabot's 2026-10-25 run on the shipped libraries.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-25 12:59:21 +07:00
poli0981andClaude Opus 5.5 a55cc478e8 deps: the NuGet updates Dependabot never proposed - .NET 10.0.13 servicing (Hosting, Sqlite, EventLog), Dapper 2.1.89, CsWin32 0.3.363, the test SDK and xunit; coverlet stays at 10.0.1 (beta.29 PR-2) (#335)
- Shipped: Microsoft.Extensions.Hosting, Microsoft.Data.Sqlite, System.Diagnostics.EventLog 10.0.12 -> 10.0.13 (the
  October servicing release); Dapper 2.1.86 -> 2.1.89; the CsWin32 source generator 0.3.333 -> 0.3.363.
- Tests: Microsoft.NET.Test.Sdk 18.11.0, xunit.v3.mtp-off 4.0.2, xunit.runner.visualstudio 4.0.1.
- legal/licenses/nuget: tools/license-gather.ps1 re-run - 32 files name the new versions; no licence text changed.
- Not taken: coverlet.collector 10.1.0 - the tracker it adds to every assembly it instruments declares a constant
  (ModuleTrackerRegistryKey) whose value reflection cannot read, and NoSecondMatcherTests reads every string constant
  in Application, Domain and Infrastructure; measured locally with coverage on (10.1.0 fails, 10.0.1 passes), after
  the first CI run had blamed CsWin32. Directory.Packages.props says so beside it. Also not taken: Markdig 1.5.0,
  Velopack 1.2.161, FluentAssertions 8; Meziantou is Dependabot's to propose.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-25 12:02:07 +07:00
poli0981andClaude Opus 5.5 a644dd873e ci(sonar): SonarCloud from CI - the sonarcloud job, SonarQube.Analysis.xml, the scanner as a local tool, the C++ through the compilation database; Dependabot cooldown, the NuGet audit, CodeQL reads the workflows (beta.29 PR-1) (#334)
The owner turned SonarCloud's Automatic Analysis off and set SONAR_TOKEN (2026-10-24) and asked for
the CI-based analysis with the newest scanner, run until its gate passed, and for Dependabot, the
audit and code scanning to be brought up to date (owner decision D68, replacing D67).

- ci.yml: a second job, sonarcloud, after check - SonarScanner for .NET 12.0.0 from
  .config/dotnet-tools.json; begin -> its own `dotnet build` -> end. Its own build because the
  scanner's targets turn TreatWarningsAsErrors off in the build they instrument. Advisory, not a
  required check; sonar.qualitygate.wait makes a failed gate a red job. Runs for this repository's
  pull requests (not a fork's, not Dependabot's - no secret) and for main: the organisation's plan
  refuses any other branch ("not allowed to access data from non main branches"). Permissions per
  job, none at workflow level (githubactions:S8264 on the first analysis).
- Coverage: build.ps1 collects "XPlat Code Coverage;Format=cobertura,opencover"; the job downloads
  check's artifact. C# only: sonar.coverage.exclusions leaves the PowerShell tools and src/native,
  which have no coverage report, out of the figures (SonarCloud counted build.ps1's 232 executable
  lines as uncovered).
- C++: FrameLedger.Infrastructure.csproj names src/native's .cpp/.h as FlNativeSource items that
  exist only while the scanner instruments the build; analysed with CMake's compilation database
  (configure with CMAKE_CXX_SCAN_FOR_MODULES=OFF - the .modmap response files only a build writes
  stopped CFamily - and fl_ac_floor_gen): 32 compilation units, all in full.
- SonarQube.Analysis.xml replaces .sonarcloud.properties; the version is the newest v* tag, so the
  project's "Previous version" new code is everything since the last release; S8417 (src/native)
  and csharpsquid:S6640 (Infrastructure, Shared) ignored where they apply by design;
  sonar.cs.roslyn.ignoreIssues.
- Dependabot: a seven-day cooldown on version updates; the actions' minor and patch releases
  grouped. It has never proposed a NuGet library update here (#66-#314: analyzers only) - beta.29
  PR-2 makes the missed ones. Directory.Build.props: the NuGet audit written down (all, low).
  codeql.yml: the actions language; superseded pull-request runs cancelled.
- Docs: 13_CI_CD (ci.yml, codeql.yml, SonarCloud rewritten with D67 kept as history and the first
  analyses measured, Dependabot and the NuGet audit, the checklist), 12_BUILD, CLAUDE.md, HANDOFF's
  D68 row, the wiki's Releasing page, CHANGELOG.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-25 11:00:35 +07:00
poli0981andClaude Opus 5.5 410c66d146 release: 0.1.0-beta.28 - its changelog file, HANDOFF's beta.28 section (every game being recorded on the Dashboard), owner-only item 23, the release lines (beta.28 PR-2) (#333)
- docs/changelog/0.1.0-beta.28.md: [Unreleased] moved under its heading, with the opening and how to
  update from beta.27 (nothing shown again - Disclaimer 2.11, Privacy Policy 2.12; schema 21; rules
  2026.10.4; only the App changes); its row in CHANGELOG.md's Releases table.
- docs/HANDOFF.md: beta.27's START HERE moved verbatim to docs/handoff/history/0.1.0-beta.27.md (its
  row in the split table); beta.28's START HERE - no new owner decision, the choices made for the
  cards, the traps; owner-only item 23 (two and three games at once).
- The release lines: README, the accuracy block (legal/ACCURACY.md and its copies), LIMITATIONS.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-20 05:10:29 +00:00
poli0981andClaude Opus 5.5 2188373239 feat: the Dashboard shows every game being recorded - one live card per running session, hooked first, two to a row, the games counted; two native injection cases wait up to 12 s (beta.28 PR-1) (#332)
The owner, 2026-10-20: "Thêm cơ chế hiển thị UI/UX Dashboard khi chạy >=2 game trong cùng 1 thời
điểm". The Agent records one session per executable, so two games are two sessions; the Dashboard had
one live card, which a hooked session took and kept, and the second game showed only as "Running
sessions: 2".

- DashboardViewModel.LiveCards: a LiveCaptureViewModel per running session, made by its session's
  first event or seed (LiveSessions) and fed only its own session's events; hooked first, each kind in
  the order it started, moved never rebuilt; LiveIdle, LiveCountText ("2 games recording" from two
  on, Dashboard_Live_Count_Format en/vi/ja) and LiveColumns (two to a row from two on).
- LiveCaptureViewModel: a card is one session's (a constructor with its guid; another session's start
  or seed no longer takes it).
- DashboardPage: the header with the count, one idle card, an ItemsControl of cards in a UniformGrid.
- Docs: 08_UI §Dashboard, guide/07-screens, CHANGELOG.
- Tests: DashboardViewModelTests (two games, a third, each ending; the existing cases per card),
  LiveCaptureViewModelTests, PagesLoadTests' surfaces draw a hooked and a held card in both themes.

Then, from this PR's first CI run (the native OpenGL and window-hold injection cases wait up to 12 s for their frames - 4 s was not enough on a loaded CI runner (beta.28 PR-1)):

#332's first CI run: fl_guard_test "OpenGL: the injected Overlay hooks opengl32!wglSwapBuffers ..."
failed with writeIndex 0 and apiMask 0x10 - the hook installed (the OpenGL bit is set at install),
no frame recorded in the 4 s the case waited; the suite took 115 s on that runner. Nothing native
changed in beta.28.

- Both cases with that wait (OpenGL, and the D3D11 chain on a real window) hold the harness 16 s and
  wait up to 12 s, ending at the 20th record as before; the child is terminated when the case ends,
  so the longer hold costs nothing.
- The OpenGL case's failure says the hooks mask, the writer's status and whether the harness still
  runs; the window case's says the status.
- CHANGELOG [Unreleased] (developers only).

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-20 04:42:29 +00:00
poli0981andClaude Opus 5.5 94120d3308 release: 0.1.0-beta.27 - its changelog file, HANDOFF's beta.27 section (six faults from the owner's eight sessions; the crash-safety question left to the owner), owner-only item 22, the release lines (beta.27 PR-2) (#331)
- docs/changelog/0.1.0-beta.27.md: [Unreleased] moved under its heading, with the opening and how to
  update from beta.26 (nothing shown again - Disclaimer 2.11, Privacy Policy 2.12; schema 21; rules
  2026.10.4; the frame-generation fix reads stored sessions at once, the rest applies to new ones);
  its row in CHANGELOG.md's Releases table.
- docs/HANDOFF.md: beta.26's START HERE moved verbatim to docs/handoff/history/0.1.0-beta.26.md (its
  row in the split table); beta.27's START HERE - no new owner decision, the owner's two ways for
  Steam games and why the note was taken, one question left to the owner (the crash safety counting
  a direct start's hand-off), what the ledger copy measured, the traps; owner-only item 22 (the driver's report and 20(b), Start directly on Lies of P, one window
  per session, display sizes).
- The release lines: README, the accuracy block (legal/ACCURACY.md and its copies), LIMITATIONS.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-20 10:53:28 +07:00
poli0981andClaude Opus 5.5 24a87159f4 fix: the owner's eight sessions of 2026-10-20 - a x2.52 state, the driver's DLSS word lost at exit, Start directly losing the game Steam starts, two summary windows, display sizes, a bare DLSS line; the Steam note; the two load-flaky tests (beta.27 PR-1) (#330)
The owner ran the installed 0.1.0-beta.26 (sessions 64-71) and asked for the results to be checked,
the two flaky tests fixed, bugs fixed, and a release if there were bugs. Read from a backup copy of
the ledger and the logs (docs/spike-notes/23-owner-runs-2026-10-20.md).

- FgWindow.IsNearWholeMultiplier: a window is a state's only within 10 % of a whole multiplier of two
  or more (FgSlices.Slice.IsActive); FgMixRecord.Parse reads stored rows by the same rule. Silent Hill
  2 under Dynamic MFG listed x2.52 for 12.8 s - windows where the multiplier stepped; it now reads
  x2.0, x3.0, none and 7.36 % not classified.
- NgxDriverState / CaptureSession: the driver is not asked after the game has gone, and CREATED |
  EVALUATE stand once a reading carried them. The last NGX reading, taken after the target exited,
  replaced every in-game one: none of the 14 answered sessions kept the two bits, so DLSS
  (driver-reported) and the NVIDIA App's mode (D63) never showed on an NGX-direct title.
- CaptureOrchestrator: a launch says it ended on its own (Recorded) with the pids it recorded
  (Targets), so a process turned away while it ran - the game Steam starts after Lies of P hands
  itself over - is recorded when it ends; the launch's own process never is.
- SessionSummaryOpener: one window per session; opening it again brings it forward.
- DisplayTally: the sizes are the mode's last sample that saw the window (a game leaving exclusive
  fullscreen closes it first; five sessions stored none).
- DlssText.Line: no line that says only "DLSS".
- Tests: the guard's scan set includes the test host above the harness, which under a full gate
  releases modules while it starts its other classes - ModuleScanFailed (reproduced 1 run in 12 of
  the assembly with coverage; 15 of 15 green after), ProcessUnreadable on 2026-10-19.
  ShmDrainIntegrationTests.InjectAsync asks again on those two reasons only (4 times at most, 250 ms
  apart); the pause case waits for READY; every injection suite waits for the harness's flushed
  "presenting" line instead of 800 ms (tests/Shared/HarnessReady.cs).
- Docs: 03_METRICS (the mix, the driver-reported rung, display sizes), 04_CAPTURE, 06_DATA_MODEL,
  08_UI, 14_TESTING, 18_GPU_VENDOR_APIS, 19_SAFETY (direct starts counted by the crash safety -
  measured, the policy unchanged), LIMITATIONS, guide (troubleshooting, results), spike-notes section
  23, HANDOFF items 20 and 21, CHANGELOG.

Then, on the owner's word about Steam games (Play > Start directly says a Steam game may hand itself to Steam - the notice, the tooltip and Settings (en/vi/ja); why a note rather than a fixed Steam rule (beta.27 PR-1)):

The owner, 2026-10-20: Steam games hand themselves to Steam; a note in the UI, or a fixed setting
that Steam's games always go through the Steam client - the choice left open. The note:

- GamePlayer: PlayResult.SteamGame - the game the agent starts (Start directly, or an App running as
  administrator, or a Steam record with no link) is one Steam's own records name; the notice then
  reads Play_Started_Steam_Format / Play_Elevated_Steam_Format. Store records are read once a press.
- Strings: Play_ToolTip_Direct and Settings_PlayMode_Body say a Steam game may hand itself to Steam
  and the game Steam then starts is recorded; Settings adds that a few will not start outside Steam
  at all. en/vi/ja, ja marked review; Strings.Designer regenerated.
- Why not the fixed rule: three of the five Steam games started directly on 2026-10-20 ran and were
  measured from their first frame, and a Vulkan game is measured only when FrameLedger starts it
  (Everhex Demo) - recorded in 08_UI.
- Docs: 08_UI, guide/08-settings, LIMITATIONS, CHANGELOG.
- Tests: GamePlayerTests (Steam started directly and elevated say it; a loose or GOG game does not).

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-20 10:31:47 +07:00
poli0981andClaude Opus 5.5 ea3a8d3ee0 release: 0.1.0-beta.26 - its changelog file, HANDOFF's beta.26 section (the x1336 state fixed, measured on the owner's ledger), the release lines (beta.26 PR-3) (#329)
- docs/changelog/0.1.0-beta.26.md: [Unreleased] moved under its heading, with the opening and how to
  update from beta.25 (nothing shown again - Disclaimer 2.11, Privacy Policy 2.12; schema 21; rules
  2026.10.4; recorded sessions read by the new rule); its row in CHANGELOG.md's Releases table.
- docs/HANDOFF.md: beta.25's START HERE moved verbatim to docs/handoff/history/0.1.0-beta.25.md (its row
  in the split table; D65 pointed there); beta.26's START HERE - why a release was needed, no new owner
  decision, what the ledger copy measured (Silent Hill 2's first fifteen seconds compiling shaders),
  the traps.
- The release lines: README, the accuracy block (legal/ACCURACY.md and its copies), LIMITATIONS.
- docs/13_CI_CD.md and HANDOFF item 20(e): the owner marked the last six SonarCloud issues the same day
  (S1244 x4 and S7631 false positives, S3869 accepted); main's analysis at 6b07eb2 has none open.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-19 23:41:34 +07:00
poli0981andClaude Opus 5.5 c14340e4f9 ci(sonar): SonarCloud's six open findings on main triaged; wiki.yml publishes only for a Release run of this repository (beta.26 PR-2) (#328)
- docs/13_CI_CD.md SonarCloud: the six left open after the owner's marking of the analysis of
  e35b971 (0.1.0-beta.25) - S3869 to accept as the table said, four S1244 false positives (exact
  comparisons on purpose: HSV's max, the scroll snap, a default scale), and S7631 fixed here - each
  with the comment to paste in the UI.
- .github/workflows/wiki.yml: the job also requires workflow_run.head_repository to be this
  repository; a fork could not start the Release run before either, and the condition now says so.
  13_CI_CD wiki.yml says so.
- HANDOFF item 20(e) annotated; CHANGELOG (developers only).
- PR-1's wording, now measured: the x1336 stretch is the session's first fifteen seconds - 1,369, 4,877
  and 1,303 presents with 1, 0 and 1 application frames, then a 13,348 ms frame - Silent Hill 2
  compiling its shaders at start (the owner), decoded from the ledger copy's frames.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-19 23:19:36 +07:00
poli0981andClaude Opus 5.5 6b07eb2dc8 fix: a frame-generation window is read only with eight application frames and a ratio up to x8 - the x1336.0 Silent Hill 2 state; the owner's runs of 2026-10-19 recorded (beta.26 PR-1) (#327)
The owner's Silent Hill 2 session (0.1.0-beta.25, NVIDIA App Dynamic multi frame generation) listed a
x1336.0 state (0.20 -> 267.20 FPS, 10 s) and the DLSS line cited it. Its two windows held one
application-frame token each against 1,336 presents: a window needed eight presents and one token.

- FgSlices.Slice.IsReadable: eight presents AND eight application frames; IsActive also caps the ratio
  at FgWindow.GenerationCeiling (x8 - no shipping technology generates more than x6). The mix and the
  steady state read the same windows.
- FgWindow refuses a ratio that held above x8 as BeyondGeneration ("beyond_generation"), after
  uniformity; its words in the capture host and the App (en/vi/ja).
- FgMixRecord.Parse reads a stored mix by today's rule: a stored state above x8 or under eight
  application frames a window joins the not-classified time. That session now reads x2.0, x3.0, x6.1,
  none and 30 s not classified; its DLSS line cites x6.1.
- Docs: 03_METRICS (the mix's amendment), 06_DATA_MODEL, LIMITATIONS, 05_DETECTION (the override's
  library names), spike-notes section 22 (the owner's runs: the Dynamic line confirmed, Lies of P read
  no FSR mode with the query hooked), HANDOFF items 20 and 21 annotated.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-19 22:36:57 +07:00
poli0981andClaude Opus 5.5 e35b971f27 release: 0.1.0-beta.25 - its changelog file, HANDOFF's beta.25 section with D65 built and owner-only item 21, the release lines (beta.25 PR-2) (#326)
- docs/changelog/0.1.0-beta.25.md: [Unreleased] moved under its heading, with the opening and how to
  update from beta.24 (nothing shown again - Disclaimer 2.11, Privacy Policy 2.12; schema 21; rules
  2026.10.4); its row in CHANGELOG.md's Releases table.
- docs/HANDOFF.md: beta.24's START HERE moved verbatim to docs/handoff/history/0.1.0-beta.24.md (its row
  in the split table; D62-D64, D66, D67 pointed there); beta.25's START HERE - D65 built, the rule the
  plan did not have (no FSR mode at a dynamic resolution), what was measured, the traps; owner-only
  item 21 (Lies of P), its decision table written before the run; D65's row in the decisions index.
- The release lines: README, the accuracy block (legal/ACCURACY.md and its copies), LIMITATIONS.
- docs/17_HOOK_ENGINE.md: the ffxDispatch row and the record layout no longer read FSR's quality byte as
  always 0xFF - #325 left both lines as they were.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-19 20:54:05 +07:00
604 changed files with 21011 additions and 2870 deletions

No files matched your search

+13
View File
@@ -0,0 +1,13 @@
{
"version": 1,
"isRoot": true,
"tools": {
"dotnet-sonarscanner": {
"version": "12.0.0",
"commands": [
"dotnet-sonarscanner"
],
"rollForward": false
}
}
}
+104
View File
@@ -59,6 +59,94 @@ dotnet_diagnostic.MA0011.severity = warning
# and GenerateDocumentationFile is on for the shipping ones.
dotnet_diagnostic.CS1591.severity = suggestion
# --- ReSharper inspections: what Qodana reads (docs/13_CI_CD.md §Qodana, D93) ---
# Qodana Community for .NET is ReSharper's InspectCode, and InspectCode reads these keys - so does Rider or ReSharper
# in the editor, which is why they are here and not in qodana.yaml: the same list everywhere. An inspection is off
# only where it argues with a choice this project made; each line says which. Everything else it reports is fixed.
[*.{cs,xaml}]
# The compiler's missing-XML-comment warning, already a suggestion above (CS1591): InspectCode reports suggestions.
resharper_c_sharp_warnings_cs1591_highlighting = none
# Naming is this file's rule and the .NET analyzers'. ReSharper's own scheme would rename product names and units
# (OpenGL -> OpenGl, XeSS -> XeSs, Presents5s -> Presents5S) and every Chart_* resource key.
resharper_inconsistent_naming_highlighting = none
# `x is long v` / `x is > 0 and int v` is how this code unwraps a nullable AND names its type; `{ } v` or `var v`
# hides it, against csharp_style_var_for_built_in_types above.
resharper_convert_type_check_pattern_to_null_check_highlighting = none
resharper_pattern_always_matches_highlighting = none
# A code-behind class names its base so that the type reads whole without the half XAML generates.
resharper_redundant_extends_list_entry_highlighting = none
# An argument that repeats a default says which value the call relies on.
resharper_redundant_argument_default_value_highlighting = none
# `partial void OnXChanged(T value)`: the signature is CommunityToolkit.Mvvm's generator's, used or not.
resharper_unused_parameter_in_partial_method_highlighting = none
# Exception messages and log lines are English by design (docs/09_I18N.md); what a user reads comes from .resx,
# and tools/resx-audit.ps1 gates that.
resharper_localizable_element_highlighting = none
# WPF UI's styles (DefaultImageStyle ...) arrive with ui:ControlsDictionary at run time, from a package's compiled
# resources the inspection does not read. A key that does not exist fails PagesLoadTests.
resharper_xaml_static_resource_not_resolved_highlighting = none
# Proposals, not findings - ReSharper's suggestions for a style this project did not take. Its style is this file,
# `dotnet format` and the analyzers the build treats as errors.
resharper_convert_to_primary_constructor_highlighting = none
resharper_merge_into_pattern_highlighting = none
resharper_merge_conditional_expression_highlighting = none
resharper_use_object_or_collection_initializer_highlighting = none
resharper_use_utf8_string_literal_highlighting = none
resharper_redundant_explicit_params_array_creation_highlighting = none
resharper_arrange_object_creation_when_type_evident_highlighting = none
resharper_convert_to_using_declaration_highlighting = none
resharper_convert_closure_to_method_group_highlighting = none
resharper_redundant_type_declaration_body_highlighting = none
resharper_replace_with_field_keyword_highlighting = none
resharper_replace_conditional_expression_with_null_coalescing_highlighting = none
resharper_append_to_collection_expression_highlighting = none
resharper_use_collection_expression_highlighting = none
resharper_use_with_expression_to_copy_struct_highlighting = none
resharper_convert_to_auto_property_highlighting = none
resharper_convert_to_static_class_highlighting = none
resharper_use_index_from_end_expression_highlighting = none
# A notice for code moving to C# 14, which this code was written in.
resharper_c_sharp14_overload_resolution_with_span_breaking_change_highlighting = none
# `await using` needs ConfigureAwait(false) on the disposable under CA2007, which reads worse than the `using` it
# replaces; the streams these name are closed synchronously on purpose.
resharper_use_await_using_highlighting = none
# A member's accessibility is what its type offers, not a count of today's callers.
resharper_member_can_be_private_global_highlighting = none
resharper_member_can_be_private_local_highlighting = none
resharper_property_can_be_made_init_only_global_highlighting = none
resharper_property_can_be_made_init_only_local_highlighting = none
resharper_auto_property_can_be_made_get_only_global_highlighting = none
resharper_auto_property_can_be_made_get_only_local_highlighting = none
# "Never used" across the solution is not what decides for a member other code can reach: an enum's values mirror
# the native layout and the stored columns, an exception type carries the constructors CA1032 asks for, a row or a
# message is read by Dapper and System.Text.Json, an interface states a contract. The private kind (.Local) stays on.
resharper_unused_member_global_highlighting = none
resharper_unused_type_global_highlighting = none
resharper_unused_auto_property_accessor_global_highlighting = none
resharper_unused_member_in_super_global_highlighting = none
resharper_unused_method_return_value_global_highlighting = none
resharper_unused_parameter_global_highlighting = none
resharper_class_never_instantiated_global_highlighting = none
resharper_event_never_subscribed_to_global_highlighting = none
# The compiler's nullable analysis is the gate (warnings are errors). These three go further and call a guard
# redundant because an annotation promises non-null - where a dependency property, a JSON document or a WPF event
# hands over null all the same.
resharper_null_coalescing_condition_is_always_not_null_according_to_api_contract_highlighting = none
resharper_conditional_access_qualifier_is_non_nullable_according_to_api_contract_highlighting = none
resharper_condition_is_always_true_or_false_according_to_nullable_api_contract_highlighting = none
# A record's positional property is part of its equality and of what it prints, read by name or not.
resharper_not_accessed_positional_property_global_highlighting = none
resharper_not_accessed_positional_property_local_highlighting = none
# Every one compares a value with the one it was copied from (max == r) or with an exact sentinel (scale == 1.0).
resharper_compare_of_floats_by_equality_operator_highlighting = none
# A nested record may name a property as the type that holds it names a helper; the compiler tells them apart.
resharper_member_hides_static_from_outer_class_highlighting = none
# `default: break;` is how a switch over a kind says that the rest is left alone on purpose.
resharper_redundant_empty_switch_section_highlighting = none
# A binding path through a null yields no value, and the template shows nothing: that is the design.
resharper_xaml_possible_null_reference_exception_highlighting = none
[src/FrameLedger.App/**.cs]
# WPF codegen constraints, not style choices. The generated App.g.cs and
# *.g.cs partials declare these types public, so making them internal is a
@@ -72,3 +160,19 @@ dotnet_diagnostic.MA0049.severity = none # type name matches containing names
[tests/**/*.cs]
dotnet_diagnostic.CA1707.severity = none # underscores in test method names
dotnet_diagnostic.CA2007.severity = none
# A test's assertion lambda runs inside the `using` scope it captures from - and reads a variable the test changes
# on purpose - and a test's `using var x = new T { ... }` leaks nothing a test process keeps.
resharper_access_to_disposed_closure_highlighting = none
resharper_access_to_modified_closure_highlighting = none
resharper_using_statement_resource_initialization_highlighting = none
# A test that dereferences a null fails, which is what it is for.
resharper_assign_null_to_not_null_attribute_highlighting = none
resharper_possible_null_reference_exception_highlighting = none
# A test double keeps the shape of what it stands for: an accessor nothing reads, a collection only filled, a result
# only some tests look at, a value an arrange step sets before the lambda that reads it runs.
resharper_unused_auto_property_accessor_local_highlighting = none
resharper_collection_never_queried_local_highlighting = none
resharper_collection_never_updated_local_highlighting = none
resharper_unused_method_return_value_local_highlighting = none
resharper_redundant_assignment_highlighting = none
resharper_return_type_can_be_not_nullable_highlighting = none
+100
View File
@@ -0,0 +1,100 @@
# ACCESSIBILITY.md (beta.35, D88) sends every accessibility barrier here. It is its own form rather than part of the bug
# report because a barrier needs different facts: what the reporter uses to read or operate the screen, and how far it
# stops them. Nothing here asks about the reporter themself.
name: Accessibility problem
description: Something in FrameLedger cannot be reached, read or seen — with the keyboard, a screen reader, a contrast theme, Magnifier or another aid
labels: [accessibility]
body:
- type: markdown
attributes:
value: |
Thank you for telling us. **You never need to tell us anything about yourself or a disability** — what you use
and what happened is enough. Screenshots and recordings help but are optional.
If FrameLedger refused to hook a game, stopped measuring or turned hooking off **without your knowing** — a
safety notice you could not perceive — say so below: it is a safety problem too, and it is handled first.
What FrameLedger aims for and what it cannot do yet: [ACCESSIBILITY.md](https://github.com/poli0981/frameledger/blob/main/ACCESSIBILITY.md).
- type: textarea
id: task
attributes:
label: What were you trying to do?
placeholder: 'e.g. switch hooking on for a game, read a session''s frame rate, answer the terms window'
validations:
required: true
- type: textarea
id: what-happened
attributes:
label: What happened instead?
description: What you heard, saw or could not do — and what you expected.
validations:
required: true
- type: textarea
id: steps
attributes:
label: How to get there
placeholder: |
1. Open Games (Ctrl+2)
2. Tab to …
3. …
- type: input
id: app-version
attributes:
label: FrameLedger version
description: Help ▸ About
validations:
required: true
- type: input
id: os
attributes:
label: Windows version
placeholder: 'Windows 11 26100.2314'
validations:
required: true
- type: dropdown
id: aid
attributes:
label: What do you use?
multiple: true
options:
- Keyboard only
- Narrator
- NVDA
- JAWS
- Windows Magnifier
- A Windows contrast theme
- Voice Access or other speech input
- Display scaling or a large text size
- Something else (say below)
validations:
required: true
- type: input
id: aid-version
attributes:
label: Its version, if you know it
placeholder: 'e.g. NVDA 2026.1'
- type: dropdown
id: severity
attributes:
label: How much does it stop you?
description: Optional — the maintainer sets it when reading the report (ACCESSIBILITY.md, How serious it is).
options:
- Not sure
- Critical — I cannot do the task at all
- Serious — only with great difficulty or a workaround
- Moderate — it is tiring or inconsistent
- Minor — it barely gets in the way
- type: textarea
id: more
attributes:
label: Anything else
description: A screenshot, a recording, or a diagnostic file from Help ▸ Report a bug (built on your PC; you choose what to attach).
+20
View File
@@ -1,5 +1,16 @@
# Central package management makes NuGet PRs single-file diffs
# (docs/12_BUILD.md, docs/13_CI_CD.md).
#
# The nuget entry also covers .config/dotnet-tools.json (the SonarScanner for
# .NET, since 2026-10-25). No dotnet-sdk entry, on purpose: global.json is a
# floor (11.0.100 since beta.37, D94) with rollForward latestFeature, so every
# machine and the CI runner already build with the newest 11.0 SDK they have;
# raising the floor is a decision, not an update (docs/12_BUILD.md).
#
# COOLDOWN (2026-10-25): a version update waits seven days after a release is
# published, so a release that is pulled or found compromised in its first
# week never reaches a pull request here. Security updates do not wait — the
# option does not apply to them.
version: 2
updates:
- package-ecosystem: nuget
@@ -7,6 +18,8 @@ updates:
schedule:
interval: weekly
open-pull-requests-limit: 5
cooldown:
default-days: 7
groups:
minor-and-patch:
update-types: [minor, patch]
@@ -21,7 +34,14 @@ updates:
- dependency-name: FluentAssertions
update-types: [version-update:semver-major]
# One pull request a week for the actions' minor and patch releases; a new
# major still comes alone, because it is the one that changes inputs.
- package-ecosystem: github-actions
directory: /
schedule:
interval: weekly
cooldown:
default-days: 7
groups:
actions-minor-and-patch:
update-types: [minor, patch]
+12
View File
@@ -30,6 +30,18 @@ review questions from `docs/19_SAFETY_AND_ANTICHEAT.md` §Review checklist.
**Measured overhead:** <!-- e.g. "0.31 µs/present, game Avg FPS delta -0.2%" -->
## User-interface changes only
Skip this section if the PR does not change what the App shows. Otherwise — `ACCESSIBILITY.md` §For contributors,
`docs/08_UI.md` §Accessibility:
- [ ] Every control that shows no text of its own has a name, from `.resx` in `en`, `vi` and `ja`
- [ ] Colours come from the theme only, and nothing is shown by colour alone
- [ ] Everything new can be reached and used with the keyboard, in reading order, and Esc leaves a new dialog
- [ ] `ACCESSIBILITY.md` (and `LIMITATIONS.md`) changed in this PR if what works or what does not moved
**Checked by hand:** <!-- e.g. "Tab through the new card with the mouse unplugged; Narrator reads its name and value" -->
## Safety-string changes only
- [ ] `Safety_*` resx keys have human-reviewed `ja` (never machine-drafted — `docs/09_I18N.md`)
+155 -10
View File
@@ -9,23 +9,29 @@
#
# So this workflow does exactly one thing of substance: ./build.ps1 check.
# Anything CI checks that local does not is a way for the two to disagree.
#
# Since 2026-10-25 (owner decision D68) a second job, `sonarcloud`, hands that
# run's coverage to SonarCloud and analyses the tree there. It is not the gate
# and not a required check: it builds again in a build of its own, and a
# SonarCloud outage or a failed quality gate is a red job beside a green
# `check`, never a blocked merge (docs/13_CI_CD.md §SonarCloud).
name: CI
on:
push:
branches: [main]
# `alpha` since 2026-10-31 (D73, docs/13_CI_CD.md §The alpha line): the same source on the .NET that line is
# trying, whose merges and syncs from main need the same gate under its own global.json.
branches: [main, alpha]
pull_request:
workflow_dispatch:
# Permissions do not inherit into reusable workflows, and defaults are broader
# than this job needs either way (docs/13_CI_CD.md).
permissions:
contents: read
# For the Changelog step below only: listing a pull request's changed files is
# the Pull Requests API, and an explicit `permissions:` block grants nothing it
# does not name. Read-only, and the job writes nothing back.
pull-requests: read
# than this job needs either way (docs/13_CI_CD.md). Since the second job
# (2026-10-25) they are granted per job and the workflow grants none: a grant at
# this level reaches every job, so `sonarcloud` would have held `check`'s
# pull-requests read for nothing (SonarCloud githubactions:S8264).
permissions: {}
concurrency:
group: ci-${{ github.ref }}
@@ -35,6 +41,12 @@ jobs:
check:
runs-on: windows-latest
timeout-minutes: 40
permissions:
contents: read
# For the Changelog step below only: listing a pull request's changed files is
# the Pull Requests API, and an explicit `permissions:` block grants nothing it
# does not name. Read-only, and the job writes nothing back.
pull-requests: read
steps:
- uses: actions/checkout@v7
@@ -166,8 +178,11 @@ jobs:
Write-Host ("vulkaninfo.exe on PATH: {0}" -f ($(if ($cmd) { $cmd.Source } else { 'no' })))
Write-Host ("HKLM:\SOFTWARE\Khronos\Vulkan\Drivers present: {0}" -f (Test-Path 'HKLM:\SOFTWARE\Khronos\Vulkan\Drivers'))
# Not for a pull request into `alpha` (D73): what the alpha line changes is written in its release's own file on
# main (docs/changelog/x.y.z-alpha.N.md), and an [Unreleased] entry on the alpha branch would collide with main's
# at every sync.
- name: Changelog
if: github.event_name == 'pull_request'
if: github.event_name == 'pull_request' && github.base_ref != 'alpha'
shell: pwsh
env:
GH_TOKEN: ${{ github.token }}
@@ -178,11 +193,141 @@ jobs:
if ($LASTEXITCODE -ne 0) { throw "could not list the pull request's changed files" }
./tools/changelog-check.ps1 -ChangedFiles @($files)
# Cobertura for a person reading it, OpenCover for the sonarcloud job below
# (build.ps1 writes both from the one test run since 2026-10-25).
- name: Upload coverage
if: always()
uses: actions/upload-artifact@v7
with:
name: coverage
path: '**/TestResults/**/coverage.cobertura.xml'
path: |
**/TestResults/**/coverage.cobertura.xml
**/TestResults/**/coverage.opencover.xml
if-no-files-found: warn
retention-days: 14
# SonarCloud, analysed from CI (owner decision D68, 2026-10-25; docs/13_CI_CD.md
# §SonarCloud). A job of its own, after `check`, for two reasons:
#
# - The scanner instruments the build it wraps and turns TreatWarningsAsErrors
# off in it (SonarQube.Integration.targets), so it cannot wrap the gate's
# build without weakening the gate. It gets a build of its own here.
# - It is advisory. `main`'s required contexts stay `check` and the two
# `analyze` jobs; a failed quality gate or a SonarCloud outage turns this job
# red and blocks nothing.
#
# It takes the gate's coverage (the `coverage` artifact) rather than running
# the tests a second time, and CMake's compilation database for the C++.
# Settings: SonarQube.Analysis.xml. The scanner: .config/dotnet-tools.json.
sonarcloud:
needs: check
# A pull request from this repository, or main. SONAR_TOKEN reaches neither a
# fork's pull request nor Dependabot's, and the scanner cannot start without
# it. Any other branch is refused by the organisation's plan - "Organization
# is not allowed to access data from non main branches", measured on a
# workflow_dispatch run of a feature branch, 2026-10-25 - so a dispatch on
# one runs `check` alone. The same plan is why a pull request INTO `alpha`
# (D73) and a push to it run `check` alone: SonarCloud analyses main's line.
if: >-
(github.event_name == 'pull_request' &&
github.base_ref != 'alpha' &&
github.event.pull_request.head.repo.full_name == github.repository &&
github.event.pull_request.user.login != 'dependabot[bot]') ||
(github.event_name != 'pull_request' && github.ref == 'refs/heads/main')
runs-on: windows-latest
timeout-minutes: 40
permissions:
contents: read
steps:
- uses: actions/checkout@v7
with:
# Blame for the new-code period, and the tags for the version.
fetch-depth: 0
- name: Set up .NET
uses: actions/setup-dotnet@v6
with:
global-json-file: global.json
# The analysis of the C++ runs the compiler of the compilation database.
- name: Set up MSVC (x64)
uses: ilammy/msvc-dev-cmd@0b201ec74fa43914dc39ae48a89fd1d8cb592756 # v1.13.0
with:
arch: x64
- name: Cache NuGet
uses: actions/cache@v6
with:
path: ~/.nuget/packages
key: nuget-${{ runner.os }}-${{ hashFiles('**/Directory.Packages.props', 'global.json') }}
restore-keys: nuget-${{ runner.os }}-
# The JRE the scanner provisions, and SonarCloud's analysers.
- name: Cache SonarCloud
uses: actions/cache@v6
with:
path: ~/.sonar/cache
key: sonar-${{ runner.os }}-${{ hashFiles('.config/dotnet-tools.json') }}
restore-keys: sonar-${{ runner.os }}-
# tests/<project>/TestResults/<guid>/coverage.opencover.xml, as `check` wrote
# them. Same workspace path on every hosted Windows runner, so the reports'
# absolute paths name these sources.
- name: Download the gate's coverage
uses: actions/download-artifact@v8
with:
name: coverage
# Configure only, plus the one header the build generates: the analysis
# reads the sources with the flags and defines CMake gives each one, and
# needs nothing built. FetchContent's sources land in build/, excluded.
#
# CMAKE_CXX_SCAN_FOR_MODULES=OFF: with C++20 and Ninja, CMake (3.28 on)
# scans every source for modules and gives each compile command an
# `@<object>.modmap` response file that only the BUILD writes, and the
# C/C++ analyser stops on a response file it cannot open ("unexpanded
# response file", the first run, 2026-10-25). Nothing here uses a module.
- name: Native compilation database
shell: pwsh
working-directory: src/native
run: |
cmake --preset x64-release -DCMAKE_EXPORT_COMPILE_COMMANDS=ON -DCMAKE_CXX_SCAN_FOR_MODULES=OFF
if ($LASTEXITCODE -ne 0) { throw 'cmake configure failed' }
cmake --build --preset x64-release --target fl_ac_floor_gen
if ($LASTEXITCODE -ne 0) { throw 'generating the blocklist floor failed' }
# The version is the newest release tag the commit descends from, so the
# project's new-code period ("previous version") is everything since the
# last release.
- name: Begin the analysis
shell: pwsh
env:
SONAR_TOKEN: ${{ secrets.SONAR_TOKEN }}
run: |
$ErrorActionPreference = 'Stop'
dotnet tool restore
if ($LASTEXITCODE -ne 0) { throw 'dotnet tool restore failed' }
$tag = git describe --tags --abbrev=0 --match 'v*' 2>$null
$version = if ($LASTEXITCODE -eq 0 -and $tag) { $tag.Substring(1) } else { (Get-Content VERSION -Raw).Trim() }
Write-Host "sonar.projectVersion: $version"
dotnet tool run dotnet-sonarscanner begin /k:poli0981_frameledger /o:poli0981 /v:$version `
/s:"$PWD\SonarQube.Analysis.xml" /d:sonar.token=$env:SONAR_TOKEN
if ($LASTEXITCODE -ne 0) { throw 'the scanner did not begin' }
# Platform: see build.ps1's Clear-VcxprojPlatform (the MSVC step exports
# Platform=x64, which MSBuild reads as a solution platform).
- name: Build for the analysis
shell: pwsh
run: |
Remove-Item Env:Platform -ErrorAction SilentlyContinue
dotnet build FrameLedger.slnx -c Release
if ($LASTEXITCODE -ne 0) { throw 'the analysis build failed' }
- name: End the analysis
shell: pwsh
env:
SONAR_TOKEN: ${{ secrets.SONAR_TOKEN }}
run: |
dotnet tool run dotnet-sonarscanner end /d:sonar.token=$env:SONAR_TOKEN
if ($LASTEXITCODE -ne 0) { throw 'the analysis failed, or its quality gate did' }
+22
View File
@@ -7,9 +7,20 @@
# Repo-local for now. The ops repo has codeql-mixed.yml, but C++ needs manual
# build mode driven by the CMake preset, and that input surface has not been
# verified. Switch to a caller stub once it has.
#
# AND the workflows themselves, since 2026-10-25: CodeQL's `actions` language
# reads .github/workflows for injection from event data, untrusted checkouts
# and over-broad tokens — the same class of finding SonarCloud raised once
# (githubactions:S7631, wiki.yml, beta.26). Its context, `analyze (actions,
# none)`, is not one of main's required checks.
name: CodeQL
# `workflow_dispatch` since 2026-11-11 (beta.37): on a pull request the C# analysis
# is an OVERLAY - it extracts the changed files on top of the database cached from
# `main` - so it cannot show what the extractor makes of the whole source, or of a
# construct it has not met (the move to .NET 11, a C# 15 feature). A dispatch on a
# branch is a full analysis of that branch (docs/13_CI_CD.md §C# 15 and the analyses).
on:
push:
branches: [main]
@@ -17,11 +28,20 @@ on:
branches: [main]
schedule:
- cron: '27 4 * * 1'
workflow_dispatch:
permissions:
contents: read
security-events: write
# A new push to a pull request replaces its run. A push to main and the weekly
# scan each get a group of their own (the run id), so none of them is ever
# cancelled or left pending behind another, and the default branch's alerts
# always come from a finished analysis.
concurrency:
group: codeql-${{ github.event_name == 'pull_request' && github.ref || github.run_id }}
cancel-in-progress: true
jobs:
analyze:
runs-on: windows-latest
@@ -35,6 +55,8 @@ jobs:
build-mode: none
- language: cpp
build-mode: manual
- language: actions
build-mode: none
steps:
- uses: actions/checkout@v7
+82
View File
@@ -0,0 +1,82 @@
# Qodana (owner decision D93, 2026-11-10; docs/13_CI_CD.md §Qodana).
#
# JetBrains' template for the Qodana Scan action, changed where FrameLedger differs
# and each change said here:
#
# - The linter is Qodana Community for .NET (qodana.yaml names it and says why): a
# Linux container, which is why this job alone runs on ubuntu-latest in a
# Windows-only project. EnableWindowsTargeting lets the .NET SDK there build and
# load projects whose target is Windows; it is passed to the container rather than
# written into Directory.Build.props, because no build of the product is meant to
# run anywhere but Windows.
# - The action is pinned to a commit (v2026.2.2, the newest; the template names
# v2026.1), as every action that is not GitHub's own is here.
# - Permissions are the ones the job uses: it reads the repository, writes a check
# run with the annotations and one comment on the pull request. The template's
# `contents: write` is for pushing quick-fixes, which this job never does.
# - A workflow of its own, as JetBrains advises, and ADVISORY: `main`'s required
# contexts stay `check` and the two `analyze` jobs. A problem Qodana finds, or a
# Qodana Cloud outage, is a red job beside a green `check`, never a blocked merge.
# - `main` only: the `alpha` branch is main's source under another release line
# (docs/13_CI_CD.md §The alpha line), and main's is what is analysed.
# - INTERIM since beta.37 (D94, 2026-11-11): main builds on .NET 11, which the
# linter's image does not carry (SDKs 8 to 10), so qodana.yaml's `bootstrap`
# installs the SDK global.json names into the container first. The Ultimate
# linter's pull request replaces this job with one on Windows.
name: Qodana
on:
workflow_dispatch:
pull_request:
branches: [main]
push:
branches: [main]
permissions: {}
concurrency:
group: qodana-${{ github.ref }}
cancel-in-progress: true
jobs:
qodana:
# A pull request from this repository, or a push or a dispatch. QODANA_TOKEN
# reaches neither a fork's pull request nor Dependabot's, and their token cannot
# write the check run or the comment.
if: >-
github.event_name != 'pull_request' ||
(github.event.pull_request.head.repo.full_name == github.repository &&
github.event.pull_request.user.login != 'dependabot[bot]')
runs-on: ubuntu-latest
timeout-minutes: 60
permissions:
contents: read
checks: write
pull-requests: write
steps:
- uses: actions/checkout@v7
with:
# The pull request's own commit, not its merge commit (empty on a push or
# a dispatch, which then check out the commit that started them).
ref: ${{ github.event.pull_request.head.sha }}
# A full history is required for pull request analysis.
fetch-depth: 0
# pr-mode false: the whole solution every time, so a pull request and `main`
# are judged by the same list. upload-result: the SARIF and the linter's log
# as an artifact of the run, for a reader with no Qodana Cloud account.
# Caches are saved from `main` only (a pull request reads them): one per
# branch would crowd the repository's cache quota, which NuGet's share.
- name: Qodana Scan
uses: JetBrains/qodana-action@3e8d76ff0e0241618abd808682f426afe84bab3f # v2026.2.2
with:
pr-mode: false
upload-result: true
cache-default-branch-only: true
env-vars-to-linter: EnableWindowsTargeting
env:
QODANA_TOKEN: ${{ secrets.QODANA_TOKEN }}
QODANA_ENDPOINT: 'https://qodana.cloud'
EnableWindowsTargeting: 'true'
+52 -16
View File
@@ -22,6 +22,13 @@
# -p:Version; the native blocks keep the numeric core (CMake's project() accepts
# nothing else).
#
# THE ALPHA LINE (2026-10-31, owner decisions D73-D76; 12_BUILD §The alpha line): the
# RELEASE_LINE file says `alpha` on the long-lived `alpha` branch, where the same source
# builds on the .NET the line is trying. Its tags are `vX.Y.Z-alpha.N` and nothing else, no other
# line may carry one, and its packages go to Velopack's `alpha` channel
# (releases.alpha.json) - which no beta reads, as no alpha reads releases.win.json
# (11_UPDATER §Channels). The version gate below enforces all three.
#
# A DRY RUN (2026-09-16, P5 prep): `workflow_dispatch` with a version runs every
# step below — the gate, the publish, the tree assertion, vpk, the checksums — and
# uploads the result as a workflow artifact, but creates no tag and no Release.
@@ -60,10 +67,15 @@ jobs:
steps:
- uses: actions/checkout@v7
# The SDK global.json names builds everything. The .NET 10 line beside it is for `vpk` (the Pack step): 1.2.161
# ships net8.0, net9.0 and net10.0 builds and none that rolls forward to another major, so on a machine with
# .NET 11 alone the tool would not start. The alphas were packed under an 11 SDK because the hosted image
# happened to carry a .NET 10 runtime; this states the dependency (2026-11-11, beta.37, D94).
- name: Set up .NET
uses: actions/setup-dotnet@v6
with:
global-json-file: global.json
dotnet-version: 10.0.x
- name: Set up MSVC (x64)
uses: ilammy/msvc-dev-cmd@0b201ec74fa43914dc39ae48a89fd1d8cb592756 # v1.13.0
@@ -101,6 +113,14 @@ jobs:
$pre = if ($m.Groups[2].Success) { 'true' } else { 'false' }
$file = (Get-Content VERSION -Raw).Trim()
if ($core -ne $file) { throw "tag $tag has numeric core $core but VERSION says $file — bump VERSION in the same commit as the changelog section, then tag" }
# D73: the release line this commit builds (Directory.Build.props refuses any other value too) and the tags it may
# carry - an alpha's on the alpha line only, and nothing else there.
$line = (Get-Content RELEASE_LINE -Raw).Trim()
if ($line -cnotin @('main', 'alpha')) { throw "RELEASE_LINE says '$line'; it must be main or alpha" }
$suffix = $m.Groups[2].Value
if ($line -eq 'alpha' -and $suffix -cnotmatch '^-alpha\.\d+$') { throw "this commit is on the alpha line (RELEASE_LINE); its tag must be vX.Y.Z-alpha.N, not $tag" }
if ($line -ne 'alpha' -and $suffix -match 'alpha') { throw "tag $tag names an alpha, but RELEASE_LINE says '$line': an alpha is tagged on the alpha branch, nowhere else" }
$channel = if ($line -eq 'alpha') { 'alpha' } else { 'win' }
New-Item -ItemType Directory -Force out | Out-Null
./tools/release-notes.ps1 -Version $full -OutFile out/notes.md
if ($LASTEXITCODE -ne 0) {
@@ -113,8 +133,9 @@ jobs:
}
"version=$full" >> $env:GITHUB_OUTPUT
"prerelease=$pre" >> $env:GITHUB_OUTPUT
"channel=$channel" >> $env:GITHUB_OUTPUT
"dry_run=$($dry.ToString().ToLowerInvariant())" >> $env:GITHUB_OUTPUT
Write-Host "$(if ($dry) { 'DRY RUN of' } else { 'releasing' }) $full (pre-release: $pre)"
Write-Host "$(if ($dry) { 'DRY RUN of' } else { 'releasing' }) $full (pre-release: $pre; line: $line; Velopack channel: $channel)"
# The Overlay's build id is `git describe --dirty` at CMake's configure
# (src/native/FrameLedger.Shm/CMakeLists.txt), and the next step edits tracked
@@ -244,38 +265,51 @@ jobs:
GH_TOKEN: ${{ github.token }}
run: |
$ErrorActionPreference = 'Stop'
dotnet tool install -g vpk --version 1.2.0
dotnet tool install -g vpk --version 1.2.161
if ($LASTEXITCODE -ne 0) { throw 'vpk install failed' }
$v = '${{ steps.version.outputs.version }}'
# D73: `win` (Velopack's default on Windows) for the main line, `alpha` for the alpha line - each release's feed
# and the previous release its delta is made from are its own line's. The main line's pack keeps its exact
# command (no --channel), so a beta is packed as every beta before the alpha line existed.
$channel = '${{ steps.version.outputs.channel }}'
New-Item -ItemType Directory out/release -Force | Out-Null
vpk download github --repoUrl "https://github.com/${{ github.repository }}" --channel win --pre --token $env:GH_TOKEN --outputDir out/release
vpk download github --repoUrl "https://github.com/${{ github.repository }}" --channel $channel --pre --token $env:GH_TOKEN --outputDir out/release
if ($LASTEXITCODE -ne 0) { Write-Host '::warning::the previous release could not be downloaded - this release carries a full package only' }
Write-Host 'previous release:'
Get-ChildItem out/release -File | ForEach-Object { Write-Host (" {0,-48} {1,12:N0}" -f $_.Name, $_.Length) }
vpk pack --packId FrameLedger.App --packVersion $v --packDir out/app --mainExe FrameLedger.exe --packTitle FrameLedger --packAuthors FrameLedger --releaseNotes out/notes.md --outputDir out/release
$pack = @('pack', '--packId', 'FrameLedger.App', '--packVersion', $v, '--packDir', 'out/app', '--mainExe', 'FrameLedger.exe', '--packTitle', 'FrameLedger', '--packAuthors', 'FrameLedger', '--releaseNotes', 'out/notes.md', '--outputDir', 'out/release')
if ($channel -ne 'win') { $pack += @('--channel', $channel) }
vpk @pack
if ($LASTEXITCODE -ne 0) { throw 'vpk pack failed' }
$built = @((Get-Content out/release/assets.win.json -Raw | ConvertFrom-Json) | ForEach-Object { $_.RelativeFileName })
if ($built.Count -eq 0) { throw 'vpk pack wrote no assets.win.json entries' }
$keep = $built + @('releases.win.json', 'assets.win.json', 'RELEASES')
$assets = "assets.$channel.json"
$index = "releases.$channel.json"
$legacyName = if ($channel -eq 'win') { 'RELEASES' } else { "RELEASES-$channel" }
$built = @((Get-Content "out/release/$assets" -Raw | ConvertFrom-Json) | ForEach-Object { $_.RelativeFileName })
if ($built.Count -eq 0) { throw "vpk pack wrote no $assets entries" }
$keep = $built + @($index, $assets, $legacyName)
New-Item -ItemType Directory out/previous -Force | Out-Null
Get-ChildItem out/release -File | Where-Object { $keep -notcontains $_.Name } | Move-Item -Destination out/previous
$feed = Get-Content out/release/releases.win.json -Raw | ConvertFrom-Json
$feed = Get-Content "out/release/$index" -Raw | ConvertFrom-Json
$feed.Assets = @($feed.Assets | Where-Object { $built -contains $_.FileName })
if ($feed.Assets.Count -eq 0) { throw 'the feed lists none of this build''s packages' }
[System.IO.File]::WriteAllText((Join-Path $PWD 'out/release/releases.win.json'), ($feed | ConvertTo-Json -Depth 8 -Compress), [System.Text.UTF8Encoding]::new($false))
if (Test-Path out/release/RELEASES) {
$legacy = @(Get-Content out/release/RELEASES | Where-Object { $built -contains ($_ -split ' ')[1] })
[System.IO.File]::WriteAllLines((Join-Path $PWD 'out/release/RELEASES'), [string[]]$legacy, [System.Text.UTF8Encoding]::new($false))
[System.IO.File]::WriteAllText((Join-Path $PWD "out/release/$index"), ($feed | ConvertTo-Json -Depth 8 -Compress), [System.Text.UTF8Encoding]::new($false))
if (Test-Path "out/release/$legacyName") {
$legacy = @(Get-Content "out/release/$legacyName" | Where-Object { $built -contains ($_ -split ' ')[1] })
[System.IO.File]::WriteAllLines((Join-Path $PWD "out/release/$legacyName"), [string[]]$legacy, [System.Text.UTF8Encoding]::new($false))
}
Write-Host 'this release:'
Get-ChildItem out/release | ForEach-Object { Write-Host (" {0,-48} {1,12:N0}" -f $_.Name, $_.Length) }
Write-Host ('feed: ' + (($feed.Assets | ForEach-Object { '{0} {1} {2}' -f $_.Type, $_.Version, $_.FileName }) -join '; '))
if (-not (Test-Path out/release/FrameLedger.App-win-Setup.exe)) { throw 'vpk did not produce FrameLedger.App-win-Setup.exe (README §Install names it)' }
$delta = "out/release/FrameLedger.App-$v-delta.nupkg"
$setup = "FrameLedger.App-$channel-Setup.exe"
if (-not (Test-Path "out/release/$setup")) { throw "vpk did not produce $setup (README §Install names the beta's, guide/11-alpha-builds.md the alpha's)" }
# The delta is the one this pack listed, not a name built here: Velopack puts a non-default channel in its packages'
# names (FrameLedger.App-<v>-alpha-full.nupkg - measured on the 0.1.0-alpha.1 rehearsal, 2026-10-31), so the name
# this step built for the default channel would have failed the second alpha.
$delta = @($built | Where-Object { $_ -like '*-delta.nupkg' })
if (Get-ChildItem out/previous -Filter '*-full.nupkg' -ErrorAction SilentlyContinue) {
if (-not (Test-Path $delta)) { throw "the previous full package was downloaded, but vpk produced no delta ($delta)" }
if ($delta.Count -ne 1) { throw "the previous full package was downloaded, but vpk produced no delta ($assets lists: $($built -join ', '))" }
} else {
Write-Host '::warning::no previous full package - this release carries no delta'
}
@@ -301,7 +335,9 @@ jobs:
run: |
$ErrorActionPreference = 'Stop'
$v = '${{ steps.version.outputs.version }}'
$ghArgs = @('release', 'create', $env:GITHUB_REF_NAME, '--title', "FrameLedger $v", '--notes-file', 'out/notes.md', '--verify-tag')
# An alpha says what it is in the list of releases too, not only in its notes (D74).
$title = if ('${{ steps.version.outputs.channel }}' -eq 'alpha') { "FrameLedger $v (experimental alpha)" } else { "FrameLedger $v" }
$ghArgs = @('release', 'create', $env:GITHUB_REF_NAME, '--title', $title, '--notes-file', 'out/notes.md', '--verify-tag')
if ('${{ steps.version.outputs.prerelease }}' -eq 'true') { $ghArgs += '--prerelease' }
$ghArgs += Get-ChildItem out/release -File | ForEach-Object { $_.FullName }
gh @ghArgs
+9 -3
View File
@@ -1,5 +1,5 @@
# The GitHub Wiki is a copy of the repository's own pages (D53/D54, the owner, 2026-10-07): wiki/ (Home, the sidebar,
# the developer pages) and guide/ (the user guide, which is the End-user part) with LIMITATIONS.md, assembled and checked
# the developer pages) and guide/ (the user guide, which is the End-user part) with LIMITATIONS.md and ACCESSIBILITY.md, assembled and checked
# by tools/wiki-build.ps1 - the check build.ps1 runs as `wiki-check`. A page edited on the Wiki tab is overwritten here;
# edit wiki/ or guide/ instead (docs/13_CI_CD.md §wiki.yml).
#
@@ -41,12 +41,18 @@ concurrency:
jobs:
wiki:
# A rehearsal of release.yml (workflow_dispatch) never publishes the wiki: only a run started by a pushed v* tag
# that succeeded.
# that succeeded - in THIS repository. A fork cannot start this repository's Release run (it runs on a tag push or by
# hand), so the head checked out below is always the owner's; the repository check says so in the condition rather
# than leaving it to release.yml's triggers (SonarCloud githubactions:S7631, beta.26).
# Nor does an alpha's release (D73, 2026-10-31): the wiki shows the newest beta, and an alpha's tag is on the `alpha`
# branch, whose guide is the beta's it was cut from - publishing it would only move the wiki's links off main's line.
if: >-
github.event_name == 'workflow_dispatch' ||
(github.event.workflow_run.conclusion == 'success' &&
github.event.workflow_run.event == 'push' &&
startsWith(github.event.workflow_run.head_branch, 'v'))
github.event.workflow_run.head_repository.full_name == github.repository &&
startsWith(github.event.workflow_run.head_branch, 'v') &&
!contains(github.event.workflow_run.head_branch, '-alpha.'))
runs-on: windows-latest
timeout-minutes: 10
env:
-22
View File
@@ -1,22 +0,0 @@
# SonarCloud Automatic Analysis — read from the default branch (docs/13_CI_CD.md §SonarCloud, decision D67).
# Automatic Analysis reads only this file: sonar.issue.ignore.* is not supported here, so the rules accepted by design
# are recorded in docs/13_CI_CD.md and marked by the owner in SonarCloud's own UI.
# What is not FrameLedger's code, or not code at all:
# - src/native/third_party: the vendored SDK headers (NVAPI, Streamline, FidelityFX, Vulkan-Headers) — 51 headers,
# 66 thousand lines, consumed unmodified (each folder's README says so and license-check holds it).
# - Strings.Designer.cs: generated by tools/resx-gen.ps1.
# - dxr_raygen_dxil.h: a compiled shader as a byte array, generated.
# - vendor-stubs: test fixtures that carry the vendors' export names and signatures on purpose.
# - tests/fixtures: the detection corpus (empty marker binaries and expected JSON).
# - legal/licenses, docs/vendor-exports.json: licence texts and a generated export list.
# - Migrations: SQLite scripts, which a SQL analyser reads as another dialect.
sonar.exclusions=src/native/third_party/**,**/Strings.Designer.cs,src/native/tools/hook-harness/dxr_raygen_dxil.h,src/native/tools/vendor-stubs/**,tests/fixtures/**,legal/licenses/**,docs/vendor-exports.json,src/FrameLedger.Infrastructure/Persistence/Migrations/**
# Tests repeat their arrange steps on purpose; duplication there is not a defect.
sonar.cpd.exclusions=tests/**,src/native/tests/**
# The native code is C++20 (src/native/CMakeLists.txt); report against it, not a later standard.
sonar.cfamily.reportingCppStandardOverride=c++20
sonar.sourceEncoding=UTF-8
+168
View File
@@ -0,0 +1,168 @@
# Accessibility
FrameLedger should be usable by everyone who plays games on a Windows PC — with a keyboard alone, with a screen reader,
with a Windows contrast theme or Magnifier, and without telling colours apart. This page says what FrameLedger aims
for, what works today, how that was checked, what does not work yet and what to do instead, and how to tell us about a
barrier. It is written for the person who has just met one; the details for developers are in
[`docs/08_UI.md`](docs/08_UI.md#accessibility).
FrameLedger is a desktop program: its own window, its dialogs, its document windows, the icon by the clock and the
notices Windows shows for it. It draws nothing inside a game, so it cannot make a game itself any easier to use.
*Beta software: this page describes version 0.1.0-beta.37. In the app: Help ▸ Accessibility.*
## What FrameLedger aims for
- **WCAG 2.2 at level AA**, applied to desktop software as W3C's
[WCAG2ICT](https://www.w3.org/TR/wcag2ict-22/) guidance explains. This is a goal that guides the work, not a claim:
no formal evaluation has been made, and FrameLedger does not say it conforms to any standard.
- **Every task can be done with the keyboard alone.**
- **A screen reader can read every control and every value**, in the language FrameLedger is shown in, and hears what
changes — a notice, a result.
- **Text and controls keep their contrast** in the light and the dark theme and under Windows contrast themes, and
**colour is never the only way something is shown.**
- **Everything stays sharp at any display scale**, and when the window moves between screens.
## What works today
### The keyboard
| Keys | What they do |
|---|---|
| **Ctrl+1** … **Ctrl+5** (also with the numeric keypad) | Open Dashboard, Games, Compare, Logs and Settings, and move the keyboard into that page; a screen reader hears its title. |
| **Alt** or **F10**, then the arrow keys and **Enter** | Move to the menus. **Alt** with a menu's underlined letter opens it (*File*, *Tools*, *Help* in English). |
| **Tab** and **Shift+Tab** | Move through a page or a dialog in reading order. |
| The **arrow keys**, **Home**, **End**, **Page Up**, **Page Down** | Move inside a list or a table — a game's sessions, the games list, the Compare list, the import checklist. |
| **Enter** or **Space** | Press the button, switch or box that has the focus. **Enter** on a game in the list opens its page. |
| **Esc** | Closes a dialog the way its **Close** or **Cancel** button does: nothing is changed. A dialog that has no Close button waits for an answer, and the terms window has its own **Decline** and **Accept**. |
| **Enter** in the hooking warning | Switches hooking on once the phrase is typed exactly; before that it does nothing. |
| On a chart: the **arrow keys**, **Ctrl** with an arrow, **A** | Tab reaches every chart. The arrows move its view, Ctrl with an arrow zooms, A shows all of it again (so does a double-click); the page around it stays put. |
The same keys are in the user guide, [The screens](guide/07-screens.md#keyboard-and-mouse).
### Screen readers
- **Every page, menu, dialog and setting can be reached and used with Narrator.** The owner checked this on
2026-11-09, keyboard only with the mouse disconnected, on 0.1.0-beta.34 and 0.1.0-alpha.3, and found no fault.
- **Every page has headings**: its title is a heading of the first level, each section one of the second, so a screen
reader's heading keys move from section to section.
- **Every chart says what it is and where its numbers are written as text**, and which keys move it.
- **Every button, switch and box that shows no text of its own has a name**, from the same translations as the screen.
- **Lists, drop-down options and table cells are read by the words they show**, and a button repeated on each row names
its row — *Open: 11/9/2026 14:03*, *Play: Cyberpunk 2077*, *Turn off: Cyberpunk 2077*.
- **The frame-rate readout says the game's own frames, the displayed frames and the frame-generation factor together**
(*Native 62 FPS, displayed 118 FPS, frame generation ×1.9*) — never the larger number alone; a ray-tracing chip says its
value and where it came from (*Ray Tracing: Yes, measured*).
- **What appears is said as it appears**: a safety notice (hooking refused, measuring stopped, hooking turned off), the
capture agent going away and coming back, an update's steps, a short message at the bottom of the window, a notice on a
game's page and a result of **Tools ▸ Database maintenance** — in the words shown, while FrameLedger's window is the
active one. While a game has the screen nothing interrupts it; the notice stays in the window, and Windows' own
notifications from the icon by the clock are read by the screen reader itself.
- **The notices above the page can be read where they are shown**, and the button that answers one says which notice it
answers.
- **Tab goes from control to control**: pictures, lists and the rows of Settings are not stops of their own.
- **Dialogs say they are dialogs**, keep the focus inside them until they close, and then give it back to the control
that opened them. A message box opens over FrameLedger's window, never behind it.
### Seeing the screen
- **Light, dark, or the same as Windows** (Settings ▸ Theme). FrameLedger takes every colour from the theme, and every
text is measured against what is painted under it, in both themes.
- **Windows contrast themes** (Settings ▸ Accessibility ▸ Contrast themes) — Aquatic, Desert, Dusk, Night sky, or one
whose colours you changed: every colour in the window becomes one of the theme's, whatever Settings ▸ Theme says, as
soon as you turn one on, edit it or turn it off. The charts draw in its colours too, their lines and marks still told
apart by pattern, and Settings ▸ Theme says a contrast theme is in use.
- **The colour a game's picture lends its page** is used only as far as every text on it still reads, and never under a
contrast theme.
- **Windows display scaling** at any size, on every screen; **Magnifier** (Windows logo key + Plus) works as with any
program.
- Labels such as *Hooking on* and *Not installed*, and the ray-tracing chips, always carry their words; a chip that reads
*N/A* is also drawn with a dashed edge.
- **No chart tells two series apart by colour alone**: its lines are solid, dashed or dotted, its points circles,
triangles or squares, its shaded stretches striped or dotted.
### Languages
FrameLedger is shown in English, Vietnamese or Japanese (Settings ▸ Language), and the names a screen reader reads come
from the same translations. The documents — the user guide, this page, the legal texts — are in English.
## How it is checked
- **On every build**, by the project's own tests: what a screen reader is given for every page, window and dialog —
every place Tab stops has a name, no list or table item is read by its program name, no text is hidden from a screen
reader inside a control, no two buttons in a list share a name; each thing that appears is said once, in its words;
every page has one first-level heading and every section title a level; no chart tells two series apart by colour
alone; a chart's keys move it and stay its own; every control that shows no text has a name; no colour is written
into a screen; every text reads against its background in both themes and after a theme switch, and under Windows'
four contrast themes and two edited ones is drawn in the theme's own colours at 4.5:1 or better; **Esc** closes the
open dialog without an answer, and a dialog gives the focus back; **Ctrl+1** … **Ctrl+5** open the pages in their
order and move the keyboard into them; a page slides in only while Windows' animation effects are on; the program
declares it follows each screen's scaling.
- **By hand**: the owner's pass of 2026-11-09 above, repeated for each release that changes a screen.
- **Not tested yet**: NVDA, JAWS, Voice Access, touch, Windows 10, and other people's PCs. They should work through the
same Windows interface Narrator uses, but nobody has checked. Contrast themes are checked by the tests above and have
not yet been looked at on a screen.
## Known limitations
Each one with what to do instead. A barrier that is not on this list is worth reporting.
- **A chart's points cannot be read one by one.** A screen reader hears the chart's name and where its numbers are:
a session's figures and *Statistics per series* in its summary, the table under the Compare chart, the Sessions table
and the list of changes under a trend chart, and **File ▸ Export ▸ Session CSV** or **Session JSON**.
- **In the user guide and the other documents the app shows, headings are read as ordinary text**: Windows' document
view gives them no heading role. Their links and their order work as on any page.
- **The short messages at the bottom of the window close after four seconds**, and cannot be read again once closed. A
screen reader is told each one as it appears.
- **Windows' text size setting** (Settings ▸ Accessibility ▸ Text size) **is not followed.** Use display scaling
(Settings ▸ System ▸ Display ▸ Scale) or Magnifier.
- **Pausing capture is only in the menu of the icon by the clock.**
- **The windows Windows itself shows** — choosing a file, the administrator prompt — are Windows', not FrameLedger's.
## Report an accessibility problem
1. Open an issue with the
[Accessibility problem form](https://github.com/poli0981/frameledger/issues/new?template=accessibility.yml).
2. Say what you were trying to do and what happened instead; your FrameLedger version (Help ▸ About) and your Windows
version; and what you use — the keyboard alone, Narrator, NVDA, JAWS, Magnifier, a contrast theme — with its version.
The steps to get there help, and so does a screenshot or a recording, but neither is required. **You never need to
tell us anything about yourself or a disability.**
3. If you want to attach details from your PC, **Help ▸ Report a bug** builds them into a file on your PC and shows you
what is inside first; nothing is uploaded by itself.
**A safety notice you could not perceive** — hooking refused, measuring stopped or hooking turned off, without your
knowing — is a safety problem as well: say so in the report, and it is handled first.
### How serious it is
You do not have to choose; the maintainer sets it when reading the report.
| Severity | What it means | For example |
|---|---|---|
| **Critical** | A task cannot be done at all. | Hooking cannot be switched off with the keyboard; the terms window or the hooking warning cannot be answered; a safety notice cannot be read. |
| **Serious** | It can be done only with great difficulty or a workaround. | A value can be read only by exporting the session. |
| **Moderate** | It is tiring or inconsistent. | A name that differs from what the screen shows; an extra stop for Tab. |
| **Minor** | It barely gets in the way. | A tooltip the keyboard cannot reach, when its words are shown elsewhere too. |
### What happens next
FrameLedger has one maintainer, so there are no promised times. Every report is read and answered, without doubting what
you describe. Critical problems come before other work; a workaround, when there is one, is written on the issue; the
fix ships in a release, and the issue is closed once you say it works for you — or when a fix has been out for a while
and nobody has answered.
## Who looks after this
The project's owner, poli0981, keeps this page and the checks behind it, and reviews both for each release that changes
a screen. A change to FrameLedger that moves anything on this page changes the page in the same pull request.
## For contributors
A change to the App keeps what the tests above hold: a name, from the translations in all three languages, for every
control that shows no text; colours only from the theme. Say in the pull request what you checked with the keyboard
and with Narrator. The rules and the checks are in [`docs/08_UI.md`](docs/08_UI.md#accessibility) and
[`CONTRIBUTING.md`](CONTRIBUTING.md).
## Feedback
To improve this page, open an issue or a pull request. A barrier goes through the form above, so that it is not lost.
+17 -16
View File
@@ -35,28 +35,29 @@ numeric core and does not move; the heading is the full version — corrected 20
## [Unreleased]
### Added
- **FSR's quality mode** (owner decision D65, planned for beta.24 and moved to this release). For a game that runs FSR
through AMD's FidelityFX libraries, the summary, the Sessions tab, the game page and the live card name the mode —
*FSR 3 Quality*, *FSR Performance*, *FSR Native AA* — when the game asked AMD's library what render size that mode
gives and then rendered at that size. A game at a dynamic resolution, one that sizes its frames without asking, and
one FrameLedger joined after it asked show none. FrameLedger reads one more call in those libraries (`ffxQuery`,
beside the `ffxDispatch` it already reads): the size or ratio AMD's library answered, nothing else — about 8 ns per
upscaled frame. The CSV export's `# quality_mode:` carries it (`native_aa (game)` for Native AA).
`legal/ACCURACY.md`'s *Quality mode* bullet gains its FSR clause, in the words approved with the beta.24 plan; the
Disclaimer stays 2.11, as it did for the accuracy statement's additions in beta.19 and beta.20. Checked with AMD's
interface on the test program; a real game is owner-only item 21. Developers: the hook has its own family bit
(`FL_HOOK_UPSCALER_QUALITY`, bit 11 of `hooksInstalledMask`), the byte is `0x10 + FfxApiUpscaleQualityMode`, the
harness asks with `--ffx-query sizes|ratios`, and `Domain.Metrics.QualityByte` is the one rule a session, its
segments and the live card read.
## Releases
Newest first. Each file holds that release's section exactly as it stood here.
| Version | Date | Notes |
|---|---|---|
| `0.1.0-alpha.4` | 2026-11-11 | [`docs/changelog/0.1.0-alpha.4.md`](docs/changelog/0.1.0-alpha.4.md) |
| `0.1.0-beta.37` | 2026-11-11 | [`docs/changelog/0.1.0-beta.37.md`](docs/changelog/0.1.0-beta.37.md) |
| `0.1.0-beta.36` | 2026-11-10 | [`docs/changelog/0.1.0-beta.36.md`](docs/changelog/0.1.0-beta.36.md) |
| `0.1.0-beta.35` | 2026-11-09 | [`docs/changelog/0.1.0-beta.35.md`](docs/changelog/0.1.0-beta.35.md) |
| `0.1.0-alpha.3` | 2026-11-06 | [`docs/changelog/0.1.0-alpha.3.md`](docs/changelog/0.1.0-alpha.3.md) |
| `0.1.0-beta.34` | 2026-11-06 | [`docs/changelog/0.1.0-beta.34.md`](docs/changelog/0.1.0-beta.34.md) |
| `0.1.0-alpha.2` | 2026-11-03 | [`docs/changelog/0.1.0-alpha.2.md`](docs/changelog/0.1.0-alpha.2.md) |
| `0.1.0-beta.33` | 2026-11-03 | [`docs/changelog/0.1.0-beta.33.md`](docs/changelog/0.1.0-beta.33.md) |
| `0.1.0-alpha.1` | 2026-10-31 | [`docs/changelog/0.1.0-alpha.1.md`](docs/changelog/0.1.0-alpha.1.md) |
| `0.1.0-beta.32` | 2026-10-31 | [`docs/changelog/0.1.0-beta.32.md`](docs/changelog/0.1.0-beta.32.md) |
| `0.1.0-beta.31` | 2026-10-26 | [`docs/changelog/0.1.0-beta.31.md`](docs/changelog/0.1.0-beta.31.md) |
| `0.1.0-beta.30` | 2026-10-26 | [`docs/changelog/0.1.0-beta.30.md`](docs/changelog/0.1.0-beta.30.md) |
| `0.1.0-beta.29` | 2026-10-25 | [`docs/changelog/0.1.0-beta.29.md`](docs/changelog/0.1.0-beta.29.md) |
| `0.1.0-beta.28` | 2026-10-20 | [`docs/changelog/0.1.0-beta.28.md`](docs/changelog/0.1.0-beta.28.md) |
| `0.1.0-beta.27` | 2026-10-20 | [`docs/changelog/0.1.0-beta.27.md`](docs/changelog/0.1.0-beta.27.md) |
| `0.1.0-beta.26` | 2026-10-19 | [`docs/changelog/0.1.0-beta.26.md`](docs/changelog/0.1.0-beta.26.md) |
| `0.1.0-beta.25` | 2026-10-19 | [`docs/changelog/0.1.0-beta.25.md`](docs/changelog/0.1.0-beta.25.md) |
| `0.1.0-beta.24` | 2026-10-19 | [`docs/changelog/0.1.0-beta.24.md`](docs/changelog/0.1.0-beta.24.md) |
| `0.1.0-beta.23` | 2026-10-14 | [`docs/changelog/0.1.0-beta.23.md`](docs/changelog/0.1.0-beta.23.md) |
| `0.1.0-beta.22` | 2026-10-13 | [`docs/changelog/0.1.0-beta.22.md`](docs/changelog/0.1.0-beta.22.md) |
+18 -6
View File
@@ -42,14 +42,14 @@ A C++ DLL (`FrameLedger.Overlay.dll`) is injected into games the user explicitly
| Concern | Choice |
|---|---|
| Managed runtime | .NET 10 (LTS, pinned via `global.json`), C# 14, TFM `net10.0-windows10.0.22621.0` with `SupportedOSPlatformVersion=10.0.19045.0` (Win10 22H2 floor, NFR-8), x64 only — `docs/12_BUILD.md` |
| Managed runtime | .NET 11 (STS, pinned via `global.json`: the 11.0 SDK band) and C# 15 since 0.1.0-beta.37 (owner decisions D94 and D96, 2026-11-11; .NET 10 and C# 14 until beta.36), TFM `net11.0-windows10.0.22621.0` with `SupportedOSPlatformVersion=10.0.19045.0` (NFR-8 as D95 amended it: Windows 11 is the supported platform; Windows 10 22H2 is not blocked, and is neither tested nor supported), x64 only — `docs/12_BUILD.md` §The main line's .NET. No preview feature (`runtime-async`, the updated memory-safety rules). **No C# 15 construct is used yet** — collection expression arguments, `closed`, `union`, labeled jumps: a construct is used only where the build, CodeQL and Qodana all read it, and Qodana's engine reads none of the four (`docs/13_CI_CD.md` §C# 15 and the analyses). .NET 11's API is used freely. **The `alpha` branch** (D73–D76, 2026-10-31) builds a released beta's source to try a newer .NET; it rests since 0.1.0-alpha.4 (D98) and then differs from main in `RELEASE_LINE` alone — `docs/12_BUILD.md` §The alpha line |
| Native | **C++20, MSVC v143+, `/MT` static CRT, `/GS`, `/guard:cf`, no RTTI, no C++ exceptions in hook paths** |
| Hooking | **MinHook** (BSD-2-Clause) for inline hooks; direct vtable-entry swap for COM interfaces |
| Vulkan | **Implicit Vulkan layer** (`VK_LAYER_FRAMELEDGER_overlay`), not hooking — `17_HOOK_ENGINE` §Vulkan |
| UI | WPF + WPF UI (`WPF-UI` pinned = 4.3.0) + CommunityToolkit.Mvvm — `docs/16_WPFUI_SYNTAX.md` |
| App composition | .NET Generic Host + DI in `FrameLedger.App` |
| Charts | ScottPlot 5 |
| Markdown in the App | **Markdig** (BSD-2-Clause, pinned 1.4.0) → WPF `FlowDocument`, HTML off, no image fetched — the Legal Gate, the user guide, Help ▸ Limitations, the update notes, About (beta.12; row added 2026-10-04) |
| Markdown in the App | **Markdig** (BSD-2-Clause, pinned ~~1.4.0~~ 1.5.0 since beta.31 — 1.4.2 in beta.30) → WPF `FlowDocument`, HTML off, no image fetched — the Legal Gate, the user guide, Help ▸ Limitations, Help ▸ Accessibility (beta.35, D88), the update notes, About (beta.12; row added 2026-10-04) |
| GPU telemetry | **The game process's own memory since beta.12 (D43):** `FrameLedger.ProcessStats.dll` (C++, loaded by the Agent, never into a game) reads its dedicated/shared GPU memory from the `GPU Process Memory` counters and its working sets from `GetProcessMemoryInfo` — `18_GPU_VENDOR_APIS` §The game process's memory. Layered: DXGI + PDH counters (all vendors) → LibreHardwareMonitorLib (MPL-2.0, all vendors) → **NVAPI (MIT, headers + `amd64/nvapi64.lib` vendored 2026-08-05** at `src/native/third_party/nvapi/`, consumed via the `fl_nvapi` target; NVIDIA extras + Reflex). **No AMD/Intel vendor SDK** — `docs/18_GPU_VENDOR_APIS.md`. ~~**No telemetry source exists in code yet**~~ **`LhmTelemetrySource` (L2) exists since 2026-09-03 (`20_OPEN_QUESTIONS` §M5 row R1, eight GPU fields unelevated); L1 (`BaselineTelemetrySource`: DXGI identity + the PDH adapter-memory counter, the first CsWin32 consumer), `CompositeTelemetrySource` and the 1 Hz `TelemetryPoller` since 2026-09-09; L3 (`NvapiTelemetrySource` over the native `FrameLedger.NvapiBridge.dll` — the only shipped binary linking `nvapi64.lib`, loaded by the Agent into its own process and never into a game) since 2026-09-10 (PR-E2)** — `ctest fl_nvapi_probe` was the only NVAPI consumer until then, and it exists so the vendoring is verified rather than asserted. This row said no source existed for six days after one did, recorded 2026-09-09 rather than repaired quietly. This row previously claimed the vendoring in the present tense while `third_party/` held only `vulkan-headers`; `legal/` had already caught the identical claim about itself and gained a bidirectional gate, which is what made the real vendoring a red-then-green |
| CPU/board sensors | LibreHardwareMonitorLib ≥ 0.9.6 (PawnIO) — **optional**, elevated only |
| Tier-2 fallback | **There is none, and Tier 2 is not a measurement.** Owner decision 2026-08-28: the ladder is two rungs — hooked, or duration + sensors + the reason. ~~ETW-based, no injection~~; ~~Intel PresentMon console binary~~ dropped 2026-08-27 after §S31 retired it. Whether a shipped build ever regains a no-injection measurement is `docs/20_OPEN_QUESTIONS.md` §G |
@@ -67,8 +67,15 @@ A C++ DLL (`FrameLedger.Overlay.dll`) is injected into games the user explicitly
FrameLedger.slnx # XML solution format (SDK default since .NET 10)
NOTICE # copyright + the GPLv3 section 7 additional terms (beta.12, D45)
CONTRIBUTING.md FORKING.md CODE_OF_CONDUCT.md # for people who build, contribute or redistribute
LIMITATIONS.md ACCESSIBILITY.md # what the software cannot do; the accessibility statement (D36, D88)
global.json # pins the SDK band — see 12_BUILD
RELEASE_LINE # `main`, or `alpha` on the alpha branch (D73, 2026-10-31) — 12_BUILD §The alpha line
build.ps1 # the quality gate; CI runs this identical script
SonarQube.Analysis.xml # SonarCloud's settings for ci.yml's sonarcloud job (D68, 2026-10-25; it replaced
.config/dotnet-tools.json # .sonarcloud.properties) and the scanner it runs — 13_CI_CD §SonarCloud
qodana.yaml # Qodana's settings for .github/workflows/qodana.yml (D93, 2026-11-10): the linter, the
# solution, a gate of zero problems; the inspections' severities are .editorconfig's
# resharper_* keys — 13_CI_CD §Qodana
src/
native/
FrameLedger.Overlay/ # C++20 DLL injected into the game (hooks + ring writer + optional overlay)
@@ -162,7 +169,7 @@ guide/ # the user guide (beta.12, D44): ~~eight~~ short
# (twelve since beta.17, D54: the screens, every setting, troubleshooting, a glossary;
# and the guide is the wiki's End-user part)
wiki/ # the wiki's own pages (beta.17, D53): Home, _Sidebar, the developer pages. wiki.yml
# publishes them with guide/ and LIMITATIONS.md to the Wiki tab at a release;
# publishes them with guide/, LIMITATIONS.md and ACCESSIBILITY.md to the Wiki tab at a release;
# tools/wiki-build.ps1 assembles and checks them (build.ps1 wiki-check)
docs/ legal/ legal/licenses/
```
@@ -171,9 +178,9 @@ Dependency direction: `App/Agent → Application → Domain`; **`Application →
## Coding conventions
**C# —** `Nullable enable`, `TreatWarningsAsErrors`, `AnalysisLevel latest-all`, file-scoped namespaces, Roslynator + Meziantou + VS Threading analyzers, `dotnet format` clean. Async suffixed `Async`, `ConfigureAwait(false)` off the UI. All user-visible strings from `.resx`. Timestamps UTC (unix-ms in SQLite); QPC ticks only inside the capture pipeline.
**C# —** `Nullable enable`, `TreatWarningsAsErrors`, `AnalysisLevel latest-all`, file-scoped namespaces, Roslynator + Meziantou + VS Threading analyzers, `dotnet format` clean. Qodana Community for .NET (ReSharper's inspections) reads the C# and the XAML in an advisory workflow of its own, with a gate of zero problems *(since 2026-11-10, D93 — `13_CI_CD` §Qodana)*: fix what it reports, or switch the inspection off in `.editorconfig` with the reason beside it — never in `qodana.yaml`, never without one. Async suffixed `Async`, `ConfigureAwait(false)` off the UI. All user-visible strings from `.resx`. Timestamps UTC (unix-ms in SQLite); QPC ticks only inside the capture pipeline.
**C++ —** `clang-format` (LLVM base, 4-space, 120 col) enforced in CI. No STL containers that allocate in hook paths. No `std::mutex` in hook paths. `-D_HAS_EXCEPTIONS=0` in the Overlay target. Every hook entry point wrapped per the `FL_HOOK_GUARD` macro (`17_HOOK_ENGINE`). Static analysis: ~~`/analyze` + clang-tidy (`bugprone-*`, `cert-*`, `concurrency-*`)~~ CodeQL (`codeql.yml`, a required check); `/analyze` and clang-tidy are not configured *(corrected 2026-10-04)*.
**C++ —** `clang-format` (LLVM base, 4-space, 120 col) enforced in CI. No STL containers that allocate in hook paths. No `std::mutex` in hook paths. `-D_HAS_EXCEPTIONS=0` in the Overlay target. Every hook entry point wrapped per the `FL_HOOK_GUARD` macro (`17_HOOK_ENGINE`). Static analysis: ~~`/analyze` + clang-tidy (`bugprone-*`, `cert-*`, `concurrency-*`)~~ CodeQL (`codeql.yml`, a required check); `/analyze` and clang-tidy are not configured *(corrected 2026-10-04)*. SonarCloud analyses the C++ too, from CMake's compilation database, in `ci.yml`'s advisory `sonarcloud` job *(since 2026-10-25, D68 — `13_CI_CD` §SonarCloud)*.
**Licence header —** every first-party source file (`.cs .cpp .h .inl .ps1 .xaml`) opens with two comment lines, `SPDX-License-Identifier: GPL-3.0-only` and `Copyright (C) 2026 poli0981 - additional terms under GPLv3 section 7: see NOTICE` (beta.12, owner decision D45). GPLv3 §7 requires additional terms to be named in the source files, and `NOTICE` holds them — (b) preserve the notices, (c) mark modified versions, (e) no trademark rights in the name. `tools/notice-check.ps1` is a `build.ps1` gate; `-Fix` writes a missing header. `src/native/third_party/` is excluded.
@@ -193,6 +200,8 @@ The version handshake is wired end to end as of 2026-08-05: `FlGuardBuildId` giv
- Hook-path changes state measured overhead in the PR body (`14_TESTING` §Hook overhead).
- Any new hook is listed in `17_HOOK_ENGINE` §Hook inventory and justified against rule 4.
- New user-visible strings exist in `en`, `vi`, `ja`.
- A change to what the App shows keeps `ACCESSIBILITY.md` §For contributors (names, theme colours, nothing by colour alone,
keyboard reach) and updates that page when it moves what works or what does not (D88).
- Any deviation from a doc updates that doc in the same PR.
## Reading order
@@ -216,7 +225,10 @@ The version handshake is wired end to end as of 2026-08-05: `FlGuardBuildId` giv
10. Remaining (`09`–`15`).
11. **`LIMITATIONS.md`** (repository root; shown in the App under Help ▸ Limitations) — what the WHOLE software cannot
do, in the user's words, each item linked to its details. When a change moves a limit, the page changes in the same
PR (D36, 2026-09-27). **`docs/LIST_GAME_TESTED.md`** — the real games FrameLedger has been run with and what each
PR (D36, 2026-09-27). **`ACCESSIBILITY.md`** (repository root; Help ▸ Accessibility) — the accessibility statement:
WCAG 2.2 AA through WCAG2ICT as a goal, never a claim; what works with the keyboard, a screen reader and contrast
themes, what does not, how a barrier is reported (D88, 2026-11-09); `docs/08_UI.md` §Accessibility holds its checks.
**`docs/LIST_GAME_TESTED.md`** — the real games FrameLedger has been run with and what each
session measured, from a copy of the owner's ledger and the repository's own evidence (D35).
**Before writing native or capture code, read `docs/20_OPEN_QUESTIONS.md`** (its open entries; since beta.24 the
+10 -3
View File
@@ -11,12 +11,15 @@ merged, and under what licence your contribution is accepted.
- **Open an issue before anything larger than a fix**, so the approach can be agreed before the work is done.
- **A game with anti-cheat that FrameLedger fails to detect** is a safety bug: use the *Safety gap* issue form.
- **A vulnerability in FrameLedger itself** goes the private route in `SECURITY.md`, never a public issue.
- **Something that cannot be reached, read or seen** — with the keyboard, a screen reader, a contrast theme — uses the
*Accessibility problem* form; `ACCESSIBILITY.md` says what the App aims for.
- Everyone who takes part follows the `CODE_OF_CONDUCT.md`.
## Building
You need Windows 10 22H2 or later (x64), Visual Studio 2022 with the C++ workload (MSVC v143), CMake 3.28 or later,
PowerShell 7, and the .NET SDK that `global.json` pins. Then:
You need Windows 11 (x64), Visual Studio 2022 or later with the C++ workload (MSVC v143 or later), CMake 3.28 or later,
PowerShell 7, and the .NET SDK that `global.json` pins — .NET 11 since 0.1.0-beta.37, which Microsoft does not support
on Windows 10 Home or Pro. Then:
```powershell
./build.ps1 check
@@ -45,13 +48,17 @@ The definition of done is the one in `CLAUDE.md`:
- a change to the hook path states its measured overhead in the PR (`docs/14_TESTING.md` §Hook overhead);
- a new hook is listed in `docs/17_HOOK_ENGINE.md` §Hook inventory and justified against rule 4;
- every new user-visible string exists in `en`, `vi` and `ja` (`docs/09_I18N.md`);
- a change to what the App shows keeps `ACCESSIBILITY.md` §For contributors — a name for every control that shows no
text, theme colours only, nothing shown by colour alone, everything reachable by keyboard — and says in the PR what was
checked with the keyboard and Narrator; if it moves what works or what does not, `ACCESSIBILITY.md` changes with it;
- a change that makes a document wrong updates that document in the same PR;
- a change under `src/` adds an entry under `## [Unreleased]` in `CHANGELOG.md`;
- every new source file carries the licence header — `./tools/notice-check.ps1 -Fix` writes it. A file you wrote
yourself may name you in its second line instead, in the same form:
`Copyright (C) <year> <your name> - additional terms under GPLv3 section 7: see NOTICE`.
The pull-request template lists the safety checks for changes to the capture layer.
The pull-request template lists the safety checks for changes to the capture layer, and the accessibility checks for
changes to the user interface.
## What will not be merged
+48 -6
View File
@@ -8,12 +8,14 @@
- TargetFramework's platform version selects which Windows API
projections are available to compile against.
- SupportedOSPlatformVersion is the floor CA1416 enforces.
NFR-8 requires Windows 10 22H2 = build 19045. Letting the supported version
default to the TFM's 19041 would silently accept installs three releases
below the stated floor.
NFR-8 names Windows 10 22H2 = build 19045 as the oldest Windows the code is
held to (since 2026-11-11, D95: not blocked there, and neither tested nor
supported - Microsoft supports .NET 11 on Windows 11). Letting the supported
version default to the TFM's 19041 would silently accept installs three
releases below that floor.
A bare `net10.0-windows` is wrong for a different reason: it resolves to
net10.0-windows7.0, and CA1416 would then error on Mica, MiniDumpWriteDump
A bare `net11.0-windows` is wrong for a different reason: it resolves to
net11.0-windows7.0, and CA1416 would then error on Mica, MiniDumpWriteDump
and IDXGIAdapter3::QueryVideoMemoryInfo — every Windows-10-era API this
application is built on.
@@ -25,7 +27,9 @@
nothing and CA1416 still enforces the 19045 floor at the API level.
-->
<PropertyGroup>
<TargetFramework>net10.0-windows10.0.22621.0</TargetFramework>
<!-- .NET 11 since 0.1.0-beta.37 (owner decision D94, 2026-11-11; docs/12_BUILD.md). net10.0 until then, and
net11.0 on the alpha branch from 2026-10-31. -->
<TargetFramework>net11.0-windows10.0.22621.0</TargetFramework>
<SupportedOSPlatformVersion>10.0.19045.0</SupportedOSPlatformVersion>
<!-- x64 only (CLAUDE.md pinned stack, NFR-8). Previously asserted in prose
@@ -67,6 +71,44 @@
<FrameLedgerVersionFile>$(MSBuildThisFileDirectory)VERSION</FrameLedgerVersionFile>
<Version Condition="'$(Version)' == '' And Exists('$(FrameLedgerVersionFile)')">$([System.IO.File]::ReadAllText('$(FrameLedgerVersionFile)').Trim())</Version>
<IncludeSourceRevisionInInformationalVersion>false</IncludeSourceRevisionInInformationalVersion>
<!-- D73 (2026-10-31): the RELEASE LINE, from the RELEASE_LINE file beside VERSION - `main`, the betas and releases on
the .NET that global.json pins, or `alpha`, a beta's source built to try a newer .NET from the long-lived `alpha`
branch, where this file and global.json are two of the few lines that differ while it does (docs/12_BUILD.md
§The alpha line).
Not a property a command line sets: the file is the one source, release.yml refuses a tag that disagrees with it,
and the target below refuses a value that is neither line. Every assembly carries it (the ItemGroup below), and
Shared.BuildLine reads it at run time. -->
<FrameLedgerReleaseLineFile>$(MSBuildThisFileDirectory)RELEASE_LINE</FrameLedgerReleaseLineFile>
<FlReleaseLine Condition="Exists('$(FrameLedgerReleaseLineFile)')">$([System.IO.File]::ReadAllText('$(FrameLedgerReleaseLineFile)').Trim())</FlReleaseLine>
<!-- D98 (2026-11-11): THE ALPHA LINE RESTS - the betas build on the same .NET as the newest alpha (0.1.0-alpha.4,
.NET 11.0.0), so no alpha is cut until a newer .NET is tried. An alpha built while this says true tells its user
that the line is paused and to install the beta: a resting alpha gets no update, its anti-cheat list included
(Shared.AlphaLine, App/Services/AlphaTexts). Stamped on both lines, read by an alpha alone. When the `alpha`
branch starts trying a newer .NET it sets this to false there - one more line of its switch (docs/12_BUILD.md
§The alpha line). -->
<FlAlphaLineRests>true</FlAlphaLineRests>
</PropertyGroup>
<ItemGroup>
<AssemblyMetadata Include="FrameLedger.ReleaseLine" Value="$(FlReleaseLine)" />
<AssemblyMetadata Include="FrameLedger.AlphaLineRests" Value="$(FlAlphaLineRests)" />
</ItemGroup>
<Target Name="FrameLedgerReleaseLineCheck" BeforeTargets="BeforeBuild" Condition="'$(FlReleaseLine)' != 'main' And '$(FlReleaseLine)' != 'alpha'">
<Error Text="RELEASE_LINE at the repository root must say 'main' or 'alpha', and it says '$(FlReleaseLine)' (docs/12_BUILD.md §The alpha line)" />
</Target>
<!-- The NuGet audit (2026-10-25, docs/13_CI_CD.md §Dependabot and the NuGet audit): every restore checks the WHOLE
package graph, transitive packages included, against the advisory database, at every severity. These were the
SDK's defaults for net10.0, written down so that a later SDK's defaults cannot move them. With
TreatWarningsAsErrors, a vulnerable package is NU1901-NU1904 and the restore - and so the gate - is red, which
is what happened with SQLitePCLRaw 2.1.11 (Directory.Packages.props). -->
<PropertyGroup>
<NuGetAudit>true</NuGetAudit>
<NuGetAuditMode>all</NuGetAuditMode>
<NuGetAuditLevel>low</NuGetAuditLevel>
</PropertyGroup>
<!-- beta.14 (D50): every managed binary names the product and who wrote it, as the native ones always have
+35 -25
View File
@@ -3,7 +3,11 @@
<!--
Central package management (docs/12_BUILD.md). Every version is pinned here
and nowhere else, which also makes Dependabot PRs single-file diffs.
All versions verified against nuget.org on 2026-08-02; re-verified and bumped 2026-09-21.
All versions verified against nuget.org on 2026-08-02; re-verified and bumped 2026-09-21; bumped again
2026-10-25 (beta.29 PR-2) with the updates Dependabot had never proposed (docs/13_CI_CD.md §Dependabot and
the NuGet audit), and 2026-10-26 (beta.30 PR-3): Velopack and Markdig, the SQLitePCLRaw pin dropped; and again
2026-10-26 (beta.31, the owner's request): the .NET 10.0.14 servicing packages and the updates beta.30 had left;
and 2026-11-11 (beta.37, D94): the three packages serviced with the runtime follow it to .NET 11.0.0.
-->
<PropertyGroup>
<ManagePackageVersionsCentrally>true</ManagePackageVersionsCentrally>
@@ -31,11 +35,13 @@
net10.0. The package ships no licence file, so its text is a reviewed override
(tools/license-overrides/Markdig.txt). HTML is disabled in the pipeline (App/Markdown/MarkdownRenderer.cs).
-->
<PackageVersion Include="Markdig" Version="1.4.0" />
<PackageVersion Include="Markdig" Version="1.5.0" />
</ItemGroup>
<ItemGroup Label="Hosting and logging">
<PackageVersion Include="Microsoft.Extensions.Hosting" Version="10.0.12" />
<!-- The three packages serviced with the runtime follow it: this one, Microsoft.Data.Sqlite and
System.Diagnostics.EventLog (docs/12_BUILD.md). -->
<PackageVersion Include="Microsoft.Extensions.Hosting" Version="11.0.0" />
<PackageVersion Include="Serilog" Version="4.4.0" />
<PackageVersion Include="Serilog.Extensions.Hosting" Version="10.0.0" />
<PackageVersion Include="Serilog.Sinks.Console" Version="6.1.1" />
@@ -44,44 +50,42 @@
<ItemGroup Label="Storage">
<!-- No EF: Dapper over Microsoft.Data.Sqlite (CLAUDE.md pinned stack). -->
<PackageVersion Include="Microsoft.Data.Sqlite" Version="10.0.12" />
<PackageVersion Include="Dapper" Version="2.1.86" />
<PackageVersion Include="Microsoft.Data.Sqlite" Version="11.0.0" />
<PackageVersion Include="Dapper" Version="2.1.89" />
<!--
Transitive pin, not a direct dependency.
Microsoft.Data.Sqlite 10.0.10 resolves SQLitePCLRaw.lib.e_sqlite3 2.1.11,
which carries GHSA-2m69-gcr7-jv3q (high severity, vulnerable range
<= 2.1.11) via its bundled SQLite. With TreatWarningsAsErrors that is
NU1903 and the build fails — correctly. Pinning the bundle forward to the
3.x line pulls a patched native library.
CentralPackageTransitivePinningEnabled is what makes this work from here.
Revisit when Microsoft.Data.Sqlite ships a build that resolves a patched
version on its own, and drop this pin rather than carrying it forever.
No transitive pin on SQLitePCLRaw since beta.30 (2026-10-26). From the scaffold (2026-08-02) to beta.29 this held
SQLitePCLRaw.bundle_e_sqlite3 at 3.0.5: Microsoft.Data.Sqlite 10.0.10 resolved SQLitePCLRaw.lib.e_sqlite3 2.1.11,
which carries GHSA-2m69-gcr7-jv3q (vulnerable range <= 2.1.11) through its bundled SQLite, NU1903 under
TreatWarningsAsErrors. Its own comment said to drop it once Microsoft.Data.Sqlite resolved a patched version on
its own; 10.0.13 declares SQLitePCLRaw 2.1.13, and the pin had become a conflict NuGet does not report - it put a
package built against the 2.x line on SQLitePCLRaw's 3.x line. The NuGet audit (Directory.Build.props) still
turns a vulnerable SQLite red (docs/13_CI_CD.md §Dependabot and the NuGet audit).
Since beta.37 (2026-11-11): Microsoft.Data.Sqlite 11 declares SQLitePCLRaw 3.0.5 itself - the 3.x line, built for
it this time, whose engine is SourceGear's SQLite package; still no pin here. The alphas shipped that graph from
2026-10-31.
-->
<PackageVersion Include="SQLitePCLRaw.bundle_e_sqlite3" Version="3.0.5" />
</ItemGroup>
<ItemGroup Label="Interop, telemetry and packaging">
<PackageVersion Include="Microsoft.Windows.CsWin32" Version="0.3.333" />
<PackageVersion Include="Velopack" Version="1.2.0" />
<PackageVersion Include="Microsoft.Windows.CsWin32" Version="0.3.367" />
<PackageVersion Include="Velopack" Version="1.2.161" />
<!-- MPL-2.0. docs/18_GPU_VENDOR_APIS.md §L2 requires >= 0.9.6, and
legal/THIRD_PARTY_NOTICES.md has a release-gate check that no
depended-upon file carries MPL-2.0 Exhibit B. Consume UNMODIFIED. -->
<PackageVersion Include="LibreHardwareMonitorLib" Version="0.9.6" />
<!-- The crash witness (04_CAPTURE §Crash & exit classification): Application log events 1000/1001. In-box
for WPF apps, a package for a class library on the Windows TFM. Microsoft, MIT. -->
<PackageVersion Include="System.Diagnostics.EventLog" Version="10.0.12" />
<PackageVersion Include="System.Diagnostics.EventLog" Version="11.0.0" />
</ItemGroup>
<ItemGroup Label="Analyzers (build-time only)">
<PackageVersion Include="Roslynator.Analyzers" Version="5.0.1" />
<PackageVersion Include="Meziantou.Analyzer" Version="3.0.307" />
<PackageVersion Include="Meziantou.Analyzer" Version="3.0.319" />
<PackageVersion Include="Microsoft.VisualStudio.Threading.Analyzers" Version="18.12.1" />
</ItemGroup>
<ItemGroup Label="Testing">
<PackageVersion Include="Microsoft.NET.Test.Sdk" Version="18.10.1" />
<PackageVersion Include="Microsoft.NET.Test.Sdk" Version="18.11.0" />
<!--
xUnit.net v3, 4.x line (2026-09-21). 4.0 made Microsoft Testing Platform v2 the default of the plain
`xunit.v3` package and dropped MTP v1. build.ps1's gates are VSTest-shaped on purpose - the
@@ -89,8 +93,8 @@
so the projects reference the SAME 4.x framework through its `mtp-off` variant, the one xunit publishes
for exactly this. Moving to MTP v2 is a build.ps1 change, not a version bump; do them together or not at all.
-->
<PackageVersion Include="xunit.v3.mtp-off" Version="4.0.1" />
<PackageVersion Include="xunit.runner.visualstudio" Version="4.0.0" />
<PackageVersion Include="xunit.v3.mtp-off" Version="4.0.2" />
<PackageVersion Include="xunit.runner.visualstudio" Version="4.0.1" />
<!--
FluentAssertions is pinned to the 7.x line ON PURPOSE, and must not be
bumped to 8.x without redoing the licence analysis.
@@ -109,7 +113,13 @@
-->
<PackageVersion Include="FluentAssertions" Version="[7.2.2]" />
<PackageVersion Include="NSubstitute" Version="6.2.0" />
<PackageVersion Include="coverlet.collector" Version="10.0.1" />
<!--
10.1.0 not taken on 2026-10-25: the tracker it injects into each instrumented assembly declares a constant,
ModuleTrackerRegistryKey, whose value reflection cannot read ("Literal value was not found"), and
NoSecondMatcherTests reads every string constant in Application, Domain and Infrastructure. Taken in beta.31
(2026-10-26): that test now leaves out the types coverlet adds (namespace Coverlet.*), which are not ours.
-->
<PackageVersion Include="coverlet.collector" Version="10.1.0" />
</ItemGroup>
</Project>
+2
View File
@@ -49,6 +49,8 @@
-->
<ItemGroup Condition="'$(IsTestProject)' == 'true'">
<Compile Include="$(MSBuildThisFileDirectory)tests\Shared\HarnessOverlayLogSweep.cs" Link="Shared\HarnessOverlayLogSweep.cs" />
<!-- When a started harness is really up (beta.27): the injection tests wait for its own "presenting" line. -->
<Compile Include="$(MSBuildThisFileDirectory)tests\Shared\HarnessReady.cs" Link="Shared\HarnessReady.cs" />
</ItemGroup>
<!--
+89 -15
View File
@@ -5,7 +5,7 @@ hooking on for — and reading the graphics calls the game makes. That is why it
resolution, the upscaler, frame generation and ray tracing apart. It is also where its limits come from. This
page lists them in plain words; each item links to the document that has the details.
*Beta software: this page describes version 0.1.0-beta.24.*
*Beta software: this page describes version 0.1.0-beta.37.*
## Games it will not measure
@@ -67,10 +67,15 @@ shown is recorded too, from outside the game. ([Capture](docs/04_CAPTURE.md))
([Metrics](docs/03_METRICS.md))
- **The mix of frame-generation states** in a session's summary (since 0.1.0-beta.24) is read over five-second
windows: frame generation that changes faster than that — the NVIDIA App's *Dynamic* mode can — reads partly as
*Not classified*, and a state shorter than 10 seconds is not listed. The multiplier chosen in a game's own menu is
not read; the measured factor is its evidence. How the NVIDIA App's *Dynamic* ceiling and *Max refresh rate* target
are stored by the driver is read from NVIDIA's own setting names and not yet checked against the App on a real
game. Sessions recorded before 0.1.0-beta.24 have no mix. ([Metrics](docs/03_METRICS.md))
*Not classified*: a window in which the multiplier stepped reads between two whole multipliers and, since
0.1.0-beta.27, is never a state of its own. A state shorter than 10 seconds is not listed. A stretch the game
presents with almost no frame
count of its own — shaders compiling at start, a loading screen, a menu drawn outside frame generation — reads as
*Not classified* too. The
multiplier chosen in a game's own menu is not read; the measured factor is its evidence. How the NVIDIA App's
*Dynamic* ceiling and *Max refresh rate* target are stored by the driver is read from NVIDIA's own setting names,
and has been checked against the App on one game. Sessions recorded before 0.1.0-beta.24 have no mix.
([Metrics](docs/03_METRICS.md))
- **Time below 30, 60 FPS and below the refresh rate** (since 0.1.0-beta.14) leaves out the small wobble of a game
held at its limit: a frame counts as below 60 when it took 10 % longer than 1/60 s, or when the frames around it ran
2 % slower. So a game running steadily just under the line — 59 FPS against 60 — reads partly as at it. Time below
@@ -96,11 +101,18 @@ shown is recorded too, from outside the game. ([Capture](docs/04_CAPTURE.md))
The mode chosen in a game's own menu is not readable for DLSS without Streamline, and is not inferred from the
render scale. How the driver numbers DLAA in
its report is NVIDIA's documented value, not yet seen on a real game. The render resolution is N/A where the
game's own calls do not carry it (DLSS without Streamline, for one). ([Metrics](docs/03_METRICS.md))
game's own calls do not carry it (DLSS without Streamline, for one). Sessions recorded before 0.1.0-beta.27 kept
the NVIDIA driver's answer from after the game had closed, which never says DLSS ran: on a game no hook names, they
show neither the driver's report nor the NVIDIA App's mode. ([Metrics](docs/03_METRICS.md))
- **Which DLSS ran** (since 0.1.0-beta.24) is named only from what the session showed: the model preset the NVIDIA
driver reports (L or M: DLSS 4.5; J or K: DLSS 4), a measured multi-frame factor (×5 or ×6: DLSS 4.5; ×3 or ×4:
DLSS 4), or a library whose major version names one (2.x, 3.x). A 310 library with no such evidence shows its
version only. DLSS 5 is shown only as *runtime loaded*, by a library name not yet seen on a real game. Where each
DLSS 4), the NVIDIA App's *Dynamic* frame generation that the driver reports applied (DLSS 4.5, whatever multiplier
it chose — since 0.1.0-beta.34), or a library whose major version names one (2.x, 3.x). A *Fixed* ×5 or ×6 set in
the App names DLSS 4.5 only when the frames show it. A 310 library with no such evidence shows its
version only. **DLSS 5**
(since 0.1.0-beta.34) is named where the game was seen running its neural rendering through Streamline, with the share
of rendered frames; its library loaded and nothing seen reads *runtime loaded* — *not seen running* only where the
Overlay looked. A game that runs neural rendering outside Streamline is not seen. Where each
library was loaded from is read from its folder, for sessions recorded since 0.1.0-beta.24.
- **Ray tracing** is *Yes*, *No* or *N/A* — measured from the game's ray-tracing calls on Direct3D 12, and
N/A where FrameLedger could not look. **Path tracing is never stated as a fact**: there is no API signal
@@ -131,7 +143,9 @@ shown is recorded too, from outside the game. ([Capture](docs/04_CAPTURE.md))
"Fullscreen". FrameLedger reports what the game asked for.
- The mode is sampled ten times a second in a measured session and once a second in an unmeasured one; very
short switches can be missed. A session recovered after a crash, and every session recorded before
beta.10, read N/A. ([Display mode](docs/03_METRICS.md#display-mode--both-tiers-beta10))
beta.10, read N/A. Some sessions recorded before 0.1.0-beta.27 of a game in exclusive full-screen show no window or
monitor size: the game's last moments, after its window had closed, replaced them.
([Display mode](docs/03_METRICS.md#display-mode--both-tiers-beta10))
## Engine version
@@ -177,7 +191,13 @@ you accept the prompt. Turn it on only if you trust everything that runs under y
## Platform and what has been tested
- **Windows 10 22H2 or Windows 11, 64-bit only.**
- **Windows 11, 64-bit only.** FrameLedger is built on .NET 11 since 0.1.0-beta.37, which Microsoft supports on
Windows 11 and, on Windows 10, only in its LTSC and IoT editions. **Windows 10 22H2 Home and Pro are not blocked,
not tested and not supported**: FrameLedger may run there, and nobody has checked that it does
([Build](docs/12_BUILD.md)).
- **It does not start at all on a processor without SSE4.2 and POPCNT** — .NET 11's requirement, which every
processor Windows 11 accepts meets. On such a PC an update from 0.1.0-beta.36 or older installs and then does not
start; installing 0.1.0-beta.36 again brings FrameLedger back, with your data as it was.
- The games FrameLedger has actually been run with, and what was measured on each, are listed in
[LIST_GAME_TESTED.md](docs/LIST_GAME_TESTED.md). Everything was measured on one machine (an NVIDIA
GeForce RTX 5080 with an Intel Core i7-14700KF on Windows 11); other hardware is untested.
@@ -188,6 +208,15 @@ you accept the prompt. Turn it on only if you trust everything that runs under y
anti-cheat, never to judge it, and recording or measuring a game vouches for nothing. Four itch.io downloads this
project once used as examples turned out to carry malware ([details](docs/spike-notes.md)).
## Accessibility
What works with the keyboard alone, a screen reader, a contrast theme or Magnifier, what does not yet, and how to report
a barrier is on its own page: [Accessibility](ACCESSIBILITY.md) (in the app: Help ▸ Accessibility). The largest limits:
- **A chart's points cannot be read one by one.** A screen reader hears its name and where its numbers are written —
the session's figures, the tables, **File ▸ Export**; its keys move it.
- **Windows' text size setting is not followed** — use display scaling or Magnifier.
## Play
- **Through GOG GALAXY or itch, you finish in their app.** GOG GALAXY runs the game as its own shortcuts do, and the
@@ -196,14 +225,42 @@ you accept the prompt. Turn it on only if you trust everything that runs under y
- **FrameLedger never starts a game as administrator.** *Start directly* does not start a game that asks for it — start
that one from its store or its own shortcut — nor a game whose recording is off: FrameLedger starts only what it
records. While FrameLedger itself runs as administrator, Play starts every game directly, with your standard rights.
- **Some games will not start directly** (seen on two Steam games, 2026-10-19 and 20). Lies of P, started by *Start
directly*, hands itself to Steam within seconds — since 0.1.0-beta.27 the game Steam then starts is recorded —, and
Clair Obscur: Expedition 33 closes within seconds, with or without FrameLedger's hook. Each such start ends a
measured session early, which the crash safety counts: two turn hooking off for the game. Start such a game through
its store (Settings ▸ Games ▸ *Play button*); the notice after Play says when a Steam game may hand itself to Steam.
([details](docs/spike-notes/23-owner-runs-2026-10-20.md))
## Xbox app and Microsoft Store games
- **Only games built on Microsoft's GDK** (since 0.1.0-beta.33) — what the Xbox app and the Microsoft Store install into
a games folder you chose, PC Game Pass games included — are found by **Import library**. An older Store app (UWP) is
not listed, and a game Windows has not installed for you, such as one left behind on a drive, is not offered.
([details](docs/spike-notes/25-xbox-gdk.md))
- **Their executables cannot be read by other programs** — Windows refuses it to anything outside the game's own
package — so FrameLedger shows no Unreal Engine version and no *Runs as* for them, and says what it could not read
rather than guessing. A Unity game's version still reads, from its player library.
- **The anti-cheat list's per-game entries know Steam ids only.** An Xbox copy of a game listed there by its Steam id is
checked like any other game — its files, its executables, the anti-cheat drivers and services on your PC — but not
by that entry. ([Safety](docs/19_SAFETY_AND_ANTICHEAT.md), [open question](docs/20_OPEN_QUESTIONS.md))
- **Play starts them through Windows, in either Play mode** — as their Start-menu tile does — because Windows starts
such a game only through its package: *Start directly* cannot start one, so it is recorded once it appears, a few
seconds after its start, and the first frames before then are not measured. ([Play](docs/08_UI.md),
[capture](docs/04_CAPTURE.md))
- **An older Store app (UWP), and a game Windows runs under code protection the hook cannot live under** — only
Microsoft-signed code, no generated code, strict stack or control-flow protection — **is never hooked**: its session
keeps its duration, your PC's sensors and the reason. Measuring a game from the Xbox app with the Vulkan graphics API
has not been tried. ([Safety](docs/19_SAFETY_AND_ANTICHEAT.md), [open question](docs/20_OPEN_QUESTIONS.md))
## Game artwork
- **Only the Steam and GOG GALAXY apps keep pictures FrameLedger can show** (since 0.1.0-beta.23). A game's page shows
the cover and banner those apps keep on your PC for a game they installed, read where they keep them — nothing is
downloaded or copied. A game from itch, the Epic Games Launcher or another store, or one whose `.exe` is outside a
store's own folder, shows a picture only once you choose one (**Edit… ▸ Choose image…**). A GOG picture needs Windows'
WebP support, which Windows 11 and most Windows 10 installs have. ([Game page](docs/08_UI.md))
- **Only the Steam and GOG GALAXY apps keep pictures FrameLedger can show** (since 0.1.0-beta.23) — **and, since
0.1.0-beta.33, an Xbox game ships its own**: its square logo and its splash image, shown from its own folder. A game's
page shows the cover and banner those apps keep on your PC for a game they installed, read where they keep them —
nothing is downloaded or copied. A game from itch, the Epic Games Launcher or another store, or one whose `.exe` is
outside a store's own folder, shows a picture only once you choose one (**Edit… ▸ Choose image…**). A GOG picture needs
Windows' WebP support, which Windows 11 and most Windows 10 installs have. ([Game page](docs/08_UI.md))
- The pictures belong to the games' owners; FrameLedger ships none ([names and trademarks](legal/TRADEMARKS.md)).
## Your data
@@ -226,3 +283,20 @@ administrator prompt names an unknown publisher. Each release publishes SHA-256
loaded until the game exits, and Windows will not let the update replace it; *Restart to update* says which file is held
until you close that game ([details](docs/11_UPDATER.md)). Copies older than 0.1.0-beta.14 look only for stable
releases unless you choose *Beta* in Settings ▸ Updates, and apply a downloaded update the next time they start.
## Alpha builds
*Only for an alpha — a version ending in `-alpha.N`, an experimental build on a new .NET
([Alpha builds](guide/11-alpha-builds.md)).*
- **It is built to try a newer .NET — at times one Microsoft has not finished** — and has not been tested the way a
beta is: everything on this page applies to it, and so can problems no beta has shown
([Alpha notice](legal/ALPHA_NOTICE.md)).
- **The alphas are paused since 0.1.0-alpha.4, and a paused alpha gets no updates** — the list of anti-cheat software
it refuses included, which arrives only inside an update. The betas run on the same .NET 11 since 0.1.0-beta.37:
install the latest beta over the alpha. Once ten betas have followed 0.1.0-alpha.4, an older alpha no longer finds
it as an update ([Updater](docs/11_UPDATER.md)).
- **It shares the beta's data folder.** It copies the database into `backups` before it first opens it, and does not
open it if the copy cannot be made; the newest three copies are kept and older ones it made are deleted.
- **It updates only to newer alphas**, and its update channel is locked; going back to the beta means installing the
beta over it.
+16 -11
View File
@@ -6,14 +6,15 @@
**New here? Start with the [user guide](guide/README.md)** — install, record a game, read your results, stay safe with
anti-cheat, and look after your data, a page each, then every screen, every setting and what to do when something goes
wrong. What FrameLedger cannot do is on one page: [Limitations](LIMITATIONS.md). Both are in the app too (Help ▸ User
guide, Help ▸ Limitations), and on the project's [wiki](https://github.com/poli0981/frameledger/wiki) with the developer
pages.
wrong. What FrameLedger cannot do is on one page: [Limitations](LIMITATIONS.md). How it works with the keyboard alone, a
screen reader or a contrast theme, and how to report a barrier: [Accessibility](ACCESSIBILITY.md). All three are in the
app too (Help ▸ User guide, Help ▸ Limitations, Help ▸ Accessibility), and on the project's
[wiki](https://github.com/poli0981/frameledger/wiki) with the developer pages.
<!-- accuracy-block:begin -->
> ⚠ **What FrameLedger actually measures today — 2026-10-19.** The software is a beta; its latest
> **pre-release is `0.1.0-beta.24`** (2026-10-19), an unsigned installer built from that tag with its
> checksums published beside it. The source holds the desktop app
> ⚠ **What FrameLedger actually measures today — 2026-11-06.** The software is a beta; its latest
> **beta is `0.1.0-beta.37`** (2026-11-11), an unsigned installer built from that tag with its
> checksums published beside it (alphas — experimental builds that try a newer .NET — are published apart). The source holds the desktop app
> (library, store import, charts, settings) and the background Agent, which records a session when a
> game in the library runs (unless you switched its recording off), injects only into games you enabled
> and only past the safety guard, and
@@ -44,7 +45,9 @@ pages.
> every other case — FSR at a dynamic resolution among them — no mode is shown.
> - **DLSS version:** the version of each DLSS library the game loaded and whether it came from the game or from
> the NVIDIA driver; "DLSS 4" or "DLSS 4.5" only when the session shows it (the model preset the driver reports,
> or a measured multi-frame factor); DLSS 5 only as "runtime loaded".
> a measured multi-frame factor, or the NVIDIA App's Dynamic frame generation that the driver reports applied);
> "DLSS 5" only when the game was seen running its neural rendering, otherwise "runtime loaded" when its library was
> loaded.
> - **Render → output resolution:** measured where the vendor's own per-frame call carries the render
> size (AMD FidelityFX dispatches, and Streamline titles whose resource tags state it); `N/A` where it
> does not: DLSS titles that bypass Streamline, Streamline titles whose tags carry no size, and Vulkan
@@ -133,7 +136,7 @@ Most tools tell you your frame rate. FrameLedger tells you **what produced that
- **Shader-compilation stutter attribution** — which frame spikes were pipeline compiles.
- **PC latency** when the game uses Reflex.
Plus the usual: Avg / Min / Max / Median FPS, 1% Low, 0.1% Low, frametime distributions, stutter metrics, CPU/GPU temperatures, session history, cross-session comparison, and Steam/GOG/Epic/itch.io library import. UI in **English / Tiếng Việt / 日本語**.
Plus the usual: Avg / Min / Max / Median FPS, 1% Low, 0.1% Low, frametime distributions, stutter metrics, CPU/GPU temperatures, session history, cross-session comparison, and Steam/GOG/Epic/itch.io/Xbox library import. UI in **English / Tiếng Việt / 日本語**.
## How it works — and the trade-off, stated plainly
@@ -166,7 +169,8 @@ The tier is recorded on every session and shown in the UI. Metrics unavailable a
## Requirements
- Windows 10 (22H2) or Windows 11, 64-bit
- Windows 11, 64-bit. Windows 10 (22H2) is not blocked, but FrameLedger is built on .NET 11 since 0.1.0-beta.37, which Microsoft does not support on Windows 10 Home or Pro, and FrameLedger has never been tested there
- A processor with SSE4.2 and POPCNT — any that Windows 11 accepts. Without them FrameLedger does not start
- A 64-bit DirectX 11/12 or OpenGL game, or a Vulkan game FrameLedger starts, for hooked (Tier-1) capture. **32-bit games — including most DirectX 9 titles — cannot be measured at all**: the component FrameLedger loads is x64 and an x64 DLL cannot enter a 32-bit process. Such a title records duration and hardware telemetry and nothing else. *(This line previously said "supported at Tier 2 only", which meant frame times without injection. That tier no longer exists.)*
- Optional: [PawnIO](https://pawnio.eu/) for CPU temperature, read only when the Agent runs as administrator (since 0.1.0-beta.3; not yet checked on real hardware). CPU load, memory in use and all GPU telemetry work without it
@@ -174,7 +178,7 @@ Elevation is **optional — for everything.** Hooked capture is the normal path
## Install
> **The latest pre-release is `v0.1.0-beta.24` (2026-10-19); before it `v0.1.0-beta.23` (2026-10-14), `v0.1.0-beta.22` (2026-10-13), `v0.1.0-beta.21` (2026-10-13), `v0.1.0-beta.20` (2026-10-12), `v0.1.0-beta.19` (2026-10-12), `v0.1.0-beta.18` (2026-10-07), `v0.1.0-beta.17` (2026-10-07), `v0.1.0-beta.16` (2026-10-06), `v0.1.0-beta.15` (2026-10-06), `v0.1.0-beta.14` (2026-10-06), `v0.1.0-beta.13` (2026-10-04), `v0.1.0-beta.12` (2026-10-04), `v0.1.0-beta.11` (2026-10-03), `v0.1.0-beta.10` (2026-09-28), `v0.1.0-beta.9` (2026-09-26), `v0.1.0-beta.8` (2026-09-25), `v0.1.0-beta.7` (2026-09-23), `v0.1.0-beta.6` (2026-09-23), `v0.1.0-beta.5` (2026-09-22), `v0.1.0-beta.4` (2026-09-21), `v0.1.0-beta.3` (2026-09-21), `v0.1.0-beta.2` (2026-09-17) and `v0.1.0-beta.1` (2026-09-16).** They are pre-releases: read the notes of the one you install — `CHANGELOG.md` links each release's own file under `docs/changelog/` — for what it measures, what it does not yet, and how to update, before installing. A source build is `docs/12_BUILD.md`.
> **The latest beta is `v0.1.0-beta.37` (2026-11-11); before it `v0.1.0-beta.36` (2026-11-10), `v0.1.0-beta.35` (2026-11-09), `v0.1.0-beta.34` (2026-11-06), `v0.1.0-beta.33` (2026-11-03), `v0.1.0-beta.32` (2026-10-31), `v0.1.0-beta.31` (2026-10-26), `v0.1.0-beta.30` (2026-10-26), `v0.1.0-beta.29` (2026-10-25), `v0.1.0-beta.28` (2026-10-20), `v0.1.0-beta.27` (2026-10-20), `v0.1.0-beta.26` (2026-10-19), `v0.1.0-beta.25` (2026-10-19), `v0.1.0-beta.24` (2026-10-19), `v0.1.0-beta.23` (2026-10-14), `v0.1.0-beta.22` (2026-10-13), `v0.1.0-beta.21` (2026-10-13), `v0.1.0-beta.20` (2026-10-12), `v0.1.0-beta.19` (2026-10-12), `v0.1.0-beta.18` (2026-10-07), `v0.1.0-beta.17` (2026-10-07), `v0.1.0-beta.16` (2026-10-06), `v0.1.0-beta.15` (2026-10-06), `v0.1.0-beta.14` (2026-10-06), `v0.1.0-beta.13` (2026-10-04), `v0.1.0-beta.12` (2026-10-04), `v0.1.0-beta.11` (2026-10-03), `v0.1.0-beta.10` (2026-09-28), `v0.1.0-beta.9` (2026-09-26), `v0.1.0-beta.8` (2026-09-25), `v0.1.0-beta.7` (2026-09-23), `v0.1.0-beta.6` (2026-09-23), `v0.1.0-beta.5` (2026-09-22), `v0.1.0-beta.4` (2026-09-21), `v0.1.0-beta.3` (2026-09-21), `v0.1.0-beta.2` (2026-09-17) and `v0.1.0-beta.1` (2026-09-16).** They are pre-releases: read the notes of the one you install — `CHANGELOG.md` links each release's own file under `docs/changelog/` — for what it measures, what it does not yet, and how to update, before installing. A source build is `docs/12_BUILD.md`.
1. Download the latest `FrameLedger.App-win-Setup.exe` from [Releases](https://github.com/poli0981/frameledger/releases). It installs into `%LOCALAPPDATA%\FrameLedger.App`; your data stays in `%LOCALAPPDATA%\FrameLedger`, and uninstalling asks before touching it.
2. SmartScreen may warn — releases are not code-signed (free, open-source project). Verify the SHA-256 checksum published with each release, then **More info → Run anyway**.
@@ -201,7 +205,8 @@ FrameLedger is GPL-3.0-only free software, and you are welcome to build it, chan
- **Build it:** [`docs/12_BUILD.md`](docs/12_BUILD.md) — `./build.ps1 check` is the whole quality gate, the same one CI runs.
- **Contribute:** [`CONTRIBUTING.md`](CONTRIBUTING.md) — the definition of done, what will not be merged, and that a
contribution is licensed GPL-3.0-only with the [`NOTICE`](NOTICE) terms (no CLA). Conduct:
[`CODE_OF_CONDUCT.md`](CODE_OF_CONDUCT.md). Security reports: [`SECURITY.md`](SECURITY.md).
[`CODE_OF_CONDUCT.md`](CODE_OF_CONDUCT.md). Security reports: [`SECURITY.md`](SECURITY.md). Accessibility — the goal,
the checks and how a barrier is reported: [`ACCESSIBILITY.md`](ACCESSIBILITY.md).
- **Fork or redistribute:** [`FORKING.md`](FORKING.md) — what the GPL asks of anyone who distributes builds, and the names
a fork must change so it does not share FrameLedger's update feed, install folder, data, pipe or Vulkan layer.
- **Find your way around:** the [wiki](https://github.com/poli0981/frameledger/wiki)'s developer pages are short, and each
+1
View File
@@ -0,0 +1 @@
alpha
+84
View File
@@ -0,0 +1,84 @@
<?xml version="1.0" encoding="utf-8"?>
<!--
SonarCloud, analysed from CI since 2026-10-25 (docs/13_CI_CD.md §SonarCloud, owner decision D68): ci.yml's
`sonarcloud` job passes this file to the SonarScanner for .NET's begin step (/s:). It replaces
.sonarcloud.properties, which only Automatic Analysis read (D67). The project key, the organisation, the version
and the token are given on the command line; everything that does not change from one run to the next is here.
-->
<SonarQubeAnalysisProperties xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://www.sonarsource.com/msbuild/integration/2015/1">
<Property Name="sonar.host.url">https://sonarcloud.io</Property>
<!--
What is not FrameLedger's code, or not code at all:
- src/native/third_party: the vendored SDK headers (NVAPI, Streamline, FidelityFX, Vulkan-Headers), consumed
unmodified (each folder's README says so and license-check holds it).
- Strings.Designer.cs: generated by tools/resx-gen.ps1.
- dxr_raygen_dxil.h: a compiled shader as a byte array, generated.
- vendor-stubs: test fixtures that carry the vendors' export names and signatures on purpose.
- tests/fixtures: the detection corpus (empty marker binaries and expected JSON).
- legal/licenses, docs/vendor-exports.json: licence texts and a generated export list.
- Migrations: SQLite scripts, which a SQL analyser reads as another dialect.
And, since the scanner reads the whole checkout for the languages it finds outside the projects (PowerShell,
YAML, JSON), what a build writes into it: the native build tree with the sources CMake fetched into it, out/,
every project's bin/ and obj/, and the test results the coverage comes from.
-->
<Property Name="sonar.exclusions">src/native/third_party/**,**/Strings.Designer.cs,src/native/tools/hook-harness/dxr_raygen_dxil.h,src/native/tools/vendor-stubs/**,tests/fixtures/**,legal/licenses/**,docs/vendor-exports.json,src/FrameLedger.Infrastructure/Persistence/Migrations/**,build/**,out/**,**/bin/**,**/obj/**,**/TestResults/**</Property>
<!-- Tests repeat their arrange steps on purpose; duplication there is not a defect. -->
<Property Name="sonar.cpd.exclusions">tests/**,src/native/tests/**</Property>
<Property Name="sonar.sourceEncoding">UTF-8</Property>
<!--
The native code: CMake's compilation database for the x64-release preset, which the job configures before the
begin step. The sources reach the analysis through FrameLedger.Infrastructure.csproj's FlNativeSource items,
because the scanner analyses only files an MSBuild project names. Reported against C++20, the standard
src/native/CMakeLists.txt sets.
-->
<Property Name="sonar.cfamily.compile-commands">build/native/x64-release/compile_commands.json</Property>
<Property Name="sonar.cfamily.reportingCppStandardOverride">c++20</Property>
<!--
The gate's coverage: build.ps1 writes OpenCover beside the Cobertura that tools/coverage-gate.ps1 reads, one
report per test project in TestResults/<guid>/. The second copy the trx logger keeps under In/ is not matched.
-->
<Property Name="sonar.cs.opencover.reportsPaths">tests/*/TestResults/*/coverage.opencover.xml</Property>
<!--
Coverage is measured for the C# only. SonarCloud counts the executable lines of a file no report covers as
uncovered - the first analysis read build.ps1's 232 lines to cover, every one uncovered, and failed the gate on the
two a pull request changed - so the PowerShell tools (tested by their own -SelfTest cases, which no coverage tool
reads) and the native code (Catch2 suites and the injection tests, with no coverage collector) are left out of the
coverage figures. They are analysed for issues as everything else is.
-->
<Property Name="sonar.coverage.exclusions">**/*.ps1,**/*.psm1,src/native/**</Property>
<!--
Roslynator, Meziantou, the VS threading analyzers and the .NET analyzers already gate the build (warnings as
errors); what they report at a lower severity is the project's choice. Only SonarCloud's own rules are imported.
-->
<Property Name="sonar.cs.roslyn.ignoreIssues">true</Property>
<!--
Two rules this project breaks by design everywhere they apply (the triage of 2026-10-19 in docs/13_CI_CD.md
accepted every instance):
- S8417, sequentially consistent atomics: the SPSC ring and the hook counters use explicit acquire/release and
relaxed orders on purpose (07_IPC); sequential consistency would add fences on the per-present path. The rule
key's repository is a wildcard because a header is indexed as C and a source file as C++.
- csharpsquid:S6640, unsafe code: interop with the native layer and the shared-memory mirror, confined to
Infrastructure and Shared (CLAUDE.md: the native layer is reachable only through Infrastructure).
-->
<Property Name="sonar.issue.ignore.multicriteria">atomics,unsafeInfrastructure,unsafeShared</Property>
<Property Name="sonar.issue.ignore.multicriteria.atomics.ruleKey">*:S8417</Property>
<Property Name="sonar.issue.ignore.multicriteria.atomics.resourceKey">src/native/**/*</Property>
<Property Name="sonar.issue.ignore.multicriteria.unsafeInfrastructure.ruleKey">csharpsquid:S6640</Property>
<Property Name="sonar.issue.ignore.multicriteria.unsafeInfrastructure.resourceKey">src/FrameLedger.Infrastructure/**/*</Property>
<Property Name="sonar.issue.ignore.multicriteria.unsafeShared.ruleKey">csharpsquid:S6640</Property>
<Property Name="sonar.issue.ignore.multicriteria.unsafeShared.resourceKey">src/FrameLedger.Shared/**/*</Property>
<!-- The end step waits for the quality gate, so a failed gate is a red job, not a check nobody opens. -->
<Property Name="sonar.qualitygate.wait">true</Property>
<Property Name="sonar.qualitygate.timeout">600</Property>
</SonarQubeAnalysisProperties>
+6 -3
View File
@@ -285,8 +285,11 @@ function Invoke-Managed([bool]$FixFormat) {
# the hosted runner); the mini dump goes to TestResults beside the trx.
# --blame-hang did NOT stop the deadlocked xUnit v3 executable it was added for (measured 2026-09-17); the
# wall-clock limit of Invoke-TestsWithin is what bounds a hang now. The suite takes 4-5 minutes on the runner.
$testArgs = @('test', "`"$solution`"", '-c', $Configuration, '--no-build', '--collect:"XPlat Code Coverage"',
'--logger', 'trx;LogFileName=results.trx')
#
# Two coverage formats from the one run (2026-10-25, D68): Cobertura for the coverage gate below, OpenCover for
# SonarCloud, whose C# importer reads no Cobertura. ci.yml's sonarcloud job takes them from this run's artifact.
$testArgs = @('test', "`"$solution`"", '-c', $Configuration, '--no-build',
'--collect:"XPlat Code Coverage;Format=cobertura,opencover"', '--logger', 'trx;LogFileName=results.trx')
if ($SkipIntegration) {
Skip-Gate 'integration tests' 'the guard refuses a .NET test host that loads a `protect`-matching module (20_OPEN_QUESTIONS §S19(b)) — run ./build.ps1 check with no switches to include them'
Invoke-TestsWithin 25 ($testArgs + @('--filter', 'Category!=Integration'))
@@ -464,7 +467,7 @@ function Invoke-ProjectGates {
Invoke-Checked 'notice-check (self-test)' { & $noticeTool -SelfTest }
Invoke-Checked 'notice-check' { & $noticeTool -RepoRoot $repo }
# beta.17 (D53/D54): the GitHub Wiki is built from wiki/, guide/ and LIMITATIONS.md, and wiki.yml publishes it when a
# beta.17 (D53/D54): the GitHub Wiki is built from wiki/, guide/, LIMITATIONS.md and (beta.35) ACCESSIBILITY.md, and wiki.yml publishes it when a
# release is made. A link or a section that leads nowhere, a page nothing leads to, a sidebar out of the guide's
# order, a path that names nothing or a version written into a page is red here, not on the published wiki.
# Self-test first (nine cases, both directions), then the live assembly into a temporary folder.
+7
View File
@@ -99,6 +99,11 @@ Guard re-runs every 30 s for the life of the session; anti-cheat appearing late
- The DLL is **not unloaded** from a live process after unhooking (threads may still be inside trampolines). It disables its hooks, stops writing, and goes dormant until the process exits. Documented, deliberate.
- ~~UI exit does not stop the Agent when background capture is enabled; otherwise UI sends `Shutdown`.~~ *(Corrected 2026-10-04: closing the UI never stops the Agent. `Shutdown` is sent only for an update, by the uninstall hook and for the admin mode's restart; the background-capture setting was read by nothing, and its switch is gone since beta.12 — `06_DATA_MODEL` §Settings registry.)*
- Single instance via named mutexes; the ring name is per-PID so multiple games can be captured simultaneously (rare but supported).
- **An alpha build's `--serve` waits for the Alpha notice (D74, 2026-10-31):** it reads `legal_acceptance` after opening the
ledger and, until the App's Legal Gate has recorded the notice at the version the build carries (`Shared.AlphaNotice`),
logs why and exits **8** — the logon task or the admin mode's prompt can start it before the App ever showed the notice.
The App holds its own start of the Agent while the gate is open and starts it at the Accept; the maintenance verbs
(`--register-vklayer`, `--install-task` and their reverses) are not held. The main line serves as before.
> **The single instance was specified here and not built until 2026-09-17**, and 0.1.0-beta.1 ran four Agents: an
> App started as administrator was refused by the pipe of the Agent already serving (`07_IPC` §C, amended the same
@@ -137,6 +142,8 @@ breadcrumbs\<pid>.json (corrected 2026-10-04: never created — the breadc
tmp\<sessionGuid>.partial crash-safety flush of raw buffers, every 60 s (04_CAPTURE §Ring draining)
covers\game-<id>-<ms>.png the images users chose for their games (beta.23, D60) — ~~covers\*.jpg, never created~~;
a store app's own artwork is shown from where that app keeps it, never copied here
backups\ledger-before-<v>.db an alpha build's copy of ledger.db before it first opened it, newest three (D73,
2026-10-31; 06_DATA_MODEL §Migrations) — the alpha shares this folder with the beta
```
*(beta.15, D52: `FrameLedger.exe --data-dir <folder>` reads a COPY of this folder instead — a viewer that starts and
+13 -7
View File
@@ -6,13 +6,13 @@ Requirement IDs (`FR-x`, `NFR-x`) are referenced by other docs, commits, and tes
### FR-1 Game library
- FR-1.1 Add game by picking an `.exe`, or drag-dropping an exe/shortcut.
- FR-1.2 Auto-import from Steam, GOG Galaxy, Epic, itch.io with a review checklist. **Import never enables hooking for anything.**
- FR-1.3 Editable metadata (name, cover, publisher, version, notes); auto-detected fields badged and overridable. *(The cover is built since beta.23, D60: the user's own image, else the Steam or GOG GALAXY app's artwork on this PC — `08_UI` §Games.)*
- FR-1.2 Auto-import from Steam, GOG Galaxy, Epic, itch.io with a review checklist — and, since beta.33 (D79), the Xbox app and the Microsoft Store (GDK titles: each drive's `.GamingRoot` folders and each game's package files, `05_DETECTION` §Platform signatures & metadata). **Import never enables hooking for anything.**
- FR-1.3 Editable metadata (name, cover, publisher, version, notes); auto-detected fields badged and overridable. *(The cover is built since beta.23, D60: the user's own image, else the Steam or GOG GALAXY app's artwork on this PC — `08_UI` §Games; since beta.33 also the square logo and splash image an Xbox game ships in its own package folder.)*
- FR-1.4 Remove game (asks whether to keep or delete its sessions).
- FR-1.5 "Supports" row shows shipped-capability hints (DLSS/FSR/XeSS/FG) — visually distinct from measured per-session values (`05_DETECTION` §Capability hints).
- FR-1.7 Delete all sessions (beta.11, owner decision D40): of one game from its page, or of every game from Settings ▸ Data, after a confirmation that says how many — with their frame and sensor series and notes; the library, the settings and every consent stay. The Agent deletes them (the rows are its, `06_DATA_MODEL` §Writer ownership) and refuses while a session it would delete under is being recorded.
- FR-1.8 Uninstalled games leave the library by themselves (beta.19, owner decision D55, amending D41): an entry whose executable has been gone for ten minutes — its drive connected and the folder it was installed in still there, so an unplugged or re-lettered drive never counts, and neither does a folder Windows will not list (`ExecutablePresenceProbeTests`) — and that has no session (stored, being recorded or waiting to be recovered) is removed by the Agent, behind Settings ▸ Data ▸ *Remove uninstalled games* (on by default). Never an entry carrying an anti-cheat block, an exception or a failed-trial mark (FR-2.2, rule 2). The App is told (`GameRemoved`).
- FR-1.9 Play (beta.21, owner decision D59): a game's page and each library entry start the game — through the app of the store whose own records name its folder (Steam, the Epic Games Launcher, GOG GALAXY, itch), or by the agent's launch mode (FR-3.2), as Settings ▸ Games says; never as administrator, and never in a viewer (`08_UI` §Games).
- FR-1.9 Play (beta.21, owner decision D59): a game's page and each library entry start the game — through the app of the store whose own records name its folder (Steam, the Epic Games Launcher, GOG GALAXY, itch), or by the agent's launch mode (FR-3.2), as Settings ▸ Games says; never as administrator, and never in a viewer (`08_UI` §Games). *(beta.33, D80: a game the Xbox app or the Microsoft Store installed starts through Windows in either mode — its package activated as its Start-menu tile does — and never by the agent's launch mode, which cannot start it in its package.)*
- FR-1.6 Recording switch per entry (2026-09-23, HANDOFF D29): off, the program is not watched at all — no session, no measurement, no injection — and a session of it that is running stops. On by default; entries an old import made for Steam's own tools start with it off. The library card says "Not recorded".
### FR-2 Hooking consent & control (new, safety-critical — see `19_SAFETY`)
@@ -57,7 +57,8 @@ Requirement IDs (`FR-x`, `NFR-x`) are referenced by other docs, commits, and tes
### FR-6 History & comparison
- FR-6.1 Sessions table per game: date, duration, tier badge, Native, Displayed, FG×, lows, resolution + upscaler, RT/PT/RR chips, crash badge, tags.
- FR-6.2 Compare 2–5 sessions; **mixed-tier comparisons require explicit acknowledgement** and are marked on the chart.
- FR-6.3 Hardware snapshot per session; trend charts mark changes ("GPU driver 572.16 → 576.02").
- FR-6.3 Hardware snapshot per session; trend charts mark changes ("GPU driver 572.16 → 576.02") — since beta.30 a
numbered badge per day that changed, its changes listed under the chart (owner decision D70).
- FR-6.6 Charts across a game's sessions (beta.11, owner decision D39): the Sessions tab opens with an overview of every hooked session's rate and lows (Presented FPS, or Native and Displayed where frame generation was measured; 1% and 0.1% lows), a click selecting the session; and the Trend draws more metrics beside the selected one, two units at most (the second against the right axis).
- FR-6.4 Sessions with mid-session settings changes are excluded from trends by default, with a toggle.
- FR-6.5 Session tags and notes.
@@ -111,8 +112,13 @@ Draw live FPS/frametime/upscaler info inside the game. Only for games already ho
- **NFR-5 Storage:** raw series ≤ 3 MB per hour compressed; 50 games × 50 sessions ≤ 500 MB at default retention.
- **NFR-6 Accuracy:** per `03_METRICS` §Accuracy budget, stated per tier.
- **NFR-7 Resilience:** power loss loses at most the last 60 s of raw data; DB never corrupts (WAL + transactions); Agent restart recovers `.partial` sessions as `interrupted`.
- **NFR-8 OS support:** Windows 10 22H2+ and Windows 11, x64. No ARM64 in v1.
- **NFR-9 Accessibility:** full keyboard navigation, adequate contrast in both Fluent themes, Per-Monitor V2 DPI awareness. *(What each clause means for this app, and the check that holds it: `08_UI` §Accessibility, P4 PR-8.)*
- **NFR-8 OS support:** ~~Windows 10 22H2+ and Windows 11, x64.~~ **Windows 11, x64** — the Windows that Microsoft
supports .NET 11 on, which FrameLedger is built on since 0.1.0-beta.37. **Windows 10 22H2 is not blocked** (the code
is still held to it: `SupportedOSPlatformVersion` 10.0.19045.0, CA1416) **and is neither tested nor supported**
there; a processor needs SSE4.2 and POPCNT (x86-64-v2), without which .NET 11 does not start. No ARM64 in v1.
*(Amended 2026-11-11, owner decisions D94 and D95 — `12_BUILD` §The main line's .NET. Windows 10 was never tested
on any version: `ACCESSIBILITY.md`, `08_UI` §Accessibility.)*
- **NFR-9 Accessibility:** full keyboard navigation, adequate contrast in both Fluent themes, Per-Monitor V2 DPI awareness. *(What each clause means for this app, and the check that holds it: `08_UI` §Accessibility, P4 PR-8.)* *(Widened 2026-11-09, beta.35, owner decisions D88–D91: and a screen reader reads every control and value and is told what changes; Windows contrast themes are followed; nothing is shown by colour alone. The goal behind all of it is WCAG 2.2 AA as W3C's WCAG2ICT applies it to desktop software — a goal, not a conformance claim — stated to users in `ACCESSIBILITY.md`.)*
- **NFR-10 Offline-first:** everything except updates and opt-in metadata works with zero connectivity.
- **NFR-11 Auditability:** the entire set of hooks is enumerable in `17_HOOK_ENGINE` §Hook inventory and matches the code; a reviewer must be able to verify in minutes that nothing reads game memory.
@@ -120,4 +126,4 @@ Draw live FPS/frametime/upscaler info inside the game. Only for games already ho
**Permanently:** any evasion technique (`19_SAFETY`); reading/writing game memory; kernel drivers; hardware control (overclocking, fan curves, power limits — `18_GPU_VENDOR_APIS` is read-only); online/competitive titles.
**v1:** Microsoft Store/UWP/Game Pass titles (packaged-app injection constraints); macOS/Linux; cloud sync; benchmark automation; ARM64. **Tier-1 capture of 32-bit games, including most Direct3D 9 titles** — the Overlay is x64-only and an x64 DLL cannot be loaded into a 32-bit process; those titles are Tier 2, which since 2026-08-28 means **not measured at all** — duration, sensors and the reason (`17_HOOK_ENGINE` §Build profile, `20_OPEN_QUESTIONS` §Scope).
**v1:** ~~Microsoft Store/UWP/Game Pass titles (packaged-app injection constraints)~~ *(narrowed 2026-11-03, beta.33, owner decisions D78–D80: Microsoft Store, Xbox app and PC Game Pass titles built on the GDK — full-trust packages — are in scope; what "the constraints" are was measured in `spike-notes` §25. UWP apps, which run in an app container, stay out: refused with a reason of their own)*; macOS/Linux; cloud sync; benchmark automation; ARM64. **Tier-1 capture of 32-bit games, including most Direct3D 9 titles** — the Overlay is x64-only and an x64 DLL cannot be loaded into a 32-bit process; those titles are Tier 2, which since 2026-08-28 means **not measured at all** — duration, sensors and the reason (`17_HOOK_ENGINE` §Build profile, `20_OPEN_QUESTIONS` §Scope).
+47 -3
View File
@@ -488,10 +488,34 @@ F_app = Σ fgEvaluations (APPLICATION frames, counted at the
> session has one. Rows: the states by rising factor, then *no frame generation*, then *not classified*. **Never an
> average across states** (CLAUDE.md rule 6), and ×5 and ×6 are 20 % apart and never pool.
>
> **Amended 2026-10-19 (beta.26): a window needs application frames, and a ratio frame generation can produce.**
> "≥ 8 samples and tokens" was built as eight presents and ONE token, and the owner's Silent Hill 2 session listed a
> ×1336.0 state — the session's first ten seconds, the game compiling its shaders, presented with one token per window
> (`spike-notes` §22); the DLSS line cited it. A window is now read only with ≥ 8 presents AND ≥ 8 application frames (`FgSlices.Slice.IsReadable`, both
> active and *no frame generation*), and is active only up to **×8** (`FgWindow.GenerationCeiling`: no shipping
> technology generates more than five frames per application frame, DLSS 4.5's ×6); every other window is *not
> classified*. The steady state reads the same windows, so it can no longer pick such a stretch either. A session-wide
> or live ratio that held above ×8 is refused as **`beyond_generation`** (after uniformity: a session that changed
> state stays `non_uniform` and keeps its steady state and its mix). **A stored mix is read by today's rule**
> (`FgMixRecord.Parse`): a row above ×8, or whose windows averaged fewer than eight application frames, joins the
> not-classified time — so the session stored with the ×1336.0 row reads ×2.0, ×3.0, ×6.1, no frame generation and
> 30 s not classified, and its shares still add up.
>
> **Amended 2026-10-20 (beta.27): a state is near a whole multiplier.** Every frame generation that ships multiplies by
> a whole number — ×2 for FSR, XeSS and DLSS 3, up to ×4 for DLSS 4, up to ×6 for DLSS 4.5 — and its windows read near
> one: 1.98, 3.01, 6.06. The owner's Silent Hill 2 session of 2026-10-20 under the NVIDIA App's *Dynamic* mode listed
> a **×2.52** state for 12.8 s: windows in which the multiplier stepped between ×2 and ×3 read ×2.21–×2.70 — at 135 s,
> 251 application frames followed by one generated frame and 270 by two — and three of them pooled into a state nobody
> held (`spike-notes` §23). A window is now active only within **10 %** of a whole multiplier of two or more
> (`FgWindow.IsNearWholeMultiplier`: ×1.8–×2.2, ×2.7–×3.3, … ×5.4–×6.6); a window between two is *not classified*, and
> the steady state reads the same windows. A stored mix is read by the same rule (`FgMixRecord.Parse`): that session
> reads ×2.0 27.30 %, ×3.0 62.41 %, no frame generation 2.93 % and 7.36 % not classified. Of the 70 sessions in the
> owner's ledger copy it was the only stored row between two multipliers.
>
> **When there is a mix.** Only where the session's frame generation was named (`Named` / `ActiveUnidentified`) and the
> session-wide count either stood or was refused as `NonUniform` / `AmbiguousBand` — a change of state is exactly what a
> mix describes. Every other refusal (not counted, unattributed, interleaved streams, either saturation, no
> evaluations, too short, no batches) gets none — slicing does not make a refused record set trustworthy, the steady
> evaluations, too short, no batches, and since beta.26 a ratio beyond any frame generation) gets none — slicing does not make a refused record set trustworthy, the steady
> state's rule — and so does a session in which no state formed.
>
> **Stored, never replayed.** `sessions.fg_mix` (schema 0020) holds the rows as JSON (`FgMixRecord`), written by the
@@ -511,7 +535,10 @@ F_app = Σ fgEvaluations (APPLICATION frames, counted at the
> in a game's menu is not read — it reaches the runtime through `sl::DLSSGOptions`, the route `HANDOFF` §2b refused —
> so the measured row is its evidence. The dynamic ceiling (`NGX_DLSSG_DYNAMIC_MULTI_FRAME_COUNT_MAX`) is decoded as
> `NGX_DLSSG_MULTI_FRAME_COUNT` is (frames generated per rendered frame) and the automatic target as "max refresh
> rate"; NVIDIA's header names neither, and owner-only item 20(a) checks both against the App.
> rate"; NVIDIA's header names neither, and owner-only item 20(a) checks both against the App. *(2026-11-06, beta.34:
> the ceiling's decode held on the owner's Phantom Blade Zero — a ceiling of 5 held states up to ×6.0, a ceiling of 2
> nothing above ×3.0 — `spike-notes` §26. And the context line is no longer the only place the Dynamic mode shows: the
> DLSS line names DLSS 4.5 where the driver reports Dynamic applied, D83, `05_DETECTION` §DLSS generation.)*
`fgEvaluations` is recorded per present by ~~the NGX/Streamline/FFX/XeSS FG hooks~~ the `slGetNewFrameToken`
detour; where Streamline never issued a token, by the FidelityFX dispatches — new PREPARE `frameID`s, else UPSCALE
@@ -614,6 +641,9 @@ carries the three shapes.
> *DLSS · NVIDIA App override*, *DLSS Quality*. The live card names what the report settles by itself
> (`upscalerQualityOverride`, `07_IPC`). Nothing infers a mode from the render scale (`HANDOFF` §7a). Silent Hill 2's
> own session reads no mode: its word lacks `CREATED | EVALUATE`, so no super resolution ran that the driver saw.
> *(Corrected 2026-10-20: it lacked them because the word stored had been read after the game closed — §The
> driver-reported rung. A session recorded from beta.27 keeps them; one recorded before, on a title no hook names, never
> reads the override's mode.)*
From the upscaler hooks we get, per frame:
@@ -726,6 +756,16 @@ Tier 2 has none of this: `upscaler = unknown`, ratio `N/A`.
> same word through `SessionProgress.upscalerDriverReported` (`07_IPC`). Segments carry no driver word: the driver's
> bookkeeping is per process, not per settings change. **Nothing native changed and no NGX hook was added**: the
> licence bar in `20_OPEN_QUESTIONS` stands.
>
> **Corrected 2026-10-20 (beta.27): every stored word had lost the rung.** The loop asked the driver once more after its
> last drain — on a session that ended because the game closed, after the game had gone — and that answer, the last,
> was the state (`NgxDriverState`: "the last ANSWERED reading is the state"). The driver still answers for the pid,
> with `CREATED | EVALUATE` cleared: Expedition 33 read `0x8067F` while it ran (2026-09-06) and its stored sessions
> `0x8007F`, the same word without the two bits. Of the 14 sessions in the owner's ledger copy in which the driver
> answered, none kept them — so no stored session reads *DLSS (driver-reported)*, and none on an NGX-direct title under
> an NVIDIA App override reads its mode (D63). Since beta.27 the driver is not asked once the game has gone, and the
> two bits stand once a reading carried them: a game releasing its features on its way out no longer unsays them, and
> every other bit is still the last reading's. Sessions recorded before keep what they stored (`spike-notes` §23).
**The render scale over time (beta.14, D49).** The session summary draws `100 × √(render pixels / output pixels)` — the
per-axis scale, `100 / upscale_ratio` — as steps over the session: from the `render_res` blob where the resolution
@@ -855,7 +895,11 @@ and how much of the time". Schema 0016 (`06_DATA_MODEL`), shared-memory region 4
excludes a pause to within one tick at each edge, as the frame series' gap does. A mode's **share** is its milliseconds
over the observed time (every mode but *No window*). `display_changes` counts samples whose mode differs from the one
before, no-window samples skipped. The sizes — `display_window_*` (client area), `display_buffer_*` (back buffer),
`display_monitor_*` and `display_monitor_hz` — are the ones seen in the mode that lasted longest; `display_source` is the
`display_monitor_*` and `display_monitor_hz` — are the ones seen in the mode that lasted longest *(corrected 2026-10-20,
beta.27: the last ones a sample of that mode SAW — a game leaving exclusive fullscreen closes its window while its swap
chain's last word is under 2 s old, and those last samples, exclusive with no window, had replaced every size: two Lies
of P and three Dark Souls III sessions stored none. A mode no sample of which saw its window keeps the back buffer
alone)*; `display_source` is the
strongest witness any sample had (`swapchain` > `opengl` > `window`). `sessions.swap_effect`, a column since 0001 with no
writer, is written from region 4.
+11 -2
View File
@@ -132,6 +132,7 @@ which makes the notification more important than it was, not less.
## Process watcher
- 1 Hz snapshot via `CreateToolhelp32Snapshot` (CsWin32): pid, ppid, exe path (`QueryFullProcessImageName`).
- **One spelling of the exe path for the whole capture path (beta.33).** The watcher keys a game on the kernel's image name (`QueryFullProcessImageName`), and `TargetResolver`, which re-finds the game just before the guard, read the loader's (`Process.MainModule`) until beta.33: for a game started through a junction — a package Windows activates from `C:\Program Files\WindowsApps\<package>`, a junction to the game's own folder — the two could differ, and the session would end `TargetNotRunning` about a game the watcher had just matched. Both read `Infrastructure.Io.ProcessImagePath` now; the resolver still opens a candidate with the guard's own rights (`PROCESS_QUERY_LIMITED_INFORMATION | PROCESS_VM_READ`), so a process an anti-cheat driver closes stays `TargetUnreadable` (D21). `spike-notes` §25 measured the two spellings equal on the owner's eleven Xbox titles; one reader keeps them equal by construction (`TargetResolverTests`).
- Watchlist match on normalized full path (~~`GetFinalPathNameByHandle`~~ `File.ResolveLinkTarget` *(corrected 2026-10-04 — `ExecutableIdentity` says why)* — junctions/symlinks), ~~filename fallback with a stale-path warning badge~~ **and a file name alone never starts a session (2026-09-23, HANDOFF D25): it can only be the entry's own executable on a drive that changed its letter (the relocator's rule), or it is not in the library.**
- Process tree assembled from ppid chains; the **capture target** is the descendant that actually presents. In launch mode we know it; in attach mode we wait for the first ring handshake. ~~or (Tier 2) elect the PID with the most presents in the first 10 s~~ — there is no Tier-2 present stream to elect from. Re-elect if the presenting PID dies while the tree lives (level-transition relaunches).
@@ -160,7 +161,12 @@ which makes the notification more important than it was, not less.
> now remembers the newest such process per executable and starts its session when the running one ends, if that one
> ended on its own (not cancelled with the host), the process is the same (pid and start time) and it is then the
> executable's ONLY process — a helper of a game still running has the game beside it and stays turned away, as before
> (`CaptureOrchestratorTests`: the restart recorded, the helper not, a process that left meanwhile not). **Behaviour change:** a game whose folder moved (not its drive letter) records nothing until
> (`CaptureOrchestratorTests`: the restart recorded, the helper not, a process that left meanwhile not). *(beta.27,
> 2026-10-20:)* a launch never said it had ended on its own, so after **Play** ▸ *Start directly* nothing turned away
> while it ran was ever recorded — Lies of P hands itself to Steam within seconds, and twice on 2026-10-19 the game
> Steam started went unrecorded (`spike-notes` §23). A launch now says so, with the processes it and its election
> recorded: the one it started appears to the watcher after the launch began and is turned away like any other, and a
> launch the user stopped does not start again on it. **Behaviour change:** a game whose folder moved (not its drive letter) records nothing until
> *Change executable* points its entry at the new file. `ProcessTree` reads ppid chains with the one rule that defeats pid
> reuse: a child that started before its parent is not its child. `DescendantElection` picks the newest-started
> descendant whose image is tracked — a launcher's consent does not extend to what it spawns, so the elected image
@@ -237,6 +243,8 @@ which makes the notification more important than it was, not less.
**Attach mode.** Game launched from Steam/GOG/Epic normally; watcher sees it, guard runs, inject. Feature hooks install late, so early-init facts may be missed; the Overlay compensates by re-reading state on the first `EvaluateFeature` call it does observe, and the session is flagged `late_attach = true` so the UI can note that startup-time settings may be incomplete.
> **A game the Xbox app or the Microsoft Store installed is always attach mode (beta.33, D80).** Windows starts it through its package — **Play** runs `explorer.exe shell:AppsFolder\<AUMID>` in either mode — and started by its path it is never the game in its package (`spike-notes` §25: `CreateProcess` of the launch executable makes Windows activate the package itself, so the game is not the launcher's descendant; of an Unreal shipping executable, the game runs outside its package). So `LaunchGame` for an executable whose install root is a GDK package root answers `PackagedGame` and starts nothing (`OrchestratorOptions.IsPackaged` = `GdkPackageFiles.IsInPackage`), the watcher records the game when it appears, and the session is `late_attach`: §25 measured an Unreal title's D3D device 2.4–3.7 s after its process, a Unity title's 0.1–1.2 s, so what ran before the hook is in `dxgiPresentsBeforeHook`. The Vulkan layer's switch (`FRAMELEDGER_ENABLE_VK_LAYER=1`) is set only by `ProcessLauncher`, so a Vulkan GDK title cannot get it (`20_OPEN_QUESTIONS` §G).
~~Steam users can also set FrameLedger as a launch option wrapper; documented in the UI rather than automated (never modify a user's Steam config for them).~~ *(Corrected 2026-10-04: not built — there is no wrapper entry point and no UI text; a game started from Steam is recorded in attach mode. The parenthesis still holds: never modify a user's Steam config for them.)*
## The guard
@@ -420,7 +428,8 @@ because a layer cannot leave a running game's loader chain.
> - **Recovery never throws.** A file it cannot finalize is set aside as `<guid>.partial.failed` (never retried, kept for
> a bug report) and reported `Failed`; the next file is recovered, and the watcher starts either way.
> - The Agent's host logs through Serilog since the same day: a background service that stops the host is now in
> `agent-*.log`, where before it was in no file at all.
> `agent-*.log`, where before it was in no file at all. *(Since beta.37, on .NET 11, that service's exception also
> ends the Agent through its crash report instead of an exit 0 — `10_LOGGING` §Crash handling.)*
> **Built 2026-09-10 (P2 PR-D): `Application.Recording`.** The state machine above is the intent; what
> runs is one class per box. `SessionRecorder` owns a session end to end — the row's identity and time
+58 -7
View File
@@ -70,7 +70,7 @@ Rules are **data, not code**: `rules/detection-rules.json`, bundled ~~and updata
The `anticheat` block is the same file that feeds the hard guard in `19_SAFETY` — shipping it as updatable data is what lets a newly-protected game be blocked without waiting for an app release. ~~**Rules updates that touch the `anticheat` block are treated as security updates:** applied on next check regardless of the user's auto-update preference for other rules.~~ *(Corrected 2026-10-04: there is no feed and no auto-update preference, so today a newly-protected game waits for a release; the sentence is what a feed must do once built, §S20.)*
Signal types evaluated by `RuleEvaluator` (Domain): `file_exists`, `dir_exists`, `sibling_glob`, **`path_contains`**, `pe_company_contains`, `pe_product_contains`, `strings_contains` (bounded 8 MB scan), `manifest_field`. Combine with `all` / `any` — **not nested**, which schemaVersion 2 forbids. Version extractors: `pe_file_version` (of the sibling its `from` names, not of the executable), `pe_product_version_regex`, **`strings_regex`**, `manifest_field`, and since 2026-09-27 **`unreal_build`** (no parameter; decided in code, §Engine version). A regex extractor must capture exactly **one** group — the evaluator returns the first — and `rules-validate.ps1` refuses any other count and any pattern that does not compile (both promised by the rules file's `$comment` and enforced by nothing until beta.10).
Signal types evaluated by `RuleEvaluator` (Domain): `file_exists`, `dir_exists`, `sibling_glob`, **`path_contains`**, `pe_company_contains`, `pe_product_contains`, `strings_contains` (bounded 8 MB scan), `manifest_field`, and since beta.33 **`root_file`** — an exact file name directly in the install root, answered from that one folder's own listing (`GameFileSnapshot.RootFiles`), so a deep walk that ran short makes its miss no less certain; a root that could not be listed makes it `Unknown`. Combine with `all` / `any` — **not nested**, which schemaVersion 2 forbids. Version extractors: `pe_file_version` (of the sibling its `from` names, not of the executable), `pe_product_version_regex`, **`strings_regex`**, `manifest_field`, and since 2026-09-27 **`unreal_build`** (no parameter; decided in code, §Engine version). A regex extractor must capture exactly **one** group — the evaluator returns the first — and `rules-validate.ps1` refuses any other count and any pattern that does not compile (both promised by the rules file's `$comment` and enforced by nothing until beta.10).
> `path_contains` and `strings_regex` were in the shipped data and the schema
> and missing from this list; the schema's own `$comment` said so and nobody had
@@ -312,6 +312,7 @@ engine compiled only, reads as not found. One Ren'Py install was measured.
| Platform | Signals | Metadata |
|---|---|---|
| Xbox *(beta.33, D79; first in the array)* | **both** `MicrosoftGame.config` and `appxmanifest.xml` directly in the install root (`root_file`, `all`): a GDK package root. First because a GDK build can ship Steam's DLL — every FINAL FANTASY Pixel Remaster from the Xbox app carries `Plugins\x86_64\steam_api64.dll` (`spike-notes` §25) — and a `root_file` miss is never `Unknown` for want of a deep walk, so a large Steam install behind it still reads *steam* | each drive's `.GamingRoot` → `<games folder>\<Game>\Content\`: `MicrosoftGame.config` (Identity, ShellVisuals, ExecutableList, StoreId) and `appxmanifest.xml` (the Application id); the package family name and its registration from Windows (`PackageFamilyNameFromId`, `GetPackagesByPackageFamily`) |
| Steam | `steam_api64.dll`/`steam_api.dll` sibling, or path contains `steamapps\common` | nearest `steamapps/appmanifest_<id>.acf` (walk up): `appid`, `name`, `buildid` → version |
| GOG | `goggame-<id>.info` sibling, or `Galaxy64.dll` | `.info` JSON: `gameId`, `name`, `version` |
| Epic | `EOSSDK-Win64-Shipping.dll`~~, or path under an Epic install~~ *(corrected 2026-10-04: the rule has no path signal)* | `%ProgramData%\Epic\EpicGamesLauncher\Data\Manifests\*.item` matched by `InstallLocation` |
@@ -324,9 +325,12 @@ engine compiled only, reads as not found. One Ren'Py install was measured.
> (`StoreRecords.Owning`, as Play finds it). `Infrastructure.Art.SteamArtCache` and `GogArtCache` read them; nothing is
> downloaded, so the *(opt-in)* online lookup in the publisher/version order below still does not exist. Epic, itch and
> other stores keep no image files: their games show the image the user chooses, or none. The detail: `08_UI` §Games ›
> Game detail, *The header's cover*.
> Game detail, *The header's cover*. *(beta.33: an Xbox game ships its own — `Infrastructure.Art.XboxArtCache` reads the
> `Square480x480Logo` (else `Square150x150Logo`) and the `SplashScreenImage` its `MicrosoftGame.config` names, inside
> the package root only, as a square cover and the banner; `IStoreArtCache.Find` takes the owning record rather than the
> id, because those pictures live in the install folder.)*
**Auto-import (FR-1.2):** Steam via `libraryfolders.vdf` → all `appmanifest_*.acf` except `SteamLibrarySource.KnownTools` (2026-09-22: Steamworks Common Redistributables, Borderless Gaming, Wallpaper Engine, SteamVR, the Proton and Steam Linux Runtime entries, Blender — tools Steam's manifests do not distinguish from games, and which became library rows the watcher recorded); GOG via `HKLM\SOFTWARE\WOW6432Node\GOG.com\Games\*`; Epic via `Manifests\*.item`; itch by receipt scan. Import presents a review checklist; nothing is launched, nothing is hooked on import.
**Auto-import (FR-1.2):** Steam via `libraryfolders.vdf` → all `appmanifest_*.acf` except `SteamLibrarySource.KnownTools` (2026-09-22: Steamworks Common Redistributables, Borderless Gaming, Wallpaper Engine, SteamVR, the Proton and Steam Linux Runtime entries, Blender — tools Steam's manifests do not distinguish from games, and which became library rows the watcher recorded); GOG via `HKLM\SOFTWARE\WOW6432Node\GOG.com\Games\*`; Epic via `Manifests\*.item`; itch by receipt scan; *(beta.33)* Xbox by each drive's `.GamingRoot` and each game's package files. Import presents a review checklist; nothing is launched, nothing is hooked on import.
> **Built 2026-09-14 (P4 PR-4).** `Application.Import.LibraryImporter` over four `IStoreLibrarySource` adapters in
> `Infrastructure.Import` — `SteamLibrarySource` (`libraryfolders.vdf` + `appmanifest_*.acf` through
@@ -363,6 +367,22 @@ engine compiled only, reads as not found. One Ren'Py install was measured.
> is fetched (CLAUDE.md rule 8's "opt-in store metadata" is the online lookup, which does not exist). First-run
> step 4 now points at File ▸ Import library… rather than saying "later build".
> **beta.33 (owner decisions D78/D79, `spike-notes` §25): the Xbox app's and the Microsoft Store's games.**
> `XboxLibrarySource` reads each ready fixed or removable drive's `.GamingRoot` (`GamingRoots`: `RGBX`, a count, UTF-16
> folder names relative to the drive), lists the `<games folder>\<Game>\Content\` folders that are GDK package roots
> (`GdkPackageFiles`: `MicrosoftGame.config` beside `appxmanifest.xml`, read with DTDs prohibited and a 1 MB cap), and
> keeps those whose package Windows says is installed for this user (`PackageFamilyNameFromId`, then
> `GetPackagesByPackageFamily`). The record: the store id is the package family name, the install directory is `Content`
> (the spelling the game's own process reports — never the `C:\Program Files\WindowsApps` junction, whose name carries
> the version), the launch key is the AUMID `<family name>!<Application Id>` that Play activates, the version is the
> package's. It names no executable, so `ExecutableLocator` ranks: the WinGDK or Win64 shipping binary over the stub the
> package launches, the Unity player over its crash handler, never `gamelaunchhelper.exe` (a runtime helper since
> beta.33), with the folder above `Content` as the install's name. **What cannot be read:** every game `.exe` under
> `Content` refuses `FILE_READ_DATA` to a process outside its package, so its PE header, version resource, imports and
> strings are not read — the architecture reads `unknown` (never "not x64", so nothing is turned off for it), no Unreal
> version is shown, and the Unity version still reads, from `UnityPlayer.dll`. A UWP app has no `MicrosoftGame.config`
> and is not listed (D78).
> **beta.19 (owner report 2026-10-12): a store's own pick can be a helper, and a launcher is not the game.** The owner's
> A Doll's Locket - Remake (itch 5085165, RPG Maker MZ) was imported as `Dolls Locket\notification_helper.exe` — NW.js's
> toast helper. The pick was **butler's verdict**, taken as is: butler stores a *filtered* verdict (the shallowest
@@ -445,7 +465,9 @@ App's DLSS override loads the driver's `nvngx_dlss.dll` from the driver store un
2026-10-19: unmeasured, and the one measurement says otherwise — the owner's Silent Hill 2 session ran ×6 frame
generation through the NVIDIA App's override and no module with a census name was loaded. Since beta.24 every module
under `%ProgramData%\NVIDIA\NGX` is recorded whatever its name, with its folder class — §DLSS generation below —, and
owner-only item 20(c) records what the override loads.)* The session summary prints the loaded list and names such a
owner-only item 20(c) records what the override loads.)* *(Measured 2026-10-19, `spike-notes` §22: under the
override, Silent Hill 2 loaded `160_E658700.bin` 310.9.16.0 and `1B0_E658703.dll` 2.14.16.0 from the NGX folder —
names no census lists; which feature each serves is not established.)* The session summary prints the loaded list and names such a
difference ("the game ships 3.7.10.0: another copy was loaded"); since beta.24 the DLSS line says where each DLSS
library was loaded from (the game, the graphics driver, Windows) — by folder, never who put it there.
@@ -460,12 +482,27 @@ never the path), and the super-resolution preset the driver reports applied:
|---|---|---|
| Super-resolution render preset **L or M** that the NVIDIA driver reports applied, in a session where super resolution ran | DLSS 4.5 (2nd-gen transformer) | `ngx_driver_words` — the SR word's `PRESET` bit and `renderPreset`; presets L/M arrived with DLL 310.5.0 (NVIDIA's DLSS 4.5 release, driver 591.74) |
| A DLSS Frame Generation state measured at **×5 or more** | DLSS 4.5 (Dynamic / 6× multi-frame generation) | `fg_mix` / `fg_factor` with `fg_mode = dlssg` |
| The NVIDIA App's **Dynamic** frame generation — set in the game's profile and reported applied by the driver — in a session where DLSS Frame Generation was identified *(beta.34, owner decision D83)* | DLSS 4.5 (Dynamic multi frame generation, set in the NVIDIA App) | `driver_profile`'s `NGX_DLSSG_MODE` = 4 (dynamic), `ngx_driver_words`' FG word with `FG_MODE` (bit 13), `fg_mode = dlssg` |
| Preset **J or K** reported applied | DLSS 4 (transformer) | as above |
| A DLSS Frame Generation state at **×3 or ×4** | DLSS 4 (multi-frame generation) | as above |
| `nvngx_dlss.dll` **2.x** | DLSS 2 | `runtime_modules` |
| `nvngx_dlss.dll` **3.x**, or `nvngx_dlssg.dll` **1.x–3.x** | DLSS 3 | `runtime_modules` |
| A **310.x** library alone, a CNN preset (A–F), ×2 | *no label* — the versions are shown | DLSS 4 and 4.5 ship the same major number; the preset is what names the model |
| `nvngx_dlssnr.dll` loaded | "DLSS 5 runtime loaded" — never a generation of these features | the module name is community-sourced until owner-only item 20(d) sees it load |
| ~~`nvngx_dlssnr.dll` loaded~~ | ~~"DLSS 5 runtime loaded" — never a generation of these features~~ | ~~the module name is community-sourced until owner-only item 20(d) sees it load~~ *(replaced 2026-11-06 by the two rows below, D84)* |
| DLSS 5's neural rendering **evaluated** — `kFeatureDLSS_NR` (Streamline 2.14) on some of the frames the game rendered through Streamline, seen by an Overlay that decodes it *(beta.34, owner decision D84)* | DLSS 5 (neural rendering on N % of rendered frames) — **heads the table** | `dlss_nr_pct` (schema 0022), from `FL_FEAT_SL_NEURAL_RENDERING` under `FL_HOOK_SL_NEURAL_RENDERING` |
| `nvngx_dlssnr.dll` loaded, neural rendering not seen evaluated | "DLSS 5 runtime loaded" — and "…, not seen running" where an Overlay that decodes it drained Streamline batches and none carried it (0 %); never a generation | `runtime_modules` (the name seen on Hogwarts Legacy, 2026-11-06) and `dlss_nr_pct` |
**Amended 2026-11-06 (beta.34, owner decision D83): Dynamic is DLSS 4.5's.** The NVIDIA App's *Dynamic* frame
generation and its ×6 mode exist only in DLSS 4.5, so a session the driver reports running Dynamic is DLSS 4.5 whatever
multiplier the mode chose: the owner's Phantom Blade Zero under *Dynamic, up to ×3* held ×2.0 and ×3.0 — nine hooked sessions
from 2026-11-03 to 11-05 — and read *DLSS 4 (a ×3.0 frame-generation state)* until then. The row needs all three: the
profile's Dynamic (`NGX_DLSSG_MODE` = 4, NVIDIA's own name for the value), the driver's report that its frame-generation
override applied in the game's process (the FG word's `FG_MODE` bit), and DLSS Frame Generation identified in the session
(`fg_mode = dlssg`; its factor need not have been counted) —
a profile set to Dynamic that the driver never applied is a setting, not evidence. The driver's own mode number is not
read: it answers 3 under Dynamic and 1 under *Fixed* on every stored session (`spike-notes` §26), and NVIDIA's header
names neither. A *Fixed* ×5 or ×6 is not this row — Witcher 3 under the App's Fixed ×6 still presented ×2.0 — and
names DLSS 4.5 only where a state is measured at ×5 or more, which ranks above it.
Never a default preset inferred from a version: what a DLL "would" run by default is the game's and the driver's to
decide. A preset the driver applied to a super resolution it never saw created and evaluated names the model of
@@ -473,7 +510,21 @@ nothing and is not used (the owner's Silent Hill 2 session: preset L applied, no
the ×6.0 state's). **Sources:** NVAPI's `NV_NGX_DLSS_OVERRIDE_GET_STATE_PARAMS_V1` (the vendored
`src/native/third_party/nvapi/nvapi.h`); presets L/M with DLL 310.5.0 — PCGH's DLSS 4.5 test and NVIDIA's driver
591.74 release notes; DLSS 4.5's Dynamic MFG and 6× — NVIDIA's announcement (driver 595, RTX 50); DLSS 5 — NVIDIA's
GTC 2026 announcement and its 2026-09-03 launch; `nvngx_dlssnr.dll` — community reports only.
GTC 2026 announcement and its 2026-09-03 launch; ~~`nvngx_dlssnr.dll` — community reports only~~ `nvngx_dlssnr.dll` —
loaded by the owner's Hogwarts Legacy with Neural Rendering on, 310.9.16.0 from the game's folder (2026-11-06,
`spike-notes` §26), beside its Streamline plugin `sl.dlss_nr.dll`; `kFeatureDLSS_NR = 1004` — Streamline `v2.14.16`'s
public `sl_core_types.h` (re-vendored for it, `src/native/third_party/streamline/README.md`).
**Amended 2026-11-06 (beta.34, owner decision D84): DLSS 5 is named where it ran.** Until then a session could say only
that DLSS 5's runtime was LOADED — and Hogwarts Legacy, Neural Rendering on, loaded it. The Overlay's
`slEvaluateFeature` detour now decodes `kFeatureDLSS_NR` into its own per-frame fact (`FL_FEAT_SL_NEURAL_RENDERING`,
the feature byte's last bit, under the condition every Streamline fact shares) and publishes
`FL_HOOK_SL_NEURAL_RENDERING` with the detour; the Agent stores the share of Streamline batches that carried it
(`dlss_nr_pct`) **only from a writer that published that family** — an older Overlay drains the same batches and never
sets the bit, and its silence must not read as 0 %. Above every other row because DLSS 5 is named for that feature as
DLSS 4.5 is for its own: the session's super resolution, ray reconstruction and frame generation are the libraries the
line lists after it. Whether the game routes neural rendering through `slEvaluateFeature` at all is owner-only item
30(a)'s run; a title that does not reads *runtime loaded*, never *not running*.
## Anti-cheat pre-scan (static)
@@ -507,7 +558,7 @@ Three things this section previously implied that are not true, and are worth st
> the user's and stays; a `detected` entry is refreshed; **an empty field with no entry has nothing to protect
> and is filled and badged `detected`** — without that clause a freshly added game could never receive an
> engine at all, since `EnsureAsync` writes no provenance. A null detected value erases nothing.
> `capability_flags` is written whole every run (a JSON array of the rule ids — `dlss`, `dlss_g`, `dlss_rr`,
> `capability_flags` is written whole every run (a JSON array of the rule ids — `dlss`, `dlss_g`, `dlss_rr`, `dlss_nr` (beta.34),
> `streamline`, `fsr`, `xess`, `xefg`) because the Supports row has no user-edit surface and a stale "Supports
> DLSS-G" after the DLL left is the confusion §Capability hints exists to prevent.
- Strings scans bounded to 8 MB, local only.
+33 -5
View File
@@ -43,7 +43,7 @@ CREATE TABLE games (
exe_path TEXT NOT NULL UNIQUE, -- where the executable lives; rewritten by ExecutableRelocator when the
-- SAME bytes (exe_size_bytes, exe_mtime_ms) turn up under another drive
-- letter (2026-09-22), and by Change executable for a DIFFERENT binary
platform TEXT NOT NULL DEFAULT 'none', -- steam|gog|epic|itch|none
platform TEXT NOT NULL DEFAULT 'none', -- steam|gog|epic|itch|xbox|none (xbox since beta.33, D79; no CHECK constraint, so no migration)
store_id TEXT,
engine TEXT, engine_version TEXT,
-- (schema 0015, ALTERed last) engine_version_source TEXT: where engine_version came from — a
@@ -252,7 +252,8 @@ CREATE TABLE sessions (
fg_source TEXT, -- api|cadence|manual (`etw` removed 2026-08-28: no producer, no tier)
fg_factor REAL,
-- schema 0003 (2026-09-14): why fg_factor is NULL while fg_mode names a technology — FgRefusalKind as
-- Vocabulary.FgRefusal spells it (not_counted, no_evaluations, non_uniform, dxgi_saturated, …). NULL when a
-- Vocabulary.FgRefusal spells it (not_counted, no_evaluations, non_uniform, dxgi_saturated, …; beyond_generation
-- since beta.26: a ratio above FgWindow.GenerationCeiling that held throughout). NULL when a
-- factor stands or the writer predates the column. A REASON for the UI, never an input to fg_mode or a number.
fg_refusal TEXT,
-- FlWriterState.runtimeCensus, raw (FlRuntimeCensus bits). Which vendor runtime modules
@@ -319,6 +320,9 @@ CREATE TABLE sessions (
-- schema 0021 (2026-10-19, beta.24, D64): each loaded runtime module's folder class — 05_DETECTION §DLSS generation
runtime_module_sources TEXT, -- {"nvngx_dlss.dll":"graphics_driver", …}: game | graphics_driver | windows; never a path
-- schema 0022 (2026-11-06, beta.34, D84): DLSS 5's neural rendering — 05_DETECTION §DLSS generation
dlss_nr_pct REAL, -- 0–100 of the Streamline batches that evaluated kFeatureDLSS_NR; NULL = nothing could tell
-- schema 0020 (2026-10-19, beta.24, D62): every frame-generation state the session held — 03_METRICS §The mix
fg_mix TEXT, -- {"Rows":[{"Kind":"generated","Factor":4.0,"NativeFps":…,"DisplayedFps":…,
-- "Seconds":…,"Share":…,"Windows":…}, …]}: states by rising factor, then
@@ -336,7 +340,7 @@ CREATE TABLE sessions (
display_nowindow_ms INTEGER, -- no window could be read
display_changes INTEGER, -- mode changes between samples
display_source TEXT, -- swapchain | opengl | window: the strongest witness any sample had
display_window_w INTEGER, display_window_h INTEGER, -- client area, in the mode that lasted longest
display_window_w INTEGER, display_window_h INTEGER, -- client area, in the mode that lasted longest (the last seen, beta.27)
display_buffer_w INTEGER, display_buffer_h INTEGER, -- the swap chain's back buffer, same mode
display_monitor_w INTEGER, display_monitor_h INTEGER, display_monitor_hz INTEGER
);
@@ -419,7 +423,9 @@ CREATE TABLE settings (key TEXT PRIMARY KEY, value TEXT NOT NULL);
CREATE TABLE legal_acceptance (doc TEXT PRIMARY KEY, version TEXT NOT NULL, accepted_at INTEGER NOT NULL);
```
> **Written since 2026-09-14 (P3 PR-9).** `doc` is one of `eula` / `gpl` / `disclaimer` / `privacy`
> **Written since 2026-09-14 (P3 PR-9).** `doc` is one of `eula` / `gpl` / `disclaimer` / `privacy` *(and `alpha` since
> 2026-10-31, D74: the Alpha notice, written by an alpha build's gate only and read by an alpha's Agent before it serves;
> a beta never reads that row)*
> (`App.Services.LegalDocuments.Keys`); `version` is the document's own `**Version:**` line as embedded in the
> App at build (`GPL-3.0-only` for the licence text) — the App is the only writer, one row per document per
> Accept, re-recorded when the embedded version differs from the row's. `20_OPEN_QUESTIONS` §G "Legal doc
@@ -543,6 +549,16 @@ Default: raw blobs for the **last 20 sessions per game** (configurable N or unli
## Migrations
> **The alpha's copy before it opens the ledger (D73, 2026-10-31).** An alpha build shares this file with the beta, so
> before it first opens it — the App or the Agent, whichever comes first — `LedgerDatabase.OpenAsync(backupFirst:)`
> copies it whole with SQLite's online backup into `backups\ledger-before-<version>.db` beside it
> (`Infrastructure.Persistence.LedgerBackup`), once per alpha version, under a lock of its own
> (`Local\FrameLedger.Ledger.Backup.<hash of the path>`, waited on for five minutes — the migration lock gives a waiter
> 30 s). The newest three copies are kept and only files so named are deleted. A copy that cannot be made — no room, the
> folder unwritable — throws `LedgerBackupException` and the ledger is not opened: the App says so in its start-failure
> dialog, the Agent exits 7 (*ledger refused*) with the reason in its log. The main line passes no request and copies
> nothing; a viewer (D52) reads a copy and makes none. Every case is `LedgerBackupTests`', in scratch folders.
Sequential embedded SQL (`Migrations/0001_init.sql`, `0002_*.sql`, …), applied at startup by whichever process opens the DB first, guarded by `schema_migrations` + a named mutex. Never edit an applied script; only append.
> **`0002_annotation_overrides_and_removal.sql` (P3 PR-3, 2026-09-13) — the first append**, and the first
@@ -688,7 +704,9 @@ Sequential embedded SQL (`Migrations/0001_init.sql`, `0002_*.sql`, …), applied
> frame generation was named and whose count stood or was refused only as `non_uniform` / `ambiguous_band`; NULL
> otherwise. A session before it has none and is **never rebuilt** from its `frame_blobs` (one Generated bit per frame,
> the DXGI-counted presents lost). The `.partial` needs no change: a recovered session is aggregated from its records
> like any other. `LatestVersion` is 20; `LedgerDatabaseTests.ScriptTwentyAddsTheFgMixColumnAndAnEarlierSessionHasNone`,
> like any other. **Read by today's rule since beta.26:** `FgMixRecord.Parse` folds a stored state no window of the build
> would form (above ×8, or under eight application frames a window) into the not-classified time — beta.24 and beta.25
> stored one (`spike-notes` §22). `LatestVersion` is 20; `LedgerDatabaseTests.ScriptTwentyAddsTheFgMixColumnAndAnEarlierSessionHasNone`,
> `SqliteSessionRepositoryTests.ASessionRoundTripsColumnForColumn`. **A beta.23 cannot open a ledger beta.24 migrated.**
> **`0021_runtime_module_sources.sql` (beta.24, 2026-10-19, owner decision D64) — where each loaded module lived.** One
@@ -700,6 +718,16 @@ Sequential embedded SQL (`Migrations/0001_init.sql`, `0002_*.sql`, …), applied
> from its crash file (which carries no module list). `LatestVersion` is 21;
> `LedgerDatabaseTests.ScriptTwentyOneAddsTheModuleSourcesColumnAndAnEarlierSessionHasNone`, the repository round trip.
> **`0022_dlss_nr.sql` (beta.34, 2026-11-06, owner decision D84) — DLSS 5's neural rendering, measured.** One REAL column,
> ADD COLUMN only: `dlss_nr_pct`, the share (0–100) of the presents that drained a Streamline evaluation on which the game
> evaluated `kFeatureDLSS_NR` (`Domain.Metrics.NeuralRendering`). Written by the recorder's aggregation
> (`SessionAggregator.ApplyRt`) **only when the writer published `FL_HOOK_SL_NEURAL_RENDERING`** — an Overlay older than
> the script drains the same batches and never sets the bit, so its NULL is "could not tell", never 0. NULL before, and
> never rebuilt (`frame_blobs` keep no feature byte); a session recovered from its crash file is re-aggregated from its
> raw records and keeps it. `LatestVersion` is 22;
> `LedgerDatabaseTests.ScriptTwentyTwoAddsTheNeuralRenderingColumnAndAnEarlierSessionHasNone`, the repository round trip.
> **A beta.33 or alpha.2 cannot open a ledger beta.34 migrated** (the alpha keeps its copy first, D73).
> **Every open used to migrate, and one that should not have did — 2026-09-16.** The Agent's `--console sessions`,
> a verb that prints, was run against the owner's ledger while the file on disk was at schema 2 and applied 0003 and
> 0004 to it. `LedgerDatabase.OpenReadOnlyAsync` exists since that day: an existing file, `PRAGMA query_only`, no
+1 -1
View File
@@ -393,7 +393,7 @@ Unchanged in spirit from v1, bumped to `v2` for the new message set.
| `Hello` | UI→A | `{ appVersion, protocol: 2 }` → `HelloAck { agentVersion, protocol, pid, elevated, overlayBuildId, vulkanLayerRegistered, telemetrySource /* composite, e.g. l1+lhm+nvapi */, cpuTempAvailable, disclosureVersion /* P3 PR-4, D14: the FR-2.1 text this Agent stamps against */, exceptionDisclosureVersion /* D33, 2026-09-26: the user-mode exception's disclosure this Agent grants against */, elevationOutcome /* beta.10, D34: the admin mode's answer at this start — granted, declined, other-account, failed — or null when nobody asked */, ~~etwAvailable~~ }` — `etwAvailable` struck 2026-09-13 with the tier it described (2026-08-28); `pid` added. ~~`vulkanLayerRegistered` is **false by construction** today (the layer is per-launch, never registered)~~ `vulkanLayerRegistered` is the HKCU implicit-layer registration as the Agent found it at start *(corrected 2026-10-04: since P3 PR-8b; true while `VkLayerReconciler` keeps the layer registered for a hook-enabled Vulkan game, P4 PR-2)* and `cpuTempAvailable` false unelevated; `telemetrySource` is the composite stood up once on the first `Hello` |
| `GetStatus` | UI→A | → `StatusAck { state, activeSession?, tier? }` — and `activeSessions[]`, one `{ sessionGuid, gameId, gameName?, pid, tier, startedAt, hold? }` per running session. **`hold` added 2026-09-23, optional:** present on a session held unhooked (Tier 2), with the same words `SessionStarted.hold` carries; a session listed at tier 2 WITHOUT a `hold` has not attached yet — it is starting, not held. The App reads this list on every (re)connect (§Client behavior) |
| `SetWatchlist` | UI→A | `{ entries: [{ gameId?, exePath }] }` — ~~full replace~~ **ensure, never remove** (built 2026-09-13, PR-1b): each entry's path is normalised by the Agent, its row ensured with hooking OFF when new, and the ack is `WatchlistAck { games: [{ gameId, exePath, name }], unreadable: [exePath] }`; `gameId` in a request is a hint and never trusted over the path. UI re-sends on connect. **Carries no hooking state** (see §The pipe is not a trust boundary). *Since the App writes `games` rows itself under `06_DATA_MODEL` §Writer ownership (HANDOFF §P3 D15), this is the pipe's way of adding a row, not the only one; the watcher reads the table at 1 Hz either way.* |
| `LaunchGame` | UI→A *(the App sends it since beta.21: Play in its Start directly mode, and in the store mode where no store installed the game — `App.Services.GamePlayer`, D59)* | `{ gameId, arguments? }` → ~~suspended-launch~~ launch mode as built ("inject late", `04_CAPTURE` §Launch mode) → `LaunchAck { gameId, accepted, outcome, sessionGuid? }` — `outcome` is `Accepted` · `UnknownGame` · `SessionRunning` (one per game at a time) · `Unavailable` · `RecordingOff` (2026-09-23: the entry's recording switch is off, FR-1.6 — FrameLedger does not start what it will not record). *(Built 2026-09-13, PR-1b: `CaptureOrchestrator.LaunchAsync` over an `ILaunchRecorderFactory` the Agent composes with the Vulkan layer's environment — or none when FR-2.4's switch is on — and the launcher election runs after, as the console's `launch` does; the elected session is not addressable by the launch's guid.)* |
| `LaunchGame` | UI→A *(the App sends it since beta.21: Play in its Start directly mode, and in the store mode where no store installed the game — `App.Services.GamePlayer`, D59)* | `{ gameId, arguments? }` → ~~suspended-launch~~ launch mode as built ("inject late", `04_CAPTURE` §Launch mode) → `LaunchAck { gameId, accepted, outcome, sessionGuid? }` — `outcome` is `Accepted` · `UnknownGame` · `SessionRunning` (one per game at a time) · `Unavailable` · `RecordingOff` (2026-09-23: the entry's recording switch is off, FR-1.6 — FrameLedger does not start what it will not record) · `PackagedGame` (beta.33, D80: the executable's install root is a GDK package root — a game the Xbox app or the Microsoft Store installed, which Windows starts through its package and never by its path, `spike-notes` §25; nothing is started, and the App says to start it from the Xbox app or the Start menu. The App hands such a game to Windows itself and sends this only when it found no package record for it. Additive: an older App says the unknown outcome as a failure). *(Built 2026-09-13, PR-1b: `CaptureOrchestrator.LaunchAsync` over an `ILaunchRecorderFactory` the Agent composes with the Vulkan layer's environment — or none when FR-2.4's switch is on — and the launcher election runs after, as the console's `launch` does; the elected session is not addressable by the launch's guid.)* |
| `SetHookEnabled` | UI→A | `{ gameId, enabled, disclosureVersion? }` — Agent re-runs the static AC pre-scan and may reply `Refused`. **The Agent stamps the consent timestamp itself.** *(Built 2026-09-13, PR-1b, as far as it can be: `enabled: false` → `RevokeAsync` → `HookEnabledAck { gameId, enabled: false, outcome }`; `enabled: true` → the pre-scan of the executable's directory, a refusal or a "could not verify" recorded through `RecordGuardBlockAsync` and answered `Refused { gameId, reason, family?, signal? }`; a clean scan → ~~**`Error DisclosureUnavailable`, nothing stamped** — the reviewed FR-2.1 text does not exist, and a client's `disclosureVersion` is a claim, not a disclosure shown. PR-4 replaces that last branch with the stamp~~ **since PR-4 (2026-09-13): the client's `disclosureVersion` compared with the Agent's own `SafetyDisclosure.Version`; equal → the stamp from the Agent's clock with `ConsentProvenance.ConsentDialog`, answered `HookEnabledAck { enabled, outcome, prescan: "clean" }`; anything else → `Error DisclosureVersionMismatch`, nothing written (D14). `DisclosureUnavailable` remains for a composition that wired no version, which `--serve` never is.)* **Since beta.8 (2026-09-25):** the pre-scan is of the executable (the guard resolves the install root, PR-2 of that train), and BEFORE it an executable known not to run as x64 is answered `Refused { gameId, reason: "ExecutableNotX64", signal: "x86" | "anycpu32" | "arm64" | "arm" }` with nothing scanned and nothing written — not a guard reason and not a block (`05_DETECTION` §What the files say about themselves). **Since D33 (2026-09-26):** for a blocked game whose user-mode exception is in force for the executable on disk (the option on, a grant made on these bytes, the block naming that family) the pre-scan NAMES the family, and a pass under it is stamped as ever and answered `prescan: "exception"`; a finding about the game under it also ends the exception. |
| `SetAntiCheatException` | UI→A | **Added 2026-09-26 (D33).** `{ gameId, enabled, disclosureVersion? }` — grant or withdraw a game's user-mode anti-cheat exception (`19_SAFETY` §The user-mode exception). `enabled: false` → the exception ends (`Withdrawn`), hooking goes off while the block stands → `AntiCheatExceptionAck { gameId, granted: false, outcome, family? }`. `enabled: true` → `Error DisclosureVersionMismatch` unless `disclosureVersion` is the Agent's `AntiCheatExceptionDisclosure.Version`; `Error ExceptionsOff` while `hooking.usermode_ac_exceptions` is off; `Refused { reason: "BlockNotExceptionable" }` for a title list or an unreadable block; then the Agent's OWN facts — ~~the successful Tier-1 sessions (`Refused { reason: "TooFewSessions", signal: <count> }` under two)~~ *(D38, 2026-10-03: no session is needed)*; a game an exception of which ended during its trial is refused before anything is scanned (`Refused { reason: "TrialFailed", family, signal: <unix ms> }`); a tolerant pre-scan of the executable on disk naming the block's family (`Refused { reason, family, signal }` unless the guard let exactly that family through) — and the store writes the grant only over facts that make the game eligible, and never over a failed trial → `AntiCheatExceptionAck { granted, outcome, family }`. **A grant turns nothing on**: hooking is FR-2.1's `SetHookEnabled`, afterwards. Not answered (`UnknownType`) by an Agent composed without the exception. |
| `PauseCapture` / `ResumeCapture` | UI→A | global → `PauseAck { paused }`; `StatusAck.paused` reports it. *(Built 2026-09-13, PR-1b: one in-memory flag, `CapturePause`, read by every session loop at its tick and told to the ring once per transition; supervision — the guard scan, the kill switch, the safety stop — never pauses. Not persisted: an Agent that restarts resumes.)* |
+275 -30
View File
@@ -1,6 +1,9 @@
# 08 — UI
WPF + **WPF UI (Wpf.Ui, Fluent)**. Shell = `ui:FluentWindow` with custom `ui:TitleBar`, a thin classic **Menu bar** (file-level operations), and a left **`ui:NavigationView`** (`PaneDisplayMode="LeftFluent"`) as primary navigation. Light/Dark/System themes via `ApplicationThemeManager` + `SystemThemeWatcher`; Mica backdrop on Windows 11 with automatic solid fallback on Windows 10. All XAML follows `16_WPFUI_SYNTAX.md` — that doc is mandatory reading before writing views.
WPF + **WPF UI (Wpf.Ui, Fluent)**. Shell = `ui:FluentWindow` with custom `ui:TitleBar`, a thin classic **Menu bar** (file-level operations), and a left **`ui:NavigationView`** (`PaneDisplayMode="LeftFluent"`) as primary navigation *(since beta.34, D86, its items use
our copy of WPF UI 4.3.0's LeftFluent item template — `FlLeftFluentNavigationViewItemTemplate` in `Styles/FrameLedger.xaml` —
whose only change is that the selected page keeps its label; WPF UI's animates it away, and the owner's screenshot of
Compare showed the icon alone)*. Light/Dark/System themes via `ApplicationThemeManager` + `SystemThemeWatcher`; Mica backdrop on Windows 11 with automatic solid fallback on Windows 10. *(beta.35, D91: a Windows contrast theme wins over all three while it is on — §Contrast.)* All XAML follows `16_WPFUI_SYNTAX.md` — that doc is mandatory reading before writing views.
## Shell
@@ -38,10 +41,15 @@ WPF + **WPF UI (Wpf.Ui, Fluent)**. Shell = `ui:FluentWindow` with custom `ui:Tit
**NavigationView items:** Dashboard · Games · Compare · Logs — `Settings` lives in `FooterMenuItems`. Icons from `SymbolIcon` (Fluent System Icons; pick from the `SymbolRegular` enum — see 16 §Icons).
**Menu bar**
- **File:** Add game… · Import library (Steam / GOG / Epic / itch.io) · Export ▸ (Session CSV / Session JSON / Chart PNG) · Exit
- **File:** Add game… · Import library (Steam / GOG / Epic / itch.io / Xbox *— since beta.33*) · Export ▸ (Session CSV / Session JSON / Chart PNG) · Exit
- **Tools:** Agent status… · Update detection rules · Vulkan layer registration… · Open data folder · Database maintenance…
- **Help:** User guide (beta.12) · Check for updates · Report a bug… · ~~Documentation~~ Online documentation · Limitations · About FrameLedger (~~App / Developer / Third-party licenses tabs~~ — built beta.12 as *This app* / *Third-party licences* / *Legal documents*, below)
- **Help:** User guide (beta.12) · Check for updates · Report a bug… · ~~Documentation~~ Online documentation · Limitations · Accessibility (beta.35) · About FrameLedger (~~App / Developer / Third-party licenses tabs~~ — built beta.12 as *This app* / *Third-party licences* / *Legal documents*, below)
> **Help ▸ Accessibility, beta.35 (owner decision D88, 2026-11-09):** `ACCESSIBILITY.md` — the accessibility statement —
> as the build embeds it (`Services.AccessibilityDocument`), in a `Windows/DocumentWindow` of its own like Limitations,
> and after Limitations in the user guide's window so the guide's links to it open there. Information, not one of
> FR-11's documents. What it says and the checks behind it are §Accessibility below.
>
> **Help ▸ Limitations, beta.10 (D36):** `LIMITATIONS.md` as the build embeds it (`Services.LimitationsDocument`), in a
> ~~read-only, scrolling WPF UI `MessageBox` with *Open on GitHub*~~ window of its own since beta.12 (`Windows/DocumentWindow`,
> rendered — below; corrected 2026-10-04). It is information, not one of FR-11's documents:
@@ -60,7 +68,7 @@ WPF + **WPF UI (Wpf.Ui, Fluent)**. Shell = `ui:FluentWindow` with custom `ui:Tit
>
> **Documents are rendered, beta.12 (owner request 4, D45).** Every Markdown document the App shows — the Legal Gate's
> three texts, Help ▸ Limitations, the update notes, About's documents — is drawn by `Markdown/MarkdownRenderer`
> (Markdig 1.4.0, BSD-2-Clause) into a WPF `FlowDocument` inside `Controls/MarkdownView` (a read-only
> (Markdig ~~1.4.0~~ 1.5.0 since beta.31 — 1.4.2 in beta.30 —, BSD-2-Clause) into a WPF `FlowDocument` inside `Controls/MarkdownView` (a read-only
> `FlowDocumentScrollViewer`: selectable, Ctrl+C, Ctrl+wheel zoom): headings, emphasis and strikethrough, inline and
> fenced code in monospace, quotes, nested and numbered lists, pipe tables with a header row, rules, links. **HTML is
> off** — a tag is shown as the text it is; **no image is fetched** — its description stands in; a node the renderer
@@ -141,8 +149,12 @@ The Menu sits in its own row **below** the TitleBar (never inside the drag regio
## Notifications policy
- **In-app, transient** (rules updated, export done, non-fatal capture warning): `ISnackbarService` snackbar, 4 s.
- **In-app, persistent** (Agent offline, ~~PawnIO missing,~~ update downloaded, a viewer's folder, the safety notices): `ui:InfoBar` banner pinned above content with action button. *(Corrected 2026-10-07: no PawnIO banner was ever built — CPU temperature reads N/A, and Settings ▸ System says it needs the admin mode and PawnIO; the viewer's banner (D52) and the safety notices were missing from the list.)*
- **In-app, transient** (rules updated, export done, non-fatal capture warning): `ISnackbarService` snackbar, 4 s — shown
only through `IMessageStrip` (`Services/SnackbarStrip`) since beta.35, which says it to a screen reader as it shows it
(D89; `AnnouncementsTests.OnlyTheStripShowsASnackbarAndNoXamlSetsALiveSetting`).
- **Every one of these is said to a screen reader as it appears (beta.35, owner decision D89)** — §Accessibility, Screen
readers.
- **In-app, persistent** (Agent offline, ~~PawnIO missing,~~ update downloaded, a viewer's folder, the safety notices, *an alpha build* — since 2026-10-31, D74): `ui:InfoBar` banner pinned above content with action button. *(Corrected 2026-10-07: no PawnIO banner was ever built — CPU temperature reads N/A, and Settings ▸ System says it needs the admin mode and PawnIO; the viewer's banner (D52) and the safety notices were missing from the list.)*
- **System-level, app possibly minimized** (session saved with "View" action, capture error while in tray, update available): tray balloon/toast via H.NotifyIcon.
- One event → exactly one channel; never duplicate the same event across snackbar *and* tray.
@@ -240,7 +252,7 @@ All screens are `Page`s registered with the navigation page provider and navigat
### Dashboard
- Agent status `ui:CardControl` (state, capability badges as `InfoBadge`: telemetry source, Vulkan layer, ~~ETW fallback~~, PawnIO/CPU-temp, elevation — Repair button on error).
- **Live capture card** (visible during capture): game name, **tier badge**, elapsed, live `FpsReadout` (5 s rolling), **measured** `renderW×H → outputW×H` with upscaler + quality, RT-active dot, CPU/GPU temp, ~~per-process VRAM~~ the game's own VRAM and RAM (beta.12: read from outside the game, so a held session has them too), sparkline (last 120 s) fed by `SessionProgress`. Tier 1 shows measured settings — this is the payoff of hooking and should read as facts, not guesses.
- **Live capture cards** (one per running session since beta.28, two to a row): game name, **tier badge**, elapsed, live `FpsReadout` (5 s rolling), **measured** `renderW×H → outputW×H` with upscaler + quality, RT-active dot, CPU/GPU temp, ~~per-process VRAM~~ the game's own VRAM and RAM (beta.12: read from outside the game, so a held session has them too), sparkline (last 120 s) fed by `SessionProgress`. Tier 1 shows measured settings — this is the payoff of hooking and should read as facts, not guesses.
- Recent sessions list (last 10 across games) → click opens session summary.
- Totals strip: games tracked, total playtime, sessions this week (`ui:Card` row).
@@ -270,9 +282,28 @@ All screens are `Page`s registered with the navigation page provider and navigat
> open is on it at once; the completion notice names the session that completed (`SessionCompleted.gameName`)
> and a `faulted` completion is no notice (the strip's `CaptureError` already said it). Until this date the
> Agent announced only hooked sessions: every other game read "Nothing is being captured." while it ran.
>
> **beta.28: one card per running session** (the owner, 2026-10-20: "Thêm cơ chế hiển thị UI/UX Dashboard khi chạy >=2
> game trong cùng 1 thời điểm"). The Agent records one session per executable, so two games run as two sessions, and
> until beta.28 the second showed only as *Running sessions: 2* — the one card went to a hooked session and stayed with
> it. `DashboardViewModel.LiveCards` keeps a `LiveCaptureViewModel` per session, each fed only its own session's events
> (a card is made by its session's first event or seed and is one session's for life); hooked sessions come first, each
> kind in the order it started, and a card that changes place is moved, never rebuilt. The header counts the games from
> two on (*2 games recording*, `Dashboard_Live_Count_Format`) and the cards stand two to a row (`LiveColumns`); with none
> running, one card says *Nothing is being captured.* Each card is the card it was — name, tier badge, elapsed, the
> readout or why nothing is measured, the measured settings, the temperatures (the machine's, so alike on every card) and
> the game's own memory. Tests: `DashboardViewModelTests` (two games, a third, each ending), `LiveCaptureViewModelTests`,
> and the page in `PagesLoadTests`' surfaces with a hooked and a held session, in both themes and through a switch.
### Games (grid → detail)
- `GridView`-style panel of cover cards (`ui:CardAction`): name, platform badge, engine badge, total playtime, last played, mini trend sparkline (avg Native FPS last 10 sessions). Sort/filter/`ui:AutoSuggestBox` search.
> **The filters, beta.34 (owner request 2026-11-06, D85)** — specified here since P3 and never built: a row under the
> search and sort with **Store**, **Engine** (the stores and engines the library holds, each list naming its
> "everything" first; *Added by hand* for an entry with no store, *Engine not identified* for one with none),
> **State** (the card's one state, as its pill says it), **Installed** and **Played**, and *Clear filters*. While a filter
> or the search narrows the list the title counts what is shown of all (*Games · 12 of 65*). Kept while the App runs —
> the page is the window's (`WindowPageCache`) — and not saved. Tests:
> `GamesViewModelTests.TheFiltersNarrowTheLibraryAndTheHeaderCountsWhatIsShown`.
> **The library, beta.11 (owner requests 2026-10-03).** *The empty band on the right:* the cards were 300 px in a plain
> `WrapPanel`, so at ~1350 px three fitted and a card's width was left unused; the grid is now
> `Controls.UniformWrapPanel` — as many columns as fit at 300 px or wider, every card an equal share of the width, each row
@@ -293,7 +324,14 @@ All screens are `Page`s registered with the navigation page provider and navigat
> message at once in its one snackbar, so only the last name stayed on screen. And only the newest read of the library is
> shown: reads overlap — a session that ends, an import, a removal — and the one that started first could finish last,
> its executable checks waiting on a slow drive, and put back a removed game's card (`GamesViewModel.LoadAsync`,
> `GamesViewModelTests.AnOlderReadThatFinishesLastIsNotShownOverANewerOne`)*). **The page reloads by itself** while it is on screen when a session ends (`SessionCompleted`) or an
> `GamesViewModelTests.AnOlderReadThatFinishesLastIsNotShownOverANewerOne`)*). *(beta.34, owner request 2026-11-06 —
> "switching to Games stalls 0.5–1.5 s", `spike-notes` §27: the window keeps the page it built and shows it again on
> every later visit, reading the library again behind it; the library is read on the thread pool; the cards appear
> before any executable is checked — 39 of the owner's 41 Steam games are on a USB drive that sleeps — and each card
> gets its *Not installed* pill when its check answers; a read keeps every card that would look the same; the list
> view is bounded (`MaxHeight` 640) so it builds the rows on screen. `GamesViewModelTests`
> `.TheCardsComeBeforeTheExecutableChecksAndThePillAfter`, `.APageShownAgainReadsTheLibraryAndKeepsTheCardsThatLookTheSame`,
> `WindowPageCacheTests`.)* **The page reloads by itself** while it is on screen when a session ends (`SessionCompleted`) or an
> import adds games (`LibraryChanges` — navigating to the page already on screen does nothing in WPF UI 4.3.0, so an
> import from the menu never showed until the page was left). **Import** (FR-1.2): the games already in the library — at
> this path or under another drive letter — are hidden by default (*Show the N games already in the library* brings them
@@ -344,6 +382,13 @@ All screens are `Page`s registered with the navigation page provider and navigat
> surfaces' game page has artwork), `…TheArtworkBandFollowsAThemeSwitch` and `…TheGamePagesArtworkIsDrawn` with
> `AccessibilityTests.NoStyleOfAWpfUiControlLeavesOutItsTemplate` (the cover once took its place and drew nothing, a
> `ui:Image` style not based on WPF UI's; caught in a render before it shipped). The library's cards still have no image.
>
> **beta.33 (D79): an Xbox game's own pictures.** A game the Xbox app or the Microsoft Store installed ships its pictures
> in its package folder, and `MicrosoftGame.config` names them: the `Square480x480Logo` (else `Square150x150Logo`) is the
> cover, drawn **square** (150×150, `ArtCoverIsSquare`) so a logo is never cropped to a portrait, and the
> `SplashScreenImage` (1920×1080 on the owner's titles) is the banner. The square logo comes before a landscape header.
> Read from inside the package root only; the tooltip says *Artwork from the game's own files (Xbox app)*
> (`Art_Source_Xbox`). `GameArtTests.AnXboxGamesSquareLogoIsItsCoverDrawnSquareAndItsSplashTheBanner`.
> **Built 2026-09-14 (P3 PR-5): the grid, the detail page's header, the two rows, the hooking control and
> the Sessions tab.** Grid: `ui:CardAction` cards with platform / engine / hooking badges, sessions, playtime,
@@ -361,7 +406,10 @@ All screens are `Page`s registered with the navigation page provider and navigat
> the executable's folder, and the nearest folder still there when that one is gone; nothing for a drive that is not
> connected, where Windows opens its last folder; owner request 2026-10-12, `GameFolderTests`), **one App per data folder since 2026-09-21** (`Services.SingleInstance`: a named mutex and a named event keyed on a hash of the data directory, claimed in `Program.Main` after Velopack's hooks and before any window; a later start sets the event and exits 0, and the first instance brings its window forward through `ShellHost.Reveal` — from the tray too. Nothing stopped a second App before: the owner's log shows two started 360 ms apart, two tray icons, a second log file. `--diag` never claims), ~~**the guard-bypass switch since 2026-09-21**~~ **withdrawn 2026-09-22** (the card, its dialog, the session mark and the export line are gone; a blocked row's toggle is disabled and `Safety_Blocked_Toggle_Format` is the whole story; a refusal or unhook notice that turned hooking off ends with `Safety_HookingTurnedOff` — `19_SAFETY` §What a finding does to the game), **Supports** (from `capability_flags`; ~~empty until P4's scan writes it, and the card says so~~ **written by the Agent's detection sweep since P4 PR-1, 2026-09-14** — the rule ids as product names via `CapabilityNames`, "not scanned yet" only until the Agent's next tick) beside
> **Last session measured** (upscaler · resolution, frame generation, the non-N/A chips — accent pills, from the
> hooks). Hooking: the toggle is `OneWay` from the row and its command runs `HookingConsent`; a refusal, a
> hooks). Hooking: the toggle is `OneWay` from the row and its command runs `HookingConsent` *(since beta.30 the command
> raises the switch's property whatever happened, so the switch reads the row again: a click flips it through
> `SetCurrentValue`, and a command that changed nothing — declined, refused, no Agent — used to leave it showing *on*
> beside *off*, the owner's report of 2026-10-26)*; a refusal, a
> mismatch or a failure is a persistent `InfoBar` on the page (never a toast); a blocked row disables the
> switch with `Safety_Blocked_Toggle_Format` inline; an unverified pre-scan leaves it enabled and says so;
> auto-disabled shows `Safety_AutoDisabled_Format` with the re-enable button. Sessions tab: the `DataGrid` of
@@ -372,7 +420,8 @@ All screens are `Page`s registered with the navigation page provider and navigat
>
> **The recording switch (2026-09-23, FR-1.6).** A `ui:CardControl` **Recording** above the hooking control, its
> `ToggleSwitch` `OneWay` from `games.record_sessions` and its command writing the row through
> `GameLibrary.SetRecordingAsync` — no dialog (it deletes nothing; sessions already recorded stay) and nothing over
> `GameLibrary.SetRecordingAsync` (and, since beta.30, raising the switch's property after it, as the hooking switch's
> does) — no dialog (it deletes nothing; sessions already recorded stay) and nothing over
> the pipe (the Agent reads the table each tick). Status line *Recorded when it runs* / *Ignored — nothing is
> recorded*; the body says what off means (the program is not watched; a running session stops) and when to use it
> (a utility that starts with Windows). The library card shows **Not recorded** in place of the hooking badge, since an
@@ -425,7 +474,8 @@ All screens are `Page`s registered with the navigation page provider and navigat
> what the game's files and its store say (`05_DETECTION` §What the files say about themselves): *Runs as* (64-bit
> (x64) · 32-bit (x86) · ARM64 · .NET, any CPU (runs as 64-bit) · …), *File version* and *Product version* (the
> executable's PE resource — for an Unreal title often the engine's), *Store* ("Steam build 20374416", "GOG version
> 1.2.3" — or *Version* when the user typed it), *Engine*, and *Ships with*, one line per capability file: "DLSS:
> 1.2.3", since beta.33 "Xbox version 1.3.5124.0" — or *Version* when the user typed it), *Engine*, and *Ships with*,
> one line per capability file: "DLSS:
> nvngx_dlss.dll 3.7.10.0", "XeSS: libxess.dll (no version)". A row the Agent has not read yet says so. The subtitle
> labels the store's version the same way and then drops the bare store name it would repeat. **An executable that
> cannot run as x64** (x86, 32-bit-preferring .NET, ARM) disables the hooking switch with `Hooking_NotX64_Format` under
@@ -446,7 +496,7 @@ All screens are `Page`s registered with the navigation page provider and navigat
1. **Sessions** — `DataGrid`: date, duration, **tier badge (T1/T2)**, Native, Displayed, FG×, 1% Low, 0.1% Low, resolution + upscaler, max GPU temp, API, chips, ⚠ crash badge, tags. Row → Session summary. ~~Multi-select → "Compare".~~ (not built; Compare's own picker chooses) Tier-2 rows render ~~`—`~~ `N/A` (not blank, not zero) in Tier-1-only columns, with a tooltip explaining why *(corrected 2026-10-04: as built — `—` means a measured none, §FPS display rule)*.
2. **Frametime** — ScottPlot timeline of selected session (decimated), stutter markers, sensor overlay toggle (temp on right axis).
3. **Distribution** — FPS histogram + percentile curve of selected session(s).
4. **Trend** — metric-over-date line (selector: Native avg / Displayed avg / 1% Low / 0.1% Low / max GPU temp), vertical **hardware-change markers** with tooltip "GPU driver 572.16 → 576.02" (FR-6.3).
4. **Trend** — metric-over-date line (selector: Native avg / Displayed avg / 1% Low / 0.1% Low / max GPU temp), vertical **hardware-change markers** with tooltip "GPU driver 572.16 → 576.02" (FR-6.3). *(The tooltip stood here unbuilt until beta.30 — 2026-10-26, owner decision D70: a numbered badge per day that changed, its changes in the list under the chart, the same text in the tooltip; below.)*
> **Across sessions, beta.11 (owner decision D39, FR-6.6).** The **Sessions** tab opens with *Sessions at a glance*: a
> `TrendChart` of every hooked session's Presented FPS (sessions that counted no generated frame), Native and Displayed
@@ -502,7 +552,8 @@ All screens are `Page`s registered with the navigation page provider and navigat
> Presented where it was not, the note beside the chart says so; Displayed only where measured; the lows; max
> GPU °C), FR-6.4's exclusion of `settings_changed_midsession` sessions by default with the toggle and the
> excluded count, and FR-6.3's markers — labelled dashed lines wherever two consecutive sessions' hardware
> snapshots differ in GPU driver, GPU, CPU, display mode or OS ("GPU driver: 572.16 → 576.02"). **Sensors**:
> snapshots differ in GPU driver, GPU, CPU, display mode or OS ("GPU driver: 572.16 → 576.02") *(numbered since
> beta.30, the label's text in the list under the chart — below)*. **Sensors**:
> GPU core / hotspot °C, load % and power W (right axis) on one plot; VRAM on another with ~~the game's own
> per-present `vram_proc` (a held 1 Hz sample) and~~ the adapter-wide `vram_adapter` sensor ~~as two
> differently-labelled series~~ (corrected 2026-10-03: the Overlay never produced `vram_proc`, so the game's line was
@@ -526,8 +577,30 @@ All screens are `Page`s registered with the navigation page provider and navigat
> measured — and the trend opens on Native when the newest measured session counted generated frames; the machine
> metrics count **Tier-2 sessions too** (a game never hooked had no trend); a point that describes part of its session —
> settings changed, or a steady state, for Native and Displayed as well as the factor — is drawn **hollow** and the
> note says so; hardware changes on one day are **one** marker; the metric list is built in the language the page opens
> in; the empty text names the metric.
> note says so; hardware changes on one day are **one** marker *(numbered since beta.30, its changes listed under the
> chart)*; the metric list is built in the language the page opens in; the empty text names the metric.
>
> **Hardware-change markers, numbered — beta.30 (owner decision D70, "Số + danh sách").** The owner's screenshot of
> 2026-10-26 showed the label "Driver GPU: 32.0.16.1742 → 32.0.16.2101" with its top cut off: ScottPlot's `VerticalLine`
> label grows up from the data area into the top-axis panel, which nothing sized for it (about 15 px for a 25 px box),
> every further line of a day's label was lost above the control's edge, and its white on the orange read 1.78:1 (dark)
> and 2.63:1 (light). Asked, the owner chose numbers and a list. `TrendSeriesBuilder.Markers` numbers the days that
> changed oldest first (`ChangeMarker`: the number, the day, each change once) and the view model hands the same list to
> both charts and both lists, so a number means one day everywhere on the page. On the chart, `ChangeMarkerPlottable`
> draws each day's dashed line in the data area and, in a band kept above it (`Axes.Top.MinimumSize`, measured from the
> badge's font), a numbered badge in the palette's orange with `ChartTheme.TextOn`'s text — black in both themes, 11.79:1
> and 8.00:1 — joined to its line by a short connector; `ChangeBadgeLayout` keeps every badge inside the data area's
> width and off every other: too close, they stand aside in their lines' order; farther than about one badge from their
> lines, or with no room at all, the nearest neighbours become one badge for the run (*3–5*). A badge is never cut off
> and never over another, at any width; a day outside a zoomed range has no line and no badge. Under each chart
> `ChangeMarkerList` gives every number its day (`Formats.Day`, the regional short date) and its changes in full,
> wrapping, with a `ChangeBadge` chip in the badge's colours; the Trend's list stands with its chart. Pointing within
> 14 px of a line, or at a badge, shows the same text in a tooltip, which closes on a press, a wheel or leaving the
> chart. The pointer is read through the element's DPI now (`GetPlotPixelPosition`): `WpfPlot.DisplayScale` is taken
> once, before the control has a window, and the overview's click used it. `ChangeBadgeLayoutTests`,
> `PagesLoadTests.EveryChangeBadgeIsWholeInsideTheChartAndNoneIsOverAnother` (the Trend's 640×320, the overview's 220
> px, a 300 px window, markers on the data area's edges, thirty days in a row), `ChartMathTests` (the badge's text in
> both palettes) and the readable and theme-switch sweeps over the game page's list hold it.
>
> **FPS with two decimals (same day, owner item 7).** Settings ▸ Window: *Show FPS with two decimals*
> (`ui.fps_decimals`, off by default) — every FPS figure through `Formats.FpsNumber`: "62.40" when on, "62" when off,
@@ -557,6 +630,18 @@ All screens are `Page`s registered with the navigation page provider and navigat
> mode): recorded from the first frame, never as administrator, refused for a recording-off entry. A viewer's (D52) Play is
> off and its composition holds no `ShellStarter`. Tests: `StoreLaunchesTests`, `StoreRecordsTests`, `GamePlayerTests`,
> `ViewerModeTests`.
>
> **beta.27: a Steam game may hand itself to Steam.** Started by the agent — *Start directly*, or every press while the
> App runs as administrator — a game Steam's records name may leave within seconds and have Steam start it again (Lies
> of P, 2026-10-19; `spike-notes` §23), and since beta.27 the game Steam starts is recorded. The notice says so for such
> a game (`Play_Started_Steam_Format`, `Play_Elevated_Steam_Format`; `PlayResult.SteamGame` from the same store records
> the store mode reads), and the *Start directly* tooltip and Settings ▸ Games ▸ Play button say it for every Steam
> game, the latter adding that a few will not start outside Steam at all. The owner offered two ways (2026-10-20: a note
> in the UI, or a fixed rule that Steam's games always go through Steam) and left the choice open; the note was taken
> because the rule would cost too much: three of the five Steam games started directly on 2026-10-20 ran and were
> measured from their first frame, and a Vulkan game is measured only when FrameLedger starts it (Everhex Demo).
>
> **beta.33 (D80): a game the Xbox app or the Microsoft Store installed always starts through Windows.** In either mode, and from an App running as administrator too, **Play** runs `explorer.exe shell:AppsFolder\<AUMID>` — the user's shell activates the game's package, unelevated, as its Start-menu tile does (`StoreLaunches`: the AUMID is the record's `<family name>!<application id>`, checked against the shape Windows gives one). Started by its path a GDK game is never the game in its package (`spike-notes` §25), so no mode sends `LaunchGame` for it, and the agent answers `PackagedGame` to one that reaches it anyway (an entry the App found no package record for). The notices: `Play_Xbox_Format` (started), `Play_Xbox_NotStarted_Format` and `Play_PackagedGame_Format` (start it from the Xbox app or the Start menu), all warnings but the first; the *Through the store* and *Start directly* tooltips and Settings ▸ Games ▸ Play button say it. The session is attach mode, `late_attach` (`04_CAPTURE` §Launch mode vs attach mode). Tests: `StoreLaunchesTests`, `GamePlayerTests`, `CaptureOrchestratorTests`.
### Session summary (secondary `FluentWindow`, also the post-session toast target)
Stat cards (Avg uses `FpsReadout`, Median, 1% Low, 0.1% Low, Min/Max, σ, stutter %, duration, **Display** — beta.10: the mode shown longest with its share and the window's size, both tiers; **VRAM (this game)** and **RAM (this game)** — beta.12: the median with the peak beneath, both tiers), **Statistics per series** (beta.12: every stored series' mean / median / minimum / peak), TriState chips, API/PresentMode/upscaler line, **the display line** (beta.10: every mode's share, the changes, the window on its monitor at its refresh rate, the back buffer and swap effect, and what the facts rested on — "the swap chain said whether it was exclusive" or "from the window alone: exclusive fullscreen cannot be told from borderless"; absent for a session recorded before), crash `InfoBar` (Severity=Error) when `crashed`, frametime chart, sensor strip, tags/notes editor, Export buttons.
@@ -566,7 +651,17 @@ Stat cards (Avg uses `FpsReadout`, Median, 1% Low, 0.1% Low, Min/Max, σ, stutte
> frame-generation state)*, *DLSS 3 (library 3.7.10)* — else *DLSS*; then each DLSS library with its version and where
> it was loaded from (*Super Resolution 310.5.0, from the graphics driver, preset L (2nd-gen transformer model)*), then
> *DLSS 5 runtime loaded* when it was. The game page's *Last session measured* repeats the label; the CSV export gains
> `# dlss:`. `DlssTextTests`.
> `# dlss:`. `DlssTextTests`. *(beta.34: two more rows — the NVIDIA App's Dynamic frame generation the driver reports
> applied is *DLSS 4.5 (Dynamic multi frame generation, set in the NVIDIA App)* (D83), and *DLSS 5 (neural rendering on
> N % of rendered frames)* heads the line where the game was seen running it, its library listed like the others, *runtime
> loaded, not seen running* where the Overlay looked and saw none (D84) — `05_DETECTION` §DLSS generation.)*
> **beta.27: one window per session, and no DLSS line that says only *DLSS*.** Opening a session whose summary window is
> open — from a Sessions tab, a notification, the game page — brings that window forward, restored if minimised, rather
> than opening a second (`SessionSummaryOpener`; the owner had two windows of one Silent Hill 2 session, 2026-10-20). The
> DLSS line is not shown where it would say only *DLSS*: the header names the upscaler, and the NVIDIA App's override
> loads its libraries under names no census lists, which the *Loaded:* line prints (The Witcher 3, 2026-10-20).
> `PagesLoadTests.OpeningAnOpenSessionAgainBringsItsOneWindowForward`, `DlssTextTests`.
> **beta.24 (D63): the quality mode, on every surface alike.** The summary's header line, a Sessions-tab row, the game
> page's *Last session measured* and the live card name the upscaler through one entry point (`Formats.UpscalerOf`):
@@ -707,10 +802,20 @@ Stat cards (Avg uses `FpsReadout`, Median, 1% Low, 0.1% Low, Min/Max, σ, stutte
### Compare
Session picker (2–5, cross-game allowed) → overlaid percentile curves + stat table with best-value highlighting; FG columns always show Native and Displayed separately. Export PNG.
> **beta.34 (owner request 2026-11-06, with a screenshot; D85).** The list holds **every session** — it was the newest
> 200, read on the UI thread with one game lookup each; now one read of the names, on the thread pool — and filters by
> **Game**, **Tier** and **Frame generation** (with / without; a session that measured none is neither), with a count
> (*6 of 131 sessions*); a ticked session stays listed whatever the filters say. The selection bar — *Pick 2 to 5
> sessions*, the count, *Clear selection*, *Compare* — sits above the list on the left: it was a window's width away. The
> columns are sized to what they hold with one filler column after them (three star columns spread a wide window into
> gaps, and the Tier column was exactly its header's width, so *Tier* and *FPS* touched); the date sorts by when; the
> settings-changed cell says *Changed mid-session* beside its icon, or a dash (it was blank). The result table's session
> labels sit over their columns: the header row has the metric column's 140 px first, as every row does. Tests:
> `CompareViewModelTests.TheFiltersNarrowTheListAndATickedSessionStaysOnIt`, the page in `PagesLoadTests`' surfaces.
**Mixed-tier guard (FR-6.2):** selecting sessions from different capture tiers shows a blocking `ContentDialog` explaining that they measured different things; proceeding stamps the chart with a tier legend and greys out metrics unavailable in the lower tier. Sessions with `settings_changed_midsession` carry a warning icon and are excluded from trend lines by default.
> **Built 2026-09-14 (P3 PR-7).** `CompareViewModel` over the last 200 sessions across games: a `DataGrid`
> **Built 2026-09-14 (P3 PR-7).** `CompareViewModel` over ~~the last 200 sessions~~ every session *(since beta.34)* across games: a `DataGrid`
> picker with a checkbox column (Compare enabled at 2–5), the FR-6.4 warning icon per row; **Compare** asks
> `IMixedTierPrompt` (a `ContentDialog`, default button Cancel) when the selection mixes tiers and compares
> nothing on a decline; a comparison that proceeds carries `Compare_Mixed_Legend` as the plot's title and an
@@ -778,7 +883,7 @@ Tail view of `ui-*.log` / `agent-*.log` (toggle), level filter, search (`ui:Auto
> (`Settings_RemoveUninstalled_Applied`), not at the next session — the detection sweep reads it at every pass. Tests:
> `ViewerModeTests.EverySettingTheAgentReadsIsOffInAViewer`, `GuideDocumentsTests.TheSettingsPageOfTheGuideNamesEverySetting`.
Sections per FR-10 using the WPF UI settings idiom: `ui:CardControl`/`ui:CardExpander` rows with `ToggleSwitch`, `ComboBox`, `ui:NumberBox` (numeric inputs — min session length, sensor interval, retention). Language switch applies immediately (09_I18N). Theme selector (Light/Dark/System) drives `ApplicationThemeManager` (16 §Theming). **Capture section (top, most important):** the global **hooking kill switch** (`ToggleSwitch`, prominent) with a one-line summary of what it does; a list of games currently hook-enabled with a per-game revoke; Vulkan layer registration state + Register/Unregister; a link to the safety documentation. Turning the global switch off must take effect immediately, including for the Vulkan layer.
Sections per FR-10 using the WPF UI settings idiom: `ui:CardControl`/`ui:CardExpander` rows with `ToggleSwitch`, `ComboBox`, `ui:NumberBox` (numeric inputs — min session length, sensor interval, retention). Language switch applies immediately (09_I18N). Theme selector (Light/Dark/System) drives `ApplicationThemeManager` (16 §Theming) *(beta.35, D91: a Windows contrast theme wins while it is on, §Contrast, and a line under the selector says so, bound to `ContrastTheme.IsOn` so it comes and goes with the page shown)*. **Capture section (top, most important):** the global **hooking kill switch** (`ToggleSwitch`, prominent) with a one-line summary of what it does; a list of games currently hook-enabled with a per-game revoke; Vulkan layer registration state + Register/Unregister; a link to the safety documentation. Turning the global switch off must take effect immediately, including for the Vulkan layer.
**System (2026-09-21, FR "show the user's hardware"):** a card above Legal stating this PC as a session's hardware snapshot would record it right now — processor, graphics card, graphics driver, memory, Windows build, primary display — through the same `IHardwareSnapshotSource` the Agent stamps sessions with, read on the thread pool when the page opens, a field that could not be read as N/A, with **Copy** (the same lines as text) and a note that nothing is sent anywhere and what CPU temperature needs. Its own `SystemInfoViewModel`, not `SettingsViewModel`'s. The same snapshot is one tertiary line under the session summary's header (it was loaded for the export and shown nowhere), and `--diag` prints it; the bug bundle's `sysinfo.json` is deliberately NOT given it — its keys are the issue link's prefill.
@@ -819,6 +924,8 @@ Agent section: elevation state with a plain explanation of what elevation *optio
> `Infrastructure.Startup.RunAtLogon` — this user's `HKCU\…\Run` value, quoted executable path, never HKLM —
> and the Run entry is the truth the toggle loads from; "Minimize to tray on close" is stored now and honoured
> when the tray exists. **Privacy:** ~~`privacy.online_metadata`, off by default, with the network sentence~~ — the card is not shown since 2026-09-16 (no code makes the request; the setting stays reserved).
> **Updates (alpha, D73, 2026-10-31):** in an alpha build the channel picker is locked and its line reads *An alpha build updates only to newer alphas, whatever is chosen here…* — an alpha's packages are on Velopack's own channel (`11_UPDATER` §Channels). **The alpha's shell (D74):** an **ALPHA** badge left of the Agent pill in the title bar for as long as it runs (its tooltip names `RuntimeInformation.FrameworkDescription`), the window and taskbar titled *FrameLedger Alpha*, and a Warning InfoBar above every page at every start, closable for that run, whose button opens the Alpha notice *(since beta.37, D97 and D98: its text is one of three — the experimental-build warning; the same naming "a prerelease .NET" where the runtime's description is a prerelease's; or, in an alpha cut while the alpha line rests, that the line is paused and to install the beta — `Services/AlphaTexts`, `Shared.AlphaLine`)*; About's version line names the runtime on every line, and `--diag` prints `release_line:` and the runtime's description.
>
> **Updates:** `update.channel` is read by PR-5's updater (beta = GitHub pre-releases; since beta.14 *Automatic (Beta)* or *(Stable)* first, the default, following the running copy — D47), and `update.auto_check` — the startup check, on by default — sits beside it. **Logging:** `log.debug` moves this app's `LoggingLevelSwitch` at
> once; the Agent has no reader for the key yet, and the row says so. **Legal:** reopen is a "not yet" line
> until PR-9's gate exists. ~~Register/Unregister the layer, Register/Repair/Remove the task~~ — PR-8b, with the
@@ -856,7 +963,7 @@ Agent section: elevation state with a plain explanation of what elevation *optio
> is gone. **Refresh** shows only while a row is *Checking…*, the one time it can change anything.
### First-run flow
1. Legal Gate (FR-11): four documents, scrollable, links to GitHub-hosted versions, single Accept. **Since beta.12 (D45) Accept covers three** — the EULA, the Disclaimer, the Privacy Policy; the GPL is listed as *your licence*, with a line saying it needs no acceptance (GPLv3 §9), and gets no `legal_acceptance` row (`06_DATA_MODEL`). **Rendered since beta.12** (§Menu, *Documents are rendered*): the Markdown texts drawn, the GPL as written; a link from one document to another the gate shows opens it in the gate; *View on GitHub* opens the document at this build's source, through `IUrlOpener`.
1. Legal Gate (FR-11): four documents, scrollable, links to GitHub-hosted versions, single Accept. **An alpha build's gate shows a fifth (D74, 2026-10-31): the Alpha notice** (`legal/ALPHA_NOTICE.md`), accepted with the others under `legal_acceptance.doc = 'alpha'` — and above the documents, under the summary, a second warning box with a tick box of its own (*I understand that this is an experimental build and I use it at my own risk*): Accept is disabled until it is ticked, every time an alpha's gate is shown. While the notice is outstanding the App holds the Agent's start (`IAgentLink.SetNoticeHold`, a hold of its own beside the updater's), because an alpha's Agent does not serve before it; Accept releases it and starts the Agent at once. About ▸ Legal documents lists the notice on every line, for information. **Since beta.12 (D45) Accept covers three** — the EULA, the Disclaimer, the Privacy Policy; the GPL is listed as *your licence*, with a line saying it needs no acceptance (GPLv3 §9), and gets no `legal_acceptance` row (`06_DATA_MODEL`). **Rendered since beta.12** (§Menu, *Documents are rendered*): the Markdown texts drawn, the GPL as written; a link from one document to another the gate shows opens it in the gate; *View on GitHub* opens the document at this build's source, through `IUrlOpener`.
2. Agent setup: runs **unelevated by default** — a short, honest paragraph explains that elevation is optional and unlocks CPU temperature and elevated-game attach. ~~and the Tier-2 ETW fallback. It must be explicit that **without elevation there is no Tier 2**~~ — **struck 2026-08-28: no tier needs elevation, so there is nothing to warn about here.** Capability check results shown afterwards. ~~with Tier-2 availability listed as its own badge~~ — there is no availability to report.
3. Hooking explainer: what Tier 1 vs Tier 2 means — **and it must be explicit that Tier 2 measures nothing**, because the honest version of this screen is the one where a user who declines knows what they are declining — and that hooking stays off until enabled per game.
4. Optional library import.
@@ -900,8 +1007,9 @@ Agent section: elevation state with a plain explanation of what elevation *optio
(`ScrollViewer.CanContentScroll="False"` on the `Page` — `16_WPFUI_SYNTAX` §Gotchas: until beta.14 the wheel scrolled
nothing on five pages, and the Logs tail did not follow the newest line); a scroller nested in a dialog hands the wheel
on at its ends (`ui:PassiveScrollViewer`); over a chart a plain wheel scrolls the page and **Ctrl+wheel zooms the chart**
(`Charts/ChartWheel`, every plot through `ChartTheme.Attach`) — drag still pans and double-click still resets, as
ScottPlot does. The import checklist scrolls inside its list and nowhere else, so its intro and its count stay put.
(`Charts/ChartWheel`, every plot through `ChartTheme.Attach`) — drag still pans and ~~double-click still resets, as
ScottPlot does~~ *(corrected 2026-11-09: ScottPlot's left double-click toggled its render-time benchmark overlay; since
beta.35 a double-click shows all of the chart, `ChartTheme.ResetOnDoubleClick`, `ChartKeyboardTests`)*. The import checklist scrolls inside its list and nowhere else, so its intro and its count stay put.
## Accessibility
@@ -909,22 +1017,50 @@ NFR-9 names three things — full keyboard navigation, adequate contrast in both
and this section is what they mean for this app, each with the test that holds it (P4 PR-8, 2026-09-15). Until then
the requirement was one bullet under §UX rules, and nothing checked it.
> **The users' half is `ACCESSIBILITY.md` (beta.35, owner decision D88, 2026-11-09):** the goal — WCAG 2.2 AA as W3C's
> WCAG2ICT applies it to desktop software, a goal and never a conformance claim — what works, what does not and what to do
> instead, and how a barrier is reported (the *Accessibility problem* form, `labels: [accessibility]`) and handled (by
> severity, no promised times). It is embedded and shown under Help ▸ Accessibility. **This section is the design and the
> checks; the statement says nothing this section does not hold**, and a change that moves either changes both
> (`AccessibilityDocumentTests` holds the statement's own rules: embedded as written, a goal and no claim, a form that
> exists, no struck text in a page the App shows). NFR-9 was widened the same day to screen readers and contrast themes
> (D88–D91).
### Keyboard
| Keys | Does | Where |
|---|---|---|
| **Ctrl+1 … Ctrl+5** (and the numeric keypad's 1–5) | Dashboard · Games · Compare · Logs · Settings | `MainWindow` `InputBindings` → `MainWindowViewModel.NavigateToCommand` → `ShellShortcuts` |
| **Ctrl+1 … Ctrl+5** (and the numeric keypad's 1–5) | Dashboard · Games · Compare · Logs · Settings — and since beta.35 the page's first control takes the focus once it is shown, its title (the page's first-level heading) said to a screen reader; before, the focus stayed where it was, often on the page that had just gone | `MainWindow` `InputBindings` → `MainWindowViewModel.NavigateToCommand` → `ShellShortcuts`, then `Services/PageFocus` (the shell tells it each page shown, from `NavigationView.Navigated`) |
| **Alt**, **F10** | Focuses the menu bar; arrows and Enter walk File / Tools / Help | WPF `Menu`, nothing custom |
| **Alt** + a menu's access key | Opens that menu — `_File` `_Tools` `_Help`; `_Tệp` `_Công cụ` `Trợ _giúp`; `ファイル(_F)` `ツール(_T)` `ヘルプ(_H)` *(row added 2026-11-09: the keys existed since P3 and this table did not name them)* | the `Menu_*` strings' `_` |
| **Tab / Shift+Tab** | Moves through a page in reading order | layout order; no `TabIndex` overrides |
| **Arrows, Home/End, Page Up/Down** | Move within a `DataGrid` (Sessions, Compare picker, Import checklist) | `DataGrid` defaults |
| On a focused chart: **arrows**, **Ctrl**+arrow, **A** *(beta.35, D90)* | Pan, zoom, show all — ScottPlot's keys; the key is then the chart's, so the page neither scrolls nor moves the focus on (Tab still leaves) | `Charts/ChartPlot`, `Charts/ChartKeys` |
| **Esc** | Closes the open `ContentDialog` or `MessageBox` with no result — the same as its Close/Cancel button | `DialogKeyboard`, one class handler per dialog type registered at start-up |
| **Enter** | In the consent dialog's phrase box: enables hooking once the phrase is typed exactly, does nothing before (beta.30, D69); elsewhere in a `ContentDialog`, the default button | WPF's default button (`ConsentPrompt`: `DefaultButton = Primary`) and `ConsentDialogContent.SwallowsEnter` |
**Focus after a dialog, and motion (beta.35).** A `ContentDialog` gives the focus back to the control that opened it: WPF
UI 4.3.0's `ContentDialogHostController` stores `Keyboard.FocusedElement` when the dialog opens and focuses it again, at
`DispatcherPriority.Input`, when it closes — the App adds nothing, and
`FocusAndMotionTests.AContentDialogGivesTheFocusBackToTheControlThatOpenedIt` holds it (a first measurement said
otherwise; it ran on a thread with no dispatcher context, where the dialog's own `finally` never resumed). A WPF UI
`MessageBox` sets no owner — null before and after it is shown — so `Services/MessageBoxes` gives it the App's active
window: it opens over it and hands the focus back to it, not to another program; every box goes through it
(`EveryMessageBoxGoesThroughMessageBoxes`). A page slides in only while Windows' animation effects are on
(`SystemParameters.ClientAreaAnimation`, followed as it changes): `Services/PageMotion` sets the `NavigationView`'s
`Transition` to `None` while they are off, where WPF UI 4.3.0 played `FadeInWithSlide` whatever they were.
**Esc is the Close button, never the primary one.** On the consent dialog (FR-2.1) that is ~~"Keep it off"~~ "Keep hooking
off" *(the button's text, corrected 2026-10-07)*: nothing is
stamped. A dialog that offers no Close button is not dismissed by Esc, and the Legal Gate (FR-11) is a window of its own
(`FirstRunWindow`) with explicit Decline and Accept, on which Esc does nothing. WPF UI 4.3.0 handles no key in
either dialog type (its `ContentDialog.cs` and `MessageBox.cs` at tag 4.3.0 have no key handler — read 2026-09-15),
which is why the handler is ours.
which is why the handler is ours. *(Corrected 2026-10-26, beta.30: its code handles none, but `ContentDialog`'s
TEMPLATE binds each button's `IsDefault` to `DefaultButton` and makes Close `IsCancel` — WPF's default and cancel
buttons, read at the 4.3.0 tag. So Enter goes to the default button: in the consent dialog that was Close until
beta.30, and a typed phrase followed by Enter declined (the owner's report; D69 above in the table). Esc reaches
`DialogKeyboard` first — it handles the bubbling `KeyDown`, and WPF's access keys run after the routing and skip a
handled key — so whether Esc alone would close a dialog through `IsCancel` is read from the template, not measured.)*
### Screen readers
@@ -935,7 +1071,54 @@ which is why the handler is ours.
— corrected 2026-10-04): every `Button`, `ToggleButton`, `ToggleSwitch`, `CheckBox`, `RadioButton`, `ComboBox`,
`TextBox`, `NumberBox`, `PasswordBox`, `Slider` and `HyperlinkButton` in the App's XAML either has content or a name. A new
unnamed one is red.
- Status lines that change after an action (the Database maintenance result) are `AutomationProperties.LiveSetting="Polite"`.
- **What a screen reader is given, swept on every surface (beta.35, D88).** `PagesLoadTests.Automation` hosts every page,
window, dialog and control as the App hosts it, every tab shown in turn, and reads the UI Automation tree WPF builds — the
tree Narrator reads: **no Tab stop without an automation peer** (a plain `Control`, WPF UI's `Image`, `Card` and
`CardControl` take the focus with no peer or an empty name), **no item named by its type** (WPF names a list's, a
drop-down's and a grid row's item by `ToString()`, and a template column's cell, which has no text of its own, by
`Item: <row>, Column Display Index: n`), **every focusable control named**, **no shown text hidden in a template** (a
`TextBlock` whose templated parent is not a `ContentPresenter` is no control element), and **no two buttons in a list
sharing a name**. All five went red on `main` first — the type-named items filled 190 lines over the surfaces and their
tabs, the silent stops 37, and the safety InfoBar's title and message were hidden — and the fixes are: every item type speaks (`ToString()` through `Services/SpokenText`: `Choice` its
label, a notice its title and text, a document page its title, a session row its date, length and tier…); the display-only
controls (`FpsReadout`, `TriStateChip`, `ChangeBadge`) have a `Controls/SpokenTextAutomationPeer` — a Text element named
by their words, no children — and leave the tab order; a template column names its cells through
`Controls/CellName` (a cell style based on WPF UI's `DefaultDataGridCellStyle`, an empty cell read as *empty*); a row's
button names its row (*Open: …*, *Play: …*, *Turn off: …*); the App's InfoBar template draws its title and message through
`ContentPresenter`s; implicit styles take a plain `ItemsControl`, WPF UI's `Image` and `CardControl` out of the tab order;
a `CardExpander`'s expand button is named after its header (`Controls/ExpanderToggleName` — WPF UI 4.3.0 leaves it
unnamed). **The FPS readout says rule 6 aloud**: *Native 62 FPS, displayed 118 FPS, frame generation ×1.9*, a steady factor
with its share, a stand-alone number with its qualifier (`FpsPresentation.Spoken`). `ScreenReaderNamesTests` holds each
piece.
- **Headings (beta.35, owner decision D90).** A page's title (`FontTypography="Title"`) is
`AutomationProperties.HeadingLevel="Level1"`, a section title (`Subtitle`) `Level2`; a `Subtitle` that shows a value — the
Dashboard's three figures, a stat card's value, the FPS readout's line — says `None` on purpose.
`AccessibilityTests.EveryTitleAndSubtitleDeclaresAHeadingLevel` (every Title and Subtitle declares one),
`PagesLoadTests.EveryPageHasOneFirstLevelHeadingItsTitle`. A rendered document's headings (the guide, LIMITATIONS, this
statement, the legal texts) cannot be: a `FlowDocument` `Paragraph` has no automation peer, so it has no heading level to
give — stated in `ACCESSIBILITY.md` §Known limitations.
- **Charts (beta.35, D90).** Every plot is a `Charts/ChartPlot` — ScottPlot's `WpfPlot` with a peer: an Image whose
localized type is *chart*, named by its `AutomationProperties.Name` (`A11y_Chart_*`), its help text where its numbers are
as text (`A11y_ChartData_*`) and its keys (`A11y_Chart_Keys`); no children. Its focus is drawn with WPF UI's
`DefaultControlFocusVisualStyle`. **No two series of a chart differ by colour alone** (`Charts/ChartPatterns`: lines
cycle solid / dashed / dotted / densely dashed, then take markers; point series cycle circle / triangle / square /
diamond; the power and thermal limit spans are striped and dotted) — `PagesLoadTests.NoChartTellsTwoSeriesApartByColourAlone`
reads every chart's legend on every surface and the Compare chart with five sessions.
- **What appears is said as it appears (beta.35, owner decision D89).** `Services/IAnnouncer`, over UI Automation's
notification event in `Services/UiaAnnouncer` — the one place the App raises it, on its **active** window only (a game
that has the screen is never interrupted; the tray's Windows notifications cover a hidden window) and only when a
screen reader listens (`AutomationPeer.ListenerExists`). An **Alert** (`ImportantAll`, every one read): a safety notice as
it arrives (`SafetyNotices`), a warning in the strip, the capture agent going offline, a game page's refusal or warning.
A **Status** (`MostRecent` per activity, a newer one replacing one not yet read): the strip's info and success, the agent
back (`A11y_Agent_Connected`), an update's step (`Services/ShellAnnouncements` says a *change* only — the first state is
read with the window, a download's percent ticks are one step, a rebuilt window re-reads the same state silently), a
game page's success, every Database maintenance result line. The words are the window's, in its language.
`AnnouncementsTests`, `DatabaseMaintenanceViewModelTests.AResultIsSaidToAScreenReaderAsItAppears`.
- ~~Status lines that change after an action (the Database maintenance result) are `AutomationProperties.LiveSetting="Polite"`.~~
*(Corrected 2026-11-09: this announces nothing. WPF raises `LiveRegionChanged` only when the app raises it — "you
explicitly raise an event", Microsoft's* What's new in accessibility *for 4.7.1 — and `TextBlockAutomationPeer` raises
none (dotnet/wpf); the App raised no automation event anywhere. The setting marks the line as a live region and no
more. It came out the same day, for the announcement above; no XAML may set one.)*
### Contrast
@@ -946,7 +1129,11 @@ palette per theme, chosen with the theme). *(Corrected 2026-10-14, beta.23: the
a colour worked out at run time from the artwork and the theme's own text and fill colours, at the strongest opacity at
which every text on it keeps 4.5:1 (tertiary 3:1), so it is held by construction rather than by the theme;
`ColorMathTests` checks the hardest colours in both themes against the tests' own WCAG, and `PagesLoadTests` measures the
rendered band. Its banner's fade is an alpha mask set in code, no colour at all.)*
rendered band. Its banner's fade is an alpha mask set in code, no colour at all.)* *(beta.30: the change markers' badges
and their chips in the list are the palette's orange under black or white chosen by contrast — `ChartTheme.TextOn`,
black in both themes, 11.79:1 and 8.00:1, where ScottPlot's white label read 1.78:1 and 2.63:1;
`ChartMathTests.AChangeBadgesTextReadsOnItsOrangeInEachTheme`. The orange LINE stays under 3:1 against the light
theme's background, as it was before; the badge and the list carry its information.)*
> **"Cannot be broken locally" had a hole, closed 2026-09-16.** `ui:Badge Appearance="Info"` — the Games card's
> "Hooking on/off" and the edit dialog's "Detected" — paints its background with WPF UI's `PaletteLightBlueBrush`, a
@@ -1014,13 +1201,71 @@ rendered band. Its banner's fade is an alpha mask set in code, no colour at all.
> under it, in both themes. `EveryTextFollowsAThemeSwitch` hosts its pages in the presenter too since, and went red with
> them: a page made after a switch stayed black. All three went red on the unfixed XAML before they went green.
> **Windows contrast themes, followed (beta.35, owner decision D91).** WPF UI 4.3.0 cannot be asked to do it:
> `ApplicationTheme.HighContrast` names no dictionary; its four high-contrast files (HC1 Dusk, HC2 Night sky, HCBlack
> Aquatic, HCWhite Desert) each hold 84 red `#FFFF0000` placeholders among 97 colours and 17 brushes that throw when the
> file is read alone; their colours are Windows 11's defaults, not the user's; and they put the window text on the accent.
> So while `SystemParameters.HighContrast` is on, `Services/WpfThemeApplier` applies the light or the dark Fluent theme as
> the contrast theme is (by its window colour), with no Mica and no `SystemThemeWatcher`, and `Services/ContrastOverlay`
> over it: every key of those four files in the user's colour for its role (`Services/ContrastRoles` — a key's role is the
> colour it has in all four, opaque colours only, because inside the App a brush that throws alone falls back to the
> Fluent theme's translucent fill: `MenuBarItemBackgroundPressed` read as the white of the window text, and a pressed menu
> item was white on white; ties and placeholders by the key's name), the keys transparent there transparent, three
> Fluent-only keys by role, the 21 accent keys WPF UI writes into the application's resources as the highlight, and the
> text on the accent as the highlight's text. The colours are `SystemColors` (`ContrastPalette.FromSystem`) — the user's
> own, edited or not, Windows 10's as well — and turning a theme on, editing it or turning it off is followed at once
> (`SystemContrastSource`). What the App draws itself reads `ContrastTheme.Active`: the charts (`ChartPalette.ForContrast`,
> the theme's colours only, the series told apart by `ChartPatterns`), a badge's text (`ChartTheme.TextOn`, the theme's
> colour that reads best on the fill), the mix bar, the artwork band (no tint), the Import list (no dimmed rows), the
> unsigned-update footer (the secondary text style, not an opacity). WPF UI's Danger button paints a fixed `#F44336` in its
> style, out of any resource's reach, so every `ui:Button` takes the App's implicit style (`Styles/FrameLedger.xaml`): a
> Danger button is the theme's own button while one is on, the message boxes' Delete included. Held by `ContrastThemeTests` — the four files still placeholders; every key a role or
> transparent, none red; the roles the same over either Fluent theme; with each default theme's own colours the overlay
> is WPF UI's colours key for key, the text on the accent apart; an edited theme's colours reach every key; every Fluent
> colour key covered; every resource the App reads resolves; `ThemePlan`; the applier on and off at once — and
> `PagesLoadTests.EveryTextIsInTheContrastThemesColoursAndReadable`: every surface rendered under the four default themes
> and two edited ones, every text the theme's colour on the theme's colour at 4.5:1 or better. It went red first on the
> chips (window text on the highlight, 1.26–1.78:1), the Remove button (3.06–4.42:1 on `#F44336`) and the badges' black.
> **A sixth hole, closed 2026-11-09 (beta.35), found by measuring what no sweep renders.** The title bar and the snackbars
> are no surface, and the 3:1 sweep let 3.68:1 pass. The capture agent's pill was a `ui:Badge` whose appearance was
> BOUND — Success, Info, Caution, Danger, WPF UI's `Palette*Brush` under `BadgeForeground` — so `ContrastTests`, which reads
> literal attributes, never saw it: in the light theme 2.78, 2.63, 2.16 and 3.68:1. It is `AgentPill` now (a `Pill` on
> `SystemFillColor{Success,Caution,Critical}BackgroundBrush`, the theme's text), and a bound badge appearance is refused.
> WPF UI's Success and Caution snackbars are fixed colours under white in both themes, 2.78:1 and 2.16:1: the strip shows
> every message as Secondary, the theme's, 13.97:1 and 16.53:1, its icon saying the kind. And a Danger button's text was
> the theme's button text on `#F44336` — white in the dark theme, 3.68:1: the App's implicit button style puts
> `TextFillColorDarkPrimaryBrush` there, 5.3:1 and 5.7:1. `ContrastThemeTests.TheTitleBarsMarksReadInEveryState`,
> `ADangerButtonReadsInBothThemesAndIsTheThemesOwnButtonUnderAContrastTheme`,
> `NoButtonOrBadgeTakesAnAppearanceThatPaintsAFixedColour` and
> `AnnouncementsTests.EveryMessageOfTheStripIsDrawnInTheThemesOwnColours` hold the three.
### DPI
`app.manifest` declares Per-Monitor V2 (`AccessibilityTests.TheManifestIsPerMonitorV2`).
`app.manifest` declares Per-Monitor V2 (`AccessibilityTests.TheManifestIsPerMonitorV2`). A chart reads the pointer
through the element's DPI at that moment (`WpfPlot.GetPlotPixelPosition`, beta.30) — not `WpfPlot.DisplayScale`, which
ScottPlot reads once when the control is made, before it has a window.
### Known gaps, stated
- ScottPlot plots are not keyboard-operable (no focus, no pan/zoom by keys). The numbers behind them are on the
session summary's stat cards and in File ▸ Export (CSV/JSON).
- No screen-reader pass with Narrator has been done; the names above are necessary, not proven sufficient. That pass
is the owner's.
- ~~ScottPlot plots are not keyboard-operable (no focus, no pan/zoom by keys).~~ *(Corrected 2026-11-09, measured by
`ChartKeyboardTests` in a window off the screen: a plot takes focus — ScottPlot's control is focusable and a Tab stop —
and the keys ScottPlot reads reach it: the arrows pan, Ctrl with an arrow zooms, A shows all of it. ~~What it is not is
usable: it has no automation peer, so Narrator says nothing on reaching it, and it marks no key handled, so the page
around it acts on the same arrow too.~~ Since beta.35 it has a peer and keeps its keys, §Screen readers.)* A chart's
points are still not read one by one. The numbers behind them are on the
session summary's stat cards and in File ▸ Export (CSV/JSON); the hardware-change markers' text is WPF text in the
list under each trend chart (beta.30).
- ~~No screen-reader pass with Narrator has been done; the names above are necessary, not proven sufficient. That pass
is the owner's.~~ **The owner's pass, 2026-11-09: keyboard only with the mouse disconnected, and Narrator, on
0.1.0-beta.34 and 0.1.0-alpha.3 — every page, menu, dialog and setting reached and used, no fault.**
- **What that pass could not show**, found the same day by measuring the UI Automation tree WPF builds (in memory, on
.NET 10.0.14 — not by listening): ~~a drop-down's items are named by a record's printed form (`Choice { Value = dark,
Label = Dark }`) and plain lists' items by their type; a control with no automation peer that still takes focus — a
chart, the FPS readout, the RT/PT/RR chips, the game's artwork — is a Tab stop Narrator says nothing about; text inside
a control template (the safety notices' title and message, the readout, the chips) is hidden from the control view;
nothing is announced; no text is a heading; several charts tell series apart by colour alone~~ *(closed the same day,
§Screen readers above)*; ~~page transitions play with Windows' animation effects off~~ *(not since beta.35,
§Keyboard)*; ~~Windows contrast themes are not
followed~~ *(followed since beta.35, D91 — §Contrast)*. `ACCESSIBILITY.md` §Known limitations
states each to users with what to do instead.
+4
View File
@@ -17,6 +17,10 @@ Languages: **en** (neutral/default) · **vi** · **ja**. Same `.resx` pattern as
- One `Strings.resx` (+ `Strings.vi.resx`, `Strings.ja.resx`) per assembly that has user-visible text (`App`, `Shared` ~~for error codes~~ for the safety family, the `Safety_*` keys — corrected 2026-10-04). Access through a generated strongly-typed class; **no string literals in XAML/C# for user-visible text** (analyzer TODO: Meziantou MA0011/manual review in PR checklist). **As built (P3 PR-2, 2026-09-13):** the class is `Strings.Designer.cs`, written by `tools/resx-gen.ps1 -Resx <file>` and **committed** — not the SDK's `ResXFileCodeGenerator`, which the SDK-style WPF project does not run — with `Culture`, `ResourceManager`, `Keys`, and one property per key; the audit below fails when it is stale. The first family is `src/FrameLedger.App/Strings.resx` (65 keys); `Shared`'s arrives with PR-4's `Safety_*` text, because an empty family is what the audit refuses.
- XAML binding via `{x:Static res:Strings.Key}` ~~plus a `LocalizeExtension` for the few dynamic cases~~ *(corrected 2026-10-04: no `LocalizeExtension` exists; text that varies is composed in the view model from `Strings.*`)*.
- **Runtime switching:** setting change → set `CultureInfo.CurrentUICulture` + `Thread` defaults → re-create the main window shell (cheap; state preserved via VM). Persist in `settings`.
**The new window opens on the page that was on screen** *(beta.34, owner request 2026-11-06)* — Settings, after a
change made there. `ShellHost` remembered only the pages opened from code (`PageNavigator`), never a click in the
pane, so a language changed on Settings brought back the last game page opened; it now notes every page the live
window's NavigationView shows (`ShellHost.NoteShown`).
**Two kinds of text did not follow, until beta.15:** a list of choices built once in a static (Settings' themes and update
channels, the Logs page's two lists, the Games page's sort order — `x:Static` read the list built in the language the
App started in), and the singletons that outlive the rebuilt window (the tray's menu, the title bar's Agent pill and the
+10
View File
@@ -64,6 +64,16 @@
> and never the Agent's usage code 1. The catch exists because an exception escaping `Main` runs `Main`'s `finally`
> first, which closes the logger; the AppDomain handler alone would dump with no Fatal line.
>
> **A background service that fails, since 0.1.0-beta.37 (.NET 11, D94).** `--serve` awaits the Generic Host's
> `RunAsync` and catches nothing. On .NET 10 a `BackgroundService` whose `ExecuteAsync` threw stopped the host and
> `RunAsync` completed, so the Agent exited 0 with the fault in the log alone (the host's own line, in `agent-*.log`
> since 2026-09-23). On .NET 11 `RunAsync` rethrows that exception — an `AggregateException` when several services
> failed — so it reaches `Main`'s catch above: Fatal, the dump, and the runtime's exit code. Nothing was changed to get
> this and nothing wraps it: an Agent that stopped because a piece of it broke should not report success. The App
> hosts with `StartAsync` and `StopAsync` inside its own try/catch and is not affected. `HostBackgroundFailureTests`
> holds the runtime's behaviour — a host with one throwing service fails `RunAsync` with that exception; the three
> alphas shipped with it unobserved (`spike-notes` §24).
>
> Tests: `CrashDumpWriterTests` (a real dump of the test process starts `MDMP` and carries the UTC time in its name; the
> prune keeps five and touches no other file; an unusable directory is null and one line), `CrashReporterTests` (the
> order, no report on No, three further exceptions show nothing and are counted, a failed dump still asks, a failed
+13 -3
View File
@@ -1,6 +1,6 @@
# 11 — Updater
Velopack, feeding from GitHub Releases of `https://github.com/poli0981/frameledger`. ~~Stable channel only in v1.~~ *(Corrected 2026-10-04: two channels since P4 PR-5 — `update.channel`, ~~stable by default~~ or beta, which adds pre-releases. Every release so far is a pre-release; see §Built, Channels.)* *(Corrected 2026-10-05: the default is `auto` since beta.14, which follows the running copy — §The update audit, beta.14.)*
Velopack, feeding from GitHub Releases of `https://github.com/poli0981/frameledger`. ~~Stable channel only in v1.~~ *(Corrected 2026-10-04: two channels since P4 PR-5 — `update.channel`, ~~stable by default~~ or beta, which adds pre-releases. Every release so far is a pre-release; see §Built, Channels.)* *(Corrected 2026-10-05: the default is `auto` since beta.14, which follows the running copy — §The update audit, beta.14.)* *(2026-10-31, D73: an **alpha line** beside them, on Velopack's `alpha` channel — §Built, Channels.)*
## Flow
@@ -52,7 +52,7 @@ SemVer `MAJOR.MINOR.PATCH`. Tag `vX.Y.Z` triggers the release workflow (13_CI_CD
## Built 2026-09-14 (P4 PR-5) — what exists, and where it deviates from the above
`src/FrameLedger.App/Update/`. Velopack 1.2.0 (`Directory.Packages.props`, pinned since P0, referenced since
this PR) behind the `IUpdateClient` port — `VelopackUpdateClient` is the one implementation, `UpdateService` the
this PR; **1.2.161 since beta.30**, owner decision D71 — the library and `vpk` together) behind the `IUpdateClient` port — `VelopackUpdateClient` is the one implementation, `UpdateService` the
flow, and the tests run the flow over a fake client because nothing here may touch the network in a test.
- **Startup silent check:** `UpdateHostedService`, 5 s after the host starts (the "5 s after UI idle" above —
@@ -90,7 +90,17 @@ flow, and the tests run the flow over a fake client because nothing here may tou
log — the "re-validated after update" above. Velopack keeps `current` stable, so `Installed` is the expectation.
- **Channels:** `stable` = releases GitHub does not mark pre-release; `beta` = those too (`GithubSource(prerelease)`).
Not Velopack's own `--channel` mechanism — one package set per tag, the GitHub flag decides. `13_CI_CD` §Branch &
release policy.
release policy. *(Corrected 2026-10-31, D73: true of the main line, whose packages are on Velopack's default `win`
channel. **The alpha line uses Velopack's channels**: an alpha is packed with `--channel alpha`, so its feed is
`releases.alpha.json`, and an installed copy reads only its own channel's feed — `VelopackUpdateClient` passes no
`ExplicitChannel`, so the channel is the one the installed package was built for (its `sq.version` names it). Velopack's
`GithubSource` merges the assets of every release that carries that feed, so a beta never sees an alpha and an alpha
never sees a beta, under either setting of `update.channel` — and in an alpha build that picker is locked, its line
saying so (`08_UI` §Settings). **One limit follows from the source, read from Velopack's code 2026-10-31:** it asks
GitHub for one page of ten releases, newest first, so ten releases of one line in a row would hide the other line's
newest from its update check. The cadence is one alpha per beta (`13_CI_CD` §The alpha line) — *while the line tries a .NET; it rests since 0.1.0-alpha.4 (D98, 2026-11-11), betas then follow one another with no alpha between, and once ten of them have been published after alpha.4 a copy of alpha.3 or older no longer finds it: the alpha's notes, the guide and its banner say to install the beta.* Moving between the lines
is a deliberate install, never an update: the other line's `Setup.exe` over the installed copy, which Velopack answers
with its overwrite prompt — the packId, the install folder and the data folder are the same.)*
- **Hooks** (`VelopackHooks`, in the hand-written `Program.Main` so `VelopackApp.Run()` precedes any window):
install registers nothing; uninstall = `UninstallHook` (`12_BUILD` §Publish & package). `Run()` in a copy the
installer did not lay down returns at once and runs no hook (probed on 1.2.0); it does append a line to Velopack's
+98 -6
View File
@@ -1,10 +1,11 @@
# 12 — Build & development environment
Mixed toolchain: .NET 10 for managed projects, MSVC for the native layer.
Mixed toolchain: .NET 11 for managed projects *(since 0.1.0-beta.37, owner decision D94, 2026-11-11; .NET 10 until
0.1.0-beta.36 — §The main line's .NET)*, MSVC for the native layer.
## Prerequisites
- Windows 11 (dev), **.NET 10 SDK**, **Visual Studio 2026** with: .NET desktop development, **Desktop development with C++** (MSVC v143+, Windows 11 SDK ≥ 10.0.22621), C++ ATL not required.
- Windows 11 (dev), **.NET 11 SDK** (11.0.100 or a later 11.0 feature band), **Visual Studio 2026** with: .NET desktop development, **Desktop development with C++** (MSVC v143+, Windows 11 SDK ≥ 10.0.22621), C++ ATL not required.
- **Vulkan SDK** (~~for the layer +~~ validation layers during development, and to run `tools/vklayer-blastradius.ps1`) *(corrected 2026-10-04: the layer builds against the vendored `third_party/vulkan-headers`; CI installs no SDK)*.
- CMake ≥ 3.28 (native projects use CMake; consumed by the solution via a build target — see below).
- Optional: PawnIO for CPU-temperature testing; an NVIDIA GPU for the NVAPI/Reflex paths (dev machine: RTX 5080). AMD/Intel telemetry paths need no SDK — if you have such hardware, testing L1/L2 coverage there is valuable.
@@ -48,9 +49,9 @@ Compiler/linker flags (enforced in CMake, not per-target ad hoc): `/std:c++20 /M
## Managed build & native integration
- **`global.json` pins the SDK band** (`10.0.x`, `rollForward: latestFeature`). Without it `dotnet build` picks the newest installed SDK — on a machine with a .NET 11 preview installed that silently changes analyzer behaviour under `TreatWarningsAsErrors`, and makes local and CI disagree for reasons nobody can see in a diff.
- **`global.json` pins the SDK band** (`11.0.x` since beta.37 — `10.0.x` before — `rollForward: latestFeature`, `allowPrerelease: false`). Without it `dotnet build` picks the newest installed SDK — on a machine with a preview of the next .NET installed that silently changes analyzer behaviour under `TreatWarningsAsErrors`, and makes local and CI disagree for reasons nobody can see in a diff. *(The `alpha` branch carries the same file while its line rests, and pins the SDK it is trying when it does not — §The alpha line.)*
- `Directory.Build.props`:
- **`TargetFramework` = `net10.0-windows10.0.22621.0`** and **`SupportedOSPlatformVersion` = `10.0.19045.0`**. These are two different knobs and must not be conflated: the TFM platform version selects which Windows API projections are available to compile against, while the supported version is the floor CA1416 enforces. NFR-8 requires Windows 10 **22H2** = build **19045**; letting the supported version default to the TFM's would silently accept installs below the stated floor. Two constraints pin the target to 22621 rather than something closer to the floor: the SDK rejects `SupportedOSPlatformVersion` above `TargetPlatformVersion` (NETSDK1135), and 19045 is not a targeting-pack version in any case — the packs are cut at 19041, 20348, 22000, 22621, 26100. The Windows 11 SDK ≥ 10.0.22621 is already a prerequisite above, so this costs nothing. A bare `net10.0-windows` is wrong for a different reason: it resolves to `net10.0-windows7.0`, and CA1416 would then error on Mica, `MiniDumpWriteDump` and `QueryVideoMemoryInfo` — every Windows-10-era API this app is built on.
- **`TargetFramework` = `net11.0-windows10.0.22621.0`** *(`net10.0-…` until beta.36)* and **`SupportedOSPlatformVersion` = `10.0.19045.0`**. These are two different knobs and must not be conflated: the TFM platform version selects which Windows API projections are available to compile against, while the supported version is the floor CA1416 enforces. NFR-8 names Windows 10 **22H2** = build **19045** as the oldest Windows the code is held to *(since D95, 2026-11-11: not blocked there, and neither tested nor supported — Microsoft supports .NET 11 on Windows 11)*; letting the supported version default to the TFM's would silently accept installs below that floor. Two constraints pin the target to 22621 rather than something closer to the floor: the SDK rejects `SupportedOSPlatformVersion` above `TargetPlatformVersion` (NETSDK1135), and 19045 is not a targeting-pack version in any case — the packs are cut at 19041, 20348, 22000, 22621, 26100. The Windows 11 SDK ≥ 10.0.22621 is already a prerequisite above, so this costs nothing. A bare `net11.0-windows` is wrong for a different reason: it resolves to `net11.0-windows7.0`, and CA1416 would then error on Mica, `MiniDumpWriteDump` and `QueryVideoMemoryInfo` — every Windows-10-era API this app is built on.
- `Platforms`/`PlatformTarget` = `x64`. "x64 only" is asserted in CLAUDE.md and NFR-8 but was previously enforced nowhere except an ad-hoc `-r win-x64` on the publish command.
> **`RuntimeIdentifier` is NOT set here, and this bullet claimed it was until 2026-08-06.** The props file's own comment explains why: forcing a RID onto class libraries pulls RID-specific assets into their restore for no benefit, so each executable sets it — `FrameLedger.App`, `FrameLedger.Agent` and now `FrameLedger.CaptureHost`, plus its test project, which needs the same RID to reference a RID'd exe. A new project copying this document rather than the props file would have inherited nothing.
@@ -162,6 +163,90 @@ repairs state, it does not grant machine-wide reach on its own).
> after every sweep; the flag and the button run the same rule. The uninstall hook is still the updater's
> (P4, Velopack).
## The main line's .NET (owner decisions D94 and D95, 2026-11-11)
**The main line — the betas and the first release — builds on .NET 11 since 0.1.0-beta.37**: SDK `11.0.100` (the band
`global.json` pins), runtime and Windows Desktop `11.0.0`, C# 15 by `LangVersion latest`, and the three packages that are
serviced with the runtime (`Microsoft.Extensions.Hosting`, `System.Diagnostics.EventLog`, `Microsoft.Data.Sqlite`) at
`11.0.0`. .NET 11 shipped on 2026-11-10; the owner moved the line the next day.
- **What decided it, and what did not.** `20_OPEN_QUESTIONS` §G held a decision table written on 2026-10-31, before any
evidence: move only after (a) two alphas on the released runtime had passed the gate and an owner's run of a hooked
title, (b) the owner's word on Windows 10, and (c) something .NET 11 brings being wanted. **The owner set (a) aside** —
no alpha had run on the released runtime; three had run on Release Candidate 3 (alpha.1 to alpha.3, the gate green
each time) — decided (b) as D95, below, and for (c) asked for C# 15 in the same release (D96). What stands in for (a)
is this release's own gate on 11.0.100 (`spike-notes` §28) and owner-only item 34.
- **Windows 10 (D95).** Microsoft supports .NET 11 on Windows 11, and on Windows 10 only in its LTSC and IoT editions.
FrameLedger does not block Windows 10 22H2: `SupportedOSPlatformVersion` stays `10.0.19045.0`, so CA1416 still holds
the code to it, and nothing checks the Windows version at start. It is **untested** there — it always was
(`ACCESSIBILITY.md`, `08_UI` §Accessibility) — and now **unsupported** too; NFR-8, `LIMITATIONS.md`, the README and the
guide say so.
- **The processor.** .NET 11 needs x86-64-v2 — SSE4.2 and POPCNT among its instruction sets — and does not start without
it ("The current CPU is missing one or more of the baseline instruction sets"). Its ReadyToRun code targets x86-64-v3
(AVX2 among others); Microsoft says a processor that lacks those may pay for it at start-up, where that code is
compiled again. Every processor Windows 11 accepts has x86-64-v2.
- **What .NET 11 changes in the software**, measured or read: `IHost.RunAsync` rethrows the exception of a
`BackgroundService` that failed, so the Agent's `--serve` leaves through its crash report where on .NET 10 it exited 0
(`10_LOGGING` §Crash handling; `HostBackgroundFailureTests` holds it); `Microsoft.Data.Sqlite` 11 declares SQLitePCLRaw
3.0.5, whose engine is SourceGear's `SQLite` package; nine `Microsoft.Extensions.*` libraries are part of the runtime
and no longer packages beside it (`legal/licenses/nuget/`: 78 packages became 69).
- **C# 15 (D96)** is the language the main line compiles, and none of its constructs is used yet: the analyses do not
read them (`13_CI_CD` §C# 15 and the analyses, `spike-notes` §29). What beta.37 takes from .NET 11 is API.
- **Going back** is installing 0.1.0-beta.36 over a later build: the ledger's schema did not move with the runtime.
## The alpha line (owner decisions D73–D76, 2026-10-31; resting since D98, 2026-11-11)
The owner, 2026-10-31: an alpha build, "a place where new .NET versions are tried", with code updated where needed and a
warning that it is an experiment used at one's own risk. **The alpha line** is the source of a released beta built to
try a newer .NET — at times a prerelease one — from the long-lived `alpha` branch, published as `vX.Y.Z-alpha.N` GitHub
pre-releases on Velopack's `alpha` channel (`13_CI_CD` §The alpha line, `11_UPDATER` §Channels). It tried .NET 11:
Release Candidate 3 in alpha.1 to alpha.3 (2026-10-31 to 2026-11-06), the release itself in alpha.4.
- **The line rests since 0.1.0-alpha.4 (D98, 2026-11-11).** The main line moved to .NET 11 the day after it shipped
(§The main line's .NET), so alpha.4 is 0.1.0-beta.37's source on the same .NET 11.0.0 — published so that a copy of
alpha.3 leaves the release candidate by an update, since an alpha never updates to a beta. After it no alpha is cut
until a newer .NET has a preview to try (.NET 12's, expected in 2027). While the line rests, the `alpha` branch differs
from main in **`RELEASE_LINE` alone** (`git diff main alpha --name-only` prints that one name), and a resting alpha
gets no update: its anti-cheat list, which reaches a user only inside a release (`13_CI_CD` §rules-publish.yml), stays
the one it shipped with. Its notes, the guide and the Alpha notice tell its user to install the beta — **and the build
itself does**: `Directory.Build.props` stamps its `FlAlphaLineRests` property (true on main since beta.37) into every
assembly, `Shared.AlphaLine.Rests` reads it, and an alpha cut while it is true shows a banner that says the line is
paused and to install the beta, in place of the experimental-build one (`App/Services/AlphaTexts`; D97: the words
"a prerelease .NET" appear only where the runtime's own description is a prerelease's).
- **The switch — what `alpha` differs from main in while it tries a newer .NET, and nothing else:** `RELEASE_LINE`
(`alpha`); `global.json` (that SDK, with `allowPrerelease: true` when it is a prerelease); the TFM in
`Directory.Build.props` (`SupportedOSPlatformVersion` stays `10.0.19045.0`); the three Microsoft packages in
`Directory.Packages.props` that are serviced with the runtime (`Microsoft.Extensions.Hosting`,
`System.Diagnostics.EventLog`, `Microsoft.Data.Sqlite`); `legal/licenses/nuget/` regenerated for that package set and
the *Transitive* row of `legal/THIRD_PARTY_NOTICES.md`; `FlAlphaLineRests` set to `false` in `Directory.Build.props`;
and a fix only the newer .NET can take, if one is ever forced.
As it stood for .NET 11 RC3: SDK `11.0.100-rc.3.26522.148`, `net11.0-windows10.0.22621.0`, the three packages at
`11.0.0-rc.3.26522.148` (`spike-notes` §24). **No newer language syntax and no preview feature on `alpha`** (D76): the
source is main's, and main compiles with its own SDK.
- **Everything else lives on main**, dormant on the main line. `RELEASE_LINE` is read like `VERSION` and stamped into
every assembly as the `FrameLedger.ReleaseLine` metadata (`Directory.Build.props` refuses any value but `main` and
`alpha`); `Shared.BuildLine` reads it back for the App and the Agent, which compose with it rather than reading it
where they act, so a test hands either line to the code it tests. On the alpha line they act on it (D74): the Alpha
notice in the Legal Gate with its own tick box, the Agent's wait for it, the ALPHA badge and banner, the locked update
channel (`08_UI`), and the ledger's copy before an alpha first opens it (D73, `06_DATA_MODEL` §Migrations). What the
alpha's SDK asks of the source and main's can also take lands on main.
- **The native layer does not change.** MSVC builds it from the same source; only its build id differs (the alpha's
tag). The hook, the guard and the Vulkan layer in an alpha are the beta's.
- **Sync, and the cadence while it tries a .NET.** After each beta release a pull request merges main into `alpha` with
a merge commit (the repository allows them; the linear rule is main's) and the next alpha is cut from it — **one alpha
per beta, never several in a row**, because Velopack reads only the newest ten releases (`11_UPDATER` §Channels). A
conflict in a switch file is resolved for the switch; `legal/licenses/nuget/` by regenerating it on `alpha`
(`tools/license-gather.ps1`). An alpha older than the ledger's schema refuses to open it (`LedgerSchemaException`), so
a beta that adds a migration is followed by an alpha soon. **The sync that ended the .NET 11 trial** (alpha.4) went
the other way round: every switch file conflicted and main's version was taken for each, leaving `RELEASE_LINE`.
- **Building it locally:** check out `alpha` with the SDK its `global.json` names installed and run `./build.ps1 check`
as on main.
- **Starting the next trial** (a preview of the next .NET): the switch above on `alpha`, the whole gate in a throwaway
worktree first (`spike-notes` §24 is the pattern, with its decision table written before the run), and the Alpha
notice's sentence naming the .NET.
- **Whether the main line follows a trial** is the owner's each time: `20_OPEN_QUESTIONS` §G, *The main line's .NET*,
holds the table and what happened to it for .NET 11.
## Version
**One source: the `VERSION` file at the repository root** (`MAJOR.MINOR.PATCH`, nothing else — P4 PR-5,
@@ -217,6 +302,10 @@ vpk download github --repoUrl https://github.com/poli0981/frameledger --channel
vpk pack --packId FrameLedger.App --packVersion {ver} --packDir out/app --mainExe FrameLedger.exe --packTitle FrameLedger --packAuthors FrameLedger --releaseNotes out/notes.md --outputDir out/release
```
> **On the alpha line (D73, 2026-10-31) both vpk commands take `--channel alpha`** — the download, so an alpha's delta
> is made from the previous alpha, and the pack, so its feed is `releases.alpha.json`, which no beta reads. The main
> line's pack keeps the command above exactly (no `--channel`: Velopack's default on Windows is `win`). §The alpha line.
> **Run by `release.yml` since 2026-09-14 (P4 PR-5)** — `13_CI_CD` §release.yml carries the steps around it
> (the version gate, `{{RELEASE_DATE}}`, the published-tree assertion, checksums, the release). Both publishes
> take `-p:Version=<tag>` (§Version). No `--icon`: `assets/icon.ico` does not exist, and this line named it
@@ -299,7 +388,10 @@ would not fit).
`release.yml` call `./build.ps1 check` with no switches since 2026-09-06, as the paragraph after this list says;
only `-SkipIntegration`, which nobody passes, leaves them out, loudly)*
7. `tools/coverage-gate.ps1` — reads this run's cobertura reports; self-arming, and armed today for
`FrameLedger.Domain` and `FrameLedger.Application`
`FrameLedger.Domain` and `FrameLedger.Application`. *(Since 2026-10-25 step 6 writes OpenCover beside each
Cobertura report — `--collect:"XPlat Code Coverage;Format=cobertura,opencover"` — for SonarCloud, whose C# importer
reads no Cobertura; `ci.yml`'s `sonarcloud` job takes them from the gate's artifact, `13_CI_CD` §SonarCloud. This
gate still reads Cobertura only.)*
8. `tools/rules-validate.ps1` (schema + `anticheat` block sanity — a malformed or empty blocklist is a safety bug)
9. `tools/versioninfo-check.ps1` — reads the built binary, because what ships is what an anti-cheat vendor sees; since P4 PR-5 it also compares every `FileVersion` against the `VERSION` file (§Version); **since beta.14 (D50) both halves run — the self-test, then the native five and the managed eight from the App's and the Agent's build output** (`-ManagedDir`, `-ExpectedProductVersion` = `VERSION`), one copyright across all of them (§Version, *Identity*). Under `-SkipNative` the managed half still runs
10. `tools/chokepoint-check.ps1` — injection and evasion primitives confined to one file, native **and** managed, plus the `FL_GUARD_TESTABLE` symbol check against the shipped artifacts
@@ -309,7 +401,7 @@ would not fit).
13b. `tools/accuracy-check.ps1 -SelfTest`, then live — the accuracy block is ONE text (`legal/ACCURACY.md`) embedded verbatim in `README.md` and `legal/DISCLAIMER.md` §4; a copy that drifted, a copy with no markers, or an empty source is red. Four self-test cases, both directions (§S23-6, 2026-09-06)
13c. **`tools/notice-check.ps1 -SelfTest`, then live** (beta.12, owner decision D45, 2026-10-03) — every first-party source file (`.cs .cpp .h .inl .ps1 .xaml`, tracked or new, minus `src/native/third_party/`) opens with `SPDX-License-Identifier: GPL-3.0-only` and `Copyright (C) 2026 poli0981 - additional terms under GPLv3 section 7: see NOTICE` in its own comment syntax, because GPLv3 §7 wants additional terms named "in the relevant source files" (`NOTICE` carries them); the second line may name another holder and year in the same form (a contributor's own file).
Seven self-test cases, both directions; `./tools/notice-check.ps1 -Fix` writes a missing header, and `tools/resx-gen.ps1` generates the accessor with it
13d. **`tools/wiki-build.ps1 -SelfTest`, then `-Check`** (beta.17, owner decisions D53/D54, 2026-10-07) — assembles the GitHub Wiki from `wiki/`, `guide/` and `LIMITATIONS.md` into a temporary folder, as `wiki.yml` does at a release (`13_CI_CD` §wiki.yml), and fails on a link to a file, folder or section that does not exist, two sources for one page, a page that neither Home nor the sidebar leads to, a sidebar that lists the guide in another order than `guide/README.md`, a backticked repository path in a `wiki/` page that names nothing, and a version number written into a `wiki/` page (the footer says which release the wiki shows). Nine self-test cases, both directions
13d. **`tools/wiki-build.ps1 -SelfTest`, then `-Check`** (beta.17, owner decisions D53/D54, 2026-10-07) — assembles the GitHub Wiki from `wiki/`, `guide/`, `LIMITATIONS.md` and (beta.35) `ACCESSIBILITY.md` into a temporary folder, as `wiki.yml` does at a release (`13_CI_CD` §wiki.yml), and fails on a link to a file, folder or section that does not exist, two sources for one page, a page that neither Home nor the sidebar leads to, a sidebar that lists the guide in another order than `guide/README.md`, a backticked repository path in a `wiki/` page that names nothing, and a version number written into a `wiki/` page (the footer says which release the wiki shows). ~~Nine~~ Ten self-test cases since beta.35 (the statement's page, D88), both directions
14. `tools/changelog-check.ps1 -SelfTest` — nine cases, five expected RED. The live half needs a pull request's changed-file list and is supplied by `ci.yml`
14b. `tools/release-notes.ps1 -SelfTest` — five cases over a fixture changelog (a dated and an undated section, a missing one, a prefix that must not match, an empty one), and since beta.24 three over a temporary tree: a version with its own `docs/changelog/<version>.md` is read from it, one without from `CHANGELOG.md`, a prefix of a file name is not that file. The live half needs a tag's version and runs in `release.yml`, where a missing or empty section is a red release (P4 PR-5)
14d. **`tools/docs-split-check.ps1 -SelfTest`, then live** (beta.24, owner decision D66) — `CHANGELOG.md` holds no released section beside `[Unreleased]`; each `docs/changelog/<version>.md` holds one `## ` heading, its own `## [<version>] - date`, and no relative link (the App renders release notes as `CHANGELOG.md`); `CHANGELOG.md` and the files under `docs/changelog/`, and `docs/HANDOFF.md` and the files under `docs/handoff/` — and since PR-5 `docs/20_OPEN_QUESTIONS.md` and `docs/open-questions/`, `docs/spike-notes.md` and `docs/spike-notes/` — name each other in both directions. Eleven self-test cases, both directions
+442 -21
View File
@@ -6,9 +6,9 @@ FrameLedger uses the **`poli0981/.github` ops repo** where its templates fit, an
## Workflows (`.github/workflows/`)
### `ci.yml` — push to `main` + all PRs + `workflow_dispatch` (added 2026-10-04) · **repo-local**
### `ci.yml` — push to `main` *(and to `alpha` since 2026-10-31, D73 — §The alpha line)* + all PRs + `workflow_dispatch` (added 2026-10-04) · **repo-local**
- `runs-on: windows-latest`, .NET SDK pinned by `global.json` via `actions/setup-dotnet`, MSVC via `ilammy/msvc-dev-cmd` (pinned to its v1.13.0 commit since beta.24 — the one third-party action, SonarCloud `githubactions:S7637`; Dependabot moves the pin), NuGet cached.
- Single step of substance: **`./build.ps1 check`** — the same script, with the same switches (none), a developer runs before pushing. The gate list lives in `12_BUILD` §Local quality gate, **once**, rather than being restated here where it goes stale.
- Single step of substance: **`./build.ps1 check`** — the same script, with the same switches (none), a developer runs before pushing. The gate list lives in `12_BUILD` §Local quality gate, **once**, rather than being restated here where it goes stale. *(That is the `check` job. Since 2026-10-25 a second job, `sonarcloud`, runs after it — §SonarCloud below; it is not the gate and not a required context.)*
- ~~**`-SkipIntegration` is the one place local and CI deliberately differ**~~ — **gone since 2026-09-06.** From 2026-08-05 CI passed it for a measured reason: §S16 puts the injecting process's ancestors in the scan set, a .NET test host loads `System.Security.Cryptography.ProtectedData.dll`, and the guard's `protect` fragment refused our own harness (§S19(b)). The signer half now verifies that module's embedded signature offline and reads `O=Microsoft Corporation` on the compiled-in bound, so the `Category=Integration` cases run here — **nine** when this was written, **20 across six classes** as of 2026-09-13 (Agent 6, CaptureHost 7, Infrastructure 7); count them with `grep -rl 'Category", "Integration' tests` rather than trusting either number — and a green CI IS evidence for the managed drain and the capture host's end-to-end behaviour. The switch remains in `build.ps1`, loud, for a developer who must.
- **The hosted runner refuses guard scans intermittently — THREE failures in eight gate runs, measured
2026-09-10 while merging P2's stack.** Every one was an `Category=Integration` case, every one passed on
@@ -80,7 +80,7 @@ FrameLedger uses the **`poli0981/.github` ops repo** where its templates fit, an
The next Integration failure is the measurement: read the probe step *before* re-running. Struck rather
than deleted because a session planned a workflow change on this bullet's word.
- **Signer probe step** (2026-09-06): `fl-probe-signer` runs as its own step after the gate — `continue-on-error`, a measurement and not a gate — because `ctest fl_signer_probe` passes on a regular expression and prints nothing, so §S19(b)'s CI leg was never readable from the log. Its answers are read off this step.
- Uploads coverage artifacts.
- Uploads coverage artifacts — ~~Cobertura~~ Cobertura and OpenCover since 2026-10-25, one pair per test project, as the `coverage` artifact the `sonarcloud` job reads (§SonarCloud).
- **Changelog gate**, on pull requests only: the changed-file list comes from GitHub's own view of the PR — not `git diff`, so a shallow checkout cannot silently produce a short one — and an empty list is refused rather than read as "no `src/` changes". It is a **step of the required `check` job** and deliberately not a job of its own: `main`'s required contexts are exactly `check` and the two `analyze` jobs, so a new job would go red while the merge button stayed green, which is what already makes `Rules / validate` advisory (§S23-2).
> **Three claims in this section were false and are corrected 2026-08-06.** There is no Vulkan SDK
@@ -93,16 +93,45 @@ FrameLedger uses the **`poli0981/.github` ops repo** where its templates fit, an
> corrected with it; restating the gate list in two documents is what let one of them rot.
- **Licence guard:** `tools/license-check` fails the build if a vendored dependency is missing its licence copy, or if Intel IGCL / AMD ADLX headers appear anywhere in the tree (`docs/18_GPU_VENDOR_APIS.md` §Vendor SDKs we deliberately do not use), or — since P4 PR-6 — if `legal/licenses/nuget/` is not what `tools/license-gather.ps1` writes for the NuGet packages this build ships. A Dependabot bump therefore goes red until someone re-runs the script and commits the texts, which is the point: the new version's licence is read by a person before it ships. Licensing regressions are silent and hard to unwind later — catch them at PR time.
- **Placeholder guard:** fails if any `{{` token survives in `README.md` or `legal/*.md` *(other than `{{RELEASE_DATE}}`, which `release.yml` substitutes — added 2026-10-04)*. Those are shipped, legally operative documents (FR-11 displays them in the first-run Legal Gate); an unsubstituted `{{DEVELOPER_NAME}}` in an EULA is not a cosmetic defect.
- ~~`permissions: contents: read`.~~ `permissions: contents: read, pull-requests: read` — the second for the Changelog step's list of a pull request's files, read-only *(corrected 2026-10-04)*.
- ~~`permissions: contents: read`.~~ `permissions: contents: read, pull-requests: read` — the second for the Changelog step's list of a pull request's files, read-only *(corrected 2026-10-04)*. *Since 2026-10-25 per job:* the workflow grants nothing (`permissions: {}`), `check` holds those two and `sonarcloud` `contents: read` alone — a workflow-level grant reaches every job (SonarCloud `githubactions:S8264` on the first analysis from CI).
### `codeql.yml` — push, PR, weekly cron · **repo-local**
### `codeql.yml` — push, PR, weekly cron, `workflow_dispatch` (since 2026-11-11) · **repo-local**
> **Not a caller stub, which this heading said until 2026-08-06.** `codeql.yml`'s own header says
> the opposite: the ops repo has `codeql-mixed.yml`, but C++ needs manual build mode driven by the
> CMake preset and that input surface has not been verified. The paragraph below already anticipated
> exactly this outcome; the heading was never updated when it happened.
- Languages: `csharp` **and `cpp`** (manual build mode for C++, driven by the CMake preset). The native layer is where memory-safety bugs would live; excluding it would defeat the purpose. Verify the mixed template exposes a C++ build-command input; if it does not, this one goes repo-local too.
- **And `actions`, since 2026-10-25** (build mode `none`): CodeQL reads `.github/workflows` for injection from event data, untrusted checkouts and over-broad tokens — the class of finding SonarCloud raised once (`githubactions:S7631`, `wiki.yml`, beta.26). Its context, `analyze (actions, none)`, is not one of `main`'s required checks; adding it to them is the owner's setting.
- **Concurrency, since 2026-10-25:** a new push to a pull request cancels that pull request's run; a push to `main` and the weekly scan each run in a group of their own (the run id), so none is cancelled or left pending, and the default branch's alerts come from a finished analysis.
- `permissions: security-events: write, contents: read`.
- **On .NET 11 since beta.37 (D94) — measured on the pull request that moved the line (#376, run 42916491104, CodeQL
2.27.4).** CodeQL's documentation lists C# up to 14 and .NET up to 10, and `analyze (csharp, none)`, a required
context, had never met `net11.0`. With build mode `none` the extractor reads the source with its own compiler front
end and uses a `dotnet` only for references: it found the 11.0.100 SDK `setup-dotnet` had installed and used that (on
.NET 10 it downloaded 10.0.100 for itself), restored, and reported 363 resolved references and none unresolved, 9
types it could not resolve (main's last run on .NET 10, 42862718138: 23, in three `Windows.Win32` namespaces), and
**`CodeQL scanned 1220 out of 1220 C# files`** — main's line, word for word — in 4 min 5 s. The source it read used
no C# 15 construct. **What it reads of C# 15 is measured construct by construct before one is used** (D96): a
construct in whose file the extractor reports an error is not used on main until CodeQL reads it, and the same holds
for Qodana's engine (§Qodana).
*(Corrected the same day, two pull requests later: that run was an **overlay** — on a pull request the C# analysis
extracts the files it changed on top of the database cached from `main`, then a .NET 10 one — so its "1220 out of
1220" was `main`'s baseline figure and its other numbers the changed files'. The whole source on `net11.0` was first
read by `main`'s own run after the merge (42921492229, "Overlay mode not enabled"): 1,221 source files, 363
references resolved and none unresolved, 23 types unresolved in the three `Windows.Win32` namespaces — the figure it
had on .NET 10 — and "CodeQL scanned 1221 out of 1221 C# files", in 4 min 45 s. So CodeQL reads `net11.0` as it
read `net10.0`; and for a construct it has not met, a pull request's run is not the evidence — a
`workflow_dispatch` on the branch is, §C# 15 and the analyses.)*
### `qodana.yml` — push to `main`, pull requests into `main`, `workflow_dispatch` · **repo-local, built 2026-11-10 (D93)**
- One job, `qodana`, on `ubuntu-latest` — the only Linux job in this repository, because the linter is a Linux
container: `JetBrains/qodana-action` (pinned to `v2026.2.2`'s commit; Dependabot moves the pin) runs Qodana Community
for .NET over `FrameLedger.slnx` with `qodana.yaml`'s settings. §Qodana below says what it reads, what was changed
from JetBrains' template and where an inspection is switched off.
- **Advisory, with a gate of zero problems:** one problem turns the job red; it is not a required context.
- `permissions: contents: read, checks: write, pull-requests: write` — the annotations and the one comment; granted to
the job, the workflow grants none.
### `release.yml` — on tag `v*` · **repo-local, built 2026-09-14 (P4 PR-5)**
@@ -159,13 +188,21 @@ FrameLedger uses the **`poli0981/.github` ops repo** where its templates fit, an
package) moves to `out/previous`, the feed and `RELEASES` are filtered to this build, and a downloaded previous package
with no delta beside it fails the job. A failed download is a warning: the release is full-only, as every one before it
was (`11_UPDATER` §Built).
- `vpk pack --packId FrameLedger.App` (the `vpk` tool pinned to the library's 1.2.0) with the release notes;
- `vpk pack --packId FrameLedger.App` (the `vpk` tool pinned to the library's ~~1.2.0~~ 1.2.161 since beta.30, D71) with the release notes;
`FrameLedger.App-win-Setup.exe` must come out, because README §Install names it. **Not `--packId FrameLedger`**:
Velopack installs into and uninstalls `%LOCALAPPDATA%\<packId>`, which with that id is the data folder
(`12_BUILD` §Publish & package). No `--icon` until `assets/icon.ico` exists.
- `SHA256SUMS.txt` over every asset, published beside them and printed into the release body (`11_UPDATER`
§Unsigned releases).
- `gh release create` with the assets, `--verify-tag`, and `--prerelease` for a `-beta.N` tag.
- **The alpha line (D73, 2026-10-31):** the version gate reads `RELEASE_LINE` beside `VERSION` and refuses a tag that
disagrees with it — on the `alpha` line only `vX.Y.Z-alpha.N`, and an `-alpha.` tag nowhere else. An alpha's download
and pack take `--channel alpha`, so the feed, the asset list, the legacy index and the installer are named for that
channel (`releases.alpha.json`, `assets.alpha.json`, `RELEASES-alpha`, `FrameLedger.App-alpha-Setup.exe`, and the
packages themselves, `FrameLedger.App-<version>-alpha-full.nupkg` / `-alpha-delta.nupkg` — measured on the first alpha's
rehearsal, after which the delta check reads the name from `assets.<channel>.json` rather than building it) and its delta
is made from the previous alpha; the main line's pack is unchanged. The release is titled *(experimental alpha)*, and
its notes — the alpha's own file, `docs/changelog/x.y.z-alpha.N.md` — open with the warning (§The alpha line).
- The assets and the notes are also uploaded as a workflow artifact for the smoke checklist (`14_TESTING`
§Release smoke).
- ~~Optional final step: submit installer hash to VirusTotal~~ — not built; an upload of the installer to a third
@@ -201,15 +238,18 @@ FrameLedger uses the **`poli0981/.github` ops repo** where its templates fit, an
### `wiki.yml` — after a successful Release run, and by hand · **repo-local, built 2026-10-07 (beta.17, D53/D54)**
- **What:** the GitHub Wiki is a copy of the repository's own pages — `wiki/` (Home, the sidebar, the developer pages)
and `guide/` (the user guide: the End-user part, the same pages the App shows) with `LIMITATIONS.md`.
`tools/wiki-build.ps1` names each page (a guide page after its first heading, `guide/README.md` as *User-guide*,
`LIMITATIONS.md` as *Limitations*), rewrites links between pages to page names and every other repository link to
and `guide/` (the user guide: the End-user part, the same pages the App shows) with `LIMITATIONS.md` and, since
beta.35 (D88), `ACCESSIBILITY.md`. `tools/wiki-build.ps1` names each page (a guide page after its first heading,
`guide/README.md` as *User-guide*, `LIMITATIONS.md` as *Limitations*, `ACCESSIBILITY.md` as *Accessibility*), rewrites links between pages to page names and every other repository link to
its address on GitHub **at the release's tag**, drops each page's first heading (the wiki prints the page name), and
writes a footer naming the tag. The same assembly is `build.ps1`'s `wiki-check` gate (`12_BUILD` §Local quality gate,
13d), so a dead link is red on the pull request, never on the published wiki.
- **When:** `workflow_run` on `Release`, completed — the job runs only when that run succeeded and was started by a
pushed `v*` tag, so a `workflow_dispatch` rehearsal of `release.yml` never publishes. It checks out the run's
`head_sha` (a `workflow_run` job runs `main`'s copy of this file) and links at `head_branch`, the tag. By hand:
pushed `v*` tag in this repository (`head_repository` is checked since beta.26: a fork cannot start the Release run,
and the condition now says so — SonarCloud `githubactions:S7631`), so a `workflow_dispatch` rehearsal of
`release.yml` never publishes. It checks out the run's
`head_sha` (a `workflow_run` job runs `main`'s copy of this file) and links at `head_branch`, the tag. **Not after an
alpha's release** (D73, 2026-10-31: a `-alpha.` tag is skipped): the wiki shows the newest beta. By hand:
`gh workflow run wiki.yml -f ref=main -f publish=false` builds, checks and uploads the pages as an artifact; with
`publish=true` it publishes them.
- **Why not a step of `release.yml`:** the release stays as it was, its rehearsal stays a pure rehearsal, and a wiki
@@ -222,9 +262,156 @@ FrameLedger uses the **`poli0981/.github` ops repo** where its templates fit, an
- `permissions: contents: write` — the repository's default workflow token is read-only (read from the API,
2026-10-07), and pushing to the wiki repository needs write.
## SonarCloud — Automatic Analysis, no workflow (beta.24, owner decision D67)
## The alpha line — the `alpha` branch (owner decisions D73–D76, 2026-10-31; resting since D98, 2026-11-11)
The project `poli0981_frameledger` is analysed by SonarCloud's GitHub app in **Automatic Analysis** mode: on every
What it is, what differs on the branch and why it rests since 0.1.0-alpha.4: `12_BUILD` §The alpha line. What CI and the
release do with it:
- **`ci.yml`** runs `check` on a push to `alpha` and on every pull request into it, under the branch's own `global.json`
— `setup-dotnet` installs the exact SDK it names whatever the `rollForward`, a prerelease one included. The
`sonarcloud` job does not run for the branch (the organisation's plan analyses main alone, §SonarCloud), and neither
does the `Changelog` step: what an alpha changes is written in its release's own file on main, never in an
`[Unreleased]` entry on `alpha`, which would collide with main's at every sync.
- **`codeql.yml` and `qodana.yml`** stay on main: the source is main's, and it is analysed there. *(Until beta.37 the
reason given here was the alpha's compiler — C# 15, where CodeQL's extractor read C# 14. Main compiles C# 15 since
beta.37; what CodeQL reads of it is §`codeql.yml`'s to say.)*
- **The branch is not protected** (an owner's setting; none was asked for): pull requests into it are how changes land
(squash), and the sync from main is a pull request merged with a merge commit — main's linear rule is main's alone.
- **A release of the line**, in order: the alpha's notes on main (`docs/changelog/x.y.z-alpha.N.md` opening with the
warning, its row in `CHANGELOG.md`'s Releases table, a line in HANDOFF's START HERE) → the sync pull request into
`alpha` → a `release.yml` dispatch on `alpha` (`gh workflow run release.yml --ref alpha -f version=x.y.z-alpha.N`) →
the signed tag on `alpha`'s head → the run (§release.yml: the line's tag rule, `--channel alpha`). **No wiki publish**
(`wiki.yml` skips an `-alpha.` tag) and **no release line moves**: README, ACCURACY, the Disclaimer's copy,
LIMITATIONS and ACCESSIBILITY keep naming the newest beta.
- **The cadence while the line tries a .NET:** one alpha per beta, cut from it. Velopack's GitHub source reads the
newest ten releases (one page, `perPage` 10), so ten alphas in a row would hide every beta from the betas' own update
check, and the other way round (`11_UPDATER` §Channels). **While it rests** no alpha is cut, and that limit has a
consequence the alpha's notes state: once ten betas have followed alpha.4, a copy of alpha.3 no longer finds it.
## SonarCloud — from CI, `ci.yml`'s `sonarcloud` job (owner decision D68, 2026-10-25)
**D68 — SonarCloud is analysed from CI.** The owner turned SonarCloud's Automatic Analysis off and set the
`SONAR_TOKEN` secret (2026-10-24), and asked for the CI-based analysis with the newest scanner, run until its quality
gate passed on issues and coverage both. It replaces D67 (the subsection below, as it stood): `.sonarcloud.properties`
is gone, `SonarQube.Analysis.xml` holds what it held, and the two rules broken by design everywhere are configuration
rather than marks in the UI.
**How it runs.** A second job of `ci.yml`, after `check` (`needs: check`), on every pull request from this
repository and every push to `main` (or a `workflow_dispatch` of `main`) — never another branch: the organisation's
plan refuses a branch analysis ("Organization is not allowed to access data from non main branches", a dispatch of
the feature branch, 2026-10-25), so a dispatch of any other branch runs `check` alone:
1. a full-depth checkout (blame dates the new code; the tags name the version), .NET, MSVC, the NuGet and
`~/.sonar/cache` caches;
2. the gate's coverage — the `coverage` artifact `check` uploaded, not a second test run;
3. `cmake --preset x64-release -DCMAKE_EXPORT_COMPILE_COMMANDS=ON -DCMAKE_CXX_SCAN_FOR_MODULES=OFF` and the one
header the build generates (`fl_ac_floor_gen`) — the compilation database, with nothing compiled. *Scanning off
because the first run failed on it:* with C++20 and Ninja, CMake gives every compile command an
`@<object>.modmap` response file that only the build writes, and the C/C++ analyser (CFamily 6.85) stops with
`IllegalStateException: unexpanded response file`; no source here uses a module;
4. **SonarScanner for .NET 12.0.0** (2026-10-15, the newest), a local tool (`.config/dotnet-tools.json`, `dotnet tool
restore`; Dependabot's nuget entry moves it), which provisions its own JRE: `begin` with `/s:SonarQube.Analysis.xml`
→ `dotnet build FrameLedger.slnx -c Release` → `end`.
**Why a job of its own, and a build of its own.** The scanner's targets turn `TreatWarningsAsErrors` off and empty
`WarningsAsErrors` in every build they instrument (`SonarQube.Integration.targets`, read in 12.0.0's source), so
wrapping the gate's build would quietly weaken the gate. And the job is **advisory**: `main`'s required contexts stay
`check`, `analyze (csharp, none)` and `analyze (cpp, manual)`. It waits for the quality gate
(`sonar.qualitygate.wait`), so a failed gate — or a SonarCloud outage — is a red job beside a green `check`, never a
blocked merge, and SonarCloud's app still posts its own *SonarCloud Code Analysis* check on the pull request.
**The C++.** The SonarScanner for .NET analyses only files an MSBuild project names: it drops `sonar.sources`, and
its scan of the files outside the projects (`sonar.scanner.scanAll`: PowerShell, YAML, JSON and a dozen more) has no
C or C++ in its list (`AdditionalFilesService`, 12.0.0). So `FrameLedger.Infrastructure.csproj` — the project that
reaches the native layer — names `src/native`'s `.cpp` and `.h` files, `third_party` excepted, as `FlNativeSource`
items, read through the scanner's `SQAdditionalAnalysisFileItemTypes`. The items exist only in a build the scanner
instruments (its ImportBefore targets set `SonarQubeTempPath`), so a normal build, an IDE and a publish never see them;
because they lie outside the project's folder, the scanner analyses them at the root, with the compilation database:
MSVC's own flags and defines, where Automatic Analysis guessed them. Native code has no coverage report (below).
**Coverage.** `build.ps1` collects `"XPlat Code Coverage;Format=cobertura,opencover"`: Cobertura for
`tools/coverage-gate.ps1`, as before, and OpenCover for SonarCloud, whose C# importer reads no Cobertura. The
reports' paths are absolute, and every hosted Windows runner checks out to the same path, so the reports `check`
wrote name the sources this job reads. Only `tests/*/TestResults/<guid>/` is read; the trx logger's second copy under
`In/` is not. **Coverage is the C#'s alone** (`sonar.coverage.exclusions`): SonarCloud counts the executable lines of
a file no report covers as uncovered — the first pull request analysis read `build.ps1`'s 232 lines to cover, every
one uncovered, and failed the gate at 0 % on the two it changed — so the PowerShell tools (proven by their own
`-SelfTest` cases, which no coverage tool reads) and the native code (Catch2 and the injection tests, with no coverage
collector) are left out of the coverage figures; they are analysed for issues as everything else is. Measuring the
native code would be the runner's Visual Studio coverage tool and `sonar.cfamily.*` coverage paths — not done.
**The version, and so the new code.** The project's new-code period is SonarCloud's *Previous version*. Until now
every analysis was "not provided", so the new code was everything since the first analysis (2026-09-27): 34,268 lines
on 2026-10-20. The job now passes `/v:` the newest `v*` tag the commit descends from, so new code is everything
since the last release — **from the second analysis with a version on**, measured on `main` (below): the first,
`main`'s first from CI, still counted from before any version existed; the second set the start at the last analysis
without one (2026-10-20 05:11; 257 new lines on 2026-10-25). An issue the CI analysis raises on an older line is
dated by blame — the newest line of its path — and is new code only when that line is. The gate is *Sonar way*: its
coverage condition (80 % on new code) was skipped while no analysis had coverage, and applies from the first analysis
from CI.
**What it reads** — `SonarQube.Analysis.xml`: the exclusions of `.sonarcloud.properties` (below) and what a build
writes into the checkout, since the scanner walks all of it (`build/`, with the sources CMake fetches there, `out/`,
every `bin/` and `obj/`, `TestResults/`) — SonarCloud also drops what `.gitignore` names (the first run: "63 files
ignored because of scm ignore settings"), and the patterns say it in the file rather than rely on that; the same
duplication exclusions; C++20; UTF-8; the OpenCover paths; the compilation database;
**`sonar.cs.roslyn.ignoreIssues`** — Roslynator, Meziantou, the VS threading and the .NET
analyzers already gate the build, warnings as errors, and what they report at a lower severity is this project's
choice, so only SonarCloud's own rules are imported; and **two rules ignored where they apply by design** — `S8417`
(sequentially consistent atomics) in `src/native`, any repository because a header is indexed as C, and
`csharpsquid:S6640` (unsafe code) in Infrastructure and Shared. Those are the optional rows of the owner's steps below,
which the UI's *Ignore issues on multiple criteria* would have held; a pull request adding atomics no longer fails the
gate on them.
**What it does not cover.** A fork's pull request and Dependabot's get no secrets, so the job is skipped for them;
Dependabot's would run if the owner added `SONAR_TOKEN` to the repository's *Dependabot secrets*. A pull request's
analysis lists only the issues on the lines it changed, and no other branch can be analysed (above), so what the
analysis from CI finds in the older code shows on `main`'s first analysis from CI and nowhere before it.
**The first analyses (2026-10-25, PR #334).** Run 40147463349: the scanner began, the build ran, the C# coverage was
imported (635 files) — and CFamily stopped on the `.modmap` response files (step 3). Run 40148541525, with scanning
off: everything analysed — 1,300 files indexed, 249 left out by the exclusions and 63 by `.gitignore`; of the
compilation database's 181 units, 32 analysed in full (none partly; 118 whose sources are not analysed — the vendor
stubs and what CMake fetched, Catch2 and MinHook —, 18 duplicates, 13 it does not support) in 139 s; 21 C and 32 C++
files indexed (a `.h` is C to SonarCloud) — and the
gate failed on two conditions, both fixed the same day: `githubactions:S8264` (a C security rating: workflow-level
permissions reaching both jobs) and 0 % coverage on new code (`build.ps1`'s lines, before the coverage exclusions).
A dispatch of the branch (40148544753) analysed it and was refused the gate, which is how the plan's limit was found.
**`main`'s first analysis from CI (run 40160302893, the merge of #334).** The gate failed on one condition, a C
reliability rating on new code, and passed the others (84.7 % coverage on new code). The 34 open issues were all C++,
raised there for the first time — the real MSVC flags let CFamily see them — and each dated by blame, 2026-08-02 to
2026-10-19. Two were new code: `hook-harness`'s null dereferences, whose paths reach lines changed on 2026-10-19 — two
MAJOR bugs, so C; the BLOCKERs were older lines. (A pull request's analysis never showed any of them: it reports no new
issue on an old line.) The next analysis, the merge of #335 at 05:20, moved the new code's start to 2026-10-20 05:11
and turned the gate green with nothing fixed; the merge of #336 at 06:17 closed 33 of the 34. The 34th, `S3519` in
`fl_patch_check.h`, stayed open: its `NOSONAR` sat on `p -= 5`, and SonarCloud reports the read on the line after —
moved there by the release pull request. The C# had none open. Beta.29 PR-3 settled them — fixed where the code was
wrong, `// NOSONAR` with its reason above it where the analyser was (five):
| Rule | Where | n | What it was | Done |
|---|---|---|---|---|
| `cpp:S2275` format/argument | `fl-probe-nvapi` | 19 | `%u` for `NvU32`, an `unsigned long` (32 bits on Windows, so nothing printed was wrong) | `%lu`; the machine line `CaptureHost` parses prints the same |
| `cpp:S2259` null dereference | `hook-harness` `main.cpp` ×2, `proxy_swapchain.h` | 3 | **real:** `--vulkan` and `--opengl` create no D3D11 objects, and `--opengl` alone ran the default probes through a null swapchain, as did any D3D11 mode beside either flag | `HaveD3D11`, asked first by every mode that drives the D3D11 swapchain; the duplicate mode flags are one |
| `cpp:S2259` | `fl_ring.h` `Publish` | 1 | the path runs on past a failed `REQUIRE(w.Init(...))` in `ring_test`, which ends the test case; every real caller publishes through a writer whose `Init` succeeded, before any hook is installed | `NOSONAR` — a comment on the per-present path, no code |
| `cpp:S3519` negative offset | `fl_patch_check.h` | 1 | by design: the 5 bytes before a hot-patchable function are its patch area, which the check reads under `StillOurs`' SEH guard | `NOSONAR`, no code |
| `cpp:S6232` union pun | `dllmain.cpp`, the log's QPC epoch | 2 | `LARGE_INTEGER f{}` makes the union's first member, the `LowPart`/`HighPart` struct, the active one, so reading `QuadPart` reads a member that is not — undefined in C++, whatever `QueryPerformanceFrequency` wrote | initialised through the member read, `{.QuadPart = 0}` |
| `cpp:S6232` | `guard_test.cpp` | 2 | a `ULARGE_INTEGER` to take a second off a `FILETIME` | 64-bit arithmetic on the two halves |
| `cpp:S5813` `strlen` | `guard_test.cpp` | 1 | `strlen` of a fixed-size rules value | `strnlen(…, kMaxValueLen)` |
| `cppsecurity:S9340` index from input | `layer.cpp`, `fl-baseline-probe` | 2 | the terminator written at the count `ReadFile` / `fread` returned, which never exceeds the request | the bound tested first (in the layer, its once-per-process enable-list read — whose `LARGE_INTEGER size{}` drew this PR's own `S6232` twice, and is initialised through `QuadPart` too) |
| `cppsecurity:S5145` log injection | `rules_budget_test.cpp`, `fl-baseline-probe` ×2 | 3 | console output of a test and a probe: four numbers, and the ids of the seed rules file fixed at build time | `NOSONAR` |
**The C# gate is the server's profile, not the analyser's defaults.** SonarCloud applies *Sonar way core* here (166 C#
rules, 176 C++). A local build with the `SonarAnalyzer.CSharp` package and its own default rules reports about 240
findings in this code, nearly all from rules that profile does not activate (`S3358`, `S6667`, `S3267`, `S108`,
`S3236`, `S2094`, `S927` among them); chasing them changes code for nothing the gate reads. What counts is
`api/issues/search` for `main` or the pull request.
### Until 2026-10-25 — Automatic Analysis, no workflow (beta.24, owner decision D67)
*The text from here to the end of this section stood as written; what changed is marked.* ~~The project
`poli0981_frameledger` is analysed by SonarCloud's GitHub app in **Automatic Analysis** mode: on every~~ The project
`poli0981_frameledger` was analysed by SonarCloud's GitHub app in **Automatic Analysis** mode: on every
push to `main` and on every pull request, with no workflow in this repository and no logs published. Its check on a
pull request (*SonarCloud Code Analysis*) is advisory — it is not a required status.
@@ -240,7 +427,8 @@ git-ignored and never reach it.
**What it cannot do.** `sonar.issue.ignore.*` is not read by Automatic Analysis, so a rule this project breaks by
design is recorded here and marked in SonarCloud's own UI — by the owner, who holds the account. A CI-based scan (the
only way to import coverage or analyse one build variant of the C++) would mean turning Automatic Analysis off, a
`SONAR_TOKEN` secret, OpenCover output beside today's Cobertura and a full-depth checkout; it is not done.
`SONAR_TOKEN` secret, OpenCover output beside today's Cobertura and a full-depth checkout; ~~it is not done~~ *done
2026-10-25 (D68, above)*.
**The triage of 2026-10-19** — the analysis of `main` at `372389c` (2026-09-28; nothing had been analysed since),
341 open issues, none resolved. Rules broken by design are *Accept*ed and false positives marked as such, each with
@@ -276,34 +464,265 @@ the comment below; the rest are fixed in the same train (beta.24 PR-2).
checked is shorter than `MAX_PATH`, so it is terminated.
- `fl-baseline-probe/main.cpp:55` — a literal (a developer probe, not shipped).
**The six left open after the trains (2026-10-19, beta.26)** — the analysis of `main` at `e35b971` (0.1.0-beta.25),
after the owner's marking: 366 issues resolved (284 fixed — the exclusions and beta.24 PR-2 —, 49 accepted, 33 false
positives) and six open, all in the new-code period, which is why its quality gate read C for reliability and security.
Five were written after the analysis of `372389c` the table above was built from.
| Rule | Issues | Verdict | Comment for the UI |
|---|---|---|---|
| `csharpsquid:S3869` `DangerousGetHandle` | 1 | **Accept** — the row above | as above |
| `csharpsquid:S1244` floating-point equality | 4 | **False positive** | Exact on purpose. `ColorMath.Hsv` compares `max` with `r` and `g` — `Math.Max` returned one of them, the same double; `MarkdownView`'s `next == _wheelTarget` is true only when `next` was assigned `_wheelTarget` (the snap that ends the easing); `SensorsChart.Line`'s `scale == 1.0` compares a parameter with its own default literal to skip a copy. |
| `githubactions:S7631` untrusted code from a fork | 1 | **False positive**, and hardened in beta.26 | `wiki.yml` checks out `workflow_run.head_sha` only after a successful Release run started by a pushed `v*` tag, which a fork cannot start; since beta.26 it also requires `workflow_run.head_repository` to be this repository. |
**Marked by the owner the same day** (2026-10-19, 14:27–14:29 UTC), each as the table says: the four `S1244` and
`S7631` as false positives, `S3869` accepted. `main`'s next analysis (`6b07eb2`) has no open issue and its quality gate
passes.
**The owner's steps** after the next analysis of `main`: for each rule above, open
`https://sonarcloud.io/project/issues?id=poli0981_frameledger&resolved=false&rules=<rule>`, select all, *Bulk change*,
choose *Accept* or *False positive* and paste the comment. Optionally, *Administration ▸ General Settings ▸ Analysis
Scope ▸ Ignore issues on multiple criteria*: `cpp:S8417` and `cpp:S6232` on `src/native/**/*`, `csharpsquid:S6640`
on `src/FrameLedger.Infrastructure/**/*` and `src/FrameLedger.Shared/**/*`, so new instances of the by-design rules
stop reappearing on pull requests.
stop reappearing on pull requests. *(Since D68 the `S8417` and `S6640` rows are `SonarQube.Analysis.xml`'s, in the
repository; `S6232`'s are not — a union read outside `LARGE_INTEGER` would be a finding — and its 24 stay marked.)*
## Dependabot (`.github/dependabot.yml`)
## Qodana — `qodana.yml`, a workflow of its own (owner decision D93, 2026-11-10)
**D93 — Qodana reads the C# and the XAML from CI.** The owner made the project on Qodana Cloud, set the `QODANA_TOKEN`
secret (2026-11-10) and asked for Qodana in CI from the workflow JetBrains gives, changed where it had to be, with what
it reports fixed. Asked which licence the Qodana Cloud organisation holds, the owner answered: a 30-day trial. So the
linter is **Qodana Community for .NET** (`qodana-cdnet`) — ReSharper's InspectCode in a Linux container, which runs
under every licence — and not Qodana for .NET (`qodana-dotnet`, Rider), which needs Ultimate and would turn the job red
the day the trial ends. JetBrains calls the Community linter Early Access.
**How it runs.** `.github/workflows/qodana.yml`, on every pull request into `main` from this repository, every push to
`main`, and by hand: a full-depth checkout of the pull request's own commit, then `JetBrains/qodana-action` pinned to
the commit of `v2026.2.2` (the newest; the template names `v2026.1`, and every action that is not GitHub's own is pinned
by commit here). The action brings the Qodana CLI of its own version, the CLI the linter's image
(`jetbrains/qodana-cdnet:2026.2` — InspectCode 2026.2.3.1 on the image's .NET SDK 10.0.403), and the linter reads
`qodana.yaml`: the solution (`FrameLedger.slnx`), the configuration (Release), the gate. It builds the solution itself,
then inspects it — the whole solution every time (`pr-mode: false`), so a pull request and `main` are judged by one
list. The report goes to Qodana Cloud, a summary to the pull request as a comment and annotations, and the SARIF and
the linter's logs to the run as the `qodana-report` artifact.
**What had to change from the template, and why.**
- **`EnableWindowsTargeting=true`, passed to the container** (`env-vars-to-linter`). Every project here targets
`net10.0-windows`, and the .NET SDK on Linux refuses such a project unless that property is set. With it, the
container restores, builds and loads all thirteen projects — WPF's markup compiler and CsWin32's generator are managed
code — which the first run showed (below). It is the workflow's, not `Directory.Build.props`': no build of the product
is meant to run anywhere but Windows. JetBrains' own page says a project with an OS-specific target needs Qodana for
.NET in native mode; that is the Ultimate linter, and the Community one did the work.
- **`ubuntu-latest`, the one Linux job here** — the Community linter ships as a Linux image only.
- **Permissions:** `contents: read`, `checks: write` (the annotations), `pull-requests: write` (the comment). The
template's `contents: write` is for pushing quick-fixes, an Ultimate feature this job never uses.
- **`main` only.** The `alpha` branch is main's source under another release line (§The alpha line); main's is what
is analysed. *(Until beta.37 the reason was the alpha's prerelease .NET, which the image does not carry.)*
- **Interim since beta.37 (D94, 2026-11-11): the .NET 11 SDK is installed into the container first.** Main builds on
.NET 11 and the image carries the SDKs 8 to 10, so `qodana.yaml` has the `bootstrap` line JetBrains' page gives for
an SDK the image lacks — `dotnet-install.sh` with `global.json`, into `/usr/share/dotnet`. It lasts until the
Ultimate linter's pull request replaces this job with one on Windows, where `setup-dotnet` does it. Measured on its
first run (#376, run 42916491047): the script installed SDK 11.0.100 beside the image's own, InspectCode 2026.2.3.1
loaded and inspected all thirteen `net11.0-windows` projects, and it reported one problem — a redundant `!` in the
test that pull request added, fixed there. So the 63 keys and the zero held across the move.
- **Not a fork's pull request, nor Dependabot's:** neither gets the secret or a token that can write the comment.
- **Caches are saved from `main` only** (`cache-default-branch-only`); a pull request reads them.
**What it reads, and what it does not.** The C# of the thirteen projects, their XAML and `.resx`. **Not the C++:**
`src/native` is a CMake tree no solution names, and it is MSVC-only, which no Linux container compiles — CodeQL and
SonarCloud read it. The native DLLs are absent in the container, so the `.targets` that copy them warn and the build
goes on, as on a fresh clone (measured here the same day: `dotnet build` of a clean worktree, 15 warnings, 0 errors).
**The gate is zero, and it is advisory.** `qodana.yaml` sets `failureConditions.severityThresholds.any: 0`: one
problem and the job is red. `main`'s required contexts stay `check`, `analyze (csharp, none)` and
`analyze (cpp, manual)`, so a problem Qodana finds — or a Qodana Cloud outage — is a red job beside a green `check`,
never a blocked merge. That it can fail was shown before it was
relied on: run 42847369329 had the settings and none of the fixes, found 409 problems and ended red — "Detected 409
problems across all severities, fail threshold 0".
**Where an inspection is switched off: `.editorconfig`, never `qodana.yaml`.** InspectCode reads its severities from
`.editorconfig`'s `resharper_*_highlighting` keys, and so do Rider and ReSharper in the editor — one list for the job
and for the person at the keyboard, beside the analyzer severities already kept there, and testable without CI. Each
key has its reason on the line above it. The rule: **what Qodana reports is fixed, unless the inspection argues with a
choice this project made** — then it is off, and the reason says which choice. Sixty-three keys, in these groups:
| Group | Inspections | The choice it argues with |
|---|---|---|
| The compiler's missing-XML-comment warning | `CS1591` | already a suggestion in this file; InspectCode reports suggestions — 2,050 of the first run's 3,679 |
| Naming | `InconsistentNaming` | names follow this file's rule and the .NET analyzers'; ReSharper's scheme renames `OpenGL`, `XeSS`, `Presents5s` and every `Chart_*` resource key |
| Unwrapping a nullable | `ConvertTypeCheckPatternToNullCheck`, `PatternAlwaysMatches` | `x is long v` and `x is > 0 and int v` name the type, as `csharp_style_var_for_built_in_types = false` asks |
| What a guard is for | three `…AccordingToAPIContract` inspections | the compiler's nullable analysis is the gate; a dependency property, a JSON document and a WPF event hand over null whatever an annotation promises |
| Said on purpose | `RedundantExtendsListEntry`, `RedundantArgumentDefaultValue`, `RedundantEmptySwitchSection`, `MemberHidesStaticFromOuterClass`, `CompareOfFloatsByEqualityOperator` | a code-behind names its base; an argument repeats a default it relies on; `default: break;` says the rest is left alone; exact float comparisons are with a copied value or a sentinel |
| Not this code's to change | `UnusedParameterInPartialMethod`, `Xaml.StaticResourceNotResolved`, `Xaml.PossibleNullReferenceException`, `LocalizableElement` | CommunityToolkit's generated signatures; WPF UI's run-time resources (`PagesLoadTests` fails a wrong key); a binding through null shows nothing, by design; exception and log text is English (`09_I18N`), and `resx-audit` gates what a user reads |
| Records | `NotAccessedPositionalProperty.*` | a positional property is part of equality and of what the record prints |
| Style proposals | twenty, from `ConvertToPrimaryConstructor` to `UseAwaitUsing` | the style is this file, `dotnet format` and the analyzers; `await using` under CA2007 reads worse than what it replaces |
| Accessibility proposals | `MemberCanBePrivate.*`, `PropertyCanBeMadeInitOnly.*`, `AutoPropertyCanBeMadeGetOnly.*` | a member's accessibility is what its type offers, not a count of today's callers |
| "Never used" across the solution | eight `.Global` inspections | enum values mirror the native layout and stored columns, exception types carry CA1032's constructors, rows and messages are read by Dapper and System.Text.Json; the private kind (`.Local`) stays on — and what this group named on 2026-11-10 is listed below |
| In `tests/` only | eleven | an assertion lambda runs inside the `using` it captures from; a test that dereferences null fails, which is its job; a test double keeps the shape of what it stands for |
Five places carry a `// ReSharper disable once …` comment with its reason instead, where the inspection is right in
general and wrong once: the tolerance channel closed early in `CaptureSession`, the volatile read in
`SessionEventPublisher`, the awaited `Task.Run` in `CaptureOrchestrator`, the window read lazily in
`SessionSummaryOpener`, and a test row that is never on.
**The first run, and what was done (2026-11-10, PR #373).** Run 42842741359, the template's shape with no settings:
the container built the solution and inspected it in under six minutes, and reported **3,679 problems** — 858 warnings
and 2,821 suggestions, in 93 inspections. About 400 were fixed in the code, in 181 files, none changing what the
software does:
| What | n | Done |
|---|---|---|
| Redundant qualifiers, casts, `using` directives, `!` suppressions, `unsafe` modifiers, tuple names | 290 | removed, by script from the report's own positions; the build (warnings as errors, Release and Debug) and `dotnet format` held every one — one cast of a pair in `SqliteGameMerge` was needed after all, and stayed |
| `var` for a built-in type, a block body for a one-line method | 52 | this file's own style (`csharp_style_var_for_built_in_types`, `…expression_bodied_methods`), applied by `dotnet format` |
| XAML bindings the inspection could not resolve | 35 | every item template names its `DataType`; a binding that reached the page through `DataContext.ViewModel` with `AncestorType=Page` names the page's type and its `ViewModel` — the same object at run time, and now navigable in the editor (`ViewerModeTests` pins the new text) |
| Left over in the code | 12 | `LogsViewModel`'s unread `_strip` field and `PipeServer.Client`'s unread `_run`; two initialisers a constructor overwrote; `GameFileProbe.UnityDataFile`'s unused parameter; `SpokenTextAutomationPeer` no longer assumes `GetNameCore` returns a string; a redundant setter and two grid positions in XAML; a `$` on a string with no hole; `!Any(==)` as `All(!=)`; a `foreach` variable's type |
| In the tests | 14 | unused variables, lambda parameters and an accessor; a linear `Contains` on a set; three simplifications |
The rest was settled by the settings above — 2,050 of it the one inspection the project had already made a
suggestion. A suggestion to use `m[^1]` inside an expression tree was wrong (CS8790) and its inspection is off.
**The runs (PR #373).** 42842741359 — the template's shape, no settings: 3,679 problems, the job green (no gate yet).
42847369329 — the settings and the gate, none of the fixes: 409 problems, every one in an inspection left on, the job
red; so `.editorconfig`'s keys are read in the container as they are on Windows, and the 3,270 others were the
settings'. 42849331796 — the fixes: **0 problems**, the job green; and `main`'s first run, the merge of #373
(run 42852304026): 0 problems. A job takes about ten minutes.
**Named by the "never used" group and left as it is (2026-11-10).** Nothing in the solution, its tests included, uses
these; whether each is vocabulary, a piece not wired yet, or dead is the owner's to say, so none was removed:
`AtomicFileWrite` (the class and `PublishAsync`), `ExecutableMarkerScan` and `IExecutableMarkerScan.Scan`,
`FpsPresentation.GeneratedLine`, `IPageNavigator.GoBack`, `OperatorDisclosure.VersionOf` and `ProvenanceOf`,
`CrashReporterCatalog.AlwaysOn`, `ProcessWatcher.Tracked`, `LedgerWalCheckpoint.Complete`,
`LhmTelemetryOptions.EnableCpuAndMemory`, `MeasuredFacts.StreamlineNoneWithheldFrom`, `ILegalAcceptanceStore.ListAsync`
and `ITelemetryPoller.Dropped` (only their implementations are called), `DocumentBrowser.PageChanged` and
`UrlOpener`'s getter, the charts' `PercentilePlot`, `NoteText` and `TempsPlotView`, `GameDetailViewModel`'s
`TrendEmptyText`, `LatencyHeader` and `SensorsEmptyText`, `GamesViewModel.SortLabel`, `TriStateChipModel.IsNo`,
`AboutWindow`'s `AppTab` and `ThirdPartyTab`, `NvapiNgxWords.Degraded`, `IpcMessages`' `TelemetryUnavailable` and
`DbWriteFailed`, `IpcProtocol.Keepalive`, `ShmLayout.GuardTickDeadlineMs`, `HarnessOverlayLogSweep.Own`; and the
getters of 49 auto-properties, among them view-model texts no page binds and columns of stored rows. The list is
`UnusedMember.Global` and its siblings in run 42842741359's report.
**Running it on a developer's PC.** The same InspectCode is a .NET tool:
`dotnet tool install JetBrains.ReSharper.GlobalTools --version 2026.2.3.1 --tool-path <somewhere>`, then, after
`dotnet build FrameLedger.slnx -c Release`:
`jb inspectcode FrameLedger.slnx --no-build --format=Sarif --output=<file> --caches-home=<folder> --properties:Configuration=Release --toolset-path="C:\Program Files\dotnet\sdk\<11.0.x>\MSBuild.dll" --dotnetcore="C:\Program Files\dotnet\dotnet.exe"`.
Two things measured on the owner's PC: without `--toolset-path` it picked Visual Studio 18 Insiders' MSBuild, which
crashed at start ("No files to inspect were found"); and a `--caches-home` a failed run had written left one project
unloaded on the next (2,875 false compile errors, all in `Infrastructure.Tests`) — a fresh folder loaded all thirteen.
A clean run there reports what the container does, to within a handful of findings that differ between Windows and
Linux (3,679 in the container, the same inspections on Windows with counts a few apart).
**What it does not cover, and what would change it.** No C++ (above); no `alpha`; no pull request from a fork or from
Dependabot; no quick-fixes, coverage or licence audit (Ultimate). **If the organisation gets an Ultimate licence** —
JetBrains has a programme for open-source projects — Qodana for .NET runs natively on Windows: `linter: qodana-dotnet` in
`qodana.yaml`, `runs-on: windows-latest`, `args: --within-docker false`, .NET set up from `global.json` first, and
`EnableWindowsTargeting` dropped. Until then the trial's end changes nothing here: the token only names the project
the report is sent to.
## C# 15 and the analyses (owner decision D96, 2026-11-11)
The main line compiles C# 15 since beta.37 — `LangVersion latest` on the .NET 11 SDK — and the owner asked for its
constructs to be used. **None is used yet, and this section is why.** The rule the plan was approved with: a construct
is used on main only where (1) the build, its analyzers and `dotnet format` take it with no analyzer switched off,
(2) CodeQL extracts its file without an error, and (3) Qodana reports nothing that is only its engine not knowing the
syntax — the first two are required checks, and Qodana's gate is zero. Each construct was written once, in a file of its
own, and shown to each tool (`spike-notes` §29, the canary):
| Construct | Build and analyzers | ReSharper's engine — InspectCode 2026.2.3.1, which Qodana 2026.2 runs, and 2026.3.0 | Used on main |
|---|---|---|---|
| Collection expression arguments, `[with(…), …]` | taken | an error: "Feature 'collection expression arguments' is not available. Please use language version 'preview'." | no |
| Closed hierarchies, `closed` | taken | not parsed ("Cannot resolve symbol 'closed'") | no |
| Unions, `union` | CA1815, from the SDK's own rules, on every union | not parsed ("Cannot resolve symbol 'union'") | no |
| Labeled `break` / `continue` | taken; `dotnet format` moves the label one indent to the left | not parsed by 2026.2.3.1; "not available… language version 'preview'" in 2026.3.0 | no |
**CodeQL's reading of them is not established**: its documentation lists C# up to 14, and a pull request's C# analysis
is an overlay that prints no per-file result (§`codeql.yml`). A full analysis of a branch is a `workflow_dispatch` of
`codeql.yml` on it.
**What moves this:** a ReSharper engine that reads C# 15 as a released language, in the Qodana linter this repository
runs; then the canary again, and a dispatched CodeQL run. `spike-notes` §29 lists where each construct would go.
**What main does take from .NET 11:** its API — the `string` overloads that name the comparison of a `char` search, and
`Process.TryGetProcessById`. The two preview features (runtime-async, the updated memory-safety rules) stay out, as D76
kept them out of the alphas.
## Dependabot (`.github/dependabot.yml`) and the NuGet audit
```yaml
version: 2
updates:
- package-ecosystem: nuget
- package-ecosystem: nuget # also .config/dotnet-tools.json (the SonarScanner, since 2026-10-25)
directory: /
schedule: { interval: weekly }
cooldown: { default-days: 7 } # since 2026-10-25
groups: { minor-and-patch: { update-types: [minor, patch] } }
# ignore: WPF-UI*, FluentAssertions majors — the file says why
- package-ecosystem: github-actions
directory: /
schedule: { interval: weekly }
cooldown: { default-days: 7 } # since 2026-10-25
groups: { actions-minor-and-patch: { update-types: [minor, patch] } }
```
Central package management makes Dependabot PRs single-file diffs.
- **Cooldown (2026-10-25):** a version update waits seven days after its release is published, so a release that is
pulled or found compromised in its first week never becomes a pull request here. Security updates do not wait — the
option does not apply to them. The actions' minor and patch releases come as one pull request; a new major comes
alone, because it is the one that changes inputs.
- **No `dotnet-sdk` entry, on purpose:** `global.json` is a floor (11.0.100 since beta.37, D94; 10.0.100 before) with
`rollForward: latestFeature`, so a developer's machine and the runner already build with the newest SDK of that band
they have (the runner installed 10.0.402 on 2026-10-20, 10.0.404 on 2026-11-10). Raising the floor is a decision
about what a contributor must install, not an update — the owner's, as D94 was.
- **Dependabot has never proposed a NuGet library update here — measured 2026-10-25.** Every NuGet pull request it
opened, #66 (2026-08-09) through #314 (2026-10-18), updated analyzers only (Meziantou, Roslynator, the VS threading
analyzers), while Dapper 2.1.89 (published 2026-09-23), coverlet 10.1.0 (09-27), xunit.v3.mtp-off 4.0.2 (10-09) and
the 10.0.13 servicing packages (10-13) were never proposed. Its update runs are GitHub Actions runs of their own (`gh
run list`, event `dynamic`), and the run of 2026-10-18 (39134906593) logs the test projects' resolution failing —
`Requested dependency resolution to include coverlet.collector/10.1.0 but it was instead resolved to 10.0.1`, `The
package FluentAssertions.7.2.2 is not compatible. Incompatible project frameworks: net10.0-windows10.0.22621` — and
opens nothing for them. The run of 2026-10-25 (40160307095), the first with the cooldown, says it of the shipped
libraries too, the versions in use among them — `The package Dapper.2.1.86 is not compatible. Incompatible project
frameworks: net10.0-windows10.0.22621`, and the same of Hosting, Sqlite, EventLog, Markdig and Velopack. Why its
resolver reads a package that targets `netstandard2.0` as incompatible with this framework is **unmeasured**. So a
quiet Dependabot is not evidence that the packages are current: `dotnet list FrameLedger.slnx package --outdated` is,
and the updates it had missed were made by hand in beta.29 PR-2 (#335) — `coverlet.collector` 10.1.0 excepted,
whose reason `Directory.Packages.props` gives beside it.
- **beta.30 (2026-10-26), by hand under the same cooldown** (the owner: "check the dependencies and conflicts, update if
needed"): Velopack and `vpk` 1.2.0 → 1.2.161 (the owner's decision, D71 — never 1.2.158, NuGet-deprecated), Markdig
1.4.0 → 1.4.2 (parser fixes; its licence text unchanged at the packaged commit), and **the `SQLitePCLRaw` pin
dropped**: `Microsoft.Data.Sqlite` 10.0.13 declares the patched 2.1.13, and the 3.0.5 pin had put it on SQLitePCLRaw's
3.x line — a cross-major resolution NuGet does not report, because the declared range has no upper bound. The engine
is now 2.1.13's, SQLite 3.53.3 (it was 3.53.4 under the pin; 2.1.14 carries 3.54.0 and comes with Microsoft's next
servicing). Not taken: the 10.0.14 servicing packages (published 2026-10-25, the out-of-band Brotli fix — which is
the RUNTIME's, shipped by the SDK the release builds with, not in a package referenced here), Markdig 1.5.0
(2026-10-24), CsWin32 0.3.366 (it changes how SafeHandles are generated; 0.3.367, its fix, is from 2026-10-22), and,
as before, `coverlet.collector` 10.1.0 and FluentAssertions 8. Catch2 3.16, NVAPI R615 (its licence file changed),
the Vulkan and Streamline headers and clang-format (paired with Visual Studio's) were read and not needed.
- **beta.31 (2026-10-26), the owner's request — inside the cooldown, on purpose** ("làm thêm bản beta 31 với các deps
còn lại (.net 10.0.14) và 1 số thư viện khác"; owner decision D72): `Microsoft.Extensions.Hosting`,
`Microsoft.Data.Sqlite` and `System.Diagnostics.EventLog` 10.0.14 (published the day before; `Microsoft.Data.Sqlite`
10.0.14 still declares `SQLitePCLRaw` 2.1.13), Markdig 1.5.0 (its licence text again byte-identical at the packaged
commit), CsWin32 0.3.367 (0.3.366 changed how SafeHandles are generated, 0.3.367 fixed its overflow; nothing here
needed a change), Meziantou.Analyzer 3.0.317 (no new finding), Catch2 3.16.1 for the native tests (clean under
`/W4 /WX`, the `/EHsc` fix kept), and `coverlet.collector` 10.1.0 — `NoSecondMatcherTests` now leaves out the
`Coverlet.*` types the collector injects, whose constant reflection cannot read; they were never ours. Still not
taken: FluentAssertions 8 (its licence), and the vendored native SDKs (NVAPI R615's licence file changed; the Vulkan
and Streamline headers follow the measured loader and titles).
- **The NuGet audit** (`Directory.Build.props`, written down 2026-10-25): `NuGetAudit` on, `NuGetAuditMode` `all`
(transitive packages too), `NuGetAuditLevel` `low` — the SDK's defaults for net10.0 when they were written down,
stated so that a later SDK's defaults cannot move them (and net11.0's did not). With `TreatWarningsAsErrors` a vulnerable package is NU1901–NU1904 and the restore, so
the gate, is red — what `SQLitePCLRaw` 2.1.11 did (`Directory.Packages.props`). `dotnet list FrameLedger.slnx
package --vulnerable --include-transitive` read none on 2026-10-25.
- **The repository's own alerts:** Dependabot alerts and security updates are enabled, and so are secret scanning and
its push protection (read from the API, 2026-10-25); no alert of either kind, and no code-scanning alert, was open.
## Branch & release policy
- `main` protected: CI + CodeQL required, linear history, no direct pushes.
- Release: in ONE commit, bump `VERSION` and move the `[Unreleased]` entries of `CHANGELOG.md` under `## [X.Y.Z] - date` (Keep a Changelog format) *(since beta.24, D66: into their own file, `docs/changelog/X.Y.Z.md`, which opens with that heading, plus its row in `CHANGELOG.md`'s Releases table — `release-notes.ps1` reads the version's own file)* → tag `vX.Y.Z` → `release.yml` does the rest (and refuses a tag that disagrees with either file) *(corrected 2026-10-04: for a pre-release tag `vX.Y.Z-beta.N`, do not bump `VERSION` — it already holds the numeric core the gate compares, and it read `0.1.0` through eleven betas; the section is `## [X.Y.Z-beta.N] - date`, the full version. Bump `VERSION` only when the numeric core moves)* → smoke-test the produced installer on a clean Win 10 VM + Win 11 (manual checklist in 14_TESTING §Release smoke).
- Pre-releases: `vX.Y.Z-beta.N` tags mark the GitHub release as pre-release; the App's `stable` channel ignores them and its `beta` channel (Settings ▸ Updates, `update.channel`) includes them — built with P4 PR-5, so ~~explicit beta channel is v2 backlog~~ is struck. The managed assemblies carry the full tag version; the native VERSIONINFO blocks carry the numeric core (`12_BUILD` §Version).
- **Alphas (D73, 2026-10-31):** `vX.Y.Z-alpha.N`, tagged on the `alpha` branch only — `release.yml` refuses one anywhere
else, and any other tag there — published as GitHub pre-releases on Velopack's `alpha` channel. §The alpha line above.
## Repo hygiene checklist
@@ -314,9 +733,11 @@ Central package management makes Dependabot PRs single-file diffs.
**In the tree — done:**
- [x] Repo-local `ci.yml`, `codeql.yml`, `release.yml`, `rules-publish.yml` (all four repo-local by decision, §Workflows); ~~caller stubs pointing at `poli0981/.github`~~ — never the design, see the first paragraph *(and `wiki.yml` since beta.17, repo-local too: five)*
- [x] Issue forms `bug_report.yml`, `feature_request.yml`, `safety_gap.yml`; `ISSUE_TEMPLATE/config.yml` pointing a vulnerability at private reporting; PR template referencing CLAUDE.md's definition of done
- [x] `.github/dependabot.yml` (nuget + github-actions, weekly)
- [x] Repo-local `ci.yml`, `codeql.yml`, `release.yml`, `rules-publish.yml` (all four repo-local by decision, §Workflows); ~~caller stubs pointing at `poli0981/.github`~~ — never the design, see the first paragraph *(and `wiki.yml` since beta.17, repo-local too: five; and `qodana.yml` since 2026-11-10, D93: six)*
- [x] Issue forms `bug_report.yml`, `feature_request.yml`, `safety_gap.yml`; `ISSUE_TEMPLATE/config.yml` pointing a vulnerability at private reporting; PR template referencing CLAUDE.md's definition of done *(and since 2026-11-09, beta.35, D88: `accessibility.yml`, the form `ACCESSIBILITY.md` sends a barrier to, and the PR template's user-interface section)*
- [x] The labels the forms apply exist *(2026-11-09: `accessibility`, and `safety` and `priority-high`, which `safety_gap.yml` had named since it was written (2026-08-02) while the repository had neither — GitHub applies only a label that exists, so no Safety gap report was ever labelled)*
- [x] `ACCESSIBILITY.md` — the accessibility statement: WCAG 2.2 AA through WCAG2ICT as a goal, never a claim; how a barrier is reported and handled (2026-11-09, D88)
- [x] `.github/dependabot.yml` (nuget + github-actions, weekly; a seven-day cooldown and the actions grouped since 2026-10-25 — and a NuGet library update it never proposed is `dotnet list package --outdated`'s to find, §Dependabot and the NuGet audit)
- [x] `SECURITY.md` — the private route for a vulnerability, the public route for a safety gap, and the honest response intent (2026-09-16)
- [x] A release rehearsal: `release.yml` `workflow_dispatch` runs every step but the Release itself (§release.yml)
@@ -324,7 +745,7 @@ Central package management makes Dependabot PRs single-file diffs.
- [x] Branch protection as §Branch & release policy states *(marked 2026-10-04, read from the API: required checks `check`, `analyze (csharp, none)` and `analyze (cpp, manual)`; linear history; a pull request required; force pushes off; enforced for admins)*
- [ ] `Rules / validate` as a required check (§S23-2, after its skip-shim)
- [ ] Dependabot alerts + security updates (the manifest is in the tree; the alerts are a setting)
- [x] Dependabot alerts + security updates (the manifest is in the tree; the alerts are a setting) *(marked 2026-10-25, read from the API: both enabled, with secret scanning and its push protection)*
- [x] Private vulnerability reporting enabled (Settings ▸ Security), so `config.yml`'s link resolves *(marked 2026-10-04: GitHub reports it enabled)*
- [ ] Wiki editing restricted to collaborators (Settings ▸ General ▸ Features ▸ Wikis ▸ *Restrict editing to collaborators only*): otherwise anyone with a GitHub account can change a page until the next release overwrites it (§wiki.yml, beta.17)
- [ ] Repo topics: `windows`, `wpf`, `benchmark`, `fps`, `game-performance` (~~`presentmon`~~ — dropped 2026-08-27, §G)
+21 -1
View File
@@ -125,6 +125,21 @@ own work item on the STA thread and puts back — and with the keys a parameter,
`AnotherHookHarnessRunningBesideTheSuiteDoesNotMakeTheTargetAmbiguous` runs a second harness beside the capture (red
against the shared name: `TargetAmbiguous`). A suite that attaches by pid (`ShmDrainIntegrationTests`, the native
`fl_guard_test`) is not exposed and keeps the staged name.
- **Test readiness: an injection test waits for the harness to say it presents** (beta.27). The suites that start
hook-harness and then inject into it or look for it — `ShmDrainIntegrationTests`, `CaptureHostEndToEndTests`,
`AgentEndToEndTests`, `PartialRecoveryEndToEndTests` — slept 800 ms after starting it, a guess at when it presents.
They now wait, bounded at 30 s, for the line the harness prints and flushes right before its present loop
(`tests/Shared/HarnessReady.cs`, compiled in by `FrameLedger.DrainFixtures.targets`), and the pause case — which read
the writer's status as INIT once under a full gate on 2026-10-19 — waits for the writer's READY
(`WaitUntilInitFinishedAsync`) before it pauses.
- **The guard reads the test host too** (beta.27). The guard's scan set is the target and its ancestors up to a platform
launcher, so for an injection test it includes the test host that started the harness, `dotnet test` and the shell
above them. Under a full gate the test host is still starting its other test classes, and a module it releases
between the guard's list and the module's name refuses as `ModuleScanFailed` — measured 2026-10-20, once in the gate
and once in twelve runs of `FrameLedger.Infrastructure.Tests` with coverage, never in a run of the class alone;
`ProcessUnreadable` (2026-10-19, twice) is the same race met at the list. `ShmDrainIntegrationTests.InjectAsync` asks
again, four times at most, on those two reasons only. The end-to-end suites inject through the Agent or the capture
host, which records such a session as Tier 2; they have the same exposure and have not shown it.
- Guard integration: harness loads a **dummy DLL named like an anti-cheat module** → injection refused pre-launch; loaded late → safety unhook. (A renamed harmless DLL, not real anti-cheat software.)
## Hook overhead measurement (NFR-1, per release)
@@ -186,7 +201,7 @@ that it was checked against anything.
| Axis | Values |
|---|---|
| OS | Win 10 22H2 VM · Win 11 dev machine |
| OS | Win 11 dev machine · a Win 10 22H2 VM where one exists — since beta.37 (D95) Windows 10 is not blocked and is neither tested nor supported, so a run there is information, not a gate |
| GPU vendor | NVIDIA (primary) · AMD or Intel if available, else document as untested |
| API | D3D11 · D3D12 · Vulkan (layer path) · OpenGL · **a 32-bit title, asserting it is correctly refused and recorded as Tier 2 with the reason** |
| Upscaler | DLSS SR · DLSS-G · DLSS-RR · FSR2/3 · XeSS · none |
@@ -194,9 +209,14 @@ that it was checked against anything.
| Mode | launch mode · attach mode · mid-session settings change |
| Safety | game with anti-cheat → toggle disabled · simulated late AC load → unhook · double-crash → auto-disable |
| Tier | forced Tier 2 (records duration, available sensors and the reason — and nothing else) · Tier 1 → Tier 2 degradation notice |
| Accessibility *(added 2026-11-09, beta.35, D88)* | **keyboard only** with the mouse disconnected — every page, menu and dialog, Ctrl+1…5, Esc · **Narrator** — names, values, headings, the notices as they appear · a **contrast theme** on and off (Aquatic, Desert) · Windows **animation effects** off · a large **display scale**. The owner's first pass: 2026-11-09, keyboard only and Narrator on 0.1.0-beta.34 and 0.1.0-alpha.3, no fault (`ACCESSIBILITY.md` §How it is checked; the automated half is `08_UI` §Accessibility) |
| Update | Velopack delta; update deferred while a game is hooked (FR-12) — *a delta needs a previous release, so this row is reachable from the second release, not the first* *(corrected 2026-10-04: no release has carried a delta — `release.yml` never fetches the previous release before `vpk pack`, `11_UPDATER` §Built — so the update leg is a full package; **since beta.13** a release carries a delta against the previous one, and the first
update that can use it is beta.12 → beta.13 — HANDOFF owner-only item 10)* |
## Release smoke
Clean-VM install → Legal Gate → Agent setup (unelevated) → add a game → consent dialog → hooked 2-min session → charts render → CSV opens in Excel → Vulkan layer registered/unregistered cleanly → uninstall removes layer registration, task, and asks about data.
*(Added 2026-11-09, beta.35, D88:)* and an **accessibility smoke**, the same build: the Legal Gate, the consent dialog and
the session summary reached and answered with the keyboard alone; Narrator reads the notice a refused game raises; the
window readable under one contrast theme. The release's owner-only item in `HANDOFF` lists what that release moved.
+1 -1
View File
@@ -344,7 +344,7 @@ CI/CD with the native build (`release.yml` exists since P4 PR-5, 2026-09-14 —
- ~~PresentMon Service + API2 for a richer Tier 2~~ — **struck 2026-08-27**, and the shape hardened 2026-08-28: v1's ladder has two rungs and Tier 2 is not a measurement. What v2 may want is **a no-injection measurement at all** — which would restore two things at once: the FG oracle §S31 spent four attempts looking for, and `14_TESTING`'s Tier-1 accuracy cross-check, which is struck for the same reason (§G)
- **YouTube overlay export**: frametime/FPS graph as transparent PNG sequence for DaVinci Resolve benchmark videos (SkullMute workflow)
- CapFrameX-compatible CSV import/export
- Microsoft Store / Game Pass titles (packaged-app injection constraints)
- ~~Microsoft Store / Game Pass titles (packaged-app injection constraints)~~ *(struck 2026-11-03: GDK titles from the Xbox app and the Microsoft Store are imported, played and measured since beta.33, D77–D82, `spike-notes` §25; UWP apps stay out, refused with a reason of their own)*
- AFK segmentation via `GetLastInputInfo`
- GPU frame time via timestamp queries (needs care: injecting queries into the game's command lists is more invasive than anything in v1 — needs its own risk review)
- ~~Beta update channel;~~ ARM64 *(struck 2026-10-04: the beta channel shipped with P4 PR-5 — `update.channel`, Settings ▸ Updates; `13_CI_CD` §Branch & release policy)*
+93 -2
View File
@@ -6,7 +6,7 @@ Mandatory conventions for all XAML/C# in `FrameLedger.App`. WPF UI = lepoco's Fl
| Package (NuGet id) | Pin | Notes |
|---|---|---|
| `WPF-UI` | **= 4.3.0** (exact; bump deliberately) | Assembly/namespace is `Wpf.Ui`. Targets `net8.0-windows` → resolves cleanly for our `net10.0-windows10.0.22621.0` TFM (`12_BUILD` §Managed build; this row said `19041` until 2026-09-21, which is no TFM this repository ever built — `Directory.Build.props` has been `22621` with a 19045 floor throughout) |
| `WPF-UI` | **= 4.3.0** (exact; bump deliberately) | Assembly/namespace is `Wpf.Ui`. Targets `net8.0-windows` → resolves cleanly for our `net11.0-windows10.0.22621.0` TFM — `net10.0-…` until beta.36 — (`12_BUILD` §Managed build; this row said `19041` until 2026-09-21, which is no TFM this repository ever built — `Directory.Build.props` has been `22621` with a 19045 floor throughout) |
| `WPF-UI.Abstractions` | ~~transitive~~ **= 4.3.0**, referenced directly (corrected 2026-10-04) | Navigation abstractions (`INavigationViewPageProvider`) |
| `WPF-UI.DependencyInjection` | match `WPF-UI` | DI glue (`services.AddNavigationViewPageProvider()`); verify exact id/version at scaffold |
| `WPF-UI.Tray` | **not used** | Tray stays on H.NotifyIcon.Wpf (CLAUDE.md stack table) |
@@ -62,6 +62,7 @@ private static readonly IHost _host = Host.CreateDefaultBuilder()
Theme rules:
- Manual Light/Dark: `ApplicationThemeManager.Apply(ApplicationTheme.Dark)`.
- System: `SystemThemeWatcher.Watch(mainWindow)` — call it in the window's `Loaded` handler (needs an HWND), and unwatch when switching to manual.
- A Windows contrast theme (beta.35, D91): wins over all three while it is on, and is never left to the watcher, which would apply WPF UI's own high-contrast files (§Gotchas). `Services/ThemePlan.For` is the table, `Services/WpfThemeApplier` applies it.
- Persist the choice in `settings`; re-apply before the main window shows to avoid a flash. **Measured 2026-09-13: this is a correctness rule, not a cosmetic one** — `ApplicationThemeManager.Apply(theme, backdrop, updateAccent: true)` is what registers the `SystemAccentColor*` resources the control templates `StaticResource` at first Measure; a `FluentWindow` shown before any `Apply` throws `XamlParseException: Cannot find resource named 'SystemAccentColorPrimary'`. The shell applies the theme in its constructor before `InitializeComponent()` and again from `Loaded` for the watcher.
- Subscribe `ApplicationThemeManager.Changed` once, centrally, to re-theme ScottPlot (below).
@@ -115,6 +116,14 @@ Code-behind wires services once: `navigationService.SetNavigationControl(RootNav
- Navigate **only** via `INavigationService.Navigate(typeof(SomePage))` — never manipulate `Frame` directly, never `new` a Page.
- Pages implement `INavigableView<TViewModel>` with `ViewModel` injected via constructor DI; `DataContext = this` in the page constructor (WPF UI template idiom) so bindings read `ViewModel.*`.
- Page state: pages are Transient; anything that must survive navigation lives in the ViewModel-backing services/DB, not the Page.
**Except the library, since beta.34** (owner request 2026-11-06, "Games stalls 0.5–1.5 s"; `spike-notes` §27): the window
keeps the `GamesPage` it built — `Services.WindowPageCache`, the window's own `INavigationViewPageProvider`, set after
`INavigationService.SetNavigationControl` (which hands the NavigationView the container's provider) — and its view model
reads the library again each time the page is shown (`GamesViewModel.Attach`). Still Transient in the container; one
instance per window, so a language change's new window builds its own in the new language. **Not**
`NavigationViewItem.NavigationCacheMode`: WPF UI 4.3.0 reads it only when the NavigationView has neither a service
provider nor a page provider (`NavigationView.Navigation.cs`, `GetNavigationItemInstance`), and this App sets one — the
attribute would have changed nothing.
## Control mapping (always prefer these)
@@ -160,6 +169,26 @@ Native `Menu`, `TabControl`, `ComboBox`, `Slider`~~, `ListView`~~ are fine — t
tertiary 3:1). It follows a theme switch through a **resource reference on the band** (`SetResourceReference` on a
private attached property bound to `ApplicationBackgroundColor`), not through `ApplicationThemeManager.Changed`, which
only `ApplicationThemeManager.Apply` raises — a page made and switched in the tests' harness would never hear it.
- The change markers (beta.30, D70) take the palette's `Chart_StutterPso` under `ChartTheme.TextOn` — black or white by
WCAG contrast, black in both themes. The chart reads `ChartTheme.Current` at every render; the WPF chip in the list
(`Controls/ChangeBadge`) follows a switch through the same resource reference as `ArtTint` and `FgMixBar`
(`ChartPalette.ForBackground`). No colour in XAML.
- Third exception (beta.35, D91): **a Windows contrast theme's colours**, read from `SystemColors` in one place
(`Services/ContrastPalette.FromSystem`) and laid over the theme by `Services/ContrastOverlay` — never written in XAML. A
colour the App works out itself reads `Services.ContrastTheme.Active` first (the charts, the badges, the artwork band);
XAML that must change with it binds `{Binding Path=(services:ContrastTheme.IsOn)}`, a static property WPF hears through
its `StaticPropertyChanged` event.
- **`ui:Button Appearance="Danger"` / `Info` / `Success` / `Caution` / `Dark` / `Light` paint fixed colours** — values in
WPF UI 4.3.0's button style (`#F44336` for Danger), not resources, so no theme and no contrast theme reaches them, under
the theme's button text (white on the red in the dark theme, 3.68:1). Danger is the one the App uses: its implicit
`ui:Button` style (`Styles/FrameLedger.xaml`) puts the theme's dark text on the red, and the theme's own button under a
contrast theme — message boxes' buttons included. The other five are refused
(`ContrastThemeTests.NoButtonOrBadgeTakesAnAppearanceThatPaintsAFixedColour`).
- **A snackbar's appearances are fixed colours too** (`ISnackbarService.Show`): Success, Caution, Info, Danger, Primary,
Dark and Light are values under white or black text — Success 2.78:1, Caution 2.16:1 in both themes. Only Secondary is
the theme's: `Services/SnackbarStrip`, the one place a snackbar is shown, uses it for every message.
- **A `ui:Badge` with a BOUND palette appearance** is the same hole as a literal one, and no XAML scan of literals sees it
(the agent's pill, beta.35: `AgentPill` now). A bound badge appearance is refused by the same test.
## FlowDocument (rendered documents, beta.12)
@@ -182,6 +211,9 @@ Native `Menu`, `TabControl`, `ComboBox`, `Slider`~~, `ListView`~~ are fine — t
- `TriStateChip`: `Border` CornerRadius 12, states — Yes: `AccentFillColorDefaultBrush` bg + on-accent text; No: transparent bg + `ControlStrokeColorDefaultBrush` 1px border; N/A: dashed `StrokeDashArray="2 2"` border + `TextFillColorTertiaryBrush` text.
- **Built 2026-09-14 (P3 PR-5):** both derive from `Control` with one dependency property, `Model` (`FpsReadoutModel` / `TriStateChipModel`, decided by `Services.FpsPresentation` and the view models — the control renders, it never decides), templates in `Styles/FrameLedger.xaml` with `DataTrigger`s on the model's flags; the dashed N/A outline is a `Rectangle` behind the `Border` (a `Border` cannot dash). The source suffix icon became the tooltip: the Fluent System Icons names for 🔍/✎/↧ are not certain in this pinned version and a wrong `SymbolRegular` is a build error. The override flyout is PR-6's.
- No `SystemColors.*` anywhere.
- `ChangeBadge` (beta.30): a `Control` with one `Text` property, not focusable (the row's text carries the meaning), its
template a `Border` and a `TextBlock` bound to `Background`/`Foreground`, which the control sets in code from the chart
palette (`Styles/FrameLedger.xaml` writes no colour).
## Dialogs & notifications
@@ -200,7 +232,12 @@ var result = await box.ShowDialogAsync(); // Wpf.Ui.Controls.MessageBoxResult.Pr
⚠ Name clash with `System.Windows.MessageBox` — in App code, `using MessageBox = Wpf.Ui.Controls.MessageBox;` ~~and ban the System one (BannedSymbols/analyzer note)~~ *(corrected 2026-10-04: nothing bans it. Three paths use the Win32 box on purpose — the crash dialog, the startup-failure dialog and the uninstall question — because they run when the shell's dialog host cannot be trusted. Use the WPF UI one everywhere else.)*
- Rich in-flow dialogs: `IContentDialogService` (host wired in MainWindow — a `ui:ContentDialogHost`, since 4.3.0 marks `SetDialogHost(ContentPresenter)` obsolete).
- Transient in-app: `ISnackbarService.Show(title, message, ControlAppearance.Success, new SymbolIcon(SymbolRegular.Checkmark24), TimeSpan.FromSeconds(4))`.
- Transient in-app: ~~`ISnackbarService.Show(title, message, ControlAppearance.Success, new SymbolIcon(SymbolRegular.Checkmark24), TimeSpan.FromSeconds(4))`~~
`IMessageStrip` (`Info` / `Success` / `Warn`) — `Services/SnackbarStrip` is the one caller of `ISnackbarService.Show`, and
says each message to a screen reader (beta.35, D89). A view model never holds `ISnackbarService`.
- A change a screen reader must hear goes through `IAnnouncer` (`Services/UiaAnnouncer`, UI Automation's notification
event). **`AutomationProperties.LiveSetting` alone says nothing in WPF**: the app must raise `LiveRegionChanged` itself,
and no XAML of the App's sets one (beta.35).
- System/tray notifications: H.NotifyIcon only (08_UI §Notifications policy).
## ScottPlot theme sync
@@ -216,10 +253,43 @@ On startup and on `ApplicationThemeManager.Changed`: for every live plot set fig
> Pinned `ScottPlot.WPF` 5.1.59: `Add.SignalXY` for the decimated series, `Add.Scatter` (no line) for markers,
> `Add.HorizontalSpan` for the ribbon, `Add.Bars` over `Statistics.Histogram.WithBinCount`, `Add.ScatterLine`
> for the percentile curve, a series' `Axes.YAxis = plot.Axes.Right` for the sensor overlay.
>
> **Accessible charts, beta.35 (D90).** Every plot in XAML is `charts:ChartPlot` (a `WpfPlot` subclass; ScottPlot's
> default style and input stay) with `AutomationProperties.Name` and `HelpText` from `A11y_Chart_*` / `A11y_ChartData_*`.
> `ChartTheme.Attach` adds `Charts/ChartKeys` (arrows and A marked handled after ScottPlot's class handler has acted — an
> instance handler runs after it) and `ResetOnDoubleClick` (`DoubleLeftClickBenchmark(false)` and a `DoubleClickResponse` on
> the left button that autoscales). A series takes `ChartPatterns.Line` / `Points` / `Hatch` by its index — a new series
> without one is red in `NoChartTellsTwoSeriesApartByColourAlone`. Under a Windows contrast theme `ChartTheme.Current` is
> `ChartPalette.ForContrast(ContrastTheme.Active)` — the theme's window under every plot, its text, link, highlight,
> button text and disabled text for the rest — and the patterns carry the series apart (D91).
>
> **The trend's change markers, beta.30 (D70):** `Charts/ChangeMarkerPlottable`, an `IPlottable` + `IRenderLast` added
> with `Add.Plottable` (which assigns no axes: the chart sets `Axes.XAxis`/`YAxis` itself), draws the dashed lines in
> `Render` — clipped to the data area — and the numbered badges in `RenderLast`, after the panels and unclipped, in a
> band kept with `plot.Axes.Top.MinimumSize` (the top axis is unused and measures 15 px; `MinimumSize` clamps it up, and
> `Clear` keeps it, so `Show` sets it every time — 0 with no marker). `LabelStyle.Measure` sizes a badge with a
> `Paint.NewDisposablePaint()`; `Charts/ChangeBadgeLayout` places them. `GetAxisLimits` returns
> `AxisLimits.HorizontalOnly`, so the markers count toward the date axis's autoscale as `VerticalLine`s did.
## Gotchas checklist
- [ ] Dictionaries order: `ThemesDictionary` → `ControlsDictionary` → app styles. Wrong order = default-looking controls.
- [ ] **A ScottPlot `VerticalLine` label grows into a panel nothing sizes for it (5.1.59).** With `LabelOppositeAxis` it is
anchored 5 px above the data area, its box (text + 5 px padding each side) growing up into the top-axis panel, which
an unused axis measures at 15 px; clipping is off, so the control's edge cut it — the owner's "Driver GPU: … → …",
beta.30. `LabelAlignment` is overwritten each frame (only `ManualLabelAlignment` holds), and
`LabelStyle.LastRenderPixelRect` includes the 3 px default `ShadowOffset` even with no shadow. The trend draws its
own badges now (§ScottPlot theme sync).
- [ ] **`WpfPlot.DisplayScale` is read once, in the constructor**, from `VisualTreeHelper.GetDpi` before the control has
a window. Read a pointer with `GetPlotPixelPosition(e)` (the element's DPI now); ScottPlot's pixels are device
pixels while no `Plot.ScaleFactor` is set, and none is.
- [ ] **WPF UI 4.3.0's high-contrast theme cannot be applied as it is** (beta.35, D91). `ApplicationTheme.HighContrast` has
no dictionary (the watcher picks HC1/HC2/HCBlack/HCWhite by Windows' theme name); each of those holds 84 `#FFFF0000`
placeholders among 97 colours and 17 brushes (`SystemFillColor*Brush`, `MenuBar*`) that throw when the file is read
alone — inside the App their forward references fall back to the application's resources and read as the Fluent
theme's fills; their colours are Windows 11's defaults, not the user's; their text on the accent is the window text.
Never let `SystemThemeWatcher` watch while a contrast theme is on: it would apply them. The App reads them for each
key's role only (§Theming & brushes; `08_UI` §Contrast).
- [ ] `SystemThemeWatcher.Watch` after HWND exists (`Loaded`), not in the constructor — but `ApplicationThemeManager.Apply(…, updateAccent: true)` BEFORE the first window's XAML loads, or the accent resources are missing at first Measure (§App bootstrap).
- [ ] Menu row lives **outside** `ui:TitleBar` (its area is the drag region; a Menu inside becomes undraggable/unclickable territory).
- [ ] Don't set `AllowsTransparency`/`WindowStyle` on `FluentWindow` — it manages its own chrome.
@@ -234,6 +304,21 @@ On startup and on `ApplicationThemeManager.Changed`: for every live plot set fig
bar with no exit, which is exactly how the safety notices shipped (2026-09-14). `Styles/FrameLedger.xaml` carries
the upstream template plus one presenter column; `PagesLoadTests.TheInfoBarTemplateRendersItsContent` renders both
templates and turns red when upstream gains a presenter, which is when the copy comes out.
- [ ] **What a screen reader is given is the UI Automation tree, and WPF builds it with four holes** (beta.35, D88;
`PagesLoadTests.Automation` sweeps every surface for each). (1) **A control with no automation peer** — a plain `Control`
or `ContentControl`, WPF UI's `Image`, `Card`, `Badge`, `InfoBar` (measured on .NET 10.0.14) — is skipped by the tree; if
it is also focusable (a `Control` is, by default) it is a Tab stop Narrator says nothing about. Give a display-only
control a peer (`Controls/SpokenTextAutomationPeer`) and take it out of the tab order; `ui:CardControl` has a peer with an
empty name even with a string `Header` — the App's implicit style takes it out of the tab order. (2) **A list's,
drop-down's or grid row's item is named by its `ToString()`**: a record's is its printed form (`Choice { Value = dark,
Label = Dark }`), a class's its full type name. Every item type overrides it (`Services/SpokenText` builds the words).
(3) **A `TextBlock` written straight into a `ControlTemplate` is no control element** (`TextBlockAutomationPeer`: not when
its templated parent is something other than a `ContentPresenter`): draw a template's text through a `ContentPresenter`
(the App's InfoBar template), or give the control a peer that says it. (4) **A `DataGridTemplateColumn`'s cell has no text
of its own**, so WPF names it `Item: <row>, Column Display Index: n`: name it with `controls:CellName.Path` (a cell style
based on `DefaultDataGridCellStyle`, the one WPF UI's grid gives every cell). Also: a plain `ItemsControl` is focusable
(the App's implicit style says no), and WPF UI's `CardExpander` leaves its expand button (`ExpanderToggleButton`)
unnamed (`Controls/ExpanderToggleName`, set by the App's implicit CardExpander style).
- [ ] **WPF UI 4.3.0 keys its DataGrid parts' styles and defines no implicit one** (`DefaultDataGridRowStyle`,
`DefaultDataGridCellStyle`, `DefaultDataGridColumnHeaderStyle`, handed to the grid by its implicit `DataGrid` style's
`RowStyle`/`CellStyle`/`ColumnHeaderStyle` setters). A local `RowStyle` replaces WPF UI's; based on
@@ -298,6 +383,12 @@ On startup and on `ApplicationThemeManager.Changed`: for every live plot set fig
such overload is public; the Close button's own path is `TemplateButtonCommand.Execute(MessageBoxButton.Close)`.
`Services/DialogKeyboard` registers one class handler on `Window` (bubbling `KeyDown`, so a dropdown's Esc wins) and
closes through those paths; `AccessibilityTests.EscapeClosesTheOpenDialogWithNoResult` holds it (`08_UI` §Accessibility).
*(Corrected 2026-10-26, beta.30: the CODE handles no key, but `ContentDialog.xaml` does route them — each template
button's `IsDefault` follows `DefaultButton`, Close is `IsCancel`, and while the primary is disabled a trigger makes
Close the default. Enter therefore clicks the default button from a single-line text box: the consent dialog's
`DefaultButton = Close` declined a typed phrase on Enter (the owner's report; D69 made the primary the default and the
content keeps Enter until the phrase matches). Esc through `IsCancel` is read from the template, not measured —
`DialogKeyboard` handles it first.)*
- [ ] **`ui:TextBlock Appearance` keeps the theme a text was made under (4.3.0).** `TextBlock.OnAppearanceChanged` stores
`TryFindResource(…)` in the internal `AppearanceForeground`, and `TextBlockMetadata` coerces every TextBlock's `Foreground`
to it — the brush found when the element was made, never looked up again (read at tag 4.3.0, 2026-10-07; `main` is the
+3 -3
View File
@@ -194,10 +194,10 @@ Every hook must be listed here with a purpose. Anything not on this list is not
|---|---|
| NGX: `NVSDK_NGX_D3D11/D3D12/VULKAN_CreateFeature`, `EvaluateFeature`, `ReleaseFeature` | Which NGX feature is *actually created and evaluated per frame*: SuperSampling (DLSS), RayReconstruction (DLSS-D), FrameGeneration (DLSS-G) |
| NGX parameter accessors (`NVSDK_NGX_Parameter_SetI/GetI/SetUI`) — **exported by `sl.common.dll` only; see below** | `Width`/`Height` (render) vs `OutWidth`/`OutHeight` (output), `PerfQualityValue` (quality preset), sharpness |
| ✅ Streamline: `slEvaluateFeature` · ⏳ `slInit`, `slSetFeatureLoaded`, `slSetConstants`, `slGetFeatureRequirements` | Feature set actually active when the game goes through SL rather than NGX directly (`kFeatureDLSS`, `DLSS_G`, `DLSS_RR`, `Reflex`, `NIS`). **Built 2026-08-09**, identity only: one MinHook detour on `sl.interposer.dll!slEvaluateFeature`, resolved **module-scoped** and installed lazily by the watchdog. Sets `FL_MEASURED_UPSCALER` + `FL_HOOK_UPSCALER_IDENTITY`; decodes `kFeatureDLSS`/`kFeatureNIS` and reports `FL_UPSCALER_UNKNOWN` for anything else. **Never `FL_UPSCALER_NONE`** — a Streamline-only writer cannot see FFX, XeSS or NGX-direct, and `NONE` is the only one of the three states that may be aggregated as a negative |
| ✅ Streamline: `slEvaluateFeature` · ⏳ `slInit`, `slSetFeatureLoaded`, `slSetConstants`, `slGetFeatureRequirements` | Feature set actually active when the game goes through SL rather than NGX directly (`kFeatureDLSS`, `DLSS_G`, `DLSS_RR`, `Reflex`, `NIS`; since beta.34 `kFeatureDLSS_NR` — DLSS 5's neural rendering, its own fact bit and family `FL_HOOK_SL_NEURAL_RENDERING`, D84; rule 4: the `feature` argument of the API hooked, nothing else). **Built 2026-08-09**, identity only: one MinHook detour on `sl.interposer.dll!slEvaluateFeature`, resolved **module-scoped** and installed lazily by the watchdog. Sets `FL_MEASURED_UPSCALER` + `FL_HOOK_UPSCALER_IDENTITY`; decodes `kFeatureDLSS`/`kFeatureNIS` and reports `FL_UPSCALER_UNKNOWN` for anything else. **Never `FL_UPSCALER_NONE`** — a Streamline-only writer cannot see FFX, XeSS or NGX-direct, and `NONE` is the only one of the three states that may be aggregated as a negative |
| ✅ Streamline: `slSetTag` — **and, since 2026-09-05, every tag's TYPE** (`slTagCensus`; a HUD-less / UI tag marks the present `FL_FG_DLSS_G`, rule 4: the same argument) | The **global** resource tags, where a title states the size of the buffer it is upscaling *from*: `kBufferTypeScalingInputColor`'s extent → `renderW/H` — **or, since 2026-09-05, the size the tagged `sl::Resource` declares when the extent is zero** (`TagSize` in `fl_sl_inputs.h`, shared by all three tag routes; GUID-checked; a Resource declaring no size is still the honest unknown). **Built 2026-08-15** (`FL_HOOK_UPSCALER_PARAMS`), and it is an ALTERNATIVE to the local tags in `slEvaluateFeature`'s `inputs`, not a layer over them — `sl_core_api.h:258` says global and local tags "do NOT interact", so a title using one yields nothing from the other and both are read. Published only on a frame where an evaluation was also seen, because a tag is viewport state that outlives any one frame. This row was MISSING from this table while the hook shipped, which is the gap the banner above now names |
| ✅ Streamline: `slSetTagForFrame` — **and every tag's TYPE, as above** | The same global tags through **Streamline 2.8's frame-based entry point**, which deprecates `slSetTag`: `(const FrameToken&, const ViewportHandle&, const ResourceTag*, uint32_t, CommandBuffer*)` — the token first, then exactly `slSetTag`'s list, handed to the same tag walk. **Built 2026-09-04** (`FL_HOOK_UPSCALER_PARAMS`, its own trampoline; the family is now **published when whole** — once every tag export the loaded interposer has is patched — because publishing on the first row entitled records the second was not yet producing, 38 of 41 on the fixture: the ffx leaves' #110 defect again, fixed the same way). Measured need: Dying Light: The Beast (SL 2.8.0) published `Dlss` identity on every batch and the params bit on none across three captures, because a 2.8 title that tags per frame never calls the deprecated export. The token is not read; the frame count stays with `slGetNewFrameToken`. The installer picks this detour by SYMBOL (`kSymbolSlSetTagForFrame`, bound to the row by `static_assert`), not by family, since the two rows share a family bit and differ in signature |
| ✅ **FidelityFX ffx-api: `ffxDispatch` on the FOUR modules a game calls** — `amd_fidelityfx_dx12.dll` (SDK 1.1.x monolith), `amd_fidelityfx_upscaler_dx12.dll`, `amd_fidelityfx_framegeneration_dx12.dll`, **and `amd_fidelityfx_loader_dx12.dll`** (added the evening of 2026-09-04: three loader-shipping titles at FSR produced zero dispatches at any leaf export, so the loader is where their calls arrive) · ⏳ FSR 3.0 host route `ffx_fsr3_x64.dll!ffxFsr3ContextDispatchUpscale` / `ffxFsr3DispatchFrameGeneration` · ~~`ffxFsr2ContextCreate`~~ · ~~`ffxCreateContext`~~ | **Built 2026-09-04** (`HANDOFF` item 7c). One observer behind three trampolines reads the DESCRIPTOR the title passed — head type first, body only after the type matched a constant from the vendored MIT headers (`third_party/fidelityfx/`, tag v2.3.0): **UPSCALE** → identity (`FSR3` from the monolith, `FSR_UNVERSIONED` from the 2.x upscaler DLL, which hosts FSR 3.1 and FSR 4 behind one type) + `renderSize` → `renderW/H` (quality and sharpness `0xFF`: the dispatch carries neither) + one COUNT; **PREPARE / PREPARE_V2** → `frameID` counted on a *new* index only — this vendor's `slGetNewFrameToken`, the `fgEvaluations` producer once a title has ever prepared, with the UPSCALE count as the fallback for a title that never does; **FRAMEGENERATION** → `fgMode = FSR_FG` on that present. Rule 4: the argument of the API we hooked, never `context`, `pNext`, a command list or a resource. **Why all four:** a UE5 title ships the two leaves with no loader and calls their exports; a loader-shipping title calls the loader's export and the signed loader reaches its providers through an object, not the leaves' exports (measured: Dying Light: The Beast, KCD2, Wukong). The morning's "never the loader" rested on the export tables alone and was reversed by the run. What guards against a loader that DID re-enter a leaf's export is the K = 1 control with all four hooked and the consumer's `frames/upscale-drained`, both of which read 2× in that case. `ffxCreateContext` is deliberately NOT a row — nothing it carries fills a field the dispatch does not, and its honest family would collide with `slEvaluateFeature`'s under the installer's equality binding. The family is compound (`IDENTITY \| PARAMS \| FG_EVALUATIONS`), pinned by `static_assert`s that also bind the leaf table to the rows both ways and refuse the loader as a row. Streamline keeps precedence for the count once it has ever issued a token, so every §S31-validated title is byte-identical. Second count: the consumer prints `frames/upscale-drained`, the AMD `tokens/batch`. **FSR 3.0 — BUILT 2026-09-05 as a fifth AMD target:** `ffx_fsr3_x64.dll!ffxFsr3ContextDispatchUpscale` (Cyberpunk's copy; named export, its own descriptor, vendored from tag **`fsr3-v3.0.4`** — the tag whose twelve `ffxFsr3*` declarations match the shipped module, not the `v1.1.4` first named). Rule 4: the detour reads `renderSize` of the descriptor the title passed and nothing else — never the context, a resource or the command list; the offset is pinned to a literal (1256) so a re-vendoring that moved it fails to compile. Same family and publish point as the four rows (`PublishFfxFamilyIfWhole` waits for a loaded host too), keyed by module in the installer; identity `FSR3` as a fact. `ffxFsr3DispatchFrameGeneration` is deliberately not a row (§H11 carries the reversal condition); the `ffx_fsr3upscaler_x64.dll` leaf is the pre-committed alternative if the facade reads silent (row B2) — never both, or `frames/upscale-drained` reads 2.00 |
| ✅ **FidelityFX ffx-api: `ffxDispatch` on the FOUR modules a game calls** — `amd_fidelityfx_dx12.dll` (SDK 1.1.x monolith), `amd_fidelityfx_upscaler_dx12.dll`, `amd_fidelityfx_framegeneration_dx12.dll`, **and `amd_fidelityfx_loader_dx12.dll`** (added the evening of 2026-09-04: three loader-shipping titles at FSR produced zero dispatches at any leaf export, so the loader is where their calls arrive) · ⏳ FSR 3.0 host route `ffx_fsr3_x64.dll!ffxFsr3ContextDispatchUpscale` / `ffxFsr3DispatchFrameGeneration` · ~~`ffxFsr2ContextCreate`~~ · ~~`ffxCreateContext`~~ | **Built 2026-09-04** (`HANDOFF` item 7c). One observer behind three trampolines reads the DESCRIPTOR the title passed — head type first, body only after the type matched a constant from the vendored MIT headers (`third_party/fidelityfx/`, tag v2.3.0): **UPSCALE** → identity (`FSR3` from the monolith, `FSR_UNVERSIONED` from the 2.x upscaler DLL, which hosts FSR 3.1 and FSR 4 behind one type) + `renderSize` → `renderW/H` (quality and sharpness `0xFF`: the dispatch carries neither — *since beta.25 the quality byte is the mode the `ffxQuery` row below names for the dispatched size, `0xFF` when none does*) + one COUNT; **PREPARE / PREPARE_V2** → `frameID` counted on a *new* index only — this vendor's `slGetNewFrameToken`, the `fgEvaluations` producer once a title has ever prepared, with the UPSCALE count as the fallback for a title that never does; **FRAMEGENERATION** → `fgMode = FSR_FG` on that present. Rule 4: the argument of the API we hooked, never `context`, `pNext`, a command list or a resource. **Why all four:** a UE5 title ships the two leaves with no loader and calls their exports; a loader-shipping title calls the loader's export and the signed loader reaches its providers through an object, not the leaves' exports (measured: Dying Light: The Beast, KCD2, Wukong). The morning's "never the loader" rested on the export tables alone and was reversed by the run. What guards against a loader that DID re-enter a leaf's export is the K = 1 control with all four hooked and the consumer's `frames/upscale-drained`, both of which read 2× in that case. `ffxCreateContext` is deliberately NOT a row — nothing it carries fills a field the dispatch does not, and its honest family would collide with `slEvaluateFeature`'s under the installer's equality binding. The family is compound (`IDENTITY \| PARAMS \| FG_EVALUATIONS`), pinned by `static_assert`s that also bind the leaf table to the rows both ways and refuse the loader as a row. Streamline keeps precedence for the count once it has ever issued a token, so every §S31-validated title is byte-identical. Second count: the consumer prints `frames/upscale-drained`, the AMD `tokens/batch`. **FSR 3.0 — BUILT 2026-09-05 as a fifth AMD target:** `ffx_fsr3_x64.dll!ffxFsr3ContextDispatchUpscale` (Cyberpunk's copy; named export, its own descriptor, vendored from tag **`fsr3-v3.0.4`** — the tag whose twelve `ffxFsr3*` declarations match the shipped module, not the `v1.1.4` first named). Rule 4: the detour reads `renderSize` of the descriptor the title passed and nothing else — never the context, a resource or the command list; the offset is pinned to a literal (1256) so a re-vendoring that moved it fails to compile. Same family and publish point as the four rows (`PublishFfxFamilyIfWhole` waits for a loaded host too), keyed by module in the installer; identity `FSR3` as a fact. `ffxFsr3DispatchFrameGeneration` is deliberately not a row (§H11 carries the reversal condition); the `ffx_fsr3upscaler_x64.dll` leaf is the pre-committed alternative if the facade reads silent (row B2) — never both, or `frames/upscale-drained` reads 2.00 |
| ✅ **FidelityFX ffx-api: `ffxQuery` on the same four modules** (beta.25, owner decision D65) — `amd_fidelityfx_dx12.dll`, `amd_fidelityfx_upscaler_dx12.dll`, `amd_fidelityfx_framegeneration_dx12.dll`, `amd_fidelityfx_loader_dx12.dll` | **Built 2026-10-19.** The mode an FSR title runs at reaches the vendor only as an argument of `ffxQuery` — "what render size (`…GETRENDERRESOLUTIONFROMQUALITYMODE`, `0x00010003`) or ratio (`…GETUPSCALERATIOFROMQUALITYMODE`, `0x00010002`) does this mode give at this display size?" — asked before the title sizes its targets; the per-frame dispatch carries the size alone. The detour calls the original FIRST, exactly once, and only when it returned `FFX_API_RETURN_OK` reads the descriptor's type, display size and mode and the values the vendor wrote through the title's own out pointers, into a five-slot table (one per `FfxApiUpscaleQualityMode`); the `ffxDispatch` UPSCALE arm names the ONE mode whose kept answer fits the dispatched `renderSize` (and `upscaleSize`, where stated) as `0x10 + mode` in `upscalerQuality`, else `0xFF` (`03_METRICS` §Upscaling). **Rule 4:** the arguments of the API we hooked — the descriptor the title passed and the out values of that same call — never `context`, a resource or anything the title did not hand the hooked export; nothing of the title's is written, and every read is under the hook's SEH guard. Both query layouts and type ids are pinned to literals by `static_assert`s, identical at SDK v1.1.4 and v2.3.0. **Its own family**, `FL_HOOK_UPSCALER_QUALITY` (bit 11 of `hooksInstalledMask`, mirrored in `FlHookFamily` and `HookFamilies`): `InstallByFamily` binds a row by equality, and the query entitles no measured field by itself — the byte rides under `FL_MEASURED_UPSCALER_PARAMS` from the dispatch arm — so the bit says only that the query was hooked, which tells "never asked" from "could not have seen it ask". Published like the dispatch family, once every loaded leaf is patched (`PublishFfxQueryFamilyIfWhole`); the FSR 3.0 host has no `ffxQuery` and no row (`static_assert`). A loader that passes a query on to a leaf's export refreshes one kept answer twice; nothing is counted, so nothing is counted twice. **Measured overhead** (a copy of the two bodies, `/O2 /guard:cf /Qspectre /MT`, 20 M calls × 3 runs, every slot holding both a size and a ratio — the worst case): 7.6–8.2 ns added per UPSCALE dispatch, i.e. per application frame, and 1.6 ns per query beside the trampoline; the per-present path gains one load. Harness: `--ffx-query sizes|ratios`; `fl_guard` "FSR's quality mode". |
| ~~XeSS: `xessD3D12CreateContext`, `xessD3D12Init`, `xessD3D12Execute`~~ **Closed at the census by licence, 2026-09-04** (`20_OPEN_QUESTIONS` §Scope decisions, `18_GPU_VENDOR_APIS` §Intel XeSS SDK): no hook on any `libxess*.dll` export *(corrected 2026-10-04)* | ~~`outputResolution`, `qualitySetting`, XeSS version; `xess_fg` variants for XeFG~~ |
| ✅ **Application frames per present** (`fgEvaluations`) — **`sl.interposer.dll!slGetNewFrameToken` since 2026-09-03** | Native vs Displayed frame counts at Tier 1 — see `03_METRICS` §Frame Generation. **The producer is the frame-token export**: Streamline hands a title one token per application frame and the title must ask; the detour counts distinct tokens between two presents (pointer changes, nothing dereferenced), `FL_HOOK_FG_EVALUATIONS` is its family, and it installs on every Streamline 2 title including the ones that evaluate nothing through `slEvaluateFeature`. Rule 4: the out-parameter of an API we hooked. Premise and its gate in `03_METRICS`; pre-committed table in `20_OPEN_QUESTIONS` §S31. *The row as it stood before:* ~~NGX/SL/FFX/XeSS FG feature evaluations per present. **Built 2026-08-15 for Streamline, and MEASURED TO YIELD NOTHING ON THAT ROUTE**~~ — `slEvaluateFeature(kFeatureDLSS_G)` is never called by Cyberpunk 2077 (0 across ~14,000 batches, four FG settings), so this row installs, is honest, and counts zero; see `docs/HANDOFF.md` item 3. Built on the detour that was already there: `kFeatureDLSS_G` contributes to a saturating COUNT in the same word the feature bits live in (`fl_sl_seen.h`) rather than to a bit, because a bit collapses several evaluations between two presents into one — and under multi-frame generation that is the common case, not the edge. The row's family is therefore compound (`FL_HOOK_UPSCALER_IDENTITY \| FL_HOOK_FG_EVALUATIONS`), pinned by a `static_assert` because `hookinventory-check` reads that column as an opaque identifier. **Counts EVALUATIONS, not generated frames** — the 2026-08-14 owner ruling; the multiplier lives in `sl::DLSSGOptions`, which is only reachable by the route §2b refused. ~~Non-NVIDIA FG vendors are **deferred with a written rationale**: `amd_fidelityfx_framegeneration_dx12.dll` 3.1.5 exports only the five generic `ffx*` entry points, identical to five sibling modules, so identity is in the arguments and we have no headers~~ — **AMD has a producer since 2026-09-04** (the FidelityFX row above: the PREPARE dispatch's `frameID`, or the UPSCALE count on a title that never prepares, feeds `fgEvaluations` when Streamline has never issued a token); Intel stays at the census (`20_OPEN_QUESTIONS` §Scope decisions, by licence); the FSR 3.0 host DLL's UPSCALE (`ffxFsr3ContextDispatchUpscale`, since 2026-09-05) counts like an ffx-api UPSCALE when neither Streamline nor a PREPARE has spoken |
@@ -481,7 +481,7 @@ struct alignas(64) FlFrameRecord { // 64 bytes exactly, static_assert'd
uint16_t outputW, outputH; // @22
uint8_t api; // @26 d3d11|d3d12|vulkan|opengl
uint8_t upscaler; // @27 0 = NOT_REPORTED; dlss|fsr2..4|xess|nis|none(8)|unknown(0xFF)
uint8_t upscalerQuality; // @28 vendor enum; 0xFF = a hook ran and could not tell
uint8_t upscalerQuality; // @28 vendor enum (FSR: 0x10 + mode, beta.25); 0xFF = a hook ran and could not tell
uint8_t fgMode; // @29 0 = NOT_REPORTED; dlss_g|fsr_fg|xefg|none(4)|unknown(0xFF)
uint8_t rtFlags; // @30 bit0 asBuildOBSERVED, bit1 dispatchOBSERVED, bit2 psoCreatedEver
uint8_t colorSpace; // @31 0 = NOT_REPORTED, 1 SDR, 2 HDR10, 3 scRGB
+1 -1
View File
@@ -237,7 +237,7 @@ Still resolve **entry points defensively at runtime**: `nvapi64.dll` may be abse
| Memory | `NvAPI_GPU_GetMemoryInfoEx` — **not `NvAPI_GPU_GetMemoryInfo`**, which this table named until 2026-08-05. The vendored headers mark it `__nvapi_deprecated_function` ("deprecated in release 520"), so under `/W4 /WX` a call to it fails the native build. **Neither is called (2026-09-10):** the vendored `nvapi.h` (`cd6918f6`) does not declare `GetMemoryInfoEx` at all — the deprecation message names a function the same header set does not ship — so the bridge's `vram` field is **reserved**, its bit is never set, and VRAM stays L1's PDH adapter counter. Taking a newer header set is the way to change that, not a call to the deprecated one |
| **Throttle reasons** | `NvAPI_GPU_GetPerfDecreaseInfo` — not available from L1 or L2. **Bridge (2026-09-10):** the raw reason mask, and 0 is a measurement (no reason), not a clear bit |
| Driver version | `NvAPI_SYS_GetDriverAndBranchVersion` — **bridge (2026-09-10):** `FlNvDriverVersion`, surfaced as `616.64 (r616_41)` |
| **NGX per-process state** | `NvAPI_NGX_GetNGXOverrideState` (R570+) — the driver's feedback word per DLSS feature for a PID, read OUT OF PROCESS by `fl-probe-nvapi --ngx-state` and, since 2026-09-06, by the capture host beside each module snapshot — **in-process through the bridge since 2026-09-10** (`NvapiNgxStateProbe`; the spawn is retired and the words, the merge and the printed block are unchanged). Measured: the SR word's `CREATED \| EVALUATE` is set without an NVIDIA-app override; the FG word follows DLSS-G once created (`CREATED \| EVALUATE` at ×4, corrected the same day — the first reading was blind because it was early), the multiplier bits stay clear; `scalingRatio` is 0 even under an override. Identity only, SR and FG (`03_METRICS` §Upscaling) — and, since beta.24 (D63), the mode an NVIDIA App override set where the word says it applied; its `performanceMode` is in NGX's own numbering (Silent Hill 2, 2026-10-13: the App's Ultra Performance, profile value 5, reported as 3) |
| **NGX per-process state** | `NvAPI_NGX_GetNGXOverrideState` (R570+) — the driver's feedback word per DLSS feature for a PID, read OUT OF PROCESS by `fl-probe-nvapi --ngx-state` and, since 2026-09-06, by the capture host beside each module snapshot — **in-process through the bridge since 2026-09-10** (`NvapiNgxStateProbe`; the spawn is retired and the words, the merge and the printed block are unchanged). Measured: the SR word's `CREATED \| EVALUATE` is set without an NVIDIA-app override; the FG word follows DLSS-G once created (`CREATED \| EVALUATE` at ×4, corrected the same day — the first reading was blind because it was early), the multiplier bits stay clear; `scalingRatio` is 0 even under an override. Identity only, SR and FG (`03_METRICS` §Upscaling) — and, since beta.24 (D63), the mode an NVIDIA App override set where the word says it applied; its `performanceMode` is in NGX's own numbering (Silent Hill 2, 2026-10-13: the App's Ultra Performance, profile value 5, reported as 3). *(Beta.27: never read after the game has gone — that reading, the last, had cleared `CREATED \| EVALUATE` on every stored session — and the two bits stand once a reading carried them: `03_METRICS` §The driver-reported rung.)* |
| **Reflex / PC latency** | `NvAPI_D3D_GetLatency` → per-frame sim/render/present/driver/GPU timestamps; hooking `NvAPI_D3D_SetSleepMode` / `SetLatencyMarker` in the Overlay tells us the game enabled Reflex (`17_HOOK_ENGINE`) |
Reflex latency is the single strongest reason L3 exists — it is genuinely unavailable anywhere else.
+70 -1
View File
@@ -387,6 +387,20 @@ Implemented in `FrameLedger.Injector` and reached from managed code through a th
> appeal. A nested executable outside a recognised store layout is therefore
> still scanned narrowly; that residual is stated, not closed.
>
> **Amended 2026-11-03 (beta.33, `spike-notes` §25): a GDK package root is a boundary too, and `GamesInstalled`
> is one natively.** The Xbox app and the Microsoft Store install to `<games folder>\<Game>\Content\` under a
> folder the user names, which no string can bound — so for the executable the import picks there (an Unreal
> title's `Content\<Project>\Binaries\WinGDK\…-Shipping.exe`), check 4 walked `Binaries\WinGDK` alone, and an
> `EasyAntiCheat\` at `Content`'s root would have read clean: the residual above, on a whole store. The package
> marks its own root — `MicrosoftGame.config` beside `appxmanifest.xml`, both files — so **only when no string
> boundary matched**, the nearest folder at or above the executable's that holds both is the root (at most eight
> levels up, never a drive's root; `ResolveInstallRoot` and the managed `InstallRoot`). Not a blind walk up: a
> marker the package writes, measured as exactly one per package at `Content`'s root on the owner's 11 titles; and
> only ever a widening relative to the executable's folder — a Steam build carrying GDK files keeps its Steam root.
> The native list also gains `GamesInstalled\<X>`, which the managed one had since #17 and the native one never
> did; one case list (`tests/fixtures/install-roots/cases.txt`), read by both suites, holds the two resolvers
> together from now on.
>
> **Amended 2026-10-13: the root AND the executable's folder.** The root replaced the executable's folder, and
> that was half the answer. The walk reaches three levels below where it starts, and an Unreal executable is
> already three below its root, so a folder **beside** the executable is four: MEASURED on Wuthering Waves, whose
@@ -461,6 +475,41 @@ the injection primitive, not a fifth question about the title.
> **There is no override.** ~~There is one, since 2026-09-21, and it is none of the things this paragraph named~~ *(one day; withdrawn 2026-09-22)*: still no hidden setting, no config-file flag, no CLI switch, no "advanced users" escape hatch, no global form. If a user disagrees with a specific entry, the path is still a GitHub issue against the rules file, reviewed in public. What exists is below — and since 2026-09-26 (D33), one narrow, evidence-bound exception for anti-cheat that is user-mode throughout, which lets a named family through while every check still runs (§The user-mode exception).
### The target must be able to take the Overlay — beta.33 (D78)
The last question before the primitive, after checks 1–4 and the payload's identity passed: **can this process take the
Overlay at all?** The guard reads it from the target itself (`Sources::TargetIsolationFacts`, one
`PROCESS_QUERY_LIMITED_INFORMATION` handle — measured 2026-11-03 to answer both questions, `GetProcessMitigationPolicy`
needing no more):
| Read | Refusal | Why it cannot work |
|---|---|---|
| `TokenIsAppContainer` | `kTargetAppContainer` | a Microsoft Store app of the UWP kind: the Overlay's shared memory, its `Local\` names and the rules file live in the user's session namespace and profile, which an AppContainer cannot open. D78: GDK games are in, UWP apps are out |
| `ProcessSignaturePolicy`: `MicrosoftSignedOnly` or `StoreSignedOnly` | `kTargetMitigation` | the Overlay is neither (CLAUDE.md rule 9: unsigned): the remote `LoadLibraryW` fails |
| `ProcessDynamicCodePolicy`: `ProhibitDynamicCode` | `kTargetMitigation` | MinHook's trampolines are dynamic code: the Overlay would load and hook nothing |
| `ProcessUserShadowStackPolicy`: strict mode, or `BlockNonCetBinaries` / `BlockNonCetBinariesNonEhcont` | `kTargetMitigation` | the Overlay is not marked CET-compatible: refused at load, or a violation ends the game |
| `ProcessControlFlowGuardPolicy`: `StrictMode` | `kTargetMitigation` | `native/CMakeLists.txt` H1: measured safe with strict mode off only; a host in strict mode could still `__fastfail` on the trampolines, which no fault policy can catch (rule 5) |
**The policy is the signal**, and only the enforcing flags count: an `Audit*` flag refuses nothing, and
`SetContextIpValidation` without strict mode is what every CET-compatible process carries (measured: `pwsh.exe`
`0x105`). A policy the running Windows does not know answers `ERROR_INVALID_PARAMETER` (measured) and cannot be in
effect. **"Could not tell" refuses** — a seam that fails, or none wired — as `kProcessUnreadable`, the module check's word
for a process it could not read. ctest `fl_guard` `[isolation]` holds each refusal through fakes, and two of them against
Windows itself: a child started under "no dynamic code" and "Microsoft-signed images only".
**Neither is a finding.** Nothing is written to the game's row and no family is named; the session is Tier 2 with the
reason, as for a 32-bit game. **No game that measured before is refused now**: each of these ended as a failed injection,
an Overlay that installed no hooks, or a risk of ending the game. It is asked once, before the injection — never by the 30 s
re-scan, which runs inside a process the Overlay is already in — and, like the payload check, it is not numbered as a
check: it is a precondition of the primitive, not a question about the title.
**A GDK game's tree, measured (`spike-notes` §25, six titles activated through their packages):** the chain is
`GameLaunchHelper.exe` → `gamingservicesui.exe` → `XboxPcTray.exe` → the launch executable (→ an Unreal title's shipping
executable), `GameLaunchHelper` exits first, and its parent is the activator — the user's shell when **Play** starts it,
which is where the scan set already stops. Every member opened with the guard's rights as a standard user, none is an
AppContainer, none runs under any of the policies above, and no member's module matched a fuzzy fragment or a blocklist
name. So the scan set needs nothing new for these titles; an Xbox title that ships anti-cheat is unmeasured
(`20_OPEN_QUESTIONS` §G).
### What a finding does to the game — owner decision 2026-09-22
**The per-game override of 2026-09-21 is withdrawn.** It shipped in `0.1.0-beta.3` and `beta.4`. Its first real use
@@ -1036,7 +1085,8 @@ Consent is stored per game (`games.hook_consent_at`), **stamped by the Agent, ne
> neither choice), what is injected and why, **Tier 1 and Tier 2 as two paragraphs of the same shape** (each
> enumerating what the session records; Tier 2 is described by what it does, never as less), the anti-cheat
> statement including the 30 s unhook, the terms-of-service statement, and the typed acknowledgement — the
> primary button is disabled until the phrase is typed exactly, and Enter never enables. `en` and `vi` are
> primary button is disabled until the phrase is typed exactly~~, and Enter never enables~~ *(Enter enables once the
> phrase matches since beta.30, owner decision D69 — below)*. `en` and `vi` are
> written (the owner reviews `vi`); **`ja` is the English verbatim, marked `safety: human review required`**,
> which the resx audit enforces (`09_I18N` §Safety-critical strings). The wording carries a version
> (`Shared.Safety.SafetyDisclosure.Version = consent-dialog/1`; bump on any change of meaning in any
@@ -1048,6 +1098,18 @@ Consent is stored per game (`games.hook_consent_at`), **stamped by the Agent, ne
> `PipeEndToEndTests` (the real pipe, the real pre-scan, the row read back) pin each half. The toggle that opens
> it is the game page's, PR-5.
> **Amended 2026-10-26 (beta.30, owner decision D69): Enter enables once the phrase is typed exactly.** "Enter never
> enables" was built as `DefaultButton = Close`, and WPF UI 4.3.0's template sends Enter to the default button (each
> button's `IsDefault` follows `DefaultButton`, read at the tag) — so the owner typed the phrase, pressed Enter and
> declined without a word, while the game page's switch went on showing *on* beside *off*. Asked with that, the owner
> chose: the primary button is the default; while the phrase does not match, the dialog's content keeps Enter
> (`ConsentDialogContent.SwallowsEnter`) and nothing happens; once it matches, Enter enables, as a click on the
> then-visible *Enable hooking* does. **The typed phrase is still the gate**: the button Enter reaches is disabled — and
> hidden — until the phrase is typed exactly, so a reflexive Enter cannot enable; Esc and *Keep hooking off* still
> decline. No `Safety_Consent_*` string changed, so `consent-dialog/1` stands. `ConsentDialogKeysTests` holds both
> halves on the real template. The tick-box dialogs (D33's exception, D34's admin mode) are unchanged: Enter keeps them
> declined.
> **The Agent stamps one since 2026-09-10 (P2 PR-F, HANDOFF §P2 decision D4):** `FrameLedger.Agent --console
> consent grant` shows `OperatorDisclosure` (the same four statements, first line naming the surface), requires
> the typed phrase, refuses redirected stdin, and records `ConsentProvenance.AgentConsoleOperator` with the
@@ -1145,6 +1207,13 @@ outlives a rules change, a game update and *Change executable*; §What a finding
## Crash & stability safety
- Two crashes of the same game within 60 s of injection ⇒ hooking auto-disabled for that game, UI explains, Tier-2 takes over. Recorded in `games.hook_autodisabled_reason`. *"Crash" here is any abnormal end: since beta.8 a session whose exit code is not an exception's (End task's 1) is `normal` on its row, and this policy still counts it inside the window — a hang our hook caused, ended by the user, is the case it exists for. The row's reason says "ended abnormally twice within 60 s of injection" (`04_CAPTURE` §Crash & exit classification).*
- **Measured 2026-10-19/20 (`spike-notes` §23): direct starts turned hooking off for exits no hook caused.** Lies of P
started by **Play** ▸ *Start directly* hands itself to Steam within seconds — its process leaves with nothing
presented and Steam starts the game again —, and Clair Obscur: Expedition 33 started directly closes within five
seconds and reads *crashed*, hooked or not (its third start, refused and unhooked, closed the same way). Each was a
hooked session's early abnormal end; the policy counted them, and two turned hooking off. It cannot tell either from
the hang it exists for, so it stands as written; whether a witness — the same executable started again within
seconds — may exempt a hand-off is the owner's decision, not taken. Users are told in `LIMITATIONS.md` §Play.
- **What reads as a crash changed in beta.14, in both directions** (`04_CAPTURE` §Crash & exit classification): a
Windows report that is not a crash (a memory-leak or hang report) no longer makes one, and an engine's crash reporter
started by a game that then left does — Unreal's crash ended with exit code 3 and read `normal`. Both feed this policy,
+4 -1
View File
@@ -1913,9 +1913,12 @@ Each of these is referenced by an existing doc but specified nowhere.
| ~~**Threading model**~~ | ~~Which component owns which thread, UI-thread rules, and how the 1 Hz telemetry poller, 10 Hz drain and pipe reader interact~~ **Answered 2026-09-09 (P2 PR-C): `04_CAPTURE` §Threading model** — four threads, one owner per shared object, the pipe reader named as one more producer. This row was not struck when the section was written; struck 2026-09-13. What is still unspecified is the UI thread's own rules, which is `08_UI`'s in P3 | `04_CAPTURE`, `18_GPU_VENDOR_APIS` |
| **Pipe/shm security** | Stated as policy ("DACL granting the current user's SID") but not as implementable SDDL, nor who creates the objects with what rights. The shm half is built (`fl_shm_host.h`, the Overlay creates the section under the current user's SID); the pipe half is **built 2026-09-13 (P3 PR-1, HANDOFF §P3 decision D11)**: `D:P(A;;GA;;;<user>)(A;;GA;;;BA)` (with the owner `O:<user>` stated since 2026-09-17, `07_IPC` §C) handed to `CreateNamedPipe` with `PIPE_REJECT_REMOTE_CLIENTS`, and the client's token user compared by impersonation on its first frame (`Infrastructure.Ipc.PipeAccessControl`, pinned by `PipeServerClientTests` including the refused stranger). **Row closed** | `07_IPC` |
| ~~**Legal doc versioning**~~ | ~~FR-11 re-shows documents "when a document version increments". Nothing says where the current version lives, who writes `legal_acceptance.version`, or how the markdown is rendered in-app~~ **Answered 2026-09-14 (P3 PR-9):** the version is the document's own `**Version:**` line, read from the copy embedded in the App at build (`App.Services.LegalDocuments`); the App writes `legal_acceptance.version` on the one Accept and re-shows any document whose embedded version differs from its row; ~~the markdown is shown as text with authoring comments stripped, not rendered~~ the markdown is shown with authoring comments stripped and, since beta.12, rendered (`08_UI` §Menu, *Documents are rendered*; §First-run flow built note) | FR-11, `06_DATA_MODEL` |
| **Accessibility / DPI** | NFR-9 states requirements; no design anywhere | NFR-9, `08_UI` |
| ~~**Accessibility / DPI**~~ | ~~NFR-9 states requirements; no design anywhere~~ **Answered 2026-09-15 (P4 PR-8): `08_UI` §Accessibility** — what each clause of NFR-9 means here and the check that holds it; this row was not struck then. Since 2026-11-09 (beta.35, D88) the users' half is `ACCESSIBILITY.md`, and NFR-9 names screen readers and contrast themes too. **Row closed** | NFR-9, `08_UI` |
| **Uninstall / data deletion** | One Velopack clause. No in-app "delete all my data", despite the privacy position | `12_BUILD`, `legal/PRIVACY_POLICY.md` |
| ~~**Cover art**~~ | ~~Appears in the schema, the data directory and the UI; nothing says where it comes from or the licence position on downloaded store art~~ **Answered 2026-10-14 (beta.23, owner decisions D60/D61):** from the user's own image (a copy in `covers\`) or what the Steam and GOG GALAXY apps already keep on this PC — nothing is downloaded, so no store art is redistributed or fetched; the art stays its owners' (`legal/TRADEMARKS.md`), the Privacy Policy 2.11 names the files read. `08_UI` §Games › Game detail. **Row closed** | `06_DATA_MODEL`, `05_DETECTION` |
| ~~**The main line's .NET**~~ *(added 2026-10-31, D73–D76; decided 2026-11-11)* | **When does the main line — the betas and the first release — leave .NET 10 LTS, and for what?** The alpha line (`12_BUILD` §The alpha line) builds the same source on .NET 11 to gather the evidence; it decides nothing by existing. What is known: .NET 11 is STS, supported 24 months to about 2028-11, no later than .NET 10 LTS (2028-11-14), so moving buys no support time; Microsoft's supported-OS list for .NET 11 has Windows 10 only in its LTSC and IoT editions, against NFR-8's Windows 10 22H2 floor; C# 15's unions and closed hierarchies would suit the tri-states and refusal reasons, but only once the main line compiles C# 15. **Decision table, written before the evidence:** move to .NET 11 only if (a) at least two alphas on the GA runtime pass the gate and an owner's run of a hooked title with no runtime-specific defect, (b) the owner accepts dropping NFR-8's floor to Windows 11 or ships knowingly unsupported on Windows 10, and (c) something .NET 11 brings is wanted — a measured gain or a language feature; otherwise stay on .NET 10 and take .NET 12 LTS (expected 2027-11) the same way, through the alpha line first. **Decided 2026-11-11 (owner decisions D94–D96), the day after .NET 11 shipped: the main line moves with 0.1.0-beta.37.** Of the table: (a) was **set aside by the owner, not met** — no alpha had run on the released runtime; alpha.1 to alpha.3 ran on Release Candidate 3 with the gate green each time, and no owner's run of a hooked title on an alpha is recorded in this repository; (b) Windows 10 22H2 is not blocked and is stated as untested and unsupported (D95, NFR-8 amended); (c) C# 15 is used from the same release (D96). What stood in for (a): the whole gate on SDK 11.0.100 (`spike-notes` §28) and owner-only item 34. .NET 12 is taken the way this row described — through the alpha line first — and whether the main line follows is asked again then. **Row closed** | `12_BUILD`, `13_CI_CD`, `02_SPEC` NFR-8, CLAUDE.md pinned stack |
| **C# 15 on the main line** *(added 2026-11-11, beta.37, D96)* | **When can the main line use C# 15's constructs?** It compiles them since beta.37 and uses none: ReSharper's engine — InspectCode 2026.2.3.1, which Qodana 2026.2 runs, and 2026.3.0 — parses neither `closed` nor `union` and calls collection expression arguments and labeled jumps preview features, so each file that used one would be an error on Qodana's gate of zero; a union also draws CA1815 from the SDK's own rules; and what CodeQL (documented up to C# 14) extracts of them is not established, a pull request's analysis being an overlay. **Answered by:** the canary of `spike-notes` §29 run again on the engine the Qodana linter then carries, and a `workflow_dispatch` of `codeql.yml` on its branch. The survey of where each construct would go is in that note | `13_CI_CD` §C# 15 and the analyses, CLAUDE.md pinned stack |
| **Xbox app / Microsoft Store titles** *(added 2026-11-03, beta.33, D77–D82)* | GDK titles are imported, played and measured since beta.33 (`spike-notes` §25: full trust, the user's token, the session's object namespace, the image path the `Content` folder's); what is NOT answered: **(1) title lists know Steam ids only (D81).** `blockedStoreIds` has no `store` value for a Microsoft Store product id or a package family name, and the guard has no reader for one, so an Xbox copy of a game listed there by its Steam id is matched by its executables, modules, files, drivers and services but not by that entry. Keying one would take a schema value (`additionalProperties: false` there is a safety control) and a reader under D31's rule — listed refuses, none is not applicable, unreadable refuses — fed by `MicrosoftGame.config`'s `StoreId`, which the import already reads. The owner chose not to, for now. **(2) A Vulkan GDK title is not measured:** the layer is enabled by `FRAMELEDGER_ENABLE_VK_LAYER=1`, which only a launch FrameLedger makes can set, and a package is started by Windows. **(3) A package that keeps write virtualization on** (all 11 measured turn it off) would put the Overlay's log in its `LocalCache`, out of the bug report's reach; capture itself never reads the log. **(4) Unmeasured:** a start from inside the Xbox app (GameLaunchHelper's parent there — the scan set's next process), any GDK title with anti-cheat, the ring from a packaged process (the owner's first hooked session) | `02_SPEC` §Out of scope, `05_DETECTION`, `19_SAFETY` check 3, `LIMITATIONS.md` |
| **Tier-2 mechanism** *(was: PresentMon distribution)* | **By what mechanism does a shipped build reach a no-injection MEASUREMENT?** Nothing names one. Since 2026-08-28 the ladder is two rungs and Tier 2 is explicitly not a measurement — duration, sensors and the reason — so this row is no longer about degraded fidelity but about whether that capability returns at all. **It now owns TWO casualties, not one:** the frame-generation oracle §S31 spent four attempts looking for, and `14_TESTING`'s Tier-1 accuracy cross-check, struck the same day because it required a second instrument measuring the same frames. **One mechanism would restore both**, which is the strongest argument for costing it. Constraints on any answer: `README`'s capture-tier table and its **safety** row *"always a way out"*, `legal/DISCLAIMER.md` §73 and `legal/EULA.md` §33; ETW needs elevation whatever the tool; and `15_ROADMAP` has no v2 fallback either | `README`, `legal/DISCLAIMER.md`, `legal/EULA.md`, `04_CAPTURE`, `14_TESTING`, `15_ROADMAP` |
---
+303 -66
View File
@@ -63,6 +63,19 @@ owner-only items stay below; the history of every train, the passed owner-only i
| `§beta.21` | [`handoff/history/0.1.0-beta.21.md`](handoff/history/0.1.0-beta.21.md) |
| `§beta.22` | [`handoff/history/0.1.0-beta.22.md`](handoff/history/0.1.0-beta.22.md) |
| `§beta.23` | [`handoff/history/0.1.0-beta.23.md`](handoff/history/0.1.0-beta.23.md) |
| `§beta.24` | [`handoff/history/0.1.0-beta.24.md`](handoff/history/0.1.0-beta.24.md) |
| `§beta.25` | [`handoff/history/0.1.0-beta.25.md`](handoff/history/0.1.0-beta.25.md) |
| `§beta.26` | [`handoff/history/0.1.0-beta.26.md`](handoff/history/0.1.0-beta.26.md) |
| `§beta.27` | [`handoff/history/0.1.0-beta.27.md`](handoff/history/0.1.0-beta.27.md) |
| `§beta.28` | [`handoff/history/0.1.0-beta.28.md`](handoff/history/0.1.0-beta.28.md) |
| `§beta.29` | [`handoff/history/0.1.0-beta.29.md`](handoff/history/0.1.0-beta.29.md) |
| `§beta.30` | [`handoff/history/0.1.0-beta.30.md`](handoff/history/0.1.0-beta.30.md) |
| `§beta.31` | [`handoff/history/0.1.0-beta.31.md`](handoff/history/0.1.0-beta.31.md) |
| `§beta.32` | [`handoff/history/0.1.0-beta.32.md`](handoff/history/0.1.0-beta.32.md) |
| `§beta.33` | [`handoff/history/0.1.0-beta.33.md`](handoff/history/0.1.0-beta.33.md) |
| `§beta.34` | [`handoff/history/0.1.0-beta.34.md`](handoff/history/0.1.0-beta.34.md) |
| `§beta.35` | [`handoff/history/0.1.0-beta.35.md`](handoff/history/0.1.0-beta.35.md) |
| `§beta.36` | [`handoff/history/0.1.0-beta.36.md`](handoff/history/0.1.0-beta.36.md) |
| `§Owner-only`, an open item | [§Owner-only](#owner-only--no-pr-can-close-these) below |
| `§Owner-only`, a passed item (3, 12, 14–19) | [`handoff/owner-only-passed.md`](handoff/owner-only-passed.md) |
| `§Traps`, `§Two corrections carried forward` | [`handoff/traps.md`](handoff/traps.md) |
@@ -70,72 +83,99 @@ owner-only items stay below; the history of every train, the passed owner-only i
---
## **START HERE** — 2026-10-19, 0.1.0-beta.24: every frame-generation state, the NVIDIA App's quality mode, which DLSS ran, SonarCloud, the documents split
## **START HERE** — 2026-11-11, 0.1.0-beta.37: the main line on .NET 11, what an alpha is now, and why no C# 15 yet
*Status is `docs/changelog/0.1.0-beta.24.md`; this is what no other file carries.* The owner, 2026-10-19: "Bạn xem xét,
đánh giá và lên plan cho bản beta mới với những nội dung như sau:" — six items: the mix of frame-generation modes inside
one session, shown in the App; the upscaler's quality mode (Ultra Performance … DLAA, FSR's too) only when captured, the
NVIDIA App's override as the standard where there is one; SonarCloud fixed and its false positives marked; a SonarCloud
configuration that keeps third-party headers out; which DLSS is in use (3, 4, 4.5, 5), if it can be found; the long
documents split — then, with the plan approved, the whole train to the release without asking again. Later the same
day: "Bạn có thể xét tới trường framegen chỉnh trong setting in-game nếu chưa có" (the frame generation chosen in the
game's own menu). Answers that set the decisions below, given before the plan: the mix as a share bar and a table; the
owner marks Sonar's false positives in its UI from a list we write; all four long documents split; the override is the
standard only where the driver confirms it applied; DLSS labels bound to evidence; FSR's mode through `ffxQuery` as a
separate PR that may slip; owner-only items 7–11 and 13 not yet run; Dependabot #314 rebased and merged in the train.
*Status is `docs/changelog/0.1.0-beta.37.md`; this is what no other file carries.* The owner, with two screenshots — a
Qodana Ultimate licence in the JetBrains console, and the Qodana Cloud project's setup page: "Bạn có thể bắt đầu với phiên
cải tiến cho .net 11 và set up cho qodana cho tất cả ngôn ngữ (gói ultimate) nhé." The session D92 had left for after
.NET 11's release (2026-11-10), and Qodana for every language on the Ultimate licence. One plan, approved whole, in
three parts: **beta.37** (#376 the move, #379 what an alpha is, #380 .NET 11's API and the C# 15 finding, and this
release) → **alpha.4** → **Qodana Ultimate in two reports**. This section is the first part; the other two follow it on
`main` the same way.
**Decisions:**
**Decisions (asked while planning, do not re-ask):**
- **D62 — the mix.** Every frame-generation state a session held, each with its own factor, Native → Displayed and its
share of the presenting time, then *no frame generation* (only where a counted `none` is allowed) and *not
classified*; never an average across states (CLAUDE.md rule 6, amended). Computed at finalize over the steady state's
own five-second windows and stored (`sessions.fg_mix`, schema 0020); sessions recorded before have none and are not
rebuilt. Above the rows, how frame generation was set — the NVIDIA App's Dynamic / Fixed from the stored driver
profile, or the game — as configuration, never as a row. The multiplier chosen in a game's menu is not read (§2b's
refusal stands); the measured row is its evidence.
- **D63 — the NVIDIA App's override is the quality mode where the driver reports it applied** (`03_METRICS`
§Upscaling, amended; `QualityResolver`, read at display time, so sessions recorded before resolve alike). Otherwise
the mode the game passed to a hooked call; otherwise none; never the game's own value under an override.
- **D64 — DLSS labels are evidence-bound** (`05_DETECTION` §DLSS generation): each library's version and folder class
(`sessions.runtime_module_sources`, schema 0021 — never the path), the preset the driver reports applied, DLSS 4 /
4.5 only from a preset or a measured multi-frame factor, DLSS 5 only as "runtime loaded".
- **D65 — FSR's quality mode through `ffxQuery`: deferred to the next beta.** The plan allowed it to slip, and it was
kept out of this train — a new hook on four FidelityFX modules, a hook-family bit in the shared layout, a new byte
encoding, the stubs and the harness, on the hook path rule 5 guards — rather than written against the release.
ACCURACY's FSR clause did not ship with it. The design stands in the plan: query → the five (mode, size) pairs → the
mode whose size the game then dispatched. The owner asked for it as 0.1.0-beta.25 the same day.
- **D66 — the long documents are split**, every original path kept as the index of its parts, moved byte for byte
(`tools/docs-split-check.ps1`; `release-notes.ps1` reads `docs/changelog/<version>.md`).
- **D67 — SonarCloud stays on Automatic Analysis** with `.sonarcloud.properties`; the by-design rules and false
positives are listed in `13_CI_CD` §SonarCloud for the owner to mark in its UI.
- **D94 — the main line moves to .NET 11 now.** Asked whether the betas move or only alpha.4 — with
`20_OPEN_QUESTIONS` §G's table quoted: two alphas on the released runtime and an owner's run of a hooked title first —
the owner chose "Chuyển main sang .NET 11 ngay". Condition (a) of that table was **set aside, not met**;
`12_BUILD` §The main line's .NET says what stood in for it, and owner-only item 34 is the run it asked for.
- **D95 — Windows 10 22H2 is not blocked, and is stated as untested and unsupported** ("Vẫn chạy, ghi rõ không được hỗ
trợ"). NFR-8 is amended; a processor needs SSE4.2 and POPCNT.
- **D96 — C# 15 in the same release** ("Áp dụng cả C# 15 ngay trong beta.37"). The plan narrowed it in writing, and was
approved with that: a construct only where the build, CodeQL and Qodana all read it.
- **D97 — all three legal texts reworded** ("Sửa cả ba văn bản"): EULA 1.7, Disclaimer 2.14, Alpha notice 1.1. Their
text was in the plan and approved with it.
- **D98 — alpha.4, then the alpha line rests** until a newer .NET has a preview ("alpha.4 rồi nghỉ tới .NET 12
Preview").
- **The order**: beta.37 → alpha.4 first, Qodana after; and Qodana in **two reports from the start** (the third part's
decision, D99).
**Measured on the owner's ledger** (a read-only SQLite backup copy — never the data folder): **the NVIDIA driver's
`performanceMode` is in NGX's own numbering, not the profile's** — Silent Hill 2 (2026-10-13) ran under the App's Ultra
Performance (profile value 5) and the driver reported 3; `NvidiaOverrides.DriverLine` had read it through the profile's
table since beta.8 and dropped the mode. The same session's SR word has no `CREATED | EVALUATE` (no mode is claimed),
its FG word applied ×6 and the session measured a ×6.0 steady state, and **none of the override's libraries carried a
census name** — the module snapshot now records everything under `%ProgramData%\NVIDIA\NGX`. Bit 19 is set on a working
override (Expedition 33's `0x8067F`) and bit 1 with no override at all (`0x60F`): only `PERF_MODE`, `SR_DLAA_MODE` and
`SCALING_RATIO` say an override applied. The App's global profile stores `NGX_DLSSG_DYNAMIC_MULTI_FRAME_COUNT_MAX = 5`.
**Choices made here:**
- **No C# 15 construct is used, although the owner asked for them.** The rule decided it, not a preference:
ReSharper's engine, which Qodana runs, reads none of the four (`13_CI_CD` §C# 15 and the analyses, `spike-notes`
§29). Unions would not have been the form in any case — the SDK's own CA1815 asks every union to hand-write its
equality, and the shapes that wanted one are closed record hierarchies. What the release takes is API.
- **.NET 11's `IHost.RunAsync` is accepted, not wrapped**: a failed background service now ends the Agent through its
crash report. A catch there would hide a fault, and could not reproduce .NET 10's exit exactly either.
- **A resting alpha says so in the build, not only in its notes**: the anti-cheat list reaches a user only inside a
release, so an alpha nobody updates carries an ageing one. `FlAlphaLineRests` is stamped on both lines; the `alpha`
branch sets it to false when it next tries a .NET.
- **"A prerelease .NET" is said only by a build that runs on one**, read from the runtime's own description — the next
preview alpha says it again with no change to the code.
- **`release.yml` names the .NET 10 runtime `vpk` needs**, rather than relying on the hosted image carrying one.
- **The Community Qodana job was kept alive across the move** by installing the SDK into its container — an interim;
the Ultimate linter replaces the job in the third part.
- **The 2026-10-31 forms stay where they read as well** (`json.AsSpan().TrimStart().StartsWith('[')` avoids a string):
.NET 11's `char` overloads replaced a span only where the span was there for .NET 10's sake.
**Measured on the way** (`spike-notes` §28 and §29): the gate on SDK 11.0.100 — two analyzer sites beyond RC3's
twenty-one, both in tests written after the last alpha; `IHost.RunAsync` rethrowing, observed for the first time; the
first delta across two runtime majors (372 of 443 files patched, 72.6 MB on the rehearsal); `main`'s first full CodeQL
C# analysis on `net11.0` (1,221 of 1,221 files, the same 23 unresolved `Windows.Win32` types as on .NET 10); the
SonarScanner 12.0.0 on the 11.0 runtime; InspectCode 2026.2.3.1 and 2026.3.0 against each C# 15 construct.
**Traps met on the way:**
- **`gh pr merge --squash --delete-branch` on a stacked PR closes the PR based on it** (#319), and a closed PR cannot be
reopened once its head was force-pushed. Recovery: push the base back, push the head back to the SHA it closed at,
reopen, retarget to `main`, push the rebased head, delete the base. Instead: retarget the next PR to `main` first,
merge without `--delete-branch`, rebase the rest (`git rebase --update-refs --onto origin/main <old tip>`, in a
temporary `git worktree` when the checkout is busy), then delete the merged branch.
- **Dependabot closed #314 itself** after `@dependabot rebase` ("updatable in another way") and did not answer
`@dependabot reopen`; the two analyzer versions it proposed went into the release PR by hand.
- **SonarCloud's PR gate fails on new `cpp:S8417`** (explicit memory orders, by design): not a required check; the
optional ignore row in `13_CI_CD` §SonarCloud stops it.
- **A Domain.Metrics enum must be listed in `MetricEnumMirrorTests`** (mirrored or explicitly local), **every enum needs
a zero member** (CA1008), **private consts in tests take the `_` prefix** (IDE1006 is `dotnet format`'s, not the
build's), and **`null` literals make overloads ambiguous** across a `string?` and a record parameter.
- **Python strings in the scratch scripts read `\N` as an escape** — a Windows path in a C# comment written through a
Python script needs its backslashes doubled, and a Bash heredoc halves them (the beta.23 trap again).
- **A pull request's CodeQL C# run is an overlay analysis**: it extracts the changed files on top of `main`'s cached
database, and its "scanned N out of N" is `main`'s baseline. #376 wrote "CodeQL reads `net11.0` whole" from one and
was corrected, dated, two pull requests later with `main`'s own run. For anything the extractor has not met, dispatch
`codeql.yml` on the branch (it takes `workflow_dispatch` since #380).
- **`ShmDrainIntegrationTests.TheGuardInjectsTheOverlayAndTheReaderDrainsRealFrames` failed once on the dev box** —
"our own harness must not start matching the blocklist mid-run": the guard's re-scan refused the harness in one gate
run of five. The class passed three times in a row straight after and no guard code had changed; not looked into.
- **A wiki page names no version** (`wiki-check`): "since 0.1.0-alpha.4" in `wiki/Releasing.md` was red. The guide's
pages may.
- **The runner queue**: with three workflows per pull request and a probe's pull request open beside the train,
`check` waited about 25 minutes for a runner. Cancel a probe's runs once it has told what it can.
- **A Bash heredoc halves the backslashes** of an inline Python regex — write the script with the Write tool.
- **`x.Should().NotBeNull(); x!.Member`**: ReSharper reads the `!` as redundant (Qodana's one finding on #376) and the
compiler wants it. Keep the value the assertion needs, not the object.
- **CA2025** on a lambda that captures a `using` variable in a test: await inside a `try`, assert after.
- **A local gate reseeds `%LOCALAPPDATA%\FrameLedger\rules`** while the owner's installed copy runs beside it: the
files were hashed before and after every gate (identical each time — the repository's rules were the installed ones).
**Owner-only, added to the list below:** item 20.
**Owner-only:** item 34 — beta.37 on real hardware, a hooked session on .NET 11.0.0, and Windows 10 if a PC with it is
at hand.
### 0.1.0-alpha.4 — the fourth alpha, the same day, and the last for now (D98)
`alpha` takes main at this pull request — `v0.1.0-beta.37` and these notes, no other change — by a merge commit. **This
sync is not like the three before it**: main now holds what the switch held (`global.json`, the TFM, the three
packages, `legal/licenses/nuget/`, the *Transitive* row), so every switch file conflicts, and each is resolved by
taking main's — the branch's RC3 lines go, `RELEASE_LINE` stays `alpha`, and `git diff --name-only origin/main` on the
merged tree must print that one name. Its gate must pass on `alpha` before the pull request is merged by hand (the
branch has no auto-merge); the release runs from the signed tag `v0.1.0-alpha.4` on `alpha`, with its delta from
alpha.3. Its notes are `docs/changelog/0.1.0-alpha.4.md`: the warning, and that it is the last alpha for now.
- **After it the line rests** (`12_BUILD` §The alpha line): no sync follows a beta and no alpha is cut until a newer
.NET has a preview. `FlAlphaLineRests` in `Directory.Build.props` says so to the build; the next trial sets it to
`false` on `alpha` with the rest of the switch.
- **What a resting alpha costs its user** is in its notes, the guide and its banner: no update, the anti-cheat list
included; and once ten betas have followed it, a copy of alpha.3 or older no longer finds alpha.4 (Velopack reads
the newest ten releases).
**Owner-only:** item 35 — the fourth alpha on real hardware, and the beta installed over it.
## Owner-only — no PR can close these
@@ -240,10 +280,176 @@ override (Expedition 33's `0x8067F`) and bit 1 with no override at all (`0x60F`)
setting*, the game's own library and no generation beyond what was observed. Record the names the override loads
under `%ProgramData%\NVIDIA\NGX` (the summary's *Loaded:* line) — they correct `05_DETECTION` §Shipped is not loaded.
(d) **DLSS 5** on the owner's DLSS 5 title: *DLSS 5 runtime loaded*. If it is not shown, record the module names it
loads (*Loaded:* line); `nvngx_dlssnr.dll` is then corrected in `CensusNames` and `05_DETECTION`.
loads (*Loaded:* line); `nvngx_dlssnr.dll` is then corrected in `CensusNames` and `05_DETECTION`. *(2026-11-06, `spike-notes` §26:
Hogwarts Legacy, Neural Rendering on, loaded `nvngx_dlssnr.dll` 310.9.16.0 from the game's folder — the name holds;
whether it ran is what beta.34 measures, item 30(a).)*
(e) **SonarCloud (D67):** bulk-mark per `13_CI_CD` §SonarCloud; optionally its *Ignore issues on multiple criteria*
rows; close PR #315. (f) The Legal Gate shows **Disclaimer 2.11** and **Privacy Policy 2.12** once. (g) The `ja`
strings marked `review`.
strings marked `review`. *(2026-10-19, the owner's first runs — `spike-notes` §22: (a) the Dynamic context line
reads the App's own words, and the mix found ×2.0 / ×3.0 / ×6.1 — plus a ×1336.0 row that was a defect, fixed in
beta.26; (c) the override loads `160_E658700.bin` 310.9.16.0 and `1B0_E658703.dll` 2.14.16.0 from the NGX folder;
(e) **done** — every issue marked; the last six, triaged in `13_CI_CD` §SonarCloud (beta.26), the same day, and
`main`'s quality gate passes. The rest is not run yet.)* *(2026-10-20, the owner's runs of beta.26 — `spike-notes`
§23: (a) **done** — ×2, ×3 and ×4 chosen in Cyberpunk 2077's menu read ×1.9 (ten seconds), ×3.0 and ×4.0, each with
its own rates, under "Set in the game — no NVIDIA App frame-generation override"; **Fixed ×6** on Expedition 33 read
×6.0 under "Set in the NVIDIA App: Fixed ×6"; *Dynamic* on Silent Hill 2 read ×2.0 and ×3.0, plus a ×2.52 row that
was a defect, fixed in beta.27. The Witcher 3 under **Fixed ×6** presented ×2.0 throughout: the rows are the frames,
the line is the setting. (b) **could not pass before beta.27**: every stored driver word had lost
`CREATED | EVALUATE`, read after the game had closed, so an NGX-direct title under the override never read its mode
— run it on beta.27. (c) The Witcher 3 under the override loaded `160_E658700.bin` 310.9.16.0 and `1B0_E658700.dll` 2.14.16.0;
Silent Hill 2 and Expedition 33 loaded `1B0_E658703.dll`.)*
21. **beta.25 on real hardware — FSR's quality mode (D65), decision table written before the run.** Lies of P (FSR
through AMD's FidelityFX libraries) launched by FrameLedger, not attached, with the game's own *FSR* at *Quality*,
then a second session at *Performance* → the summary's header reads *FSR 3 Quality*, then *FSR 3 Performance* (or
*FSR Quality* where the SDK 2.x libraries name no version), and the CSV export's `# quality_mode:` says
`quality (game)`. Then: **no mode on both** → the title sizes its frames without asking, or asked before the hook
was in: record the session's render → output resolution and the *Loaded:* line in `spike-notes`, and D65 stays built
and silent for that title. **A wrong mode** (the Quality session reading Balanced) → the answers this title receives
are not the vendor's documented ratios: record the stored `upscaler_quality` and the render size in `spike-notes`,
and the match is withdrawn until it is explained. **With the game's dynamic resolution on** (if it offers one) → no
mode. *(2026-10-19, `spike-notes` §22: the Quality session read **no mode** with the query hooked — the first
branch; 1707×961 is the engine's own rounding of 66.67 %, not the size answer, so the title asked before the hook
was in or never asked. D65 stays built and silent for Lies of P. The Performance session is not run.)*
*(2026-10-20, §23: the Performance session, started through Steam, read "FSR 3 · 1280×720 → 2560×1440" and no mode —
the first branch on both. 1280×720 is exactly the vendor's Performance size, so a query the hook met would have
matched: the title did not ask while the hook was in. It cannot be launched by FrameLedger as this item asks — started
directly it hands itself to Steam within seconds, and before beta.27 the game Steam started was not recorded at
all.)*
22. **beta.27 on real hardware.** (a) **The driver's report, and item 20(b):** Expedition 33 under the NVIDIA App's
DLSS override → the header reads *DLSS (driver-reported)* with the override's mode and *· NVIDIA App* (*Balanced*
as set on 2026-10-20); then 20(b)'s four modes. Still *Upscaler not identified* → record the session's stored
`ngx_driver_words`: no reading while the game ran said the feature was created and evaluated. (b) **Start directly
on Lies of P:** the notice says a Steam game may hand itself to Steam first, and the game Steam starts is recorded —
`agent-*.log` says *started while the last session of its executable was ending; recording it now*. The crash safety
counts the hand-off: after two such starts hooking is off again (`19_SAFETY`). (c) **One window per session:** open a session from a Sessions tab, then again from the game
page or its notification → the same window comes forward, restored if minimised. (d) **A game in exclusive
full-screen** (Dark Souls III, Lies of P) → its summary's Display card shows the window size.
23. **beta.28 on real hardware.** Two games at once — one hooked, one with hooking off (or refused) → the Dashboard
shows two cards side by side, the hooked one first, and *2 games recording* beside *Live capture*; each card's
numbers are its own game's; closing one leaves the other's card where it is, and the count goes. A third game → a
third card on the next row and *3 games recording*. (The `ja` string `Dashboard_Live_Count_Format` is marked
`review`.)
24. **beta.29 — SonarCloud from CI (D68), the owner's settings.** None blocks anything. (a) *Optional:* add
`SONAR_TOKEN` to the repository's **Dependabot secrets** (Settings ▸ Secrets and variables ▸ Dependabot) if
Dependabot's pull requests should be analysed too; until then `ci.yml`'s `sonarcloud` job is skipped for them, as it
is for a fork's. (b) *Optional:* SonarCloud's branch list holds `beta29/pr1-sonarcloud-ci`, left by a dispatch of
that branch the plan then refused (`13_CI_CD` §SonarCloud, *The first analyses*); delete it under *Branches*, or let
SonarCloud remove it after 30 days without an analysis. (c) *Optional:* `analyze (actions, none)` (CodeQL over the
workflows) and `sonarcloud` are not required checks; making either one required is the owner's setting. (d) Velopack
1.2.161 and Markdig 1.5.0 were not taken by #335 (`docs/changelog/0.1.0-beta.29.md`, *The libraries Dependabot
never updated*): the first changes how updates install and wants a run of the update path on the owner's machine,
the second its licence copy re-read. *(2026-10-26, beta.30: Velopack 1.2.161 taken — the owner's decision D71, its
update path is item 25(c); Markdig went to 1.4.2, its licence text re-read and unchanged; 1.5.0 waits for the
cooldown.)*
25. **beta.30 on real hardware.** (a) **Enter in the consent dialog** (D69): on a game whose hooking is off, turn the
switch on, type the phrase exactly and press Enter → hooking is on, and the switch and its text agree; Enter before
the phrase is complete → nothing happens; Esc → the switch is back off beside *off*, and leaving the page and coming
back shows the same. (b) **The numbered markers** (D70): the game whose GPU driver changed on 2026-10-24 — *Sessions at
a glance* and the *Trend* show a badge *1* above the chart, whole, in both themes; the list under each chart names
that day and *Driver GPU: 32.0.16.1742 → 32.0.16.2101*; pointing at the dashed line shows the same; a narrow window
keeps every badge whole. (c) **The updater** (D71): Help ▸ Check for updates on beta.29 installs beta.30 (beta.29's
updater, a delta); the update to beta.31, when it comes, is the first Velopack 1.2.161 installs — say whether it
downloaded the delta or the full package, and whether it came back. (d) The `ja` strings marked `review`
(`Trend_Changes_Header`, `Trend_Change_Heading_Format`).
26. **beta.32 on real hardware.** (a) **The update from beta.31**: Help ▸ Check for updates, *Restart to update* — the
terms window shows the EULA 1.6 and the Disclaimer 2.12 once, with no tick box, and nothing else of the alpha appears:
no ALPHA badge, no banner, the title *FrameLedger*, Settings ▸ Updates ▸ Channel as before. (b) About ▸ Legal documents
lists the Alpha notice, and its version line reads *Runs on .NET 10.0.x*; Help ▸ User guide has *Alpha builds*.
(c) Whether the update downloaded the delta or the whole package. (d) The `ja` strings marked `review`: `About_Runtime_*`
here; `Alpha_*`, `FirstRun_Alpha_*`, `FirstRun_Doc_Alpha`, `App_Title_Alpha` and `Settings_UpdateChannel_AlphaBody`
show only in an alpha.
27. **0.1.0-alpha.1 on real hardware** (D73, D74). (a) **Installing it over beta.32**: `FrameLedger.App-alpha-Setup.exe` from
its release page — Velopack asks whether to replace the installed FrameLedger; the terms window shows the Alpha notice
with its warning box, and Accept stays off until the box is ticked; *Decline* closes the App. (b) **While it runs**: the
ALPHA badge (its tooltip names .NET 11.0.0-rc.3), the title *FrameLedger Alpha*, the banner at start (closable; its
button opens the notice); About reads *Alpha build — runs on .NET 11.0.0-rc.3…*; Settings ▸ Updates ▸ Channel is locked
with its line. (c) `%LOCALAPPDATA%\FrameLedger\backups\ledger-before-0.1.0-alpha.1.db` exists and opens. (d) One
hooked (Tier-1) session of a game measured before records as on the beta; the Agent's log names the release line and
.NET 11. (e) **Going back**: the beta's `FrameLedger.App-win-Setup.exe` over it — the beta shows the alpha's session.
(f) The `ja` strings marked `review` that only an alpha shows (`Alpha_*`, `FirstRun_Alpha_*`, `FirstRun_Doc_Alpha`,
`App_Title_Alpha`, `About_Runtime_Alpha_Format`, `Settings_UpdateChannel_AlphaBody`).
28. **beta.33 on real hardware: the Xbox titles** (D77–D81). (a) **The update from beta.32** (or alpha.2's, item 29): the
terms window shows the Privacy Policy 2.13 once. (b) **Import library** offers the eleven Xbox titles as *Xbox* — the
Unreal titles with their shipping executables (`…-WinGDK-Shipping.exe`, `ValorMortisMSG-Win64-Shipping.exe`), the Unity
titles with their players, never `gamelaunchhelper.exe` — each with its package version (*Xbox version 1.3.5124.0*).
(c) Each game's page shows its square logo whole in a square slot and its splash image as the banner, captioned
*Xbox*. (d) **Play** starts Valor Mortis and FINAL FANTASY through Windows in both Play modes, and from an App run as
administrator — the notice says Windows is starting it. (e) With consent given, one hooked session of each: Tier 1,
frames, *late attach*, the engine and platform on the game page. (f) The `ja` strings marked `review`: `Store_Xbox_Format`,
`Art_Source_Xbox`, `Import_NothingFound`, `FirstRun_Import_Body`, `Settings_GameArt_Body`, `Play_Xbox_Format`,
`Play_Xbox_NotStarted_Format`, `Play_PackagedGame_Format`, `Play_ToolTip_Store`, `Play_ToolTip_Direct`,
`Settings_PlayMode_Body`, `Guard_TargetAppContainer`, `Guard_TargetMitigation`. Then
`docs/LIST_GAME_TESTED.md` gains the Xbox titles from a ledger copy (D35), approved before the commit. *(2026-11-06,
beta.34: done — inKONBINI and Valor Mortis, with the refresh the owner approved with the plan.)*
29. **0.1.0-alpha.2 on real hardware** (D73, D82). (a) **The update from alpha.1**: Help ▸ Check for updates offers
alpha.2 — the first update an alpha's updater has found — and *Restart to update* installs it; say whether it
downloaded the delta or the whole package. (b) The terms window shows the Privacy Policy 2.13 and the Alpha notice
with its box again, and Accept waits for the tick. (c)
`%LOCALAPPDATA%\FrameLedger\backups\ledger-before-0.1.0-alpha.2.db` exists beside alpha.1's, and opens. (d) Item 28's
Xbox checks, on the alpha.
30. **beta.34 on real hardware** (D83–D86). (a) **The update from beta.33** (or alpha.3's, item 31): the terms window
shows the Disclaimer 2.13 and the Privacy Policy 2.14 once. (b) **Hogwarts Legacy with Neural Rendering on**, one
hooked session → *DLSS 5 (neural rendering on N % of rendered frames)*; then **off** — `spike-notes` §26's table,
written before the run, decides (on and 0 %: neural rendering runs outside `slEvaluateFeature`, the line stays
*runtime loaded, not seen running*, and the session's `sl_tag_census` is recorded before anything is named).
(c) **Phantom Blade Zero** under the NVIDIA App's *Dynamic, up to ×3* → *DLSS 4.5 (Dynamic multi frame generation, set
in the NVIDIA App)*; the game's own ×3 with no override from the App → *DLSS 4*. (d) **Games** from any page: the
cards at once, a second visit at once; the Debug line `ui: page … shown … ms after its navigation`. (e) **Settings →
change the language** → the window comes back on Settings. (f) The filters on Games and Compare, the Compare columns
and selection bar, the selected page's label in the pane, in both themes. (g) The 34 `ja` strings this release adds,
all marked `review`: `Dlss_Basis_Dynamic`, `Dlss_NeuralRendering_NotSeen`, `Dlss_Feature_NeuralRendering`,
`Dlss_Basis_NeuralRendering_Format`, `Games_Filter_*`, `Games_Header_Filtered_Format`, `Filter_Clear`,
`Compare_Filter_*`, `Compare_Count_Format`, `Compare_Count_Filtered_Format`, `Compare_ClearSelection`,
`Compare_MidSession_Changed`, `A11y_Games_Filter_*`, `A11y_Compare_Filter_*`.
31. **0.1.0-alpha.3 on real hardware** (D73, D87). (a) **The update from alpha.2**: Help ▸ Check for updates offers
alpha.3 and *Restart to update* installs it; say whether it downloaded the delta or the whole package. (b) The terms
window shows the Disclaimer 2.13, the Privacy Policy 2.14 and the Alpha notice with its box again, and Accept waits for
the tick. (c) `%LOCALAPPDATA%\FrameLedger\backups\ledger-before-0.1.0-alpha.3.db` exists beside alpha.2's, and opens;
the ledger it left is at schema 22. (d) Item 30's checks, on the alpha.
32. **beta.35 on real hardware** (D88–D91). (a) **The update from beta.34** (or alpha.3's): no terms window, the ledger
unchanged. (b) **Narrator**: a safety notice is read as it appears; the agent's banner going and coming; Tools ▸
Database maintenance ▸ Check reads its result; a short message at the bottom is read; **H** moves between each page's
title and its sections; Settings ▸ Theme's options read their words; the Sessions table's cells read their values;
Tab to a chart says its name and where its numbers are, and its arrows, Ctrl+arrows and A move it without scrolling
the page; a double-click shows all of it. (c) **Contrast themes**: Aquatic and Desert, and one with an edited colour
(Windows 10 if at hand) — every page, a dialog, the title bar's agent pill, a short message, a chart; turned on and
off with FrameLedger open, it follows at once; Settings ▸ Theme shows its line. (d) **Ctrl+1 … Ctrl+5** put the
keyboard in the page and Narrator says its title. (e) **Animation effects off** (Settings ▸ Accessibility ▸ Visual
effects): no page slides in. (f) **Remove** on a game's page: the box opens over the window, its Cancel puts the focus
back on Remove; the light theme's agent pill and a *done* message read clearly. (g) Help ▸ Accessibility shows the
statement. (h) The 35 `ja` strings this release adds, all marked `review`: `Menu_Help_Accessibility`,
`Accessibility_Title`, `Settings_Theme_ContrastOn` and 32 `A11y_*` (the names, the chart names and keys, the
announcements).
33. **Qodana, and beta.36 on real hardware** (D93). (a) **The update from beta.35**: no terms window, the ledger
unchanged. (b) **The re-pointed bindings, by hand** — the tests pin their text, not a click: on Games, a card opens
its game and both Play buttons (card and list) start it, greyed in a viewer; on the Dashboard a recent session
opens; on a game's page a session row's *Open* opens its summary; in a session's summary a Yes/No/N/A chip opens the
override dialog; a safety notice's button dismisses it; Settings lists the hooked games with *Revoke*, the
exception rows with *Grant*/*Withdraw*, and the system information lines. (c) **Qodana Cloud**: the trial's end
changes nothing in CI (the Community linter needs no licence; the token names the project the report goes to). If
an Ultimate licence is wanted — JetBrains has a programme for open-source projects — `13_CI_CD` §Qodana says what
moves. (d) **`qodana` as a required check, or not**: advisory today, like `sonarcloud`. (e) **The members nothing
uses** (`13_CI_CD` §Qodana, 34 and 49 getters): say which are dead, and a pull request removes them.
34. **beta.37 on real hardware — the first build on .NET 11's release** (D94–D98). (a) **The update from beta.36**:
Help ▸ Check for updates offers beta.37 and *Restart to update* installs it — a download of about 70 MB, not a few;
the terms window shows the **EULA 1.7 and the Disclaimer 2.14** once and nothing else; the ledger stays at schema 22.
(b) **A hooked session on .NET 11.0.0**: one title you measure often, Tier 1 — frame times, the upscaler and frame
generation as before; the Agent's log opens with `release line main, .NET 11.0.0`, and Help ▸ About reads *Runs on
.NET 11.0.0*. This is the run `20_OPEN_QUESTIONS` §G's table asked for before the move and did not get (D94).
(c) **The Agent in admin mode and the logon task** still start it — the publish is self-contained on a new runtime.
(d) **Windows 10 22H2, if a PC or a VM with it is at hand**: does it install and start? No version has ever been run
there; D95 states it as untested, and one run would be the first evidence either way. (e) **The Japanese** of the
three alpha strings that changed or are new (`Alpha_Banner_Body_Format`, `Alpha_Banner_Body_Resting_Format`,
`About_Runtime_Alpha_Format`) and of the first-run summary's first line. (f) **Going back** — only if something is
wrong: install beta.36 over it; the ledger opens.
35. **alpha.4 on real hardware — the last alpha for now** (D98). (a) **The update from alpha.3**: Help ▸ Check for
updates offers alpha.4 and *Restart to update* installs it — a large download, the runtime moving from the release
candidate to 11.0.0. (b) The terms window shows the **EULA 1.7, the Disclaimer 2.14 and the Alpha notice 1.1** and
waits for the notice's box; `…\backups\ledger-before-0.1.0-alpha.4.db` exists beside the older copies, and opens;
the ledger stays at schema 22. (c) **The banner says the alpha line is paused** and to install the beta — not the
experimental-build warning — and Help ▸ About reads *Alpha build — runs on .NET 11.0.0*, with no "prerelease".
(d) **Then install beta.37 over it**: the installer asks to replace it; the beta opens the ledger, shows no Alpha
notice, and its update channel is no longer locked.
**Answered 2026-08-05, do not re-ask:** remove `gameguard` and keep `guard` (approved
over a red `Rules` gate, with the reasoning recorded in the merge commit); vendor NVAPI
headers **and** `amd64/nvapi64.lib`; Windows 11 is the **measurement scope** only —
@@ -319,12 +525,43 @@ Where each owner decision is recorded — the file and its section, and a label
| D59 | [`handoff/history/0.1.0-beta.21.md`](handoff/history/0.1.0-beta.21.md) | Play, in two modes switched in Settings: "1: press Play → the platform opens → it runs;… |
| D60 | [`handoff/history/0.1.0-beta.23.md`](handoff/history/0.1.0-beta.23.md) | a game's artwork is what is already on the PC |
| D61 | [`handoff/history/0.1.0-beta.23.md`](handoff/history/0.1.0-beta.23.md) | the band takes the artwork's colour as far as every text on it reads: primary and secon… |
| D62 | this file, §START HERE | the mix: every frame-generation state a session held, with its share, never averaged |
| D63 | this file, §START HERE | the NVIDIA App's override is the quality mode where the driver reports it applied |
| D64 | this file, §START HERE | DLSS labels are evidence-bound: versions and folder class, DLSS 4/4.5 only when shown, 5 only loaded |
| D65 | this file, §START HERE | FSR's quality mode through ffxQuery — deferred to the next beta |
| D66 | this file, §START HERE | the long documents are split; every original path stays as the index of its parts |
| D67 | this file, §START HERE | SonarCloud stays on Automatic Analysis with .sonarcloud.properties; the owner marks in its UI |
| D62 | [`handoff/history/0.1.0-beta.24.md`](handoff/history/0.1.0-beta.24.md) | the mix: every frame-generation state a session held, with its share, never averaged |
| D63 | [`handoff/history/0.1.0-beta.24.md`](handoff/history/0.1.0-beta.24.md) | the NVIDIA App's override is the quality mode where the driver reports it applied |
| D64 | [`handoff/history/0.1.0-beta.24.md`](handoff/history/0.1.0-beta.24.md) | DLSS labels are evidence-bound: versions and folder class, DLSS 4/4.5 only when shown, 5 only loaded |
| D65 | [`handoff/history/0.1.0-beta.25.md`](handoff/history/0.1.0-beta.25.md) | FSR's quality mode through ffxQuery — deferred from beta.24, built in beta.25; none at a dynamic resolution |
| D66 | [`handoff/history/0.1.0-beta.24.md`](handoff/history/0.1.0-beta.24.md) | the long documents are split; every original path stays as the index of its parts |
| D67 | [`handoff/history/0.1.0-beta.24.md`](handoff/history/0.1.0-beta.24.md) | SonarCloud stays on Automatic Analysis with .sonarcloud.properties; the owner marks in its UI |
| D68 | [`13_CI_CD.md`](13_CI_CD.md) §SonarCloud | SonarCloud is analysed from CI (ci.yml's sonarcloud job, SonarQube.Analysis.xml), with coverage; replaces D67 |
| D69 | [`19_SAFETY_AND_ANTICHEAT.md`](19_SAFETY_AND_ANTICHEAT.md) §User-facing consent | Enter enables once the consent phrase is typed exactly; before it Enter does nothing |
| D70 | [`08_UI.md`](08_UI.md) §Games › Trend | the hardware-change markers are numbered badges, their changes listed under each chart, with a tooltip |
| D71 | [`13_CI_CD.md`](13_CI_CD.md) §Dependabot and the NuGet audit | Velopack and vpk 1.2.161 in beta.30 (item 24(d)'s Velopack half) |
| D72 | [`13_CI_CD.md`](13_CI_CD.md) §Dependabot and the NuGet audit | beta.31 takes the remaining updates inside the seven-day cooldown: .NET 10.0.14 packages, Markdig 1.5.0, CsWin32, Meziantou, coverlet 10.1.0, Catch2 3.16.1 |
| D73 | [`12_BUILD.md`](12_BUILD.md) §The alpha line | the alpha line: a released beta's source on a prerelease .NET (.NET 11 RC3 first), on the `alpha` branch and Velopack's `alpha` channel; it replaces the beta, shares its data folder and copies the ledger before it first opens it |
| D74 | [`08_UI.md`](08_UI.md) §First-run flow | the alpha's warning: the Alpha notice with its own tick box in the Legal Gate, the alpha's Agent waiting for it, an ALPHA badge and a banner, the update channel locked |
| D75 | [`../legal/EULA.md`](../legal/EULA.md) §2B | EULA 1.6 and Disclaimer 2.12 name alphas beside betas; the Alpha notice 1.0 approved with the plan |
| D76 | [`12_BUILD.md`](12_BUILD.md) §The alpha line | alpha.1 is a retarget only: `net11.0`, C# 15 by `LangVersion latest`, three runtime-serviced packages; no preview feature, no C# 15 syntax |
| D77 | [`spike-notes/25-xbox-gdk.md`](spike-notes/25-xbox-gdk.md) | the Xbox titles measured first, by package activation, read-only, each closed by its window; the decision table before the run |
| D78 | [`19_SAFETY_AND_ANTICHEAT.md`](19_SAFETY_AND_ANTICHEAT.md) §The target must be able to take the Overlay | GDK games only; an app-container (UWP) process is refused as `TargetAppContainer`, Tier 2 |
| D79 | [`05_DETECTION.md`](05_DETECTION.md) §Platform signatures & metadata | the platform is "Xbox" (`xbox`), in full: import, artwork, Play, capture, detection, docs and legal |
| D80 | [`08_UI.md`](08_UI.md) §Games | Play on an Xbox game always activates its package, in both modes; the Agent answers `PackagedGame` and records it in attach mode |
| D81 | [`20_OPEN_QUESTIONS.md`](20_OPEN_QUESTIONS.md) §G | title lists stay keyed by Steam id; an Xbox copy is matched by everything but that entry |
| D82 | [`handoff/history/0.1.0-beta.33.md`](handoff/history/0.1.0-beta.33.md) | alpha.2 right after beta.33; on RC3 unless the train reaches it after .NET 11 ships (then SDK 11.0.100, packages 11.0.0) |
| D83 | [`05_DETECTION.md`](05_DETECTION.md) §DLSS generation | the NVIDIA App's Dynamic frame generation, reported applied by the driver in a session where DLSS Frame Generation was identified, is DLSS 4.5 (amends D64) |
| D84 | [`05_DETECTION.md`](05_DETECTION.md) §DLSS generation | DLSS 5 heads the DLSS line where its neural rendering was measured running (`kFeatureDLSS_NR`, `dlss_nr_pct`); loaded only reads "runtime loaded" (amends D64) |
| D85 | [`08_UI.md`](08_UI.md) §Games, §Compare | filters: Games — store, engine, state, installed, played; Compare — game, tier, frame generation (no period); Compare lists every session |
| D86 | [`08_UI.md`](08_UI.md) (the shell) | the left pane's selected item keeps its label: our copy of WPF UI 4.3.0's LeftFluent item template |
| D87 | [`handoff/history/0.1.0-beta.34.md`](handoff/history/0.1.0-beta.34.md) | alpha.3 right after beta.34, on RC3 (before .NET 11's release, 2026-11-10) |
| D88 | [`../ACCESSIBILITY.md`](../ACCESSIBILITY.md) | the accessibility statement at the root, under Help ▸ Accessibility and on the wiki: WCAG 2.2 AA through WCAG2ICT is a goal, never a claim; reports by severity, no promised times |
| D89 | [`08_UI.md`](08_UI.md) §Screen readers | what appears is said to a screen reader — notices, the agent's and the update's banners, the snackbars, a game page's notice, Database maintenance's results — while FrameLedger's window is active |
| D90 | [`08_UI.md`](08_UI.md) §Screen readers | page titles heading 1, section titles heading 2; every chart named with where its numbers are; no series told apart by colour alone |
| D91 | [`08_UI.md`](08_UI.md) §Contrast | Windows contrast themes are followed, whatever Settings ▸ Theme says |
| D92 | [`handoff/history/0.1.0-beta.35.md`](handoff/history/0.1.0-beta.35.md) | beta.35 in this train, no alpha; alpha.4 is the move to .NET 11's release (SDK 11.0.100, packages 11.0.0), a task of its own after 2026-11-10 |
| D93 | [`13_CI_CD.md`](13_CI_CD.md) §Qodana | Qodana Community for .NET from a workflow of its own (the organisation's licence is a 30-day trial, so not the Rider linter): a gate of zero problems, advisory; an inspection is switched off only in `.editorconfig`, with its reason |
| D94 | [`12_BUILD.md`](12_BUILD.md) §The main line's .NET | the main line moves to .NET 11 with 0.1.0-beta.37, the day after it shipped; condition (a) of `20_OPEN_QUESTIONS` §G's table — two alphas on the released runtime — set aside by the owner, not met |
| D95 | [`02_SPEC.md`](02_SPEC.md) NFR-8 | Windows 10 22H2 is not blocked, and is stated as untested and unsupported (Microsoft supports .NET 11 on Windows 11); a processor needs SSE4.2 and POPCNT |
| D96 | [`13_CI_CD.md`](13_CI_CD.md) §C# 15 and the analyses | C# 15 on the main line from beta.37, a construct only where the build, CodeQL and Qodana read it — none of the four yet (Qodana's engine reads none, 2026-11-11), so beta.37 takes .NET 11's API and no syntax; no preview feature |
| D97 | [`../legal/ALPHA_NOTICE.md`](../legal/ALPHA_NOTICE.md) | an alpha is "a beta's source built to try a newer version of .NET, at times a prerelease one": EULA 1.7, Disclaimer 2.14 (with a paragraph on Windows and the processor), Alpha notice 1.1, approved with the plan; the App says "a prerelease .NET" only where the runtime is one |
| D98 | [`12_BUILD.md`](12_BUILD.md) §The alpha line | alpha.4 is beta.37's source on .NET 11.0.0, and then the alpha line rests until a newer .NET has a preview; a resting alpha tells its user to install the beta |
---
+46 -16
View File
@@ -1,43 +1,47 @@
# Games FrameLedger has been run with
*As of 2026-09-27 (0.1.0-beta.10). Built from a copy of the developer's own FrameLedger database and the repository's
*As of 2026-11-06 (0.1.0-beta.34). Built from a copy of the developer's own FrameLedger database and the repository's
measurement notes, and reviewed by the project's owner before it was published. It lists what happened on one machine;
it promises nothing about any other.*
*(Not re-read for 0.1.0-beta.11 or 0.1.0-beta.12 — noted 2026-10-04. Refreshing it needs a new copy of the database and
the owner's review; sessions since 2026-09-27, and the game-memory figures beta.12 adds, are not here.)*
*~~(Not re-read for 0.1.0-beta.11 or 0.1.0-beta.12 — noted 2026-10-04. Refreshing it needs a new copy of the database and
the owner's review; sessions since 2026-09-27, and the game-memory figures beta.12 adds, are not here.)~~ Refreshed
2026-11-06 from a copy of the database taken that day, and reviewed by the owner with the plan of 0.1.0-beta.34: the
sessions since 2026-09-27 are below, with the graphics memory a game used where it adds something.*
**The machine.** Every row below was run on one PC: an NVIDIA GeForce RTX 5080 (the only graphics card), an Intel Core
i7-14700KF, 32 GB of DDR5, Windows 11 (Insider builds 26300 → 29648) and a 2560×1440, 240 Hz monitor. **No AMD or Intel
i7-14700KF, 32 GB of DDR5, Windows 11 (Insider builds 26300 → 29648) and a 2560×1440, 240 Hz monitor; the graphics
driver went from 32.0.16.1714 to 32.0.16.2114 over the sessions in the database. **No AMD or Intel
graphics card and no second machine has been tested**, and ~~**no real Vulkan or OpenGL game has been measured** — every
measurement below is Direct3D 11 or 12~~ **one real Vulkan game has been measured (Everhex Demo, 2026-10-13) and no
OpenGL game** — every other measurement below is Direct3D 11 or 12 *(corrected 2026-10-14)*. What the tiers mean and what FrameLedger cannot do: [LIMITATIONS.md](../LIMITATIONS.md).
**Two periods.** From 2026-08-03 to 2026-09-06 the games were measured with the developer's capture tool, one run at a
time against the game's own settings menu (reports in [spike-notes.md](spike-notes.md)). From 2026-09-16 the shipped
app and agent recorded them as a user would; the database holds the sessions from 2026-09-22 on — earlier ones went
with the 2026-09-16 recovery and with library entries removed since.
app and agent recorded them as a user would; ~~the database holds the sessions from 2026-09-22 on~~ the copy of
2026-11-06 holds the sessions from 2026-10-04 on — earlier ones went with the 2026-09-16 recovery and with library
entries and sessions removed since; a row citing the database before 2026-10-04 was read from the copy of 2026-09-27.
## Measured — hooked (Tier 1)
| Game | Engine | API | What was measured | When | Evidence |
|---|---|---|---|---|---|
| Cyberpunk 2077 | — | D3D12 | DLSS Balanced 1485×835 → 2560×1440, exact against its settings file; DLSS Frame Generation off ×1.00, ×3 (61.4 → 183.5 FPS), ×4 (58.7 → 234.1); FSR 3 + FSR frame generation ×2 (74.3 → 148.6); ray tracing *Yes* with path tracing on and *No* with it off, as set | 2026-08-15 → 09-05, about 25 runs | [spike-notes §8, §9, §11](spike-notes.md) |
| Cyberpunk 2077 | — | D3D12 | DLSS Balanced 1485×835 → 2560×1440, exact against its settings file; DLSS Frame Generation off ×1.00, ×3 (61.4 → 183.5 FPS), ×4 (58.7 → 234.1); FSR 3 + FSR frame generation ×2 (74.3 → 148.6); ray tracing *Yes* with path tracing on and *No* with it off, as set; on 2026-10-20, ×2, ×3 and ×4 chosen in the game's menu within one session read as separate states, ×4.0 at 63.8 → 255.3 FPS, with ray tracing and Ray Reconstruction *Yes* | 2026-08-15 → 10-20, about 26 runs | [spike-notes §8, §9, §11, §23](spike-notes.md), database |
| Dying Light: The Beast | — | D3D12 | DLSS Frame Generation ×4: Native 70.5 → Displayed 282.1 FPS, counted through DXGI; FSR + FSR frame generation ×2 (70.5 → 140.9); ray tracing *Yes* | 2026-09-04 → 09-06 | [spike-notes §9](spike-notes.md), [03_METRICS §Frame Generation](03_METRICS.md) |
| Hell Is Us | Unreal Engine 5.5.4 | D3D12 | DLSS Frame Generation ×4 (76.5 → 306.2); DLSS shown as *driver-reported* (it bypasses Streamline); FSR + FSR frame generation ×2 (85.7 → 171.4); XeSS frame generation shown as Presented FPS only; ray tracing *No* | 2026-09-03 → 09-16 | [spike-notes §8, §9](spike-notes.md) |
| Black Myth: Wukong | Unreal Engine 5.0.0 | D3D12 | DLSS Frame Generation ×4 (55.4 → 221.5); ray tracing *Yes* (16.2 % of frames in the app's session); a session that changed state showed its steady state (×4.1) instead of an average | 2026-08-20 → 09-16 | [spike-notes §9, §14](spike-notes.md) |
| Clair Obscur: Expedition 33 | Unreal Engine 5.4.4 | D3D12 | DLSS + Frame Generation ×4 (54.9 → 218.4) and ×2 (76.0 → 149.8); frame generation off read *none*, with DXGI agreeing; ray tracing *No* | 2026-09-04 → 09-06 | [spike-notes §9](spike-notes.md) |
| Clair Obscur: Expedition 33 | Unreal Engine 5.4.4 | D3D12 | DLSS + Frame Generation ×4 (54.9 → 218.4) and ×2 (76.0 → 149.8); frame generation off read *none*, with DXGI agreeing; ray tracing *No*; the NVIDIA App's *Fixed ×6* read ×6.0 (81.8 → 490.9) on 2026-10-20 | 2026-09-04 → 10-20 | [spike-notes §9, §23](spike-notes.md), database |
| Rune Factory: Guardians of Azuma | Unreal Engine (version not in the executable) | D3D12 | DLSS Frame Generation ×4 (128.9 → 513.0); FSR frame generation compiled into the game counted ×2 but not named; ray tracing *No* (the game has none) | 2026-08-20 → 09-06 | [spike-notes §9](spike-notes.md) |
| Kingdom Come: Deliverance II | — | D3D12 | FSR (3.1 or 4) at 1505×847 → 2560×1440; frame generation *none* (the game ships none); ray tracing *No* | 2026-09-04 | [spike-notes §9](spike-notes.md) |
| Lies of P | Unreal Engine 4.27.2 | D3D12 | FSR 3 at 1506×848 → 2560×1440 with FSR frame generation ×2.04 (57.1 → 116.4) in the app; frame generation off read *none*; DLSS shown as *driver-reported*; ray tracing *No* | 2026-08-03 → 09-16 | [spike-notes §7, §9, §14](spike-notes.md) |
| Lies of P | Unreal Engine 4.27.2 | D3D12 | FSR 3 at 1506×848 → 2560×1440 with FSR frame generation ×2.04 (57.1 → 116.4) in the app; frame generation off read *none*; DLSS shown as *driver-reported*; ray tracing *No*; on 2026-10-19 and 10-20, FSR 3 at 1707×961 and at 1280×720 → 2560×1440 with FSR frame generation ×2.0 (54.6 → 109.6, 57.6 → 116.7) and no FSR quality mode — the game never asked for one while the hook was in | 2026-08-03 → 10-20 | [spike-notes §7, §9, §14, §22, §23](spike-notes.md), database |
| Onimusha: Way of the Sword (demo) | RE Engine | D3D12 | DLSS + DLSS Frame Generation: ×3.67 and ×3.93 with the capture tool, ×4.00 in the app's steady state (60 → 240 FPS), ×3.0 (60 → 180) in the app on 2026-09-22; ray tracing *Yes* | 2026-09-05 → 09-22 | [spike-notes §9, §14](spike-notes.md), database |
| Cronos: The New Dawn (demo) | Unreal Engine (version not in the executable) | D3D12 | DLSS with frame generation off (105 FPS, *none*); on ×2 (86.8 → 172.7), DLSS Frame Generation named; ray tracing *Yes* | 2026-09-06 → 09-16 | [spike-notes §9, §14](spike-notes.md) |
| Alan Wake 2 | — | D3D12 | Path tracing Ultra with DLSS and Ray Reconstruction: ray tracing *Yes* (96.8 % of frames), frame generation read ×1.00 (the game did not apply the setting that run). On 2026-09-04: DLSS with ray tracing *Yes* (99 % of frames), 92.5 FPS, frame generation *none* by count; then ray tracing off (*No*), DLSS, Presented 114.5 FPS. The quality preset was never read | 2026-08-04 → 09-04 | [spike-notes §8](spike-notes.md), run reports |
| SILENT HILL 2 | Unreal Engine 5.1 | D3D12 | DLSS Frame Generation identified, frames not counted (Presented 78 FPS); DLSS *driver-reported*; ray tracing *Yes* | 2026-09-25 | database |
| DARK SOULS III | FromSoftware | D3D11 | Presented 59.8 FPS; no upscaler, frame generation or ray tracing loaded | 2026-09-03 | [spike-notes §9](spike-notes.md) |
| Sekiro: Shadows Die Twice | FromSoftware | D3D11 | Presented 60 FPS (the game's cap), two sessions of 15 min and 2 h 18 min | 2026-09-26 | database |
| SILENT HILL 2 | Unreal Engine 5.1 | D3D12 | DLSS Frame Generation identified, frames not counted (Presented 78 FPS) on 2026-09-25; then under the NVIDIA App's *Fixed ×6* ×6.0 (53.3 → 320.0) and under its *Dynamic, up to ×6* states ×2.0, ×3.0 and ×6.1; DLSS *driver-reported*; ray tracing *Yes* | 2026-09-25 → 10-20 | database, [spike-notes §22, §23](spike-notes.md) |
| DARK SOULS III | FromSoftware | D3D11 | Presented 59.8 FPS; no upscaler, frame generation or ray tracing loaded; then 34 sessions at the game's 60 FPS cap, the longest 6 h 12 min, four of them ended by the game crashing | 2026-09-03 → 10-25 | [spike-notes §9](spike-notes.md), database |
| Sekiro: Shadows Die Twice | FromSoftware | D3D11 | Presented 60 FPS (the game's cap): two sessions of 15 min and 2 h 18 min, then three more of up to 1 h 6 min | 2026-09-26 → 10-29 | database |
| Yu-Gi-Oh! Master Duel | Unity 6000.0 | D3D11 | Presented 239 FPS across six sessions (up to 5 h 25 min) | 2026-09-22 → 09-25 | database |
| GIRLS' FRONTLINE 2: EXILIUM | Unity 2019.4 | D3D11 | Presented 53–101 FPS; the last three sessions under the user-mode anti-cheat exception (NetEase Yidun), one of them 3 h 9 min, all ended normally | 2026-09-21 → 09-27 | database, [HANDOFF](HANDOFF.md) |
| GIRLS' FRONTLINE 2: EXILIUM | Unity 2019.4 | D3D11 | Presented 53–101 FPS; the last three sessions under the user-mode anti-cheat exception (NetEase Yidun), one of them 3 h 9 min, all ended normally; ten more under the exception, 28–72 FPS, the longest 2 h 9 min, all ended normally | 2026-09-21 → 10-20 | database, [HANDOFF](HANDOFF.md) |
| Aniimo | Unity 2022.3 | D3D12 | DLSS at 1707×960 → 2560×1440, frame generation *none* (×1.00, 205 FPS), ray tracing *No* — then blocked (below) | 2026-09-22 | database |
| AbyssMemory | Unreal Engine 4.26.1 | D3D11 | Presented 55 FPS, one short session | 2026-09-22 | database |
| Umamusume: Pretty Derby | Unity 2022.3 | D3D11 | Presented 37 FPS, one session | 2026-09-27 | database |
@@ -45,6 +49,21 @@ with the 2026-09-16 recovery and with library entries removed since.
| Flower in Us | RPG Maker MV/MZ (NW.js) | D3D11 | Presented 59.8 FPS over three swap chains, after two refusals that found the game's browser process ambiguous (fixed) | 2026-09-03 → 09-04 | [spike-notes §9](spike-notes.md) |
| UMIGARI | Unreal Engine 5.5.4 | D3D12 | Presented 95–97 FPS, frame generation *none*, ray tracing *No* | 2026-09-05 → 09-06 | run reports only |
| Everhex Demo | — | Vulkan | Presented 239.7 FPS (1 % low 213.5), 14,955 frames in 69 s, through FrameLedger's Vulkan layer — the first real Vulkan game measured; started by Play set to *Start directly* | 2026-10-13 | database *(row added 2026-10-14 from a copy of the database)* |
| The Witcher 3: Wild Hunt — Remastered | — | D3D12 | DLSS 1707×960 → 2560×1440 with DLSS Frame Generation ×2.0 (118.8 → 237.4 FPS); ray tracing and Ray Reconstruction *Yes*; under the NVIDIA App's *Fixed ×6* it still presented ×2.0 — the setting is not the frames | 2026-10-04 → 10-20 | database, [spike-notes §23](spike-notes.md) |
| Phantom Blade Zero | Unreal Engine (version not in the executable) | D3D12 | DLSS *driver-reported*; DLSS Frame Generation under the NVIDIA App's *Dynamic* mode: up to ×6 held ×4.0 (59.5 → 235.6 FPS) and ×5.2 (44.3 → 231.2), up to ×3 held ×3.0 (58–76 → 175–227) for 75–94 % of each session longer than an hour; ray tracing *Yes*; thirteen sessions, the longest 6 h 29 min (5.26 million frames); up to 9.6 GB of graphics memory | 2026-11-01 → 11-05 | database, [spike-notes §26](spike-notes.md) |
| Hogwarts Legacy | Unreal Engine (version not in the executable) | D3D12 | With the game's *Neural Rendering* on, DLSS 5's runtime (`nvngx_dlssnr.dll` 310.9.16.0) loaded from the game's folder — the first game seen loading it; DLSS *driver-reported*; DLSS Frame Generation not counted (non-uniform, ×1.97 overall), Presented 140.2 FPS; ray tracing *Yes*, Ray Reconstruction *No* | 2026-11-06 | database, [spike-notes §26](spike-notes.md) |
| Valor Mortis (Xbox app) | Unreal Engine | D3D12 | DLSS Frame Generation ×6.0 (39.9 → 239.2 FPS), DLSS *driver-reported*, ray tracing *No*; recorded in attach mode | 2026-11-04 | database |
| inKONBINI (Xbox app) | Unity 6000.0 | D3D11 | Presented 205.9 FPS, one short session | 2026-11-03 | database |
| DARK SOULS II: Scholar of the First Sin | FromSoftware | D3D11 | The game's 60 FPS cap, nine sessions up to 5 h 29 min; one was unhooked by the safety check and recorded on | 2026-10-09 → 10-12 | database |
| Mithril | Unreal Engine (version not in the executable) | D3D12 | Presented 91.5–119.4 FPS, ray tracing *Yes*, four sessions up to 3 h 4 min | 2026-10-12 → 10-16 | database |
| KEEP IT ON HER | Unreal Engine 5.8 | D3D12 | Presented 59.5–108.8 FPS, ray tracing *Yes* | 2026-10-12 → 10-13 | database |
| WALTO | Unity 6000.3 | D3D12 | Presented 212.5 FPS over 2 h 41 min (2,057,022 frames) | 2026-10-08 | database |
| White Mask Mansion | Unity 6000.1 | D3D12 | Presented 286–309 FPS, five sessions | 2026-10-27 | database |
| LIMINAL: Within Demo | Unity 2022.3 | D3D11 | Presented 222.5–228.6 FPS | 2026-10-12 | database |
| Sleepytime Village | Unity 2021.3 | D3D11 | Presented 906–1,440 FPS (the game sets no cap) | 2026-10-25 → 10-26 | database |
| Scarlet Wolf | Unity 2021.3 | D3D11 | Presented 128.5 FPS | 2026-10-15 | database |
| March Out! Playtest | Unity 2022.3 | D3D11 | Presented 118.2 FPS | 2026-10-08 | database |
| A Space for the Unbound – Prologue (GOG) | Unity 2019.4 | D3D11 | Presented 61.0 FPS, started by FrameLedger | 2026-10-20 | database |
## Recorded without measurement (Tier 2)
@@ -52,8 +71,14 @@ with the 2026-09-16 recovery and with library entries removed since.
|---|---|---|---|
| HELLO, HELLO WORLD! | A 32-bit game (RPG Maker MV): refused by the guard once, and two sessions with hooking switched off — each recorded with its duration and sensors. *Its itch.io download puts malware in front of the game — do not run it (noted 2026-10-13, [spike-notes §20](spike-notes.md))* | 2026-09-23 | database |
| Umamusume: Pretty Derby | Three sessions played with hooking switched off for the game | 2026-09-27 | database |
| Sekiro: Shadows Die Twice | One session played with hooking switched off | 2026-09-25 | database |
| Sekiro: Shadows Die Twice | Two sessions played with hooking switched off | 2026-09-25, 10-07 | database |
| GIRLS' FRONTLINE 2: EXILIUM | One session whose process Windows would not let FrameLedger open, and two recovered after the agent itself stopped mid-session (*interrupted*) | 2026-09-22 → 09-23 | database |
| Bound Between Desks | Two sessions with hooking switched off (a Ren'Py 8.5 game) | 2026-10-15 → 10-20 | database |
| Phantom Blade Zero | Three sessions after a game update changed its executable on 2026-11-04, until hooking was consented to again on 11-05; one refused because a module list came back incomplete | 2026-11-04 → 11-05 | database |
| The Witcher 3: Wild Hunt — Remastered | Three sessions before hooking was consented to | 2026-10-13 → 10-20 | database |
| Mithril | Two sessions before hooking was consented to | 2026-10-16 | database |
| Hogwarts Legacy | One session with hooking switched off; Windows logged a crash of the game | 2026-11-06 | database |
| Valor Mortis, WALTO, Scarlet Wolf, Lies of P, A Space for the Unbound – Prologue | One session each with hooking switched off | 2026-10-08 → 11-04 | database |
## Refused by the anti-cheat guard
@@ -64,7 +89,10 @@ with the 2026-09-16 recovery and with library entries removed since.
| Aniimo | NetEase Yidun with a kernel driver (`NEPKernel.sys`) in the game's folder — never eligible for an exception | 2026-09-25 | [19_SAFETY](19_SAFETY_AND_ANTICHEAT.md) |
| Goose Goose Duck | Easy Anti-Cheat's service running, and its folder | 2026-08-04 | [spike-notes §13](spike-notes.md) |
| Neverness To Everness | Anti-Cheat Expert's kernel driver in the game's folder | 2026-08-04 | [spike-notes §13](spike-notes.md) |
| Wuthering Waves | Anti-Cheat Expert, kept beside the game's executable four folder levels in, where the check did not look before beta.21: a session with hooking on was injected and unhooked 37 seconds later, when the 30-second re-check met ACE's driver (`ACE-BASE.sys`); nothing was measured. Since beta.21 its folder and its Steam id refuse it before any injection *(row added 2026-10-13 from the agent's log)* | 2026-10-12 | [spike-notes §19](spike-notes.md) |
| Wuthering Waves | Anti-Cheat Expert, kept beside the game's executable four folder levels in, where the check did not look before beta.21: a session with hooking on was injected and unhooked 37 seconds later, when the 30-second re-check met ACE's driver (`ACE-BASE.sys`); nothing was measured. Since beta.21 its folder and its Steam id refuse it before any injection *(row added 2026-10-13 from the agent's log)*; two sessions recorded without measurement on 2026-10-31 | 2026-10-12 → 10-31 | [spike-notes §19](spike-notes.md), database |
| Arknights: Endfield | Anti-Cheat Expert's folder (`AntiCheatExpert`) beside the game; one session recorded without measurement | 2026-10-31 | database |
| Stella Sora | Anti-Cheat Expert's folder (`AntiCheatExpert`); three sessions recorded without measurement | 2026-10-30 → 10-31 | database |
| Umamusume: Pretty Derby | CrackProof, on FrameLedger's title list since beta.11 (Steam 3224770) — measured before the list named it (above) | 2026-10-03 | [19_SAFETY](19_SAFETY_AND_ANTICHEAT.md) |
| Counter-Strike 2 | Valve Anti-Cheat — refused by FrameLedger's title list since beta.8. On 2026-08-04 the checks alone allowed it (VAC is invisible to them); nothing was injected | 2026-08-04, beta.8 | [spike-notes §13](spike-notes.md), [19_SAFETY](19_SAFETY_AND_ANTICHEAT.md) |
Also refused before any injection: **Deadly Heart Gambit** — a 32-bit game (2026-08-03).
@@ -74,4 +102,6 @@ Also refused before any injection: **Deadly Heart Gambit** — a 32-bit game (20
The Unreal Engine version (beta.10) was checked against ten installed Unreal games without running them: Hell Is Us
5.5.4, Black Myth: Wukong 5.0.0, Clair Obscur: Expedition 33 5.4.4, Lies of P 4.27.2, SILENT HILL 2 5.1, UMIGARI 5.5.4,
AbyssMemory 4.26.1, **Martha Is Dead 4.27.0**; Cronos (demo) and Rune Factory name no version in their executables and
read *not found*. ([spike-notes §15](spike-notes.md), [05_DETECTION §Engine version](05_DETECTION.md))
read *not found*. ([spike-notes §15](spike-notes.md), [05_DETECTION §Engine version](05_DETECTION.md)) Read since on the games
in the database: KEEP IT ON HER 5.8 and Wuthering Waves 4.26.2; Phantom Blade Zero, Hogwarts Legacy and Mithril name no
version in their executables, and an Xbox game's executable cannot be read outside its package (Valor Mortis).
+5 -1
View File
@@ -11,7 +11,7 @@ This folder is for people who build, change or review FrameLedger. **If you only
| Find your way around first | The [wiki](https://github.com/poli0981/frameledger/wiki)'s developer pages (source: [`../wiki/`](../wiki/), beta.17) — a short page per part, each linking here |
| Learn the system | [`../CLAUDE.md`](../CLAUDE.md) (the rules and the layout), then the reading order below |
| Build it | [`12_BUILD.md`](12_BUILD.md) — `./build.ps1 check` is the whole gate, the same one CI runs |
| Contribute or fork | [`../CONTRIBUTING.md`](../CONTRIBUTING.md), [`../FORKING.md`](../FORKING.md), [`../NOTICE`](../NOTICE) |
| Contribute or fork | [`../CONTRIBUTING.md`](../CONTRIBUTING.md), [`../FORKING.md`](../FORKING.md), [`../NOTICE`](../NOTICE), [`../CODE_OF_CONDUCT.md`](../CODE_OF_CONDUCT.md) *(it and `SECURITY.md`, below, added 2026-11-09: the index named neither)* |
**Status lives in four places, and nowhere else** — check a status claim against the code before you plan on it:
@@ -87,5 +87,9 @@ are safety items, and something listed there as unresolved should not be built t
- [`../legal/`](../legal/) — the documents a user accepts, the accuracy statement, the third-party notices and licence
texts, the trademark note.
- [`../LIMITATIONS.md`](../LIMITATIONS.md) — what the whole software cannot do, in a player's words.
- [`../ACCESSIBILITY.md`](../ACCESSIBILITY.md) — the accessibility statement (beta.35, D88): the goal, what works with the
keyboard, a screen reader and contrast themes, the known limits and how a barrier is reported; shown in the App under
Help ▸ Accessibility. Its checks are [`08_UI.md`](08_UI.md) §Accessibility.
- [`../SECURITY.md`](../SECURITY.md) — the private route for a vulnerability, and why the guard has no override.
- [`../rules/detection-rules.json`](../rules/detection-rules.json) — engine, platform and capability signatures and the
anti-cheat blocklist, validated by `tools/rules-validate.ps1`.
+40
View File
@@ -0,0 +1,40 @@
<!-- The first alpha's notes (D73-D76), on main as every release's are; the alpha branch takes them with its sync. CHANGELOG.md lists every release. -->
## [0.1.0-alpha.1] - 2026-10-31
> ⚠ **EXPERIMENTAL BUILD — YOU USE IT AT YOUR OWN RISK.** This is an **alpha**: the source of `0.1.0-beta.32` built on
> **.NET 11 Release Candidate 3** (SDK `11.0.100-rc.3.26522.148`, runtime `11.0.0-rc.3.26522.148`), a version of .NET
> Microsoft has not finished, with the C# 15 compiler. It has not been tested the way a beta is, and it can crash, record
> wrongly or fail to update in ways no beta has. **If you want results you can rely on, use the beta.** Before it runs it
> shows the *Alpha notice* (`legal/ALPHA_NOTICE.md` 1.0), which you must accept, with its own box to tick.
**The first alpha.** What it is and how to go back: the user guide's *Alpha builds* page
(`guide/11-alpha-builds.md`), and the *Alpha builds* section of `LIMITATIONS.md`.
**Installing it:** download `FrameLedger.App-alpha-Setup.exe` below, verify its hash against `SHA256SUMS.txt`, run it,
and let it replace the FrameLedger already installed. **It replaces the beta** — one of them is installed at a time — and
uses the same data folder: before it first opens your database it copies it to
`%LOCALAPPDATA%\FrameLedger\backups\ledger-before-0.1.0-alpha.1.db`, and it does not open the database if the copy cannot
be made. It never arrives as an update to a beta, and it updates only to newer alphas.
**Going back:** install the newest beta's `FrameLedger.App-win-Setup.exe` over it; your database stays where it is, with
any sessions the alpha recorded.
**Windows and your PC:** Microsoft supports .NET 11 on Windows 11 24H2 and later, and on Windows 10 only in its LTSC and
IoT editions; on Windows 10 22H2 Home or Pro this alpha may run, but nobody supports it there. It needs a processor with
SSE4.2 and POPCNT. .NET 11 RC3 is supported by Microsoft until .NET 11 ships (10 November 2026); the next alpha moves to
the final release.
### What differs from 0.1.0-beta.32
- **The runtime and the compiler**: .NET 11 RC3 in place of .NET 10.0.14, self-contained as always; C# 15. The source
uses no C# 15 syntax and no preview feature (owner decision D76) — what .NET 11's SDK asked of it was taken on main in
forms .NET 10 also compiles (`docs/spike-notes/24-dotnet11-probe.md`), so a beta and this alpha are the same code.
- **Three libraries serviced with the runtime**: `Microsoft.Extensions.Hosting`, `System.Diagnostics.EventLog` and
`Microsoft.Data.Sqlite` `11.0.0-rc.3.26522.148`. The database engine is SQLite 3.53.4 (`SQLitePCLRaw` 3.0.5, which
`Microsoft.Data.Sqlite` 11 declares), where the beta's is 3.53.3; the database file is the same format. Nine
`Microsoft.Extensions.*` libraries are now part of the runtime and no longer ship beside it.
- **What .NET 11 itself changes**: a failure in the capture agent's own background work ends the agent with a crash report
where the beta's exits quietly (`IHost` now reports it); the runtime's ReadyToRun code targets processors with AVX2, so
an older processor starts the program a little slower.
- **The part of FrameLedger loaded into a game is the beta's**, built from the same C++ source: it does not use .NET.
+33
View File
@@ -0,0 +1,33 @@
<!-- The second alpha's notes (D73, D82), on main as every release's are; the alpha branch takes them with its sync. CHANGELOG.md lists every release. -->
## [0.1.0-alpha.2] - 2026-11-03
> ⚠ **EXPERIMENTAL BUILD — YOU USE IT AT YOUR OWN RISK.** This is an **alpha**: the source of `0.1.0-beta.33` built on
> **.NET 11 Release Candidate 3** (SDK `11.0.100-rc.3.26522.148`, runtime `11.0.0-rc.3.26522.148`), a version of .NET
> Microsoft has not finished, with the C# 15 compiler. It has not been tested the way a beta is, and it can crash, record
> wrongly or fail to update in ways no beta has. **If you want results you can rely on, use the beta.** Before it runs it
> shows the *Alpha notice* (`legal/ALPHA_NOTICE.md` 1.0), which you must accept, with its own box to tick.
**The second alpha: `0.1.0-beta.33` on .NET 11 RC3** — games from the Xbox app and the Microsoft Store (the beta's
notes, `docs/changelog/0.1.0-beta.33.md`, say what that brings). What an alpha is and how to go back: the user guide's
*Alpha builds* page (`guide/11-alpha-builds.md`), and the *Alpha builds* section of `LIMITATIONS.md`.
**Updating from `0.1.0-alpha.1`:** Help ▸ Check for updates, then *Restart to update* with no game running — an alpha
updates only to newer alphas. Before it first opens your database it copies it to
`%LOCALAPPDATA%\FrameLedger\backups\ledger-before-0.1.0-alpha.2.db` (the newest three copies are kept). The terms window
shows the **Privacy Policy 2.13** once and, as every time an alpha's terms window opens, waits for the Alpha notice's box
to be ticked again; the notice itself stays 1.0. The ledger stays at schema 21; the detection rules move to `2026.11.1`.
**Installing it over a beta:** download `FrameLedger.App-alpha-Setup.exe` below, verify its hash against
`SHA256SUMS.txt`, and let it replace the FrameLedger already installed; the Alpha notice is shown first. **Going back:**
install the newest beta's `FrameLedger.App-win-Setup.exe` over it; your database stays where it is.
**Windows and your PC:** as for the first alpha — Microsoft supports .NET 11 on Windows 11 24H2 and later, and on Windows
10 only in its LTSC and IoT editions; it needs a processor with SSE4.2 and POPCNT. .NET 11 RC3 is supported until .NET 11
ships (10 November 2026); the next alpha moves to the final release.
### What differs from 0.1.0-beta.33
The same as `0.1.0-alpha.1` differed from `0.1.0-beta.32` (`docs/changelog/0.1.0-alpha.1.md`): the runtime and the
compiler, the three libraries serviced with the runtime, what .NET 11 itself changes — and the part of FrameLedger loaded
into a game is the beta's.
+36
View File
@@ -0,0 +1,36 @@
<!-- The third alpha's notes (D73, D87), on main as every release's are; the alpha branch takes them with its sync. CHANGELOG.md lists every release. -->
## [0.1.0-alpha.3] - 2026-11-06
> ⚠ **EXPERIMENTAL BUILD — YOU USE IT AT YOUR OWN RISK.** This is an **alpha**: the source of `0.1.0-beta.34` built on
> **.NET 11 Release Candidate 3** (SDK `11.0.100-rc.3.26522.148`, runtime `11.0.0-rc.3.26522.148`), a version of .NET
> Microsoft has not finished, with the C# 15 compiler. It has not been tested the way a beta is, and it can crash, record
> wrongly or fail to update in ways no beta has. **If you want results you can rely on, use the beta.** Before it runs it
> shows the *Alpha notice* (`legal/ALPHA_NOTICE.md` 1.0), which you must accept, with its own box to tick.
**The third alpha: `0.1.0-beta.34` on .NET 11 RC3** — DLSS 5 and DLSS 4.5 named from what the game and the driver did,
filters on Games and Compare, and a Games page that opens at once (the beta's notes, `docs/changelog/0.1.0-beta.34.md`,
say what that brings). What an alpha is and how to go back: the user guide's *Alpha builds* page
(`guide/11-alpha-builds.md`), and the *Alpha builds* section of `LIMITATIONS.md`.
**Updating from `0.1.0-alpha.2`:** Help ▸ Check for updates, then *Restart to update* with no game running — an alpha
updates only to newer alphas. Before it first opens your database it copies it to
`%LOCALAPPDATA%\FrameLedger\backups\ledger-before-0.1.0-alpha.3.db` (the newest three copies are kept). The terms window
shows the **Disclaimer 2.13** and the **Privacy Policy 2.14** once and, as every time an alpha's terms window opens, waits
for the Alpha notice's box to be ticked again; the notice itself stays 1.0. The ledger moves to schema 22, which an
alpha.2 cannot open (the copy is the database as alpha.2 left it; going back is to the newest beta, which opens it); the
detection rules move to `2026.11.2`.
**Installing it over a beta:** download `FrameLedger.App-alpha-Setup.exe` below, verify its hash against
`SHA256SUMS.txt`, and let it replace the FrameLedger already installed; the Alpha notice is shown first. **Going back:**
install the newest beta's `FrameLedger.App-win-Setup.exe` over it; your database stays where it is.
**Windows and your PC:** as for the first alpha — Microsoft supports .NET 11 on Windows 11 24H2 and later, and on Windows
10 only in its LTSC and IoT editions; it needs a processor with SSE4.2 and POPCNT. .NET 11 RC3 is supported until .NET 11
ships (10 November 2026); the next alpha moves to the final release.
### What differs from 0.1.0-beta.34
The same as `0.1.0-alpha.1` differed from `0.1.0-beta.32` (`docs/changelog/0.1.0-alpha.1.md`): the runtime and the
compiler, the three libraries serviced with the runtime, what .NET 11 itself changes — and the part of FrameLedger loaded
into a game is the beta's.
+42
View File
@@ -0,0 +1,42 @@
<!-- The fourth alpha's notes (D73, D98), on main as every release's are; the alpha branch takes them with its sync. CHANGELOG.md lists every release. -->
## [0.1.0-alpha.4] - 2026-11-11
> ⚠ **EXPERIMENTAL BUILD — YOU USE IT AT YOUR OWN RISK — AND THE LAST ALPHA FOR NOW.** This is an **alpha**: the source
> of `0.1.0-beta.37` built on **.NET 11.0.0**, Microsoft's final release of .NET 11 (SDK `11.0.100`) — the same .NET the
> betas run on from `0.1.0-beta.37`. It exists to bring an installed alpha off the release candidate. **After it the
> alphas pause**, and a paused alpha gets no update — the list of anti-cheat software FrameLedger refuses included.
> **Install the latest beta over it.** Before it runs it shows the *Alpha notice* (`legal/ALPHA_NOTICE.md` 1.1), which
> you must accept, with its own box to tick.
**The fourth alpha: `0.1.0-beta.37` on .NET 11.0.0.** The alphas were made to try .NET 11 before the betas relied on it.
.NET 11 shipped on 10 November 2026 and the betas moved to it the next day (the beta's notes,
`docs/changelog/0.1.0-beta.37.md`), so an alpha and a beta now differ in nothing but what an alpha adds for itself. This
one is published so that a copy of `0.1.0-alpha.3`, which runs on a release candidate Microsoft no longer supports,
reaches the finished .NET 11 by an update — an alpha never updates to a beta.
**Then install the beta.** No alpha will follow until there is a newer .NET to try (.NET 12's first previews, expected
in 2027). Until then this build stands still: no fixes, and **its anti-cheat list is the one it shipped with**, because
that list reaches FrameLedger only inside an update. Its banner says so each time it starts. Download the newest beta's
`FrameLedger.App-win-Setup.exe`, verify its hash against that release's `SHA256SUMS.txt`, and let it replace the alpha;
your database stays where it is, and the beta opens it. What an alpha is and how to go back: the user guide's *Alpha
builds* page (`guide/11-alpha-builds.md`), and the *Alpha builds* section of `LIMITATIONS.md`.
**Updating from `0.1.0-alpha.3`:** Help ▸ Check for updates, then *Restart to update* with no game running. Before it
first opens your database it copies it to `%LOCALAPPDATA%\FrameLedger\backups\ledger-before-0.1.0-alpha.4.db` (the
newest three copies are kept). The terms window shows the **EULA 1.7**, the **Disclaimer 2.14** and the **Alpha notice
1.1**, and waits for the notice's box to be ticked. The ledger stays at schema 22 and the detection rules at
`2026.11.2`. The download is large, because the .NET runtime inside the package is replaced whole. **One limit:**
FrameLedger's updater looks at the newest ten releases, so once ten betas have been published after this alpha, an
older alpha no longer finds it — install the beta by hand then, as above.
**Windows and your PC:** as for the beta from `0.1.0-beta.37` — Microsoft supports .NET 11 on Windows 11, and on Windows
10 only in its LTSC and IoT editions; FrameLedger is untested and unsupported on Windows 10 22H2; a processor without
SSE4.2 and POPCNT cannot start it.
### What differs from 0.1.0-beta.37
Nothing in the runtime, the compiler or the libraries: both are built on .NET 11.0.0 from the same source, and the part
of FrameLedger loaded into a game is the beta's. What an alpha adds is its own: the Alpha notice in the terms window, the
ALPHA badge and the banner — which in this build says that the alphas are paused — the locked update channel, and the
copy of the database before it is first opened.
+27
View File
@@ -0,0 +1,27 @@
<!-- Moved from CHANGELOG.md's [Unreleased] when 0.1.0-beta.25 was cut, 2026-10-19 (D66). CHANGELOG.md lists every release. -->
## [0.1.0-beta.25] - 2026-10-19
**The twenty-fifth pre-release: FSR's quality mode.** The same unsigned installer: verify its hash against
`SHA256SUMS.txt`, then *More info → Run anyway*.
**Updating from `0.1.0-beta.24`:** Help ▸ Check for updates, then *Restart to update* with no game running. Nothing is
shown for you to accept again (the Disclaimer stays 2.11, the Privacy Policy 2.12), the ledger stays at schema 21, and
no game is read again: the detection rules (`2026.10.4`) are beta.24's. FSR's quality mode is recorded for sessions
from now on; a session recorded before keeps what it had.
### Added
- **FSR's quality mode** (owner decision D65, planned for beta.24 and moved to this release). For a game that runs FSR
through AMD's FidelityFX libraries, the summary, the Sessions tab, the game page and the live card name the mode —
*FSR 3 Quality*, *FSR Performance*, *FSR Native AA* — when the game asked AMD's library what render size that mode
gives and then rendered at that size. A game at a dynamic resolution, one that sizes its frames without asking, and
one FrameLedger joined after it asked show none. FrameLedger reads one more call in those libraries (`ffxQuery`,
beside the `ffxDispatch` it already reads): the size or ratio AMD's library answered, nothing else — about 8 ns per
upscaled frame. The CSV export's `# quality_mode:` carries it (`native_aa (game)` for Native AA).
`legal/ACCURACY.md`'s *Quality mode* bullet gains its FSR clause, in the words approved with the beta.24 plan; the
Disclaimer stays 2.11, as it did for the accuracy statement's additions in beta.19 and beta.20. Checked with AMD's
interface on the test program; a real game is owner-only item 21. Developers: the hook has its own family bit
(`FL_HOOK_UPSCALER_QUALITY`, bit 11 of `hooksInstalledMask`), the byte is `0x10 + FfxApiUpscaleQualityMode`, the
harness asks with `--ffx-query sizes|ratios`, and `Domain.Metrics.QualityByte` is the one rule a session, its
segments and the live card read.
+35
View File
@@ -0,0 +1,35 @@
<!-- Moved from CHANGELOG.md's [Unreleased] when 0.1.0-beta.26 was cut, 2026-10-19 (D66). CHANGELOG.md lists every release. -->
## [0.1.0-beta.26] - 2026-10-19
**The twenty-sixth pre-release: a frame-generation state no frame generation produces, fixed.** The same unsigned
installer: verify its hash against `SHA256SUMS.txt`, then *More info → Run anyway*.
**Updating from `0.1.0-beta.25`:** Help ▸ Check for updates, then *Restart to update* with no game running. Nothing is
shown for you to accept again (the Disclaimer stays 2.11, the Privacy Policy 2.12), the ledger stays at schema 21, and
no game is read again: the detection rules (`2026.10.4`) are beta.25's. Sessions you already recorded read by the new
rule at once — nothing in them is rewritten.
### Changed
- **SonarCloud's last six findings on `main`, triaged** (developers only; D67's follow-up). After the owner's marking,
the analysis of 0.1.0-beta.25 left six open: `docs/13_CI_CD.md` §SonarCloud lists them with a verdict and the comment
to paste — one to accept as the table already said, four false positives (exact floating-point comparisons that are
exact on purpose), and one fixed here: `wiki.yml` publishes only after a Release run started by a tag pushed to this
repository, now checked by the repository's name in its condition as well as by the run's trigger.
### Fixed
- **A frame-generation "state" of ×1336.0.** The owner's Silent Hill 2 session (0.1.0-beta.25, the NVIDIA App's
*Dynamic* multi frame generation) listed a ×1336.0 state — 0.20 → 267.20 FPS for ten seconds — under *Frame
generation in this session*, and the DLSS line cited it: *DLSS 4.5 (a ×1336.0 frame-generation state)*. Those ten
seconds — the game compiling its shaders at start — were presented with one application frame counted per
five-second window, and a window needed eight presents but only one counted frame to be read. A window now needs eight
application frames and a ratio no higher than ×8 — more than any frame generation produces (DLSS 4.5's ×6 is the
most); every other window is *Not classified*, and the steady state reads the same windows. A session-wide or live ratio that held above ×8 is
refused and says why (*the ratio is beyond what any frame generation produces*), in en/vi/ja. Sessions already
recorded are read by the same rule, so that session now lists ×2.0, ×3.0, ×6.1, no frame generation and 30 seconds
not classified, and its DLSS line cites ×6.1. The owner's runs of beta.24 and beta.25 are recorded in
`docs/spike-notes/22-owner-runs-2026-10-19.md`: the *Dynamic* settings line matched the NVIDIA App's own words, the
override's two library names are written down, and Lies of P read no FSR mode with the query hooked — the title
rounds its own render size and asked nothing the hook kept.
+56
View File
@@ -0,0 +1,56 @@
<!-- Moved from CHANGELOG.md's [Unreleased] when 0.1.0-beta.27 was cut, 2026-10-20 (D66). CHANGELOG.md lists every release. -->
## [0.1.0-beta.27] - 2026-10-20
**The twenty-seventh pre-release: the owner's eight sessions of 2026-10-20, checked — six faults fixed, and *Start
directly* says what a Steam game may do.** The same unsigned installer: verify its hash against `SHA256SUMS.txt`, then
*More info → Run anyway*.
**Updating from `0.1.0-beta.26`:** Help ▸ Check for updates, then *Restart to update* with no game running. Nothing is
shown for you to accept again (the Disclaimer stays 2.11, the Privacy Policy 2.12), the ledger stays at schema 21, and
no game is read again: the detection rules (`2026.10.4`) are beta.26's. Sessions you already recorded read the
frame-generation fix at once; the driver's DLSS report, the display sizes and the game Steam starts are recorded from
this version on — nothing already stored is rewritten.
### Changed
- **Play ▸ *Start directly* says what a Steam game may do.** Some Steam games hand themselves to Steam when
FrameLedger starts them — Lies of P closes within seconds and Steam starts it again. Starting a game Steam installed,
the notice now says it may hand itself to Steam first and that the game Steam then starts is recorded; the *Start
directly* tooltip and Settings ▸ Games ▸ *Play button* say so too, adding that a few will not start outside Steam at
all. Steam games keep *Start directly*: three of the five started directly on 2026-10-20 ran and were measured from
their first frame, and a Vulkan game is measured only when FrameLedger starts it. In en/vi/ja (ja marked for review).
### Fixed
- **A frame-generation "state" of ×2.52.** The owner's Silent Hill 2 session under the NVIDIA App's *Dynamic* multi
frame generation listed ×2.52 for 13 seconds beside ×2.0 and ×3.0: the five-second windows in which the multiplier
stepped from ×2 to ×3 read in between, and three of them formed a state nobody held. Every frame generation that
ships multiplies by a whole number, so a window now counts toward a state only within 10 % of one; the others are
*Not classified*. Sessions already recorded are read by the same rule: that session lists ×2.0, ×3.0, no frame
generation and 7.36 % not classified. The owner's runs of 2026-10-20 are recorded in
`docs/spike-notes/23-owner-runs-2026-10-20.md`.
- **The NVIDIA driver's DLSS report was lost from every stored session.** FrameLedger asked the driver one last time
after the game had closed, and that answer — which no longer says DLSS ran — replaced the ones read while the game
ran. So no session said *DLSS (driver-reported)* where no hook saw DLSS, and none named the NVIDIA App's quality mode
on such a game: Clair Obscur: Expedition 33 under the App's override read *Upscaler not identified*. The driver is no
longer asked once the game has closed, and once it reports that DLSS ran, the session keeps it. Sessions recorded
before keep what they stored.
- **Play ▸ *Start directly* recorded nothing of a game that hands itself to Steam.** Lies of P, started directly, closes
within seconds and Steam starts it again; the game Steam started was turned away while the first session ended and
never recorded. It is now recorded once that session ends, as a game started again already was. Each such start
still counts toward the two early exits that turn hooking off for a game, so Limitations ▸ Play advises starting such
a game through its store.
- **Opening a session's summary twice opened two windows.** The open window comes forward instead, restored if
minimised.
- **No window or monitor size for a game in exclusive full-screen.** A game leaving exclusive full-screen closes its
window a moment before its swap chain says so, and those last samples replaced the sizes: two Lies of P and three
Dark Souls III sessions show none. The sizes are now the last ones the mode saw.
- **A DLSS line that said only "DLSS"**, under a header that already did, is no longer shown: the NVIDIA App's override
loads its libraries under names FrameLedger does not list (The Witcher 3), and the *Loaded:* line prints them.
- **Two integration tests that failed under load** (developers only). The guard reads every process above the test
harness too, the test host among them, and under a full `build.ps1 check` the test host is still starting its other
test classes: a module it released while the guard read its list refused the injection (`ModuleScanFailed`, and
`ProcessUnreadable` on 2026-10-19). The drain suite asks the guard again on those two reasons, four times at most;
the pause case, which once read the writer still starting, waits for it to be ready; and every injection test waits
for the harness's own "presenting" line instead of 800 ms (`tests/Shared/HarnessReady.cs`).
+26
View File
@@ -0,0 +1,26 @@
<!-- Moved from CHANGELOG.md's [Unreleased] when 0.1.0-beta.28 was cut, 2026-10-20 (D66). CHANGELOG.md lists every release. -->
## [0.1.0-beta.28] - 2026-10-20
**The twenty-eighth pre-release: the Dashboard shows every game being recorded.** The same unsigned installer: verify
its hash against `SHA256SUMS.txt`, then *More info → Run anyway*.
**Updating from `0.1.0-beta.27`:** Help ▸ Check for updates, then *Restart to update* with no game running. Nothing is
shown for you to accept again (the Disclaimer stays 2.11, the Privacy Policy 2.12), the ledger stays at schema 21, and
no game is read again: the detection rules (`2026.10.4`) are beta.27's. Only the App changes; the capture agent and
what it records are beta.27's.
### Added
- **The Dashboard shows every game being recorded.** Two games running at once are two sessions, and until now the
Dashboard's *Live capture* card showed one of them — a measured one first — while the other appeared only as
*Running sessions: 2*. Each running game now has its own card, side by side, with its own frame rate, settings,
elapsed time and memory, or why it is recorded without being measured; measured games come first, and the title
says how many games are being recorded (*2 games recording*). In en/vi/ja (ja marked for review).
### Fixed
- **A native injection test that failed under load** (developers only). Two `fl_guard_test` cases — the OpenGL hook,
and a swap chain on a real window — waited 4 seconds for twenty frames, and on a loaded CI runner (the suite took
115 s) the OpenGL hook, installed, had recorded none. They now wait up to 12 seconds, the harness presenting for 16,
and a failure says the writer's state.
+55
View File
@@ -0,0 +1,55 @@
<!-- Moved from CHANGELOG.md's [Unreleased] when 0.1.0-beta.29 was cut, 2026-10-25 (D66). CHANGELOG.md lists every release. -->
## [0.1.0-beta.29] - 2026-10-25
**The twenty-ninth pre-release: updated libraries, and SonarCloud analysing every change from CI.** The same unsigned
installer: verify its hash against `SHA256SUMS.txt`, then *More info → Run anyway*.
**Updating from `0.1.0-beta.28`:** Help ▸ Check for updates, then *Restart to update* with no game running. Nothing is
shown for you to accept again (the Disclaimer stays 2.11, the Privacy Policy 2.12), the ledger stays at schema 21, and
no game is read again: the detection rules (`2026.10.4`) are beta.28's. What you see and what is recorded are
beta.28's; the libraries under them are newer.
### Changed
- **SonarCloud analyses the repository from CI** (developers only; owner decision D68). The owner turned SonarCloud's
Automatic Analysis off and set the `SONAR_TOKEN` secret; `ci.yml`'s new `sonarcloud` job runs the SonarScanner for
.NET 12.0.0 (a local tool, `.config/dotnet-tools.json`) after `check`, in a build of its own — the scanner turns
warnings-as-errors off in the build it instruments, so it cannot wrap the gate's — with the gate's own test coverage
(`build.ps1` now writes OpenCover beside Cobertura; the C# only, since the PowerShell tools and the native code have
no coverage report) and CMake's compilation database for the C++, which
`FrameLedger.Infrastructure.csproj` names to the scanner only in that build. `SonarQube.Analysis.xml` replaces
`.sonarcloud.properties`. The job is advisory, not a required check, and waits for the quality gate, so a failed gate
is a red job (`docs/13_CI_CD.md` §SonarCloud).
- **Dependabot, the NuGet audit and CodeQL** (developers only). Dependabot's version updates wait seven days after a
release (security updates do not), and the actions' minor and patch releases come as one pull request a week. The
NuGet audit is written down in `Directory.Build.props` (the whole graph, every severity — the SDK's defaults for
net10.0), so a later SDK cannot move it. CodeQL also reads the workflows (`analyze (actions, none)`, not required),
and a new push to a pull request replaces its CodeQL run.
- **The libraries Dependabot never updated.** Every NuGet pull request Dependabot opened here updated analyzers only,
so the libraries fell behind with nothing to say so (`docs/13_CI_CD.md` §Dependabot and the NuGet audit). Updated by
hand, each release at least seven days old (the cooldown Dependabot now keeps): the October .NET servicing release of
`Microsoft.Extensions.Hosting`, `Microsoft.Data.Sqlite` and `System.Diagnostics.EventLog` (10.0.13) and `Dapper`
2.1.89, which ship; the CsWin32 source generator 0.3.363, which writes the Win32 declarations the shipped code calls;
for developers, the test SDK 18.11.0 and xunit 4.0.2. The licence texts under `legal/licenses/nuget/` name the new
versions; no licence changed. Not taken: Markdig 1.5.0 (published the day before, and its licence is a reviewed copy
at the packaged commit), Velopack 1.2.161 (the updater itself — a change to how updates install is the owner's to
try), FluentAssertions 8 (its licence) and `coverlet.collector` 10.1.0: the tracker it adds to each assembly it
instruments declares a constant whose value reflection cannot read ("Literal value was not found"), and
`NoSecondMatcherTests` reads every string constant in three of ours. The first CI run blamed CsWin32 for it; with
coverage collected locally the failure followed coverlet, and 10.0.1 passes (`Directory.Packages.props` says so
beside it).
### Fixed
- **The 34 C++ issues of `main`'s first SonarCloud analysis from CI** (developers only). Read with MSVC's real flags,
the native code showed issues Automatic Analysis had not, on older lines; SonarCloud dates each by blame, and the
two on lines changed since its new code began failed `main`'s gate on reliability. One was a defect in a test tool: `hook-harness --opengl` or `--vulkan` beside
a D3D11 mode — or `--opengl` alone, which ran the default probes — called through a null swapchain; every mode that
drives the D3D11 swapchain now asks first. The rest: `NvU32` printed with `%u` in `fl-probe-nvapi` (`%lu`; its
machine line reads the same), a union and a `strlen` in the guard's tests, a `LARGE_INTEGER` read through
`QuadPart` after `{}` had made its other member the active one (the Overlay's clock epoch, and the Vulkan layer's
once-per-process enable-list read — now initialised through `QuadPart`), two terminators written after a read whose
bound is now tested first, and five marked `// NOSONAR` with the reason above each. The Overlay compiles to the same
instructions: built from either side, in one folder with one build id, its `.text` is byte-identical
(`docs/13_CI_CD.md` §SonarCloud has the table).
+53
View File
@@ -0,0 +1,53 @@
<!-- Moved from CHANGELOG.md's [Unreleased] when 0.1.0-beta.30 was cut, 2026-10-26 (D66). CHANGELOG.md lists every release. -->
## [0.1.0-beta.30] - 2026-10-26
**The thirtieth pre-release: Enter in the consent dialog, readable hardware-change markers, updated libraries, and the
.NET 10.0.14 runtime.** The same unsigned installer: verify its hash against `SHA256SUMS.txt`, then *More info → Run
anyway*.
**Updating from `0.1.0-beta.29`:** Help ▸ Check for updates, then *Restart to update* with no game running — a download
of about 5 MB. Nothing is shown for you to accept again (the Disclaimer stays 2.11, the Privacy Policy 2.12), the ledger
stays at schema 21, and no game is read again: the detection rules (`2026.10.4`) are beta.29's. This update is installed
by beta.29's updater; the next one is the first that this release's updater installs.
### Changed
- **Updated libraries, and a version conflict removed** (owner decision D71 for the updater). Velopack, the installer
and updater, 1.2.0 → 1.2.161 with its packing tool: the update from beta.29 to this release is still installed by
beta.29's updater, and the next one is the first this one installs. Markdig, which draws the documents the App shows,
1.4.0 → 1.4.2 (parser fixes; its licence text is unchanged). The database's `SQLitePCLRaw` is again the version
`Microsoft.Data.Sqlite` declares, 2.1.13: a pin kept since August for a security issue fixed since had put it on
another major version with nothing to say so; the SQLite engine is 3.53.3 (it was 3.53.4). Not taken, each with its
reason in `docs/13_CI_CD.md` §Dependabot and the NuGet audit: the .NET 10.0.14 packages (a day old), Markdig 1.5.0,
CsWin32 0.3.366 and 0.3.367, `coverlet.collector` 10.1.0 and FluentAssertions 8.
### Fixed
- **Enter in the consent dialog declined, and the hooking switch then showed on beside "off"** (owner decision D69).
The dialog's default button was *Keep hooking off* — the rule was "Enter never enables" — and WPF UI's template sends
Enter to the default button, so typing `I ACCEPT THE INJECTION RISK` and pressing Enter kept hooking off without a
word. Asked with that, the owner chose: Enter enables once the phrase is typed exactly, as a click on *Enable hooking*
does, and does nothing before it; Esc and *Keep hooking off* still decline. The typed phrase is still the gate — the
button Enter reaches stays disabled and hidden until the phrase matches — and no text of the dialog changed
(`consent-dialog/1`). The game page's two switches, Hooking and Recording, now read their row again after every
click: a click that changed nothing — the dialog declined, a refusal, no agent running — left the switch on while the
text beside it said off, and the next click asked to enable again (`docs/19_SAFETY_AND_ANTICHEAT.md` §User-facing
consent, `docs/08_UI.md` §Keyboard).
- **A hardware change on a game's charts was cut off and hard to read** (owner decision D70). *Sessions at a glance* and
the *Trend* marked each day the GPU driver, GPU, CPU, display or Windows changed with a dashed line labelled with the
change itself — white on orange, its top cut off by the chart's edge, and a day with several changes showed one at
most. Each such day now carries a number — 1 for the oldest, the same on both charts — in a band kept above the chart,
dark on the orange in both themes, never cut off and never over another: badges too close for their lines stand aside,
joined to them, and a run that still cannot stand side by side is one badge (*3–5*). The list under each chart gives
each number's day and every change in full, and pointing at a line or a badge shows the same text. In en/vi/ja (ja
marked for review). A click on *Sessions at a glance* now reads the pointer at the monitor's own scale
(`docs/08_UI.md` §Games, §DPI).
### Security
- **The .NET runtime inside is 10.0.14**, Microsoft's out-of-band security release of 2026-10-25 (CVE-2026-111497, a
Brotli decompression flaw; it also completes the SocketAsyncEventArgs fix, CVE-2026-70197, that 10.0.13 left
incomplete). FrameLedger is self-contained, so
it ships the runtime of the SDK that builds it: beta.29 carried 10.0.13; this release was built with SDK 10.0.403 and
carries 10.0.14 — read from the published package's `FrameLedger.deps.json` in the release rehearsal.
+24
View File
@@ -0,0 +1,24 @@
<!-- Moved from CHANGELOG.md's [Unreleased] when 0.1.0-beta.31 was cut, 2026-10-26 (D66). CHANGELOG.md lists every release. -->
## [0.1.0-beta.31] - 2026-10-26
**The thirty-first pre-release: the remaining library updates.** The same unsigned installer: verify its hash against
`SHA256SUMS.txt`, then *More info → Run anyway*.
**Updating from `0.1.0-beta.30`:** Help ▸ Check for updates, then *Restart to update* with no game running. Nothing is
shown for you to accept again (the Disclaimer stays 2.11, the Privacy Policy 2.12), the ledger stays at schema 21, and
no game is read again: the detection rules (`2026.10.4`) are beta.30's. This is the first update that beta.30's updater
(Velopack 1.2.161) installs; if it downloads the whole package rather than a few megabytes, or the App does not come back,
the installer on this page puts it right. What you see and what is recorded are beta.30's; the libraries under them are
newer.
### Changed
- **The remaining library updates** (the owner's request after beta.30, owner decision D72 — inside the seven-day wait
the project otherwise keeps). The .NET 10.0.14 servicing packages the App and the agent use
(`Microsoft.Extensions.Hosting`, `Microsoft.Data.Sqlite`, `System.Diagnostics.EventLog`; beta.30 already carried the
10.0.14 runtime) and Markdig 1.5.0 (its licence text unchanged); for developers, the CsWin32 generator 0.3.367,
Meziantou.Analyzer 3.0.317, `coverlet.collector` 10.1.0 — a test that reads every constant of three assemblies now
leaves out the types the coverage tool adds to them — and Catch2 3.16.1 for the native tests. The SQLite engine stays
3.53.3 (`SQLitePCLRaw` 2.1.13, which `Microsoft.Data.Sqlite` 10.0.14 still declares). Still not taken: FluentAssertions
8, for its licence (`docs/13_CI_CD.md` §Dependabot and the NuGet audit).
+45
View File
@@ -0,0 +1,45 @@
<!-- Moved from CHANGELOG.md's [Unreleased] when 0.1.0-beta.32 was cut, 2026-10-31 (D66). CHANGELOG.md lists every release. -->
## [0.1.0-beta.32] - 2026-10-31
**The thirty-second pre-release: the alpha line's groundwork.** An *alpha* — the same program built on a version of .NET
Microsoft has not finished, .NET 11 first — is published beside the betas from now on, and this beta carries what that
needs; nothing in a beta's measuring changed. The same unsigned installer: verify its hash against `SHA256SUMS.txt`, then
*More info → Run anyway*.
**Updating from `0.1.0-beta.31`:** Help ▸ Check for updates, then *Restart to update* with no game running. The terms
window shows the **EULA 1.6** and the **Disclaimer 2.12** once — each now says the builds are pre-releases, betas *and
alphas*; nothing else in them moved — and the Privacy Policy stays 2.12. The ledger stays at schema 21 and the detection
rules at `2026.10.4`. A beta never updates to an alpha: an alpha is installed only on purpose, from its own release page
(the user guide's new page, *Alpha builds*).
### Added
- **The alpha line** (the owner's request of 2026-10-31, owner decisions D73–D76): an `alpha` branch builds this source
on a prerelease .NET — .NET 11 RC3 first — and publishes it as `x.y.z-alpha.N` pre-releases on an update channel of
their own, so a beta never updates to an alpha and an alpha never to a beta. What the line needs on main changes nothing
in a beta: the `RELEASE_LINE` file and the line every assembly is stamped with (`Shared.BuildLine`), `release.yml`'s
rule that an alpha is tagged on the alpha line and nowhere else and packed on Velopack's `alpha` channel, CI on the
`alpha` branch, and no wiki publish for an alpha (`docs/12_BUILD.md` §The alpha line, `docs/13_CI_CD.md` §The alpha
line, `docs/11_UPDATER.md` §Channels). Whether the main line ever leaves .NET 10 is an open question whose decision
table is written before the evidence (`docs/20_OPEN_QUESTIONS.md` §G, *The main line's .NET*).
- **An alpha says what it is, and asks first** (owner decisions D73 and D74; none of it shows in a beta). Its terms window
shows the **Alpha notice** (`legal/ALPHA_NOTICE.md` 1.0) with the other documents and a box of its own to tick — *I
understand that this is an experimental build and I use it at my own risk* — and Accept waits for it; until it is
accepted the alpha's capture agent does not run. The title bar carries an **ALPHA** badge, a banner says what the build
is at every start, Help ▸ About and `--diag` name the .NET it runs on, and its update channel is locked: an alpha updates
only to newer alphas. It replaces the beta and shares its data, so before it first opens the database it copies it to
`backups\ledger-before-<version>.db` (the newest three are kept) and does not open it if the copy cannot be made. The
user guide has a page for it, *Alpha builds*, and `LIMITATIONS.md` a section.
### Changed
- **The EULA (1.6) and the Disclaimer (2.12) say the builds are pre-releases — betas, and alphas** (owner decision D75):
they said every build was a beta, which an alpha would make untrue. Nothing else in them moved; the terms window shows
them once more after the update. About ▸ Legal documents lists the Alpha notice on every build, for information.
- **What .NET 11's SDK asks of the source, taken where .NET 10 can take it too** (owner decisions D73–D76): the whole
gate run on .NET 11 RC3 before the alpha line was cut found 21 places its analyzers flag — `LastIndexOf`,
`StartsWith` and `EndsWith` of a single character, which .NET 11 overloads with a comparison; string sets and maps
built with `[]`, which C# 15 can give a comparer; one undisposed `JsonDocument` in a test. Each is rewritten in a form
both SDKs compile and that answers exactly as before (ordinal, as it was). Every test suite passed on .NET 11 with no
change of answer (`docs/spike-notes/24-dotnet11-probe.md`).
+71
View File
@@ -0,0 +1,71 @@
<!-- Moved from CHANGELOG.md's [Unreleased] when 0.1.0-beta.33 was cut, 2026-11-03 (D66). CHANGELOG.md lists every release. -->
## [0.1.0-beta.33] - 2026-11-03
**The thirty-third pre-release: games from the Xbox app and the Microsoft Store.** PC Game Pass games included: Import
library finds the games those apps installed, a game's page shows its own logo and splash image, **Play** starts one
through Windows as its Start-menu tile does, and, with your consent, FrameLedger hooks it like any other game. How these
games are laid out, how Windows starts them and what it lets another program read were measured first on the owner's
eleven titles; a hooked session of one is still to be run. The same unsigned installer: verify its hash against
`SHA256SUMS.txt`, then *More info → Run anyway*.
**Updating from `0.1.0-beta.32`:** Help ▸ Check for updates, then *Restart to update* with no game running. The terms
window shows the **Privacy Policy 2.13** once — it names what the Xbox library reads, that Play asks Windows to start
such a game, and the two facts read from a game before any injection; the EULA and the Disclaimer do not change. The
ledger stays at schema 21; the detection rules move to `2026.11.1`, so every game in the library is read again once.
### Added
- **Games from the Xbox app and the Microsoft Store** (the owner's request of 2026-11-03, owner decisions D77–D81; PC Game
Pass games included): **Import library** finds the games those apps installed into a games folder — each drive's
`.GamingRoot` names the folders, each game's own `MicrosoftGame.config` and `appxmanifest.xml` say what it is, and
Windows says whether its package is installed for you — and lists them as **Xbox**, with the process that actually
draws (an Unreal title's shipping executable, not the stub its package launches; never the GDK's `gamelaunchhelper.exe`).
A game's page shows its own square logo and splash image, read from its folder, and its package version (*Xbox version
1.3.5124.0*). Only games built on Microsoft's GDK are listed; an older Store app (UWP) is not (`docs/05_DETECTION.md`
§Platform signatures & metadata, `LIMITATIONS.md`, the user guide). Everything was measured first, on the owner's eleven
titles: the layout, and what Windows lets another program read there — every game executable refuses to be read, so no
Unreal Engine version is shown for these games (`docs/spike-notes/25-xbox-gdk.md`).
- **The detection rules know Xbox games** (rules `2026.11.1`, so every game in the library is read again once): an `xbox`
platform, first in the list — a GDK FINAL FANTASY ships Steam's DLL and read *Steam* — decided by a new signal,
`root_file`, from the install folder's own listing, so a very large install whose deep walk ran short still reads as
its store (`docs/05_DETECTION.md`).
- **Play starts a game from the Xbox app or the Microsoft Store through Windows** (D80), in either Play mode and from an
App running as administrator: the user's shell activates the game's package as its Start-menu tile does
(`explorer.exe shell:AppsFolder\<AUMID>`), because started by its path such a game is never the game in its package —
measured on the owner's titles (`docs/spike-notes/25-xbox-gdk.md`). The capture agent refuses to start one by its path
(`LaunchGame` answers `PackagedGame`), and the game is recorded once it appears, a few seconds after its start
(`docs/04_CAPTURE.md`, `docs/08_UI.md`, `LIMITATIONS.md`).
- **The anti-cheat guard says when a game cannot take the hook at all** (D78), read from the game's own token and code-protection
settings just before the injection: `TargetAppContainer` — an older Microsoft Store app (UWP) — and `TargetMitigation` —
only Microsoft- or Store-signed code, no generated code, a strict or non-CET-blocking user shadow stack, or strict Control
Flow Guard. Neither is a finding: nothing is written to the game, and the session keeps its duration, the sensors and the
reason. Each ended before as a failed injection, a hook that installed nothing, or a risk of ending the game, so no game
that measured before is refused now (`docs/19_SAFETY_AND_ANTICHEAT.md`).
### Changed
- **The Privacy Policy is 2.13**, shown once at the next start: it names what the Xbox library reads — the games folders
`.GamingRoot` names, each game's package files, Windows' answer whether its package is installed for you, and the
pictures a game ships in its own folder — that Play asks Windows to start such a game, and that before any injection
FrameLedger reads whether a game runs in an app container and which of Windows' code protections it runs under. The
EULA and the Disclaimer do not change.
- **The capture path reads a game's executable path one way** (for developers): `TargetResolver`, which finds the game again
just before the guard, read the loader's spelling (`Process.MainModule`) where the watcher had the kernel's, so a game
started through a junction could end `TargetNotRunning` about a process the watcher had just matched. Both read
`ProcessImagePath` now, and the resolver still opens a candidate with the guard's own rights, so a process an anti-cheat
driver closes stays `TargetUnreadable` (`docs/04_CAPTURE.md` §Process watcher).
### Fixed
- **The anti-cheat check saw only part of an Xbox game's folder** (safety): no install-root boundary matched the
`<games folder>\<Game>\Content\` layout, so for an Unreal title's executable, three levels down, check 4 walked only its
`Binaries\WinGDK` folder, and anti-cheat at the root of `Content` would have read clean. A GDK package root — the folder
holding `MicrosoftGame.config` beside `appxmanifest.xml` — is now a boundary for the guard and for detection alike, used
only where no store boundary matched, so it can only widen what is walked. The guard also gained `GamesInstalled\<X>`,
which detection had had alone since #17; one case list read by both test suites now holds the two resolvers together
(`docs/19_SAFETY_AND_ANTICHEAT.md`, `tests/fixtures/install-roots/cases.txt`).
- **The second alpha's release would have stopped at its delta check** (for developers): Velopack names a non-default
channel's packages with the channel (`FrameLedger.App-<version>-alpha-delta.nupkg`), and `release.yml` looked for the
default channel's name. It now takes the delta the pack listed in `assets.<channel>.json`; the betas' packages are named
as before (seen on the `0.1.0-alpha.1` rehearsal, which had no delta to make).
+81
View File
@@ -0,0 +1,81 @@
<!-- Moved from CHANGELOG.md's [Unreleased] when 0.1.0-beta.34 was cut, 2026-11-06 (D66). CHANGELOG.md lists every release. -->
## [0.1.0-beta.34] - 2026-11-06
**The thirty-fourth pre-release: DLSS 5 and DLSS 4.5 named from what the game and the driver did, filters on Games
and Compare, and a Games page that opens at once.** The same unsigned installer: verify its hash against
`SHA256SUMS.txt`, then *More info → Run anyway*.
**Updating from `0.1.0-beta.33`:** Help ▸ Check for updates, then *Restart to update* with no game running. The
Disclaimer (2.13) and the Privacy Policy (2.14) are shown once for you to accept; the EULA does not change. The ledger
moves to schema 22, which a beta.33 cannot open. The detection rules move to `2026.11.2`, so every game in the
library is read again once. DLSS 4.5 under the NVIDIA App's *Dynamic* frame generation reads on sessions you already
have; whether DLSS 5's neural rendering ran is kept for sessions recorded from now on.
### Added
- **Filters on Games and Compare** (owner request 2026-11-06, decision D85). Games: store, engine, state, installed and
played, beside the search and sort, with *Clear filters*; the title counts what is shown of all. Compare: game, tier
and frame generation over every session (it listed the newest 200), with a count; a ticked session stays listed.
### Changed
- **The list of games FrameLedger has been run with is current again** (`docs/LIST_GAME_TESTED.md`, decision D35's
method): refreshed from a copy of the owner's database taken 2026-11-06 and reviewed by the owner — fifteen more
games measured hooked, among them Phantom Blade Zero under the NVIDIA App's *Dynamic* mode, Hogwarts Legacy loading
DLSS 5's runtime and the first two Xbox app games — and the sessions recorded without measurement or refused by the
guard since 2026-09-27. The guide's Settings page says a language change stays on Settings; the closed §S30 notes the
fifth Streamline id decoded (`docs/open-questions/closed-s.md`).
- **The Compare page's layout** (the owner's screenshot): the selection bar beside the list instead of a window's width
away, with *Clear selection*; columns sized to what they hold — *Tier* and *FPS* touched, and wide gaps split the rest —;
the date sorts by when; the settings-changed column says so in words or shows a dash (it was blank); the result
table's session labels sit over their columns.
- **The selected page keeps its name in the left pane** (D86): WPF UI's pane animates the selected item's label away
(Compare's, in the screenshot — every page's while selected); FrameLedger uses a copy of its template without that.
- **Games opens at once from any page** (owner request 2026-11-06: switching to Games stalled 0.5–1.5 s). The window
keeps the library page it built and shows it again on every later visit, reading the library again behind it; the
library is read off the UI thread; the cards appear before the executables are checked — a USB drive that sleeps
took a second or more to answer, and no card was shown until every one had — and each card gets its *Not installed*
pill when its check answers; a read keeps every card that would look the same instead of rebuilding them all; the
list view builds only the rows on screen (`spike-notes` §27).
- **Changing the language keeps the page you are on** — Settings, after a change made there. The App remembered only
the pages it opened from code, so the language changed on Settings came back on the last game page opened
(`src/FrameLedger.App/Services/ShellHost.cs`).
- **DLSS 5 is named where the game ran it** (owner decision D84, amending D64). The owner's Hogwarts Legacy, Neural
Rendering on, loaded DLSS 5's runtime (`nvngx_dlssnr.dll` 310.9.16.0, from the game's folder) and the session could say
only *DLSS 5 runtime loaded* — nothing measured whether it ran. The Overlay's Streamline hook now decodes DLSS 5's
feature (`kFeatureDLSS_NR`, Streamline 2.14) into its own per-frame fact, and the Agent keeps the share of the frames
the game rendered through Streamline that carried it (`sessions.dlss_nr_pct`, **schema 0022** — a ledger this build
migrated no longer opens in an earlier one). Seen running, the DLSS line reads *DLSS 5 (neural rendering on 97.3% of
rendered frames)*, above every other generation; loaded and seen not running, *DLSS 5 runtime loaded, not seen
running*; where nothing could tell (an earlier Overlay, a title outside Streamline), *DLSS 5 runtime loaded*, as
before. Its library is listed with its version and source like the others, its Streamline plugin `sl.dlss_nr.dll`
is recorded when loaded, and a game shipping either file shows *Supports DLSS 5 Neural Rendering* (rules
`2026.11.2`, capability `dlss_nr`). The **Privacy Policy 2.14** names neural-rendering libraries among those whose
versions are read; the **Disclaimer 2.13**'s accuracy block says when DLSS 5 is named. One hook-path change: one more
compare in the `slEvaluateFeature` detour and one more test where a present is recorded (`spike-notes` §26).
- **Streamline's headers are `v2.14.16`'s** (developers): the vendored copy was `v2.12.0`, byte for byte; three of its
eleven files change — `kFeatureDLSS_NR`, the uplift buffer types 70–72, `kStructVersion7`, the version — and
nothing FrameLedger consumed otherwise (`src/native/third_party/streamline/README.md`).
- **A session under the NVIDIA App's *Dynamic* frame generation reads DLSS 4.5** (owner decision D83, amending D64).
Dynamic and its ×6 mode exist only in DLSS 4.5, and the DLSS line named a generation from the measured multiplier
alone: the owner's Phantom Blade Zero under *Dynamic, up to ×3* held ×2.0 and ×3.0 and read *DLSS 4 (a ×3.0
frame-generation state)*. It reads *DLSS 4.5 (Dynamic multi frame generation, set in the NVIDIA App)* where the game's
driver profile sets Dynamic, the driver reports its frame-generation override applied in the game's process, and DLSS
Frame Generation was identified (whether or not its factor was counted); a state measured at ×5 or more still ranks first, and a *Fixed* multiplier names nothing
by itself (The Witcher 3 under Fixed ×6 still presented ×2.0). The game page's chip and the CSV's `# dlss:` line
(`basis=dynamic_frame_generation`) follow; the **Disclaimer 2.13** says so in its accuracy block
(`src/FrameLedger.Domain/Detection/DlssGeneration.cs`, `src/FrameLedger.App/Services/DlssText.cs`; `spike-notes` §26).
- **The guard's source reads in order again** (developers only; no behaviour changes): the note that says what runs only
for a target the anti-cheat evaluation allowed sits above the function it describes again — beta.33's two isolation
checks had come between them — and names that isolation check among what runs
(`src/native/FrameLedger.Injector/src/fl_guard.cpp`).
### Fixed
- **An Xbox game's page no longer fails on a strange picture name** in the game's own `MicrosoftGame.config` (beta.33's):
a name that points at a stream of a file (`a:b.png`) made the search for its scaled variants throw — the page then
showed no picture and logged an error, and an action on the page that reloads it could end in the crash report. Such a
name is no picture a package ships, so it is passed over like a name outside the package
(`src/FrameLedger.Infrastructure/Art/XboxArtCache.cs`). Found by a self-review of #351 and #352 after their gates
passed; no install of the owner's eleven titles has such a name.
+91
View File
@@ -0,0 +1,91 @@
<!-- Moved from CHANGELOG.md's [Unreleased] when 0.1.0-beta.35 was cut, 2026-11-09 (D66). CHANGELOG.md lists every release. -->
## [0.1.0-beta.35] - 2026-11-09
**The thirty-fifth pre-release: accessibility.** An accessibility statement (Help ▸ Accessibility); a screen reader
that reads every control and value in its words and is told what appears; headings and charts it can use; Windows
contrast themes followed; the keyboard following a page shortcut, and a message box opening over the window. And three
places where text read below WCAG's 4.5:1 in a Fluent theme, found on the way: the agent's pill, two kinds of short
message, a destructive button. The same unsigned installer: verify its hash against `SHA256SUMS.txt`, then *More info →
Run anyway*.
**Updating from `0.1.0-beta.34`:** Help ▸ Check for updates, then *Restart to update* with no game running. The legal
texts keep their versions, so nothing is shown for you to accept; the ledger stays at schema 22 and the detection rules
at `2026.11.2`. Nothing about capture or measurement changes.
### Added
- **An accessibility statement** (owner request 2026-11-09, decision D88). `ACCESSIBILITY.md` says what FrameLedger aims
for — WCAG 2.2 at level AA as W3C's WCAG2ICT applies it to desktop software, a goal and not a claim of conformance —
what works with the keyboard alone, a screen reader, a contrast theme or Magnifier, how it is checked (the project's
tests, and the owner's pass of 2026-11-09: keyboard only and Narrator on 0.1.0-beta.34 and 0.1.0-alpha.3, no fault),
what does not work yet and what to do instead, and how a barrier is reported and handled — by severity, with no
promised times. The app shows it under **Help ▸ Accessibility**, and after Limitations in the user guide's window; the
wiki gets an *Accessibility* page.
- **An *Accessibility problem* issue form** (`.github/ISSUE_TEMPLATE/accessibility.yml`) asking what was tried, what
happened and what the reporter uses — never anything about the reporter themself — and a user-interface section in the
pull-request template. The `accessibility` label exists, and so do `safety` and `priority-high`, which the *Safety gap*
form had named since its first day without either existing — so GitHub had never applied them.
- **A screen reader reads what the window shows** (decision D88's goal; measured in the UI Automation tree WPF builds on
every page, window and dialog, every tab — `PagesLoadTests.Automation`). Drop-down options were read as an internal
record (*Choice { Value = dark, Label = Dark }*), lists and table rows by their program names, table cells drawn by a
template as *Item: …, Column Display Index: n*, and the terms window's list by each document's whole text; each now
reads the words it shows, and an empty cell reads *empty*. The frame-rate readout says Native, Displayed and the
factor together (CLAUDE.md rule 6, in speech), a ray-tracing chip its value and where it came from, a change badge its
number. The safety notices' title and message reach a screen reader (they were hidden inside the notice's template),
and the notice's button says which notice it answers. A button repeated on each row names its row (*Open: …*, *Play:
…*, *Turn off: …*). Tab no longer stops on pictures, lists, Settings' rows, the FPS readout, the chips or the dialog
host, where it found nothing to say; an expander's button is named after its header.
- **A screen reader is told what appears** (owner decision D89): a safety notice as it arrives, the capture agent going
offline and coming back, an update's steps (not each percent), every short message at the bottom of the window, a
notice on a game's page and each result of Tools ▸ Database maintenance — in the words shown, and only while
FrameLedger's window is the active one, so a game that has the screen is never interrupted. The database line's live
region, which announced nothing, is gone.
- **Headings and charts a screen reader can use** (owner decision D90). Every page's title is a first-level heading and
each section title a second-level one, so a screen reader's heading keys move between sections. Every chart says what
it is and where its numbers are written as text; its keys — arrows to move, Ctrl with an arrow to zoom, A to see all of
it — now stay with the chart instead of also scrolling the page or moving the focus on, and its focus is drawn. No
chart tells two series apart by colour alone any more: Compare's five sessions, the GPU's temperature and its hot spot,
the two kinds of stutter, the two lows and the two limits each have their own line pattern, marker or hatch.
- **Windows contrast themes are followed** (owner decision D91). With a contrast theme on — Aquatic, Desert, Dusk, Night
sky, or one whose colours were edited, on Windows 10 or 11 — every colour in FrameLedger's windows is one of that
theme's, whatever Settings ▸ Theme says, and it changes the moment the theme is turned on, edited or turned off;
Settings ▸ Theme says so under its box. Before, *System* could apply WPF UI's own high-contrast files, most of whose
colours are a red placeholder, and the next window opened put the light or the dark theme back. The charts draw in the
theme's colours, their patterns telling the series apart; the frame-generation, ray-tracing and upscaler chips are the
theme's highlight and its text (WPF UI's files put the window text there, 1.26–1.78:1); a destructive button is the
theme's own button; a pressed menu item is no longer white on white; nothing is drawn translucent, and a game's picture
lends its page no colour, as before.
- **The keyboard follows a page shortcut.** **Ctrl+1** … **Ctrl+5** now move the focus into the page they open — its
first control — and a screen reader hears the page's title; before, the focus stayed where it was, often on the page
that had just gone, and Tab began again at the top of the window.
- **Pages no longer slide in while Windows' animation effects are off** (Settings ▸ Accessibility ▸ Visual effects),
followed as the setting changes.
### Fixed
- **A message box opens over FrameLedger's window** — Remove game, Delete sessions, the database's and the update's
questions. It had no owner, so it could fall behind the window it came from and, closing, give the focus to another
program; it is owned by the window that opened it now, and the focus comes back there.
- **A double-click on a chart shows all of it again**, as the user guide said; it toggled ScottPlot's render-time overlay.
- **The capture agent's state in the title bar reads in the light theme.** It was drawn on WPF UI's fixed green, blue,
orange and red under white — 2.78, 2.63, 2.16 and 3.68:1 — and is on the theme's own success, caution and critical
fills now, as the notices are; its words say the state.
- **The short messages at the bottom of the window read.** A *done* or a *warning* message was white on a fixed green or
orange, 2.78:1 and 2.16:1 in both themes; every message is in the theme's colours now, its icon saying which kind.
- **A destructive button's label reads in the dark theme** — Remove on a game's page, Delete in the confirmations: the
theme's dark text on the red, 5.3:1 and 5.7:1, where white read 3.68:1.
### Changed
- **Documents corrected**: charts do take focus and keys (`docs/08_UI.md` said neither — `ChartKeyboardTests` measures
it); the database-maintenance result's live region announced nothing, since WPF raises one only when the app does; the
"no Narrator pass" gap is the owner's pass now, beside what that pass could not show; the open question "Accessibility
/ DPI: no design anywhere" is closed; NFR-9 names screen readers and contrast themes (D88–D91). `LIMITATIONS.md` gains an
*Accessibility* section and loses its one struck sentence — a screen reader reads struck text as current, so no page
the app shows strikes text through. The guide's menu table names its menu on every row, read one row at a time.
+41
View File
@@ -0,0 +1,41 @@
<!-- Moved from CHANGELOG.md's [Unreleased] when 0.1.0-beta.36 was cut, 2026-11-10 (D66). CHANGELOG.md lists every release. -->
## [0.1.0-beta.36] - 2026-11-10
**The thirty-sixth pre-release: the same software, its C# read by a second analyser and tidied.** Nothing you see,
record or measure changes. Qodana — JetBrains' code analysis — now reads the C# and the XAML of every change, and what
its first run reported is settled: about 400 small corrections in the code, none changing what the program does. The
same unsigned installer: verify its hash against `SHA256SUMS.txt`, then *More info → Run anyway*.
**Updating from `0.1.0-beta.35`:** Help ▸ Check for updates, then *Restart to update* with no game running. The legal
texts keep their versions, so nothing is shown for you to accept; the ledger stays at schema 22 and the detection rules
at `2026.11.2`. Nothing about capture or measurement changes.
> **Added the day of the release, after the tag (2026-11-10).** The package carries the **.NET runtime 10.0.15**, where
> beta.35's carried 10.0.14: the release was built with SDK 10.0.404, November's servicing release, which the build
> machine had that day (10.0.403 the day before), and `global.json` lets a build take the newest 10.0 SDK. Nothing in
> FrameLedger's own code asked for it, and the notes above did not name it when the tag was cut. It is why the update
> from beta.35 replaces 343 of the package's 456 files (a 5.8 MB download). The NuGet libraries stay at their 10.0.14
> versions.
### Changed
- **Qodana reads the C# and the XAML from CI** (developers only; owner decision D93). The owner made the project on
Qodana Cloud and set the `QODANA_TOKEN` secret; `.github/workflows/qodana.yml` is JetBrains' workflow for its Qodana
Scan action, changed where FrameLedger differs: the linter is Qodana Community for .NET — ReSharper's inspections in
a Linux container, which runs under every licence, where the Rider-based linter needs the Ultimate licence the
organisation holds only as a 30-day trial — over `FrameLedger.slnx`, with `EnableWindowsTargeting` passed to the
container so that the Windows-only projects build and load there; the action is pinned to a commit; the job's
permissions are the ones it uses. It reads no C++ (CodeQL and SonarCloud do). Its gate is zero problems
(`qodana.yaml`), and it is advisory: a red job beside a green `check`, never a blocked merge. An inspection that
argues with a choice this project made is switched off in `.editorconfig`, where Rider reads it too, with the reason
on the line above — sixty-three keys (`docs/13_CI_CD.md` §Qodana).
- **What Qodana's first run reported is settled** — 3,679 problems, 2,050 of them the missing-XML-comment warning the
project had already made a suggestion. About 400 were fixed in the code, in 181 files, none changing what the
software does: redundant qualifiers, casts, `using` directives, `!` suppressions and `unsafe` modifiers removed (290);
`var` for built-in types and one-line block bodies brought to `.editorconfig`'s own style (52); every XAML item
template names its `DataType`, and a binding that reached its page through `DataContext.ViewModel` names the page's
type (35), so the editor resolves them; two fields nothing read (`LogsViewModel`, `PipeServer.Client`), two
initialisers a constructor overwrote and an unused parameter removed; `SpokenTextAutomationPeer` no longer assumes
the base peer's name is a string. The members nothing in the solution uses are listed in `docs/13_CI_CD.md` §Qodana
and left as they are.
+77
View File
@@ -0,0 +1,77 @@
<!-- Moved from CHANGELOG.md's [Unreleased] when 0.1.0-beta.37 was cut, 2026-11-11 (D66). CHANGELOG.md lists every release. -->
## [0.1.0-beta.37] - 2026-11-11
**The thirty-seventh pre-release: FrameLedger runs on .NET 11.** The same program, built on .NET 11.0.0 — released the
day before — where every beta until now was built on .NET 10 (owner decision D94). Nothing about how a game is measured
changes: the part of FrameLedger loaded into a game is native code, and it is 0.1.0-beta.36's. What changes is what
FrameLedger needs from your PC, and two of its legal texts. The same unsigned installer: verify its hash against
`SHA256SUMS.txt`, then *More info → Run anyway*.
**Before you update from `0.1.0-beta.36`, three things:**
- **Your processor.** .NET 11 does not start on a processor without SSE4.2 and POPCNT. Every processor Windows 11
accepts has them; one from before about 2010 may not. On such a PC this version installs and then does not start, and
0.1.0-beta.36 cannot check that for you. Installing 0.1.0-beta.36 again brings FrameLedger back, with your data as it
was.
- **Windows 10.** Microsoft supports .NET 11 on Windows 11, and on Windows 10 only in its LTSC and IoT editions.
FrameLedger does not block Windows 10 22H2 — but it has never been tested there, on any version, and nobody supports
it there (D95).
- **The update is a large download** — about 70 MB, where a usual one is a few: the .NET runtime inside the package is
replaced whole.
Then: Help ▸ Check for updates, and *Restart to update* with no game running. **The terms window appears once**, with
the **EULA 1.7** and the **Disclaimer 2.14** to accept — what an alpha build is, now that .NET 11 has shipped, and a
paragraph on Windows and the processor. The ledger stays at schema 22 and the detection rules at `2026.11.2`, so going
back to 0.1.0-beta.36 is installing it over this version.
**For anyone on an alpha:** `0.1.0-alpha.4` follows this release on the same .NET 11.0.0, and after it the alphas pause
— install the beta (`guide/11-alpha-builds.md`).
### Changed
- **FrameLedger runs on .NET 11** (owner decisions D94 and D95, 2026-11-11). The betas are built on .NET 11.0.0 —
released 2026-11-10 — where they were built on .NET 10: SDK 11.0.100, `net11.0-windows10.0.22621.0`, and the three
libraries serviced with the runtime (`Microsoft.Extensions.Hosting`, `Microsoft.Data.Sqlite`,
`System.Diagnostics.EventLog`) at 11.0.0. The runtime is inside the package as before; nothing is installed beside
it. **What a user should know:** Microsoft supports .NET 11 on Windows 11, and on Windows 10 only in its LTSC and
IoT editions — FrameLedger does not block Windows 10 22H2, and it is untested and unsupported there; **on a
processor without SSE4.2 and POPCNT it no longer starts** (every processor Windows 11 accepts has them); the
ledger's schema is unchanged, so installing 0.1.0-beta.36 again is a way back. The part of FrameLedger loaded into
a game is native code and does not change. `docs/12_BUILD.md` §The main line's .NET says what decided the move
and what was set aside.
- **The capture agent ends with a crash report when a piece of its own background work fails**, where it used to
stop and exit as if nothing had happened: .NET 11 passes that failure on, and the Agent's existing crash path — a
Fatal log entry and a crash dump — takes it. Nothing was added for it (`docs/10_LOGGING_AND_BUG_REPORTS.md` §Crash
handling).
- **The NuGet licence texts follow the package set** (`legal/licenses/nuget/`, 69 packages where there were 78):
nine `Microsoft.Extensions.*` libraries are part of the .NET 11 runtime, and SQLite's engine is SourceGear's
`SQLite` package through SQLitePCLRaw 3.0.5.
- **For developers:** `release.yml` installs a .NET 10 runtime beside the SDK for `vpk` 1.2.161, which has no build
that runs on .NET 11 alone; Qodana's container installs the .NET 11 SDK before it builds (an interim, until the
Ultimate linter); two `string.StartsWith`/`EndsWith(char)` calls in the App's tests name the comparison .NET 11's
analyzer asks for; `HostBackgroundFailureTests` holds .NET 11's `IHost.RunAsync` behaviour.
- **What an alpha is, now that .NET 11 has shipped** (owner decisions D97 and D98). 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 this version — so an alpha is now described as *a beta's source built to try a newer version of
.NET, at times a prerelease one*: **EULA 1.7** (§2B), **Disclaimer 2.14** (§0, which also gains a paragraph on
Windows and the processor), **Alpha notice 1.1** (what an alpha is, the hardware, and a new part on the pause), the
accuracy statement's line, the guide and `LIMITATIONS.md`. The terms window shows the EULA and the Disclaimer once
more; an alpha asks for its notice's tick again.
- **The alphas pause after 0.1.0-alpha.4, and a paused alpha says so** (D98). With the betas on the same .NET there is
nothing for an alpha to try, so none is published until a newer .NET has a preview — and a paused alpha gets no
update, the anti-cheat list included, which reaches FrameLedger only inside one. An alpha cut while the line rests
shows, above every page, that the line is paused and to install the latest beta; the words "a prerelease .NET" now
appear only in an alpha that really runs on one. For developers: `FlAlphaLineRests` in `Directory.Build.props`,
stamped into every assembly, `Shared.AlphaLine`, `App/Services/AlphaTexts`; three new strings in en, vi and ja.
- **.NET 11's API where it reads better, and no C# 15 syntax yet** (developers only; owner decision D96). Sixteen
`char` searches name their comparison through the `string` overloads .NET 11 adds
(`StartsWith`/`EndsWith`/`LastIndexOf(char, StringComparison)`) where they went through a span to satisfy both .NET
10 and 11, and the App finds the Agent it started with `Process.TryGetProcessById` instead of a caught exception;
nothing changes in what the software does. **C# 15's constructs were asked for and are not used**: each was tried in
a file of its own, and ReSharper's engine — what Qodana runs — reads none of the four (it does not parse `closed`
or `union`, and calls collection expression arguments and labeled jumps preview features), so every file using one
would be an error on a gate of zero; a union also draws a warning from the SDK's own analyzers.
`docs/13_CI_CD.md` §C# 15 and the analyses holds the table and what unblocks each; `docs/spike-notes/29-…` where
each would go. `codeql.yml` takes `workflow_dispatch`, so a branch can have a full analysis — a pull request's C#
analysis is an overlay on `main`'s database.
+70
View File
@@ -0,0 +1,70 @@
# HANDOFF history — 0.1.0-beta.24
*Moved verbatim from `docs/HANDOFF.md` when 0.1.0-beta.25 was cut, 2026-10-19 (owner decision D66); `docs/HANDOFF.md` §How this file is split lists every part. Nothing below was edited, so its "below" and "above" point inside the original file.*
## **START HERE** — 2026-10-19, 0.1.0-beta.24: every frame-generation state, the NVIDIA App's quality mode, which DLSS ran, SonarCloud, the documents split
*Status is `docs/changelog/0.1.0-beta.24.md`; this is what no other file carries.* The owner, 2026-10-19: "Bạn xem xét,
đánh giá và lên plan cho bản beta mới với những nội dung như sau:" — six items: the mix of frame-generation modes inside
one session, shown in the App; the upscaler's quality mode (Ultra Performance … DLAA, FSR's too) only when captured, the
NVIDIA App's override as the standard where there is one; SonarCloud fixed and its false positives marked; a SonarCloud
configuration that keeps third-party headers out; which DLSS is in use (3, 4, 4.5, 5), if it can be found; the long
documents split — then, with the plan approved, the whole train to the release without asking again. Later the same
day: "Bạn có thể xét tới trường framegen chỉnh trong setting in-game nếu chưa có" (the frame generation chosen in the
game's own menu). Answers that set the decisions below, given before the plan: the mix as a share bar and a table; the
owner marks Sonar's false positives in its UI from a list we write; all four long documents split; the override is the
standard only where the driver confirms it applied; DLSS labels bound to evidence; FSR's mode through `ffxQuery` as a
separate PR that may slip; owner-only items 7–11 and 13 not yet run; Dependabot #314 rebased and merged in the train.
**Decisions:**
- **D62 — the mix.** Every frame-generation state a session held, each with its own factor, Native → Displayed and its
share of the presenting time, then *no frame generation* (only where a counted `none` is allowed) and *not
classified*; never an average across states (CLAUDE.md rule 6, amended). Computed at finalize over the steady state's
own five-second windows and stored (`sessions.fg_mix`, schema 0020); sessions recorded before have none and are not
rebuilt. Above the rows, how frame generation was set — the NVIDIA App's Dynamic / Fixed from the stored driver
profile, or the game — as configuration, never as a row. The multiplier chosen in a game's menu is not read (§2b's
refusal stands); the measured row is its evidence.
- **D63 — the NVIDIA App's override is the quality mode where the driver reports it applied** (`03_METRICS`
§Upscaling, amended; `QualityResolver`, read at display time, so sessions recorded before resolve alike). Otherwise
the mode the game passed to a hooked call; otherwise none; never the game's own value under an override.
- **D64 — DLSS labels are evidence-bound** (`05_DETECTION` §DLSS generation): each library's version and folder class
(`sessions.runtime_module_sources`, schema 0021 — never the path), the preset the driver reports applied, DLSS 4 /
4.5 only from a preset or a measured multi-frame factor, DLSS 5 only as "runtime loaded".
- **D65 — FSR's quality mode through `ffxQuery`: deferred to the next beta.** The plan allowed it to slip, and it was
kept out of this train — a new hook on four FidelityFX modules, a hook-family bit in the shared layout, a new byte
encoding, the stubs and the harness, on the hook path rule 5 guards — rather than written against the release.
ACCURACY's FSR clause did not ship with it. The design stands in the plan: query → the five (mode, size) pairs → the
mode whose size the game then dispatched. The owner asked for it as 0.1.0-beta.25 the same day.
- **D66 — the long documents are split**, every original path kept as the index of its parts, moved byte for byte
(`tools/docs-split-check.ps1`; `release-notes.ps1` reads `docs/changelog/<version>.md`).
- **D67 — SonarCloud stays on Automatic Analysis** with `.sonarcloud.properties`; the by-design rules and false
positives are listed in `13_CI_CD` §SonarCloud for the owner to mark in its UI.
**Measured on the owner's ledger** (a read-only SQLite backup copy — never the data folder): **the NVIDIA driver's
`performanceMode` is in NGX's own numbering, not the profile's** — Silent Hill 2 (2026-10-13) ran under the App's Ultra
Performance (profile value 5) and the driver reported 3; `NvidiaOverrides.DriverLine` had read it through the profile's
table since beta.8 and dropped the mode. The same session's SR word has no `CREATED | EVALUATE` (no mode is claimed),
its FG word applied ×6 and the session measured a ×6.0 steady state, and **none of the override's libraries carried a
census name** — the module snapshot now records everything under `%ProgramData%\NVIDIA\NGX`. Bit 19 is set on a working
override (Expedition 33's `0x8067F`) and bit 1 with no override at all (`0x60F`): only `PERF_MODE`, `SR_DLAA_MODE` and
`SCALING_RATIO` say an override applied. The App's global profile stores `NGX_DLSSG_DYNAMIC_MULTI_FRAME_COUNT_MAX = 5`.
**Traps met on the way:**
- **`gh pr merge --squash --delete-branch` on a stacked PR closes the PR based on it** (#319), and a closed PR cannot be
reopened once its head was force-pushed. Recovery: push the base back, push the head back to the SHA it closed at,
reopen, retarget to `main`, push the rebased head, delete the base. Instead: retarget the next PR to `main` first,
merge without `--delete-branch`, rebase the rest (`git rebase --update-refs --onto origin/main <old tip>`, in a
temporary `git worktree` when the checkout is busy), then delete the merged branch.
- **Dependabot closed #314 itself** after `@dependabot rebase` ("updatable in another way") and did not answer
`@dependabot reopen`; the two analyzer versions it proposed went into the release PR by hand.
- **SonarCloud's PR gate fails on new `cpp:S8417`** (explicit memory orders, by design): not a required check; the
optional ignore row in `13_CI_CD` §SonarCloud stops it.
- **A Domain.Metrics enum must be listed in `MetricEnumMirrorTests`** (mirrored or explicitly local), **every enum needs
a zero member** (CA1008), **private consts in tests take the `_` prefix** (IDE1006 is `dotnet format`'s, not the
build's), and **`null` literals make overloads ambiguous** across a `string?` and a record parameter.
- **Python strings in the scratch scripts read `\N` as an escape** — a Windows path in a C# comment written through a
Python script needs its backslashes doubled, and a Bash heredoc halves them (the beta.23 trap again).
**Owner-only, added to the list below:** item 20.
+42
View File
@@ -0,0 +1,42 @@
# HANDOFF history — 0.1.0-beta.25
*Moved verbatim from `docs/HANDOFF.md` when 0.1.0-beta.26 was cut, 2026-10-19 (owner decision D66); `docs/HANDOFF.md` §How this file is split lists every part. Nothing below was edited, so its "below" and "above" point inside the original file.*
## **START HERE** — 2026-10-19, 0.1.0-beta.25: FSR's quality mode
*Status is `docs/changelog/0.1.0-beta.25.md`; this is what no other file carries.* The owner, 2026-10-19, while the
beta.24 train was merging: "Bạn có thể publish beta24 xong, làm phần pr9 thành beta25 luôn nếu được nhé." — publish
beta.24, then the train's PR-9, FSR's quality mode, as beta.25. One feature PR (#325) and this release, the whole
way without asking again.
**Decisions:**
- **D65 — FSR's quality mode through `ffxQuery`: built** (deferred from beta.24,
[`handoff/history/0.1.0-beta.24.md`](handoff/history/0.1.0-beta.24.md)). The query is hooked on the four modules
`ffxDispatch` is, each answer the vendor returned is kept (one slot per mode), and an UPSCALE dispatch whose sizes fit
exactly one answer names it as `0x10 + mode` (`03_METRICS` §Upscaling, `17_HOOK_ENGINE` §Hook inventory). **One rule
the plan did not have:** a session, a segment or the live window names FSR's mode only when no FSR frame was rendered
at a size no named frame has (`Domain.Metrics.QualityByte`). Without it a dynamic-resolution session whose top of
range matched an answer would have named the mode, against the clause approved with the plan ("FSR at a dynamic
resolution among them — no mode is shown"). The clause shipped in those words; the Disclaimer stays 2.11, as the
accuracy statement's additions did in beta.19 and beta.20.
**Measured:** on the hook harness, with the vendor stub answering as the SDK documents (`fl_guard` "FSR's quality
mode", 44 assertions): Quality named on every params record but at most one — the test allows the window's first —
through the SDK 2.x loader by size and through the 1.1.x monolith by ratio, and no record named any other mode; the
same five FFX cases ran five more times green. The added cost, from a copy of the two bodies built with the
Overlay's flags (`/O2 /guard:cf /Qspectre /MT`, 20 M calls × 3, every slot holding a size and a ratio — the worst
case): 7.6–8.2 ns per UPSCALE dispatch, 1.6 ns per query beside the trampoline. Nothing on a real title yet: item 21.
**Traps met on the way:**
- **`git rebase --update-refs` skips a branch checked out in another worktree.** The beta.25 branch sat on beta.24's
PR-8 tip in its own worktree; the rebase of beta.24's train after its first merge left it where it was, and it was
moved by hand (`git rebase --onto <new tip> <old tip>`) onto the release PR, then onto `main` as beta.24 merged.
- **A new `.cs` file written as LF fails `dotnet format`'s `ENDOFLINE`** although it builds and its tests pass —
convert it to CRLF before the gate (the checkout is CRLF).
- **A per-frame byte is not a session's answer.** The modal of the told bytes was right for Streamline's byte and wrong
for one that is told only on the frames whose size matches; read every surface's rule against the sentence the user
is promised before writing the byte.
**Owner-only, added to the list below:** item 21.
+37
View File
@@ -0,0 +1,37 @@
# HANDOFF history — 0.1.0-beta.26
*Moved verbatim from `docs/HANDOFF.md` when 0.1.0-beta.27 was cut, 2026-10-20 (owner decision D66); `docs/HANDOFF.md` §How this file is split lists every part. Nothing below was edited, so its "below" and "above" point inside the original file.*
## **START HERE** — 2026-10-19, 0.1.0-beta.26: a ×1336 frame-generation state, fixed
*Status is `docs/changelog/0.1.0-beta.26.md`; this is what no other file carries.* The owner ran the installed
beta.25 the evening it shipped and sent screenshots: "Bạn có thể thử kiểm tra kết quả (fix nếu cần), cập nhật docs,
làm chip và trigger lại sonarcloud thử nhé." Silent Hill 2's summary listed a ×1336.0 frame-generation state; the owner
pointed at the cause ("có khoảng thời gian đầu game đang biên dịch shader") and then: "Bạn có thể cân nhắc (nếu thực sự
cần) bản beta26 fix lỗi nhé." It was needed: every beta.25 session of a title that compiles its shaders under a loaded
frame-generation runtime can store such a row, and the summary and the DLSS line print it. #327 (the fix and the
owner's runs), #328 (the SonarCloud chip — the owner marked the last six issues the same day, and `main`'s quality
gate passes) and this release.
**No new owner decision.** The fix makes the window rule say what `03_METRICS` already promised ("windows with too few
frames to read") about APPLICATION frames, not presents, and bounds the ratio at ×8 (`FgWindow.GenerationCeiling`) —
no shipping frame generation passes ×6; the bound is raised only with a title measured above it. A stored mix is read
by the same rule, so no session is rewritten and none keeps the row.
**Measured on the owner's ledger** (a read-only backup copy, decoded with the App's own loader in a scratch test): the
×1336.0 row was Silent Hill 2's first fifteen seconds — 1,369, 4,877 and 1,303 presents with 1, 0 and 1 application
frames per five seconds, then a 13,348 ms frame: the game compiling its shaders at start (the owner). The only stored
value above ×8 in 60 sessions. Lies of P read no FSR mode with `ffxQuery` hooked (bit 11 in `hooks_installed_mask`):
item 21's first branch (`spike-notes` §22).
**Traps met on the way:**
- **A row written by a released build is read by every later one.** Changing what makes a state changes nothing on a
stored session unless its reader applies the rule too (`FgMixRecord.Parse`); the row would keep the old meaning.
- **A session's timeline is one scratch test away**: `SessionSeriesLoader` over a ledger copy prints presents,
generated and application frames per five seconds (a `PagesLoadTests` partial, never committed). Decoding the blobs
by hand is not needed.
- **SonarCloud's PR analysis lists only issues new in the PR**: whether a change clears a finding on `main` shows only
in `main`'s next analysis.
**Owner-only:** items 20 and 21 annotated (`spike-notes` §22); nothing added.
+49
View File
@@ -0,0 +1,49 @@
# HANDOFF history — 0.1.0-beta.27
*Moved verbatim from `docs/HANDOFF.md` when 0.1.0-beta.28 was cut, 2026-10-20 (owner decision D66); `docs/HANDOFF.md` §How this file is split lists every part. Nothing below was edited, so its "below" and "above" point inside the original file.*
## **START HERE** — 2026-10-20, 0.1.0-beta.27: the owner's eight sessions of 2026-10-20
*Status is `docs/changelog/0.1.0-beta.27.md`; this is what no other file carries.* The owner ran the installed
beta.26 the morning after it shipped: "Bạn có thể kiểm tra kết quả ở khoảng 8 kết quả gần nhất. Sửa luôn 2 test flake
luôn trong phiên này và fix bug, publish bản mới nếu có bug." — and, mid-way: "1. cyberpunk 2077 là switch in-game.
2. Fix bug mở xem 1 session nhiều lần ra nhiều cửa sổ." — then, on the Steam hand-off: "bạn có thể lựa chọn: note vào
giao diện UI là các game trên Steam sẽ tự trigger Steam trước / Thêm Setting cố định trên game Steam là luôn chạy qua
steam client". #330 (six fixes, the Steam note, the two flaky tests, `spike-notes` §23) and this release.
**No new owner decision.** Each fix makes the code do what a document already said: a state is a frame generation's
whole multiplier (`03_METRICS` §The mix), the driver's report is the session's and not the dead pid's (§The
driver-reported rung), a game started again is recorded (`04_CAPTURE`, beta.15) — after a launch too —, a summary is
one window, the display sizes are the ones seen.
**The owner's two ways for Steam games, and the one taken.** The owner offered a note in the UI or a fixed rule that
Steam's games always go through the Steam client, and left the choice open. The note was taken (`08_UI` §Games, Play):
the rule would have cost what *Start directly* exists for — three of the five Steam games started directly on
2026-10-20 ran and were measured from their first frame, and a Vulkan game is measured only when FrameLedger starts it
(Everhex Demo, a Steam game). Not every Steam game hands itself to Steam: Lies of P did, Expedition 33 closed instead.
**One question for the owner, not taken:** the crash safety counts a direct start's early exit — Lies of P handing
itself to Steam, Expedition 33 closing within five seconds even unhooked — and two such starts turn hooking off for
the game (`19_SAFETY` §Crash & stability safety, measured `spike-notes` §23). The policy cannot tell a hand-off from
the hang it exists for, so it stands, and users are told to start such a game through its store. An exemption — an
exit followed by the same executable within seconds — would loosen a safety rule and is the owner's to decide.
**Measured on the owner's ledger** (a read-only backup copy, the App's own loader in a scratch test): of 70 sessions,
the ×2.52 row was the only stored state between two multipliers; none of the 14 sessions the driver answered kept
`CREATED | EVALUATE` (Expedition 33: `0x8067F` while it ran on 2026-09-06, `0x8007F` stored); two Lies of P and three
Dark Souls III sessions stored no window size.
**Traps met on the way:**
- **A probe taken after the target exits is not the session's.** NVIDIA's driver still answers for a dead pid, with
the bits that say a feature ran cleared; any per-process question asked at a session's end must check that the game
still lives (`CaptureSession`'s last snapshot), or the last answer erases the session's.
- **A launch's own process reaches the watcher after the launch began**, so it lands among the processes turned away
"one at a time"; whatever acts on those must leave out the launch's own pids (`Running.Targets`).
- **The logs are the timeline of what the owner did**: `ui-*.log`'s `play:` lines say *through the agent* (Start
directly) or *through steam*; `agent-*.log` has every session's end, a discarded one included — the ledger keeps no
row for it. A hooking switch the user flips leaves no line: say what the logs show, not why hooking was off.
- **Decode the windows before naming a cause**: the ×2.52 windows' runs — 251 application frames followed by one
generated frame, 270 by two — showed the stepping at a glance.
**Owner-only:** items 20 and 21 annotated (§23); item 22 added.
+31
View File
@@ -0,0 +1,31 @@
# HANDOFF history — 0.1.0-beta.28
*Moved verbatim from `docs/HANDOFF.md` when 0.1.0-beta.29 was cut, 2026-10-25 (owner decision D66); `docs/HANDOFF.md` §How this file is split lists every part. Nothing below was edited, so its "below" and "above" point inside the original file.*
## **START HERE** — 2026-10-20, 0.1.0-beta.28: the Dashboard with two or more games
*Status is `docs/changelog/0.1.0-beta.28.md`; this is what no other file carries.* The owner, while beta.27 was being
released: "Thêm cơ chế hiển thị UI/UX Dashboard khi chạy >=2 game trong cùng 1 thời điểm nếu được nhé." and "Bạn có thể
chờ beta27 xong xử lý tiếp luôn bản 28 nếu được." #332 (the cards) and this release, the same day as beta.27 — whose
section, with the open crash-safety question, is `handoff/history/0.1.0-beta.27.md`.
**No new owner decision.** The Agent always recorded one session per executable, so two games were two sessions; the
Dashboard's one live card went to a hooked session and kept it, and the other game read only as *Running sessions: 2*.
Each running session now has its card (`08_UI` §Dashboard).
**Choices made here** — the owner asked for a way to show them, not for a layout: a card per session, each read the
way the one card was, rather than one large card and a list of the rest; hooked sessions first, each kind in the order
it started, a card moved rather than rebuilt when its place changes; two to a row from two on; the header counts the
games from two on. The machine's temperatures repeat on every card: each session's tick carries them.
**Traps met on the way:**
- **C# written from a Python string**: `@"D:\another\…"` in a non-raw Python string turned `\a` into BEL inside a test,
and the test still passed — both of its paths were mangled alike. Write C# through raw strings, and scan a diff for
control characters before committing.
- **An items panel binds to the page**: inside an `ItemsPanelTemplate`, `{Binding ViewModel.LiveColumns}` reads the
ItemsControl's DataContext — the page — so the panel's column count is the page view model's.
- **A page rendered for a look has no background of its own**: under the dark theme the light text is drawn on
transparency. Read the light render, or put the page on a `Border` with `ApplicationBackgroundBrush`.
**Owner-only:** item 23 added; beta.27's item 22 and the crash-safety question stand.
+93
View File
@@ -0,0 +1,93 @@
# HANDOFF history — 0.1.0-beta.29
*Moved verbatim from `docs/HANDOFF.md` when 0.1.0-beta.30 was cut, 2026-10-26 (owner decision D66); `docs/HANDOFF.md` §How this file is split lists every part. Nothing below was edited, so its "below" and "above" point inside the original file.*
## **START HERE** — 2026-10-25, 0.1.0-beta.29: SonarCloud from CI, and the libraries Dependabot never updated
*Status is `docs/changelog/0.1.0-beta.29.md`; this is what no other file carries.* The owner, 2026-10-25: "Bạn phân tích
và bắt đầu cho chuyển từ automatic sang ci analysis sonarcloud (ver mới nhất) cho repo, bạn có thể bắt đầu 1 mạch cho
đến khi kết thúc, nếu có issue hay coverage chưa đạt, tiếp tục cho đến khi xong nhé." and "Cập nhật
depenabot/audit/code scanner nếu có." — `SONAR_TOKEN` set and Automatic Analysis off beforehand; with the plan approved,
the whole train to the release without asking again. #334 (SonarCloud from CI, Dependabot, the audit, CodeQL), #335
(the libraries), #336 (the 34 C++ issues `main`'s first analysis from CI raised) and this release.
**Decisions:**
- **D68 — SonarCloud is analysed from CI** (`13_CI_CD` §SonarCloud): `ci.yml`'s `sonarcloud` job after `check`,
advisory, waiting for the gate; SonarScanner for .NET 12.0.0 as a local tool; `SonarQube.Analysis.xml` instead of
`.sonarcloud.properties`; the gate's own coverage (OpenCover beside Cobertura); the C++ through CMake's compilation
database; `sonar.projectVersion` the newest release tag, so new code is everything since the last release; `S8417`
and `S6640` ignored where they apply by design. Replaces D67.
**Choices made here** — the owner asked for the switch, not for a design:
- **A job after `check`, not steps inside it**: the scanner turns warnings-as-errors off in the build it wraps, and a
required `check` should not go red on a SonarCloud outage. The coverage is the gate's own (an artifact), not a
second test run.
- **The C++ through MSBuild items, not a second SonarCloud project**: one project keeps the history and the owner's
marks of both languages; the items exist only under the scanner.
- **The version is the newest release tag**, so the project's own *Previous version* setting means "since the last
release"; no setting in SonarCloud's UI changed.
- **The two by-design rules became configuration** (`S8417`, `S6640`), as the optional row of the old owner's steps
proposed. The 34 C++ issues of `main`'s first analysis from CI were settled line by line instead (#336): fixed where
the code was wrong, `// NOSONAR` with its reason above it where the analyser was — five of them; no rule was
switched off for them.
- **Dependabot's missed updates by hand, under the cooldown it now keeps**: CsWin32 0.3.363 rather than the three-day-old
0.3.367; Meziantou left to Dependabot, which does propose analyzers; Markdig, Velopack and FluentAssertions 8 not
taken; `coverlet.collector` kept at 10.0.1 (below).
- **CodeQL reads the workflows** (`actions`), not required.
**Measured on the way** (`13_CI_CD` §SonarCloud, *The first analyses* and *`main`'s first analysis from CI*): the
scanner's 12.0.0 source, not its documentation, answered the three design questions — it forces
`TreatWarningsAsErrors=false`, it drops `sonar.sources`, and its scan of non-project files has no C/C++ and walks the
whole checkout. CFamily analysed 32 of the compilation database's 181 units, all in full. SonarCloud counts a file's
executable lines as uncovered when no report names it, PowerShell's included (`build.ps1`: 232). The organisation's
plan analyses pull requests and `main` and refuses any other branch. `main`'s first analysis from CI failed on a C
reliability rating: 34 C++ issues on older lines, each dated by blame, of which two — on lines changed since the new
code began — were new code. Those two were a real defect: `hook-harness --opengl`, or `--vulkan` beside a D3D11 mode,
crashed through a null swapchain (`0xC0000005`, measured on `main`; exit 1 with a message after #336). The
Overlay built from either side of #336, in one folder with one `FL_BUILD_ID`, has a byte-identical `.text`, its two
`LARGE_INTEGER` initialisers changed included.
**Traps met on the way:**
- **The scanner weakens the build it wraps**: SonarScanner for .NET's targets set `TreatWarningsAsErrors=false` and
empty `WarningsAsErrors` in every build they instrument. Never `begin` before the gate's build; the analysis has a
build of its own.
- **A configure-only compilation database breaks CFamily under C++20 + Ninja**: CMake 3.28+ adds `@<object>.modmap`
response files that only the build writes, and CFamily 6.85 stops with `unexpanded response file`. Configure with
`-DCMAKE_CXX_SCAN_FOR_MODULES=OFF` (no module is used here), or build first.
- **A property condition cannot see `SonarQubeTempPath`**: the scanner's ImportBefore targets define it after the
project body, so only an item condition (evaluated after every property) sees it; the scanner reads
`SQAdditionalAnalysisFileItemTypes` during property evaluation, so that one is set unconditionally.
- **The scanner walks the whole checkout** for PowerShell/YAML/JSON (obj/*.json included) and drops `sonar.sources`;
SonarCloud also drops what `.gitignore` names.
- **A quiet Dependabot is not a current one**: its NuGet runs succeeded and proposed analyzers only, for ten weeks —
the run of 2026-10-25 calls even the shipped libraries, at the versions in use, incompatible with the framework.
- **A second job makes a workflow-level permission a vulnerability**: `githubactions:S8264` (security rating C on the
pull request) — grant per job, `permissions: {}` at the top.
- **A file with no coverage report is 0 % covered, not "not measured"**, for PowerShell too: exclude what has no report
from the coverage figures, or a pull request touching a script fails the gate.
- **The free organisation analyses only pull requests and `main`**: a `workflow_dispatch` of a feature branch uploads,
then fails on "not allowed to access data from non main branches". A pull request's analysis lists only its own
lines, so the older code's findings wait for `main`, where they are dated by blame and count against the gate only
on lines changed since the new code began.
- **The first analysis with a version keeps the old new-code start**: `main`'s went red on code changed 2026-10-19,
and the next one moved the start to the last analysis without a version and went green with nothing fixed. Judge a
fix by the issues it closes (`api/issues/search … resolved=false`), not by the gate turning.
- **A `NOSONAR` goes on the line the issue names**: `S3519`'s `NOSONAR` sat on `p -= 5`, the cause, while SonarCloud
reports the read on the next line, so the issue stayed open after #336 merged; the release pull request moved it.
- **Bisect a CI-only test failure with CI's own settings**: #335's `NoSecondMatcherTests` failed in CI only, and the
first run blamed CsWin32; a local run without coverage passed, so the CsWin32 bump was dropped for nothing. With
`--collect:"XPlat Code Coverage"` the failure was local too and followed `coverlet.collector` 10.1.0, whose injected
tracker declares a constant reflection cannot read.
- **Read the flow of an S6232 before fixing it**: `LARGE_INTEGER x{}` makes the union's first member (the
`LowPart`/`HighPart` struct) the active one, so every later `x.QuadPart` read is the finding — wherever it moves. The
issue's flow says *last active member "" is assigned here* at the declaration; #336 moved the read first, drew the
same issue on its new line, and only then initialised through `QuadPart` (`{.QuadPart = 0}`).
- **A local SonarAnalyzer is not SonarCloud's gate**: the `SonarAnalyzer.CSharp` package with its own defaults reports
about 240 C# findings here; the server's *Sonar way core* profile had none open. Read `api/issues/search`.
- **`sed -i` from Git Bash writes LF**: in this CRLF repository it rewrote whole files' line endings (git normalises
them on commit, but the working copy changed); edit with the editor tools, or restore CRLF before formatting.
**Owner-only:** item 24 added.
+76
View File
@@ -0,0 +1,76 @@
# HANDOFF history — 0.1.0-beta.30
*Moved verbatim from `docs/HANDOFF.md` when 0.1.0-beta.31 was cut, 2026-10-26 (owner decision D66); `docs/HANDOFF.md` §How this file is split lists every part. Nothing below was edited, so its "below" and "above" point inside the original file.*
## **START HERE** — 2026-10-26, 0.1.0-beta.30: Enter in the consent dialog, the hardware-change markers, the libraries
*Status is `docs/changelog/0.1.0-beta.30.md`; this is what no other file carries.* The owner, 2026-10-26, with a
screenshot of a game page: "Fix: sau khi gõ câu: "I ACCEPT..." -> Nhấn Enter -> Nút được bật, Text lại ghi "off", thoát
ra, vào lại vẫn tắt.", "Kiểm tra dependcies, conflict và sửa code, cập nhật (nếu cần)" and "Fix(UI/UX): Mốc đổi phiên bản
driver card hiện không rõ (Như trong hình)" — and, with the plan approved, the whole train to the release without asking
again. #338 (the consent dialog's Enter, the two switches), #339 (the markers), #340 (the libraries) and this release.
**Decisions** (asked while planning, each with the rule or the screenshot in front of the owner):
- **D69 — Enter enables once the consent phrase is typed exactly** (`19_SAFETY` §User-facing consent, amended): the
primary button is the dialog's default, and until the phrase matches the content keeps Enter, so nothing happens; Esc
and *Keep hooking off* still decline. No `Safety_Consent_*` string changed: `consent-dialog/1` stands. The tick-box
dialogs (D33's exception, D34's admin mode) are unchanged.
- **D70 — the hardware-change markers are numbered** — a badge per day that changed, the day's changes in the list under
each chart, the same text in a tooltip ("Số + danh sách", chosen over a full label kept on the chart) (`08_UI` §Games ›
Trend).
- **D71 — Velopack 1.2.161 now**, the library and `vpk` together: item 24(d)'s Velopack half. The first update the new
updater installs is beta.30 → beta.31 (item 25(c)).
**Choices made here** — the owner asked for the fixes, not for these:
- **The switches stay OneWay and re-read their row**: the command raises the property whatever happened
(`ThenShowStoredAsync`). A TwoWay binding would write the click into the view model before the dialog answered; a
code-behind `UpdateTarget` would leave the view model unable to say so in a test.
- **The markers draw their own badges** (`ChangeMarkerPlottable`), not ScottPlot's `VerticalLine` label with offsets:
the label's anchor is its own line, nothing could stop two from overlapping, and its colours were fixed when it was
made. A run of days too crowded to stand side by side becomes one badge (*3–5*) rather than a badge that is not drawn.
- **The `SQLitePCLRaw` pin dropped, not moved to 2.1.14**: the pin's own comment said to drop it once
`Microsoft.Data.Sqlite` resolved a patched version, and 2.1.14 (SQLite 3.54.0) would be a new pin to carry; it comes
with Microsoft's next servicing.
- **No 10.0.14 packages**: published the day before, and the out-of-band fix is in the runtime, which the release
ships from the SDK it builds with.
**Measured on the way:**
- **WPF drops a click's value when the source is raised unchanged**: `BindingExpression.TransferValue` re-transfers
outside a source update and calls `DependencyObject.InvalidateProperty(dp)`, which is `preserveCurrentValue: false`
(dotnet/wpf `main`); `ConsentDialogKeysTests` shows it on a real `ToggleSwitch`.
- **WPF UI 4.3.0's `ContentDialog.xaml`** binds each button's `IsDefault` to `DefaultButton`, makes Close `IsCancel`,
hides a disabled primary, and while the primary is disabled a trigger makes Close the default — so `DefaultButton =
Primary` alone would still have declined on an early Enter.
- **ScottPlot 5.1.59's `VerticalLine` label** is anchored 5 px above the data area and grows into the top-axis panel,
15 px for an unused axis; `Add.Plottable` assigns no axes; `LabelStyle.LastRenderPixelRect` includes a 3 px shadow
offset even without a shadow.
- **SQLite in each `SQLitePCLRaw`**, read from the native libraries: 2.1.13 → 3.53.3, the 3.0.5 pin → 3.53.4, 2.1.14 →
3.54.0.
- **The release rehearsal** (run 40303218479, `workflow_dispatch` on the deps branch): the runner installed SDK
**10.0.403** and runtime 10.0.14 (`setup-dotnet` resolves `global.json`'s `latestFeature` to the newest), and the
published package's `FrameLedger.deps.json` names `runtimepack.Microsoft.NETCore.App.Runtime.win-x64/10.0.14` and the
WindowsDesktop pack 10.0.14 — so the release carries the out-of-band security runtime with no change to `global.json`.
`vpk` 1.2.161 produced the same seven assets as 1.2.0 (Setup 115 MB, Portable and full 108 MB) and a delta from
beta.29 of 5.1 MB.
**Traps met on the way:**
- **A Visual Studio update strands CMake's cache**: Insiders moved MSVC 14.51 → 14.52 and `cmake configure failed`
("CMAKE_CXX_COMPILER … is not a full path to an existing compiler tool"). Delete `build/native/x64-release/CMakeCache.txt`
and `CMakeFiles`; the next gate configures afresh.
- **A fresh worktree cannot fetch MinHook or Catch2 on this machine**: CMake caches `GIT_EXECUTABLE` as Git's
`ucrt64\bin\git.exe`, which cannot run the `git-submodule` shell script without Git's `usr\bin` on the PATH
("'submodule' appears to be a git command, but we were not able to execute it"). Point the cache at
`C:\Program Files\Git\cmd\git.exe`, or run the gate in the main checkout (detached at the branch's commit), whose
`_deps` are already there. CI is not affected.
- **A `private const` in a test takes the `_` prefix** — IDE1006 in `dotnet format`, which the build does not report.
- **FluentAssertions' `OnlyContain` fails on an empty collection**, and `^1` cannot appear in its expression (CS8790).
- **ScottPlot's `Add.Plottable` assigns no axes** to a custom plottable; set `Axes.XAxis`/`YAxis` after
`DateTimeTicksBottom` has replaced the bottom axis.
- **SonarCloud counts a prompt's `ShowAsync` as new code**: #338's gate read 70 % (four lines of `ConsentPrompt`); the
release pull request tests it through a fake `IContentDialogService` so `main`'s gate does not inherit the gap.
**Owner-only:** item 25 added; item 24(d) updated.
+39
View File
@@ -0,0 +1,39 @@
# HANDOFF history — 0.1.0-beta.31
*Moved verbatim from `docs/HANDOFF.md` when 0.1.0-beta.32 was cut, 2026-10-31 (owner decision D66); `docs/HANDOFF.md` §How this file is split lists every part. Nothing below was edited, so its "below" and "above" mean HANDOFF.md as it stood.*
## **START HERE** — 2026-10-26, 0.1.0-beta.31: the remaining library updates
*Status is `docs/changelog/0.1.0-beta.31.md`; this is what no other file carries.* The owner, while beta.30 was being
released: "Sau bản beta 30, bạn làm thêm bản beta 31 với các deps còn lại (.net 10.0.14) và 1 số thư viện khác. Sau khi
kết thúc bản beta 31, bạn có thể cập nhật và đóng phiên." #342 (the libraries) and this release.
**Decision:**
- **D72 — the remaining updates, inside the seven-day cooldown on purpose** (`13_CI_CD` §Dependabot and the NuGet
audit): the .NET 10.0.14 packages (a day old), Markdig 1.5.0 (two days), CsWin32 0.3.367 (four days),
Meziantou.Analyzer 3.0.317, and the two beta.30 had set aside for other reasons — `coverlet.collector` 10.1.0 and
Catch2 3.16.1. The cooldown still holds for Dependabot and for every update the owner has not asked for.
**Choices made here:**
- **coverlet 10.1.0 by fixing the test, not by keeping the pin**: `NoSecondMatcherTests` reads every string constant of
three assemblies, and under coverage those assemblies also carry the collector's `Coverlet.*` types — not ours, and one
of their constants is unreadable to reflection. The test leaves that namespace out; what it guards is unchanged.
- **FluentAssertions stays at 7.2.2** (Xceed's licence), and the vendored native SDKs stay as measured: NVAPI R615
changed its licence file, and the Vulkan and Streamline headers follow the loader and the titles they were measured
against.
**Measured on the way:**
- Catch2 3.16.1 builds clean under `/W4 /WX` with the `/EHsc` fix kept; 32 of 32 native suites pass.
- `Microsoft.Data.Sqlite` 10.0.14 still declares `SQLitePCLRaw` 2.1.13: the engine stays SQLite 3.53.3.
- CsWin32 0.3.367 and Meziantou 3.0.317 changed nothing in the build: no new generated signature, no new finding.
**Traps met on the way:**
- **A Catch2 bump re-runs FetchContent's submodule step**: on this machine CMake's cached `GIT_EXECUTABLE` (Git's
`ucrt64\bin\git.exe`) cannot run `git-submodule` — point it at `C:/Program Files/Git/cmd/git.exe` in
`build/native/x64-release/CMakeCache.txt` before the gate (beta.30's START HERE has the first sighting).
**Owner-only:** no new item — item 25(c) is this update, the first that beta.30's Velopack 1.2.161 installs.
+78
View File
@@ -0,0 +1,78 @@
# HANDOFF history — 0.1.0-beta.32
*Moved verbatim from `docs/HANDOFF.md` when 0.1.0-beta.33 was cut, 2026-11-03 (owner decision D66); `docs/HANDOFF.md` §How this file is split lists every part. Nothing below was edited, so its "below" and "above" mean HANDOFF.md as it stood.*
## **START HERE** — 2026-10-31, 0.1.0-beta.32: the alpha line — .NET 11 RC3 / C# 15 beside the betas
*Status is `docs/changelog/0.1.0-beta.32.md` (and, for the first alpha, `docs/changelog/0.1.0-alpha.1.md`); this is what
no other file carries.* The owner: "Bạn có thể phân tích, tìm kiếm sự khác biệt so với .NET 10, đánh giá, lên plan và tạo
thêm bản alpha, nơi thử nghiệm các dotnet mới, cập nhật code (nếu cần) cho .NET 11 RC3/c# 15 để chuẩn bị cho .NET 11 ra
mắt, thêm cảnh báo đây là bản thử nghiệm, yêu cầu tự chịu trách nhiệm nếu cần nhé." — an analysis of .NET 11 against
.NET 10, an evaluation, a plan, and an alpha build where new .NET versions are tried, code updated where needed, with an
experimental-build, own-risk warning. #344 (the line's plumbing), #346 (the warning, the backup, the legal text), #345
(what .NET 11's SDK asks of the source) and this release; the `alpha` branch and `0.1.0-alpha.1` follow.
**Decisions (asked while planning, do not re-ask):**
- **D73 — the alpha line** (`12_BUILD` §The alpha line, `13_CI_CD` §The alpha line, `11_UPDATER` §Channels): the source of a
released beta built on a prerelease .NET from the long-lived `alpha` branch, tagged `vX.Y.Z-alpha.N`, packed on
Velopack's `alpha` channel. An alpha **replaces** the beta on the PC (same packId, install folder and data folder — the
native layer reads that folder by fixed path) and **copies the ledger before it first opens it**, once per alpha
version, newest three kept (`06_DATA_MODEL` §Migrations).
- **D74 — the warning** (`08_UI` §First-run flow and §Settings, `01_ARCHITECTURE` §Lifecycle): `legal/ALPHA_NOTICE.md`
in an alpha's Legal Gate with a tick box of its own that Accept waits for; the alpha's Agent does not serve until it is
accepted (exit 8); an ALPHA badge, a banner at every start, the update channel locked.
- **D75 — the legal text made true**: EULA 1.6 §2B and Disclaimer 2.12 §0 name alphas beside betas; the owner approved
the Alpha notice 1.0 and both sentences with the plan.
- **D76 — alpha.1 is a retarget only**: `net11.0`, C# 15 by `LangVersion latest`, the three runtime-serviced packages
`11.0.0-rc.3.26522.148`; no preview feature (no runtime-async), no C# 15 syntax — main must keep building as C# 14 on
.NET 10.
**The evaluation, as given to the owner:** .NET 11 is STS — supported to about 2028-11, no later than .NET 10 LTS
(2028-11-14) — so moving the main line buys no support time; Microsoft's supported-OS list for .NET 11 has Windows 10
only in its LTSC and IoT editions, against NFR-8's Windows 10 22H2 floor; C# 15's unions and closed hierarchies would suit
the tri-states and refusal reasons once the main line compiles C# 15. Recommendation: the main line stays on .NET 10;
the alpha line gathers the evidence; `20_OPEN_QUESTIONS` §G *The main line's .NET* holds the decision table.
**Choices made here:**
- **One alpha per beta, never several in a row**: Velopack's `GithubSource` asks GitHub for one page of ten releases, so
ten of one line in a row would hide the other line's newest from its update check (read from Velopack's code).
- **Every alpha-only behaviour lives on main, dormant**: `Shared.BuildLine` is composed and injected, so the alpha's
gate, banner, hold, Agent wait and backup are tested on main; the branch differs only by `RELEASE_LINE`, `global.json`,
the TFM, three package versions and `legal/licenses/nuget/`.
- **The App holds the Agent while an alpha's gate is open** on a hold of its own: the connection's first round runs under
the first-run window, and a held-back Agent started anyway would exit 8 and be started again every round — under the
admin mode a Windows prompt each time.
- **The backup has its own lock**, five minutes, not the migration lock: that one gives a waiter 30 s and throws.
- **.NET 11's `IHost` rethrow is accepted on the alpha**: a failed background service ends an alpha's Agent through the
crash path with a minidump, where .NET 10 exits 0 — said in `LIMITATIONS.md`.
**Measured on the way:** the whole gate on .NET 11 RC3 in a throwaway worktree (`spike-notes` §24): native 32/32, every
test suite green with no change of answer, coverage and format clean; 21 analyzer sites in 14 files (CA1307 ×13, MA0002
×7, CA2026 ×1), all fixed on main in forms .NET 10 also compiles; license-check red only because `legal/licenses/nuget/`
is the beta's package set.
**Traps met on the way:**
- **`sed -i` in Git Bash rewrites a CRLF file as LF** (seen on the probe's props files); edit CRLF files with the Edit tool
or Python with `newline=''`, and `unix2dos` a file the Write tool created.
- **The keyboxd I/O error at signing came back**: `gpgconf --kill keyboxd` (the Windows GnuPG's), then commit again.
- **A CMake configure in a fresh worktree works when the gate is started from PowerShell**, whose `git` is
`Git\cmd\git.exe`; from Git Bash, CMake caches `ucrt64\bin\git.exe` and the submodule step fails.
**Owner-only:** item 26 — beta.32 on real hardware.
### 0.1.0-alpha.1 — the first alpha, the same day
The `alpha` branch was cut from main at this pull request — `v0.1.0-beta.32` and these notes, no other change — and carries the switch alone (`12_BUILD` §The alpha line): `RELEASE_LINE`,
`global.json` (SDK `11.0.100-rc.3.26522.148`), the TFM, three packages at `11.0.0-rc.3.26522.148`, and the NuGet licence
texts of that package set (69 packages). Its gate on the 11 SDK passed whole before the pull request into `alpha`; the
release ran from the signed tag `v0.1.0-alpha.1` on `alpha`, on Velopack's `alpha` channel. Its notes are
`docs/changelog/0.1.0-alpha.1.md`, which open with the experimental-build warning.
- **The next alpha** follows the next beta: merge main into `alpha` (a merge commit), regenerate `legal/licenses/nuget/`
there if it conflicts, then the same steps (`13_CI_CD` §The alpha line). **.NET 11 ships on 2026-11-10**: from then the
switch is SDK `11.0.100` and the packages `11.0.0`, and RC3 is out of support — move the alpha even if no beta comes.
**Owner-only:** item 27 — the first alpha on real hardware.
+85
View File
@@ -0,0 +1,85 @@
# HANDOFF history — 0.1.0-beta.33
*Moved verbatim from `docs/HANDOFF.md` when 0.1.0-beta.34 was cut, 2026-11-06 (owner decision D66); `docs/HANDOFF.md` §How this file is split lists every part. Nothing below was edited, so its "below" and "above" mean HANDOFF.md as it stood.*
## **START HERE** — 2026-11-03, 0.1.0-beta.33: games from the Xbox app and the Microsoft Store
*Status is `docs/changelog/0.1.0-beta.33.md`; this is what no other file carries.* The owner: "Trong phiên này, ta sẽ tập
trung xử lý, đánh giá, phân tích cho các game thuộc MS Store/ Xbox App/Game Pass cho (các) phiên bản tiếp theo nhé. Quy
trình vẫn như mọi lần." — handle, evaluate and analyse the games of the Microsoft Store, the Xbox app and Game Pass for the
next versions, the usual train; the owner's games are in `C:\XboxGames` and `D:\xbox`. #351 (the library, the install
root, detection, the art, Privacy 2.13), #352 (Play, the guard's two refusals, one exe-path reader) and this release;
`0.1.0-alpha.2` follows (D82).
**Decisions (asked while planning, do not re-ask):**
- **D77 — measure first, on the owner's titles**: the launch chain was measured by activating six of the eleven packages
with no FrameLedger hook, read-only, each game closed by its window and never killed, with the decision table committed
before the run (`spike-notes` §25, its two commits in #351).
- **D78 — GDK only**: an app-container (UWP) process is refused with a reason of its own, `TargetAppContainer`, Tier 2
(`19_SAFETY` §The target must be able to take the Overlay); `LIMITATIONS.md` says so.
- **D79 — the platform is "Xbox"** (id `xbox`), full scope: import, art, Play, Tier-1 capture, detection, docs and legal.
- **D80 — Play on an Xbox game always activates its package**, in both D59 modes (`08_UI` §Games): started by its path a
GDK game is never the game in its package — the run corrected the plan's premise that `CreateProcess` fails with error 5
(it hands the launch executable back to the package, so the game is not the launcher's descendant; an Unreal shipping
executable runs outside it). The Agent records such a game in attach mode.
- **D81 — title lists stay keyed by Steam id**: an Xbox copy is matched by everything but that entry; the gap is
`20_OPEN_QUESTIONS` §G *Xbox app / Microsoft Store titles*.
- **D82 — alpha.2 right after beta.33** (the owner runs `0.1.0-alpha.1`, and the alpha's channel is locked): on RC3; if
the train reaches the alpha after .NET 11's release on 2026-11-10, the standing rule applies (SDK 11.0.100, packages
11.0.0) — no new decision.
The Privacy Policy 2.13's wording was approved with the plan (D36).
**Choices made here:**
- **A GDK package root is an install-root boundary**, for the guard's check 4 and for detection alike, and only where no
store boundary matched — so it can only widen what is walked (`19_SAFETY` §Pre-injection checks, amended 2026-11-03).
The guard gained `GamesInstalled\<X>` with it, and one case list read by both test suites
(`tests/fixtures/install-roots/cases.txt`) holds the two resolvers together.
- **`root_file`, a new detection signal**, answered from the install root's own listing, so the `xbox` platform rule —
first, because a GDK FINAL FANTASY ships Steam's DLL — is decidable even where a very large install's walk ran short.
- **The two refusals read the target once, before the primitive**, never at the 30 s re-scan; "could not tell" refuses as
`ProcessUnreadable`, and only enforcing flags count (`SetContextIpValidation` without strict mode is on every
CET-compatible process: `pwsh.exe` reads `0x105`).
- **`TargetResolver` reads the watcher's spelling** (`ProcessImagePath`) but keeps the guard's rights, so D21's
`TargetUnreadable` is unchanged.
**Measured on the way** (`spike-notes` §25): eleven GDK packages, full trust, the user's token, medium integrity, none of
the four mitigations; the image path and the loader's main module both in the `Content` spelling; every game `.exe`
refuses `FILE_READ_DATA`/`FILE_EXECUTE` outside its package, so no Unreal version and no *Runs as* for these titles;
`GetProcessMitigationPolicy` answers through `PROCESS_QUERY_LIMITED_INFORMATION`, and an unknown policy answers
`ERROR_INVALID_PARAMETER`.
**Traps met on the way:**
- **Malwarebytes quarantines `fl_guard_test.exe`** (`Malware.Heuristic.108256`, records in
`C:\ProgramData\Malwarebytes\MBAMService\RtpDetections`) on some builds and not others: ctest then reports `fl_guard` as
passed in 0.5 s with no output and `fl_prescan` with an empty command. Read `LastTest.log` for the assertion count before
believing a native pass; an exclusion for `E:\frameledger\build\` is the owner's to add (a security setting), and CI runs
both suites.
- **`build.ps1` finds the x64 clang-format; `Get-ChildItem … clang-format.exe` finds the ARM64 one first**, which will not
start on this PC.
- **SonarCloud's quality gate on #351 was 77.7 % new-code coverage** (≥ 80 % wanted) and one `cpp:S5813` (`wcslen`): both
closed in #352 — its own gate 95.4 %, main's after the merge 86.5 % on the code since beta.32 with no open issue. The
job is advisory, so a merge on green does not wait for it — read its verdict after each merge.
- **FluentAssertions' `OnlyContain` fails an empty collection**: a test of what this PC holds (`GamingRoots.OnThisPc()`)
passed here and failed on the hosted runner, which has no `.GamingRoot` (#352's first CI run) — assert that nothing
is wrong rather than that everything is right.
**Owner-only:** item 28 — the Xbox titles on real hardware.
### 0.1.0-alpha.2 — the second alpha, the same day (D82)
`alpha` took main at this pull request — `v0.1.0-beta.33` and these notes, no other change — by a merge commit, as
`13_CI_CD` §The alpha line says: no file the switch holds had moved on main, so nothing conflicted and the switch is the
first alpha's (SDK `11.0.100-rc.3.26522.148`, the three packages at `11.0.0-rc.3.26522.148`, the same NuGet licence
texts). Its gate on the 11 SDK must pass before the pull request into `alpha` is merged by hand (the branch has no
auto-merge); the release runs from the signed tag `v0.1.0-alpha.2` on `alpha`, and its delta from alpha.1 is the first
an alpha's release has to find — #350's lookup, by the name the pack lists. Its notes are
`docs/changelog/0.1.0-alpha.2.md`, which open with the experimental-build warning.
- **The next alpha moves to .NET 11's release**: from 2026-11-10 the switch is SDK `11.0.100` and the packages `11.0.0`,
and RC3 is out of support — move the alpha even if no beta comes.
**Owner-only:** item 29 — the second alpha on real hardware.
+90
View File
@@ -0,0 +1,90 @@
# HANDOFF history — 0.1.0-beta.34
*Moved verbatim from `docs/HANDOFF.md` when 0.1.0-beta.35 was cut, 2026-11-09 (owner decision D66); `docs/HANDOFF.md` §How this file is split lists every part. Nothing below was edited, so its "below" and "above" mean HANDOFF.md as it stood.*
## **START HERE** — 2026-11-06, 0.1.0-beta.34: DLSS 5 and DLSS 4.5 from what the game and the driver did; filters; Games at once
*Status is `docs/changelog/0.1.0-beta.34.md`; this is what no other file carries.* The owner asked for seven things, the
usual train: (1) how DLSS 5 Neural Rendering is detected on Hogwarts Legacy (Neural Rendering on in the game), and its
version; (2) under the NVIDIA App's *Dynamic* multi frame generation the label read DLSS 4, though Dynamic and ×6 exist
only in DLSS 4.5 (Phantom Blade Zero); (3) filters on Games and Compare; (4) the Compare page's layout, from a
screenshot; (5) the documents and the tested-games list, from the database; (6) switching to Games stalled 0.5–1.5 s;
(7) a language change landed on the last content page instead of Settings. And while planning: "Bạn check Streamline các
bản gần đây có gì thay đổi và sửa luôn nếu thật sự cần nhé." — check what changed in recent Streamline versions and fix it
if really needed. #356 (two fixes from a self-review of #351 and #352), #357 (D83), #358 (D84, Streamline `v2.14.16`),
#359 (items 6 and 7), #360 (items 3 and 4, D85, D86), #361 (item 5) and this release; `0.1.0-alpha.3` follows (D87) —
the owner's screenshot is of an alpha, so the alpha is how these reach the owner's PC.
**Decisions (asked while planning, do not re-ask):**
- **D83 — Dynamic frame generation is DLSS 4.5's**: the owner's rule, "Dynamic and ×6 exist only in DLSS 4.5". The
evidence is the game's driver profile setting Dynamic (`NGX_DLSSG_MODE` = 4) **and** the driver reporting its
frame-generation override applied in the game's process (`FG_MODE` in its FG word), in a session where DLSS
Frame Generation was identified (`fg_mode = dlssg`; its factor need not have been counted); a state measured at ×5 or more still ranks first, and a *Fixed* multiplier names nothing by itself
(amends D64). The driver's `frameGenerationMode` — 3 under Dynamic and 1 under Fixed in every session read, and unnamed
by NVIDIA — is recorded in `spike-notes` §26, not keyed on.
- **D84 — DLSS 5 is the session's generation where its neural rendering was measured running**: the Overlay decodes
`kFeatureDLSS_NR` in its `slEvaluateFeature` detour and the Agent keeps its share of the Streamline batches
(`sessions.dlss_nr_pct`, schema 0022) — *DLSS 5 (neural rendering on N % of rendered frames)*; loaded and seen not
running, *runtime loaded, not seen running*; where nothing could tell, *runtime loaded*, as before (amends D64).
- **D85 — the filters**: Games — store, engine, state, installed, played; Compare — game, tier, frame generation, no
period; Compare lists every session (it listed the newest 200).
- **D86 — the left pane's selected item keeps its label**: our copy of WPF UI 4.3.0's LeftFluent item template, whose
`IsActive` trigger animated it away.
- **D87 — alpha.3 right after beta.34**, on RC3: the train reaches it before .NET 11's release on 2026-11-10.
Streamline was re-vendored at `v2.14.16` on the owner's instruction above, not as a decision of its own. The wording of
the Disclaimer 2.13 and the Privacy Policy 2.14, and the tested-games list (D35), were approved with the plan (D36).
**Choices made here:**
- **Neural rendering's share is over the Streamline batches**, not every present: a generated frame evaluates nothing,
and a title that never drains a batch reads *nothing could tell* (null), never 0 %.
- **A writer older than beta.34 is told apart by its family bit**, `FL_HOOK_SL_NEURAL_RENDERING` (bit 12), published with
the detour — an old Overlay's silence leaves `dlss_nr_pct` null instead of a measured 0 %; no layout change.
- **The Games page is the window's**, kept by our own page provider (`WindowPageCache`), not `NavigationCacheMode`: WPF UI
4.3.0 reads that only when neither a service provider nor a page provider is set, and `SetNavigationControl` sets one
(`16_WPFUI_SYNTAX` §Navigation). One per window, so a language change's window builds its own.
- **The cards come before the executable checks** — 39 of the owner's 41 Steam games are on a USB drive that sleeps — and
each card gets its *Not installed* pill when its check answers.
- **The pane's item template is a copy changed in one place**, reading WPF UI's own `NavigationViewConstants.xaml`: before
the WPF UI pin moves, the upstream template is read again.
**Measured on the way:** the owner's DLSS sessions of 2026-11-01 → 11-06, the driver's frame-generation numbering and
Streamline's `v2.12.0` → `v2.14.16` changes are `spike-notes` §26 (the ledger read read-only; the vendored copy was
`v2.12.0` byte for byte); the Games page before and after is §27 (first cards 822–830 ms → 10–15 ms with the first
executable check held 800 ms; a revisit 181–215 ms → 15–16 ms). The neural-rendering decode costs nothing measurable in
the detour and 0.14–0.19 ns on the present's feature byte (#358's body; NFR-1's budget is 1 µs per present).
**Traps met on the way:**
- **`notice-check` reads the tracked tree**: a file deleted from the working tree but not from the index fails it with
*Could not find file* — after every build and test had passed (#360's first local gate). Stage the change
(`git add -A`) before the gate.
- **A new hook family bit belongs in the native token test's exact mask** (`guard_test.cpp`), and a new Streamline fact
in the 0xF00D case's list of facts it must not light — #358's first gate (`0x100f` against `15`).
- **WPF UI 4.3.0**: `NavigationCacheMode` is ignored once a page provider is set; `INavigationService.SetNavigationControl`
hands the NavigationView the container's provider, so ours is set after it; LeftFluent's item template collapses the
selected item's label.
- **Microsoft.Data.Sqlite's async methods run synchronously**: a read awaited on the UI thread blocks it — `Task.Run` it.
**Owner-only:** item 30 — beta.34 on real hardware.
### 0.1.0-alpha.3 — the third alpha, the same day (D87)
`alpha` takes main at this pull request — `v0.1.0-beta.34` and these notes, no other change — by a merge commit, as
`13_CI_CD` §The alpha line says. One file the switch holds moved on main — `legal/THIRD_PARTY_NOTICES.md`, its
Streamline row (#358) — on a line the switch does not touch (the switch changes the *Transitive* row), so the merge
takes both without a conflict (`git merge-tree` before the pull request); main's package set did not move, and the
switch stays the first alpha's (SDK `11.0.100-rc.3.26522.148`, the three packages at `11.0.0-rc.3.26522.148`, the same
NuGet licence texts) — the train reached it before .NET 11's release. Its gate on the 11 SDK must pass before the pull
request into `alpha` is merged by
hand (the branch has no auto-merge); the release runs from the signed tag `v0.1.0-alpha.3` on `alpha`, with its delta
from alpha.2. Its notes are `docs/changelog/0.1.0-alpha.3.md`, which open with the experimental-build warning. It is
the first alpha whose ledger moves (schema 22): the copy it makes first is the database as alpha.2 left it, and going
back is to the newest beta, which opens schema 22.
- **The next alpha moves to .NET 11's release**: from 2026-11-10 the switch is SDK `11.0.100` and the packages `11.0.0`,
and RC3 is out of support — move the alpha even if no beta comes.
**Owner-only:** item 31 — the third alpha on real hardware.
+74
View File
@@ -0,0 +1,74 @@
# HANDOFF history — 0.1.0-beta.35
*Moved verbatim from `docs/HANDOFF.md` when 0.1.0-beta.36 was cut, 2026-11-10 (owner decision D66); `docs/HANDOFF.md` §How this file is split lists every part. Nothing below was edited, so its "below" and "above" mean HANDOFF.md as it stood then.*
## **START HERE** — 2026-11-09, 0.1.0-beta.35: accessibility — a statement, what a screen reader is given and told, headings and charts, contrast themes, focus
*Status is `docs/changelog/0.1.0-beta.35.md`; this is what no other file carries.* The owner: "Bạn lên plan và thêm
phiên bản mới (nếu thực sự cần) cho mục accessibility: 1. đọc docs, check, sync và sửa, cập nhật thêm file
ACCESSIBILITY.md vào đúng vị trí. 2. Check các Accessibility đã có, đề xuất thêm accessibility nếu cần. 3. Đã dùng: bàn
phím only (tắt chuột) và narrators, không lỗi." — plan accessibility, with a new version if it is really needed: read,
check, sync and fix the documents and add `ACCESSIBILITY.md` where it belongs; check what exists and propose more; the
owner had used the keyboard alone, mouse disconnected, and Narrator, with no fault. With opensource.guide's
accessibility practices and the open-source-accessibility toolkit's `ACCESSIBILITY.md` template (MIT: its structure,
not its text). #366 (the statement, D88), #367 (names and peers), #368 (announcements, D89), #369 (headings and charts,
D90), #370 (contrast themes, D91, and three contrast holes outside them), #371 (focus and motion) and this release; no alpha (D92).
**Decisions (asked while planning, do not re-ask):**
- **D88 — the accessibility statement**: `ACCESSIBILITY.md` at the repository's root, in the App under Help ▸
Accessibility and on the wiki. WCAG 2.2 at level AA, as W3C's WCAG2ICT applies it to desktop software, is a goal and
never a claim; a report is handled by severity, with no promised times; the owner's pass of 2026-11-09 — keyboard only
and Narrator, on 0.1.0-beta.34 and 0.1.0-alpha.3, no fault — is its first evidence by hand.
- **D89 — what appears is said to a screen reader**: UI Automation notifications for a safety notice, the agent's and
the update's banners, every snackbar, a game page's notice and Database maintenance's results, only while
FrameLedger's window is the active one.
- **D90 — headings and charts**: a page's title is a heading of level 1, a section's title level 2; every chart is
named with where its numbers are written; no chart tells two series apart by colour alone.
- **D91 — Windows contrast themes are followed**, whatever Settings ▸ Theme says.
- **D92 — beta.35 in this train and no alpha**; alpha.4 is the move to .NET 11's release (SDK `11.0.100`, packages
`11.0.0`), a task of its own after 2026-11-10.
**Choices made here:**
- **A contrast theme is the user's colours by role**, not WPF UI's high-contrast files (84 red placeholders among 97
colours, 17 brushes that throw, Windows 11's defaults) and not a hand list of keys: every key of the four files takes
the colour of the role it has in all of them, opaque colours only (`ContrastRoles`), over the light or the dark Fluent
theme as the contrast theme is; the text on the accent is the highlight's text, the App's choice.
- **What must change while it is shown binds `ContrastTheme.IsOn`**, a static property WPF hears through
`StaticPropertyChanged`: the implicit button style, the Settings line. The charts, the badges and the artwork band read
`ContrastTheme.Active` when they draw.
- **The snackbars lost their green and orange** (white on fixed colours, 2.16–2.78:1 in both themes): every message is
Secondary, its icon saying the kind. **The agent's pill is a `Pill` on the theme's fills**, no longer a badge.
- **A content dialog's focus is WPF UI's**: its host stores and restores the focused element; a test pins it. Message
boxes get the App's active window as owner (`MessageBoxes`), which WPF UI's leaves null.
- **A page shortcut focuses the page's first control and says its first level-1 heading** (`PageFocus`); a click in the
pane leaves the focus where WPF UI puts it.
- **Left as limitations, with what to do instead** (`ACCESSIBILITY.md` §Known limitations): a chart's points one by
one, headings inside the documents the App shows (a FlowDocument paragraph has no peer), the snackbars' four seconds,
Windows' text size, pausing only from the tray.
**Measured on the way:** the UI Automation tree WPF builds, on .NET 10.0.14 — items named by `ToString()`, peerless
focusable controls, a template's text hidden from the control view, template cells read as *Item: …* (`16_WPFUI_SYNTAX`
§Gotchas); WPF UI 4.3.0's high-contrast files, its Button, Badge and Snackbar appearances (fixed colours, the ratios
above), its message box's missing owner and its content dialog host's focus restore; ScottPlot 5.1.59's keys (focusable,
none marked handled) and its double-click benchmark.
**Traps met on the way:**
- **A `ContentDialog` test needs the dispatcher's context.** `ContentDialog.ShowAsync` takes the dialog out of its host
in a `finally` after an await; on a test thread with no `DispatcherSynchronizationContext` that never resumes on the UI
thread, the dialog stays in its host and the focus on its button — a first measurement concluded WPF UI kept the focus
there; it does not.
- **A test that listens to a static event hears every test's**: subscribe inside the one STA work item.
- **Inside the App, a brush that throws when WPF UI's file is read alone falls back to the application's resources**, the
Fluent theme's translucent fills: `MenuBarItemBackgroundPressed` read as the window text's white. Count only opaque
colours as evidence.
- **WPF calls a resource reference's callback when a merged dictionary changes, even for an equal value** (Aquatic's
window is the dark theme's `#202020`): no second signal was needed, measured and pinned.
- **A forward `StaticResource` in a style dictionary fails only when that resource is first used** — `AgentPill`
`BasedOn` `Pill`, placed above it: the dictionary loaded, the style threw when found.
- **Python's `"\b"` in a non-raw string is a backspace** — it went into a C# regex twice; write regexes raw.
- **`RenderTargetBitmap.Render(child)` draws the child at its offset**: sample a child's pixel through its parent.
**Owner-only:** item 32 — beta.35 on real hardware.
+79
View File
@@ -0,0 +1,79 @@
# HANDOFF history — 0.1.0-beta.36
*Moved verbatim from `docs/HANDOFF.md` when 0.1.0-beta.37 was cut, 2026-11-11 (owner decision D66); `docs/HANDOFF.md` §How this file is split lists every part. Nothing below was edited, so its "below" and "above" mean HANDOFF.md as it stood then.*
## **START HERE** — 2026-11-10, 0.1.0-beta.36: Qodana in CI, and what its first run reported settled
*Status is `docs/changelog/0.1.0-beta.36.md`; this is what no other file carries.* The owner: "Bạn có thể thêm vào,
trigger Qodana vào CI/CD và sửa lỗi, release (nếu có) với mẫu mà jetbrains cung cấp, có thể tuỳ biến (nếu cần)" — add
Qodana to CI from the workflow JetBrains gives (the Qodana Scan action on `ubuntu-latest`, `pr-mode: false`,
`QODANA_TOKEN`), changed where needed, fix what it reports, release if there is something to release; the usual train.
The owner had made the project on Qodana Cloud and set the `QODANA_TOKEN` secret the same day. #373 (the workflow, the
settings, the fixes and the documents, D93) and this release; no alpha (D92 stands: alpha.4 is the move to .NET 11's
release).
**Decisions (asked while planning, do not re-ask):**
- **D93 — Qodana Community for .NET, from a workflow of its own.** Asked which licence the Qodana Cloud organisation
holds — it decides the linter — the owner answered "Dùng thử 30 ngày", a 30-day trial. So not the Rider-based linter
(Ultimate; the job would turn red when the trial ends) but the Community one, which runs under every licence. A gate
of zero problems, advisory; `docs/13_CI_CD.md` §Qodana.
**Choices made here:**
- **An inspection is switched off in `.editorconfig`, never in `qodana.yaml`**: InspectCode reads its severities there
and so does Rider, so the job and the editor show one list, and a change to it is tested on a developer's PC without
CI. Sixty-three keys, each with its reason; the rule is CLAUDE.md §Coding conventions'.
- **What Qodana reports is fixed unless the inspection argues with a choice the project made.** The suggestions
(ReSharper's lowest reported level) that propose another style are off as a group: the style is `.editorconfig`,
`dotnet format` and the analyzers.
- **The members nothing in the solution uses were listed, not removed** (`13_CI_CD` §Qodana): whether each is
vocabulary, a piece not wired yet, or dead is the owner's to say (owner-only item 33).
- **One pull request, the gate shown red first**: the settings and the gate were pushed before the fixes, so the run
between them (42847369329) is the gate failing on the 409 problems the settings did not cover.
- **A release although nothing a user sees changes**: the fixes are in the shipped assemblies, so the version says
which code is installed; the changelog says in its first line that nothing visible moved.
- **The XAML bindings were re-pointed, not only annotated**: `{Binding DataContext.ViewModel.X, RelativeSource
AncestorType=Page}` became `{Binding ViewModel.X, RelativeSource AncestorType={x:Type pages:GamesPage}}` — the same
object, since each page and window sets `DataContext = this` (read in the five code-behinds) — because the inspection
resolves a typed ancestor and not `DataContext`.
**Measured on the way:** the Community linter's container builds and loads all thirteen `net10.0-windows` projects on
Linux once `EnableWindowsTargeting` is set, though JetBrains' page sends such projects to the Ultimate linter's native
mode; a clean worktree with no native DLLs builds with 15 warnings and no error; InspectCode 2026.2.3.1 on Windows and
in the container agree to within a handful of findings; `.editorconfig`'s `resharper_*` keys are read in the container.
**Traps met on the way:**
- **InspectCode on the owner's PC picks Visual Studio 18 Insiders' MSBuild and dies** ("No files to inspect were
found"): pass `--toolset-path` to the .NET SDK's `MSBuild.dll` and `--dotnetcore`. And **a `--caches-home` a failed
run wrote leaves a project unloaded** on the next run — 2,875 false compile errors in `Infrastructure.Tests`, and
hundreds of false "never used" — use a fresh folder.
- **A fix scripted from the report's positions needs the build as its judge**: a redundant tuple name's region stops
before its colon; two casts in one lambda (`SqliteGameMerge`) are each redundant alone and not together; a suggested
`m[^1]` sat in an expression tree (CS8790); `public bool On => false` on a bound row is CA1822.
- **`dotnet format style --diagnostics IDE0008 IDE0022 --severity info`** applies `.editorconfig`'s suggestion-level
style, which the gate's `--verify-no-changes` (warnings and up) never asks for.
- **`CrashDumpHelperTests.TheWriterHasTheAgentDumpThisProcessFromOutside` failed once on the hosted runner** (#373's
first run, two YAML files changed): "the dumper did not finish within 30 s". Green on the next runs; not looked into.
- **SonarCloud's gate failed on #373, on one condition: coverage on new code, 77 %** — 19 of the 87 changed lines it
counts were old lines no test ever ran (the update prompts, `App.xaml.cs`, chart code-behind), and a line a fix
touches is new code. No issue, no hotspot; the job is advisory and #373 merged on its required checks. `main`'s new
code is "since the previous version", so its gate reads the same until the first analysis after the tag — which
was the release commit's own (its `sonarcloud` job started after the tag was pushed, read version 0.1.0-beta.36 and
passed); had the tag come later, a `workflow_dispatch` of `ci.yml` on `main` would have been that analysis.
- **A release's delta says what the notes forgot**: read "Delta processed … patched" in the tag's log before
calling a release verified — 343 patched files was the runtime, which no line of the notes named.
- **A shell `cd` in a tool call stays** for the next one: use absolute paths.
**The release (the tag, 2026-11-10):** `v0.1.0-beta.36` on `deaa8f3`, a rehearsal of `release.yml` first (run
42853812423, on the release branch), the tag's run 42856948658 green; the seven digests of `SHA256SUMS.txt` are
GitHub's; the wiki published. **The package carries the .NET runtime 10.0.15, not beta.35's 10.0.14**: the hosted
runner installed SDK 10.0.404 that day, 10.0.403 the day before (`global.json` rolls forward within 10.0), so the delta patched 343
of 456 files (5,756,432 bytes) where a release with these changes alone would have patched a few dozen. The notes at
the tag did not say so; the changelog file and the release's text were corrected the same day, marked. Still open
from it: the 10.0.15 servicing packages (`Microsoft.Extensions.Hosting`, `Microsoft.Data.Sqlite`,
`System.Diagnostics.EventLog` are at 10.0.14) — Dependabot's cooldown holds them a week. `main` after the tag: `check`
green, Qodana 0 problems, SonarCloud's gate OK again (its first analysis with version 0.1.0-beta.36).
**Owner-only:** item 33 — Qodana's settings on the owner's side, the never-used list, and beta.36 on real hardware.
+9
View File
@@ -121,6 +121,15 @@ rather than of an instance.
> `spike-notes` §8 and §H5 — so item 3's counter has nothing to count on this route. That is
> a separate finding with its own consequences for HANDOFF item 3, and it does not belong to
> this entry.
>
> **2026-11-06 (beta.34, D84): a fifth id is decoded, and not by guess.** `kFeatureDLSS_NR` (1004),
> DLSS 5's neural rendering, comes from Streamline `v2.14.16`'s own `sl_core_types.h`, re-vendored for it
> (`src/native/third_party/streamline/README.md`) — row O4's warning holds: no id is mapped from a number seen
> arriving. Until then an evaluation of it fell to `FL_FEAT_SL_UNDECODED`, which the Agent does not store. It
> is its own fact (`FL_FEAT_SL_NEURAL_RENDERING`, from the drain word, never from the decoded `upscaler`
> byte — the rule above), never an upscaler; the census counts it in a bucket of its own
> (`SlCensus.WithNeuralRendering`), so the buckets still add up. Whether a real game evaluates it through
> `slEvaluateFeature` is owner-only item 30(a), with its table in `spike-notes` §26.
<details>
<summary>The entry as it stood while it was open, including the pre-committed table with its two holes</summary>
+8
View File
@@ -45,3 +45,11 @@ Each section below lives in its own file under `docs/spike-notes/`, moved verbat
| §19 | Anti-cheat beside the executable — Wuthering Waves (2026-10-13, beta.21, owner decision D58) | [`spike-notes/19-wuthering-waves.md`](spike-notes/19-wuthering-waves.md) |
| §20 | The launcher in front of four itch installs is malware (2026-10-13, beta.21, owner decision D57) | [`spike-notes/20-itch-malware.md`](spike-notes/20-itch-malware.md) |
| §21 | Opening pages and switching tabs in the App (2026-10-14, beta.23) | [`spike-notes/21-app-pages-and-tabs.md`](spike-notes/21-app-pages-and-tabs.md) |
| §22 | The owner's runs of beta.24 and beta.25 on real hardware (2026-10-19) | [`spike-notes/22-owner-runs-2026-10-19.md`](spike-notes/22-owner-runs-2026-10-19.md) |
| §23 | The owner's runs of beta.26 on real hardware (2026-10-20) | [`spike-notes/23-owner-runs-2026-10-20.md`](spike-notes/23-owner-runs-2026-10-20.md) |
| §24 | The whole gate on .NET 11 RC3 — what the alpha line's SDK asks of the source (2026-10-31, beta.32, D73–D76) | [`spike-notes/24-dotnet11-probe.md`](spike-notes/24-dotnet11-probe.md) |
| §25 | Xbox app / Microsoft Store (GDK) titles — the layout, the launch chain, the image paths (2026-11-03, beta.33, D77–D82) | [`spike-notes/25-xbox-gdk.md`](spike-notes/25-xbox-gdk.md) |
| §26 | DLSS 5 on Hogwarts Legacy, Dynamic frame generation on Phantom Blade Zero, and Streamline 2.12 → 2.14.16 (2026-11-06, beta.34, D83, D84) | [`spike-notes/26-dlss5-dynamic-streamline.md`](spike-notes/26-dlss5-dynamic-streamline.md) |
| §27 | Switching to Games, and a language change that lands elsewhere (2026-11-06, beta.34) | [`spike-notes/27-games-page-2026-11-06.md`](spike-notes/27-games-page-2026-11-06.md) |
| §28 | The main line on .NET 11's release — the whole gate, and what the analyses read (2026-11-11, beta.37, D94–D96) | [`spike-notes/28-dotnet11-main.md`](spike-notes/28-dotnet11-main.md) |
| §29 | C# 15 against the checks — the canary, and where its constructs would go (2026-11-11, beta.37, D96) | [`spike-notes/29-csharp15-canary.md`](spike-notes/29-csharp15-canary.md) |
@@ -0,0 +1,57 @@
## 22 · The owner's runs of beta.24 and beta.25 on real hardware *(2026-10-19)*
The owner ran the installed 0.1.0-beta.25 the evening it shipped and sent five screenshots: Silent Hill 2's session
summary and game page (21:33 local time) and Lies of P's summary (21:47). The numbers below are read from those and from a
read-only SQLite backup copy of the ledger (sessions 60 and 61) — never the data folder. Dev PC: i7-14700KF, RTX 5080,
NVIDIA driver 32.0.16.1742, 2560×1440 at 240 Hz.
### Silent Hill 2 — owner-only items 20(a) and 20(c)
Unreal Engine 5.1, Streamline 2.4.0. The NVIDIA App's profile for the game: DLSS override (preset L, Ultra
Performance); Frame Generation override (×6, preset B, *Dynamic*, target max refresh rate); Streamline DLSS override.
- **20(a), how frame generation was set:** *Set in the NVIDIA App: Dynamic, up to ×6, target: max refresh rate* — the
App's own words. `NGX_DLSSG_DYNAMIC_MULTI_FRAME_COUNT_MAX` 5 read as "up to ×6" and the automatic target as "max
refresh rate" stand on one title.
- **The mix** under Dynamic multi frame generation: ×2.0 17.70 % (111.83 → 225.83 FPS, 35 s), ×3.0 21.60 % (95.75 →
287.18, 42.7 s, the steady state), ×6.1 7.59 % (23.20 → 140.53, 15 s), no frame generation 37.94 % (80.08 FPS, 75 s),
not classified 10.12 % (20 s) — and **×1336.0, 5.06 %, 0.20 → 267.20 FPS, 10 s: a defect.** Its two windows held one
application-frame token each against 1,336 presents each. They are the session's first fifteen seconds, read from the
ledger copy's frames five seconds at a time: 1,369, 4,877 and 1,303 presents with 1, 0 and 1 application frames, then
no present for five seconds and one frame of 13,348 ms — Silent Hill 2 compiling its shaders at start (the owner,
2026-10-19; the PSO hook was not installed in this session, so no PSO count confirms it). After it, 75 s of menus at
~97 FPS with no frame generation, a 3-second stall, then play at ×2 and ×3. A window needed eight presents
and one token, so the ratio of one token was the presents themselves, and the steady state's own rule would have
picked it had it lasted longest. The DLSS line then cited it: *DLSS 4.5 (a ×1336.0 frame-generation state)*. Fixed in
beta.26 (`03_METRICS` §The mix): a window is read only with eight application frames and a ratio up to ×8
(`FgWindow.GenerationCeiling`), a session or live ratio that held above it is refused as `beyond_generation`, and a
stored mix is read by the same rule — this session's ten seconds join *not classified* and the DLSS line cites ×6.1.
Of the 60 sessions in the ledger copy, this row was the only stored value above ×8.
- **20(c), what the override loads:** the summary's *Loaded* line lists `160_E658700.bin` 310.9.16.0 and
`1B0_E658703.dll` 2.14.16.0 from the NVIDIA driver's NGX folder — no census name, which is why the DLSS line names no
library. Which feature each serves is not established: 310.9.16 is a DLSS build number of the 4.5 generation, and
2.14.16 reads as a Streamline version beside the profile's *Streamline DLSS override*.
- The driver line: *DLSS DLL chosen by the driver · preset L · Ultra Performance · Frame Generation override (×6)* —
Ultra Performance from the report's 3, NGX's numbering (beta.24's correction, now on a second session). The header
reads *Upscaler not identified · N/A*: the driver's super-resolution word has no `CREATED | EVALUATE`, as on
2026-10-13, so no quality mode is claimed (D63's rule).
### Lies of P — owner-only item 21
Unreal Engine 4; `amd_fidelityfx_dx12.dll` 1.0.1.37507 (the SDK 1.1.x monolith) and `nvngx_dlss.dll` 3.7.0 loaded; FSR
chosen in the game's menu, its frame generation on.
- **The header reads *FSR 3 · 1707×961 → 2560×1440* — no mode.** The decision table's first branch. The query WAS
hooked: `hooks_installed_mask` 0x83F carries `FL_HOOK_UPSCALER_QUALITY` (bit 11). 1707×961 is 2560×1440 at 66.67 %
rounded up, not the vendor's answer to the size query (1706×960, truncated), so the title did not render at a size it
asked for; at a ratio it asked for (1.5) it would have matched within the pixel the ratio path allows. So it either
asked before the hook was in — a plugin's first query can follow the module's load on the loading thread before the
watchdog installs — or never asked (its own table). Nothing recorded tells the two apart, and either way the honest
answer is no mode: D65 stays built and silent for this title, as the table said. The Performance session was not run.
- Frame generation: ×2.0 for 87.93 % (54.64 → 109.62 FPS), not classified 12.07 % — FSR's own frame generation, named
from its dispatches.
- The DLSS line: *DLSS 3 (library 3.7.0) · Super Resolution 3.7.0, from the game* — the engine's DLSS plugin loads the
library while FSR upscales; D64 names DLSS 3 from its major version, and the line says the library is the evidence.
Not run yet: 20(a)'s ×2/×3/×4 chosen in a game's menu and the App's *Fixed ×6*, 20(b) (Expedition 33), 20(d) (the DLSS 5
title), 20(f)–(g), and item 21's Performance session.
@@ -0,0 +1,86 @@
## 23 · The owner's runs of beta.26 on real hardware *(2026-10-20)*
The owner ran the installed 0.1.0-beta.26 the morning after it shipped, 07:47–08:40 local time, and asked for the
latest eight sessions to be checked (sessions 64–71). The numbers below are read from a read-only SQLite backup copy of
the ledger, the Agent's, the App's and the Overlay's logs and Windows' Application log — never the data folder; the
summaries were rendered from the copy by the App's own window in a scratch test. Same PC as §22 (i7-14700KF, RTX 5080,
NVIDIA driver 617.42, 2560×1440 at 240 Hz).
| Session | Game, and how it was started | What it measured |
|---|---|---|
| 64 | Clair Obscur: Expedition 33, through Steam; the NVIDIA App's DLSS override (preset L, *Balanced*) and Frame Generation *Fixed ×6* | ×6.0 for 94.15 % (82 → 491 FPS), 5.85 % not classified; *Set in the NVIDIA App: Fixed ×6*; *DLSS 4.5 (a ×6.0 frame-generation state)*; the header *Upscaler not identified* (the driver's word, below) |
| 65 | Lies of P, through Steam | Tier 2: hooking was off for the game |
| 66 | Lies of P, through Steam; the game's FSR at *Performance*, its frame generation on | *FSR 3 · 1280×720 → 2560×1440*, no mode; ×2.0 for 95.36 % (59.42 → 118.98 FPS) |
| 67 | The Witcher 3, through Steam | Tier 2: its consent was not given yet |
| 68 | The Witcher 3 (Direct3D 12), started directly; the App's DLSS override (preset L) and *Fixed ×6* | *DLSS · 1707×960 → 2560×1440*; ×2.0 for 77.53 % (118.77 → 237.38 FPS), no frame generation 16.94 % (304 FPS), 5.54 % not classified |
| 69 | Cyberpunk 2077, started directly; ×2, ×3 and ×4 chosen in the game's menu, no App override | ×1.9 2.13 % (186 → 353 FPS, 10 s), ×3.0 13.85 % (64 → 190, 65 s), ×4.0 66.03 % (64 → 255, 310 s), no frame generation 9.59 % (375 FPS), 8.41 % not classified; *Set in the game — no NVIDIA App frame-generation override*; *DLSS 4 (a ×4.0 frame-generation state)* |
| 70 | Silent Hill 2, started directly, 67 s | refused `non_uniform` — the shader compilation at start (§22) is most of a 67-second session; no mix |
| 71 | Silent Hill 2, started outside FrameLedger; the App's *Dynamic*, up to ×6 | ×2.0 27.30 %, **×2.52 2.49 %**, ×3.0 62.41 %, no frame generation 2.93 %, 4.88 % not classified |
### Owner-only item 20(a): the three ways frame generation is set
- **Chosen in the game's menu** (Cyberpunk 2077 — the owner: "cyberpunk 2077 là switch in-game"): ×2, ×3 and ×4 each
formed a state with its own Native → Displayed, and the context line read *Set in the game*. The ×2 state was ten
seconds at 186 → 353 FPS, read ×1.9; how long the owner held ×2 is theirs to compare.
- **The App's *Fixed ×6*** (Expedition 33): ×6.0, in the App's own words.
- **The App's *Dynamic*** (Silent Hill 2): ×2.0 and ×3.0 — and a ×2.52 row, below.
- **The Witcher 3 under *Fixed ×6* presented ×2.0 throughout.** The profile and the driver's report both say the
frame-generation override applied (×6); the game presented one generated frame per application frame for the whole
session, VSync on at 240 Hz. The rows are what the game presented and the context line is the setting
(`03_METRICS` §The mix), so the summary shows both. Why the override did not reach this title — its frame generation
is DLSS 3 through Streamline 2.14.1, and the driver loaded `1B0_E658700.dll` 2.14.16.0 beside it — is not
established.
### A ×2.52 state — fixed in beta.27
Session 71's five-second windows, decoded from the copy with the App's own loader: ×2.00 for two minutes, ×3.00 for
three and a half, and where the *Dynamic* multiplier stepped, windows in between — at 135 s, 251 application frames
followed by one generated frame and 270 by two (×2.53), and ×2.62, ×2.70, ×2.31 later. Three of them pooled into a
×2.52 state for 12.8 s. Every shipping frame generation multiplies by a whole number, so a window is now a state's only
within 10 % of a whole multiplier (`FgWindow.IsNearWholeMultiplier`, `03_METRICS` §The mix); the stored row is read by
the same rule, and the session lists ×2.0, ×3.0, no frame generation and 7.36 % not classified. Of the 70 sessions in
the copy, it was the only stored row between two multipliers.
### The driver's word lost what it said while the game ran — fixed in beta.27
Expedition 33's header read *Upscaler not identified*, and no NVIDIA App mode, under an override the driver line
reports as applied (*preset L · Balanced*). Its stored super-resolution word is `0x8007F`; on 2026-09-06 the same game
under the same kind of override read `0x8067F` while it ran (§9) — the same word with `CREATED | EVALUATE`. The loop
asked the driver one last time after its last drain, after the game had closed, and that answer — the driver still
answers for the pid, with the two bits cleared — was the stored state. Of the 14 sessions in the copy in which the
driver answered, none kept the two bits; The Witcher 3's 2026-10-04 session (DLSS through Streamline, the game's own
library) stored `0x5` with its words marked *changed* between readings. So no stored session could read *DLSS
(driver-reported)*, and none on an NGX-direct title could name the override's mode (D63): owner-only item 20(b) could
not pass on any build before beta.27. Since beta.27 the driver is not asked once the game has gone, and the two bits
stand once a reading carried them (`NgxDriverState.Merge`).
### Start directly, and the crash safety
- **Lies of P hands itself to Steam** (2026-10-19, 21:43 and 21:46, *Start directly*): the process FrameLedger started
left within five seconds with nothing presented, and Steam started the game 1 s later. That process was turned away
while the first session was ending ("one at a time") and never recorded — a launch never said it had ended on its
own, so nothing turned away during one was started after it. Fixed in beta.27 (`04_CAPTURE` §Watch).
- **Expedition 33 closes when started directly** (2026-10-20, 07:49–07:50, three starts): each process left within
five seconds and read *crashed*, the third one refused and unhooked; no crash report and no Unreal crash folder for
any of them. Through Steam the game ran.
- **The crash safety counted those exits.** Each was a hooked session's early abnormal end, and two turned hooking off:
Lies of P at 21:46:36 on 2026-10-19 (the owner switched it on again within a minute; session 61 was measured),
Expedition 33 after its second direct start (07:49:46; the third start was refused) and again at 07:51:06 — after a
start outside FrameLedger that closed four seconds in with one frame presented, hooked: the only early exit of the
morning that no direct start explains. The policy cannot tell a hand-off from the hang it exists for (`19_SAFETY`
§Crash & stability safety); `LIMITATIONS.md` §Play tells users to start such a game through its store.
### The rest
- **Display sizes**: Lies of P's two sessions and three of Dark Souls III's stored no window or monitor size. A game
leaving exclusive full-screen closes its window while its swap chain's last word is still fresh, and the tally kept
the mode's last sample — exclusive, no window. Fixed in beta.27 (`03_METRICS` §Display mode).
- **The DLSS line read only *DLSS*** on The Witcher 3 under the override: the driver's copies loaded under names no
census lists (`160_E658700.bin` 310.9.16.0, `1B0_E658700.dll` 2.14.16.0 — note `…700.dll` where Silent Hill 2 and
Expedition 33 loaded `1B0_E658703.dll`). A line that would say only *DLSS* is not shown since beta.27; the *Loaded:*
line prints the files.
- **Two summary windows of one session** (the owner's screenshot): opening a session whose window is open now brings
that window forward.
- **Owner-only item 21** (FSR's mode on Lies of P): the *Performance* session read no mode either — the first branch on
both. Its render size, 1280×720, is exactly the vendor's Performance size, so a query the hook met would have
matched: the title did not ask while the hook was in. It cannot be launched by FrameLedger as the item asks.
+66
View File
@@ -0,0 +1,66 @@
## 24 · The whole gate on .NET 11 RC3 — what the alpha line's SDK asks of the source *(2026-10-31, beta.32, owner decisions D73–D76)*
**Why this was measured.** The alpha line (`12_BUILD` §The alpha line) builds this source on .NET 11. Before its switch
was written, the switch was applied in a throwaway worktree (branch `probe/net11`, never pushed) and `./build.ps1 check`
run there, to learn what the 11 SDK — its compiler, its analyzers, its runtime — asks of the source, and which of those
asks .NET 10 can also take (those land on main; the rest would be the alpha branch's).
**Where.** The dev box of §Environment (Windows 11 Pro build 29648, i7-14700KF, RTX 5080). SDK
`11.0.100-rc.3.26522.148`, runtime and Windows Desktop `11.0.0-rc.3.26522.148` (the out-of-band security release of
2026-10-25), already installed beside the 10.0 SDKs. The switch: `global.json` → that SDK with `allowPrerelease`;
`Directory.Build.props` → `net11.0-windows10.0.22621.0`; `Microsoft.Extensions.Hosting`, `Microsoft.Data.Sqlite`,
`System.Diagnostics.EventLog` → `11.0.0-rc.3.26522.148`. Nothing else.
**The decision table, written before the run:**
| Finding | Where it is fixed |
|---|---|
| A new analyzer diagnostic whose fix compiles as C# 14 and stays green on .NET 10 | main |
| A new diagnostic only C# 15 syntax or a .NET 11 API can satisfy | the alpha branch: that one rule off in its `.editorconfig`, with the reason |
| NU1510, the package graph, a licence text | the alpha branch |
| A compiler error from C# 15's breaking changes (`with(` in a collection expression, a type named `closed` or `union`, a span collection expression's scope) | main, rewritten so both compile |
| A test whose answer changes only on .NET 11 (`Math.Round`, saturating casts, `Environment.TickCount`, DI's disposal, ZIP CRC) | product code that relied on the old behaviour → main, so both runtimes give the same number; a test's own expectation → main, made robust; each case recorded here |
| `IHost.RunAsync` throwing for a failed `BackgroundService` | accepted on the alpha line; changed only if a test pins the old exit |
| A timing-sensitive test red | re-run once and named; red again → investigated as a defect |
| The coverage gate below its floor only on .NET 11 | investigated; the floor is not lowered |
| Native code | unchanged — MSVC does not see .NET; any difference is a defect |
**What the run found:**
| Step | Result |
|---|---|
| Native build and the 32 `ctest` suites | green, 32 of 32 |
| clang-format | clean |
| Managed build, warnings as errors | **red in four rounds, 21 sites in 14 files — every one fixable in a form .NET 10 also compiles** (below) |
| `dotnet format` | clean |
| Tests | **every suite green**: Domain 422, Application 553, Infrastructure 518 of 520, App 719, CaptureHost 137, Agent 29. The two Infrastructure cases not run are the two that need an administrator's token — the same two, skipped the same way, in the last .NET 10 run on this box |
| coverage-gate | OK — Domain 93.8 %, Application 97.4 %, 32 metric classes at or above 95 % |
| rules-validate, versioninfo-check, chokepoint-check, hookinventory-check, package-closure | OK |
| license-check | red, as it must be: `legal/licenses/nuget/` is the beta's package set (the nine Extensions abstractions now in the runtime, SQLitePCLRaw 3.0.5 and its engine package instead of 2.1.13). Regenerated on the alpha branch, never on main |
**The 21 sites** (`git diff` of this PR is the whole list):
- **CA1307, 13 sites.** .NET 11 adds `string.LastIndexOf(char, StringComparison)` and
`StartsWith`/`EndsWith(char, StringComparison)`, so the analyzer now asks for a comparison on every
`LastIndexOf(char)`, `StartsWith(char)` and `EndsWith(char)` (four, six and three of them, three in tests). Those
overloads do not exist on .NET 10. The span forms — `AsSpan().LastIndexOf(c)`, `AsSpan().StartsWith(c)`,
`AsSpan().EndsWith(c)` (`MemoryExtensions`, present in the 10.0 reference pack) — compare ordinally, as the char forms
did, and satisfy both. One of the three in tests sits in a FluentAssertions expression tree, where a span cannot appear
(CS8640): it reads `m.Length > 0 && m[m.Length - 1] == ' '`.
- **MA0002, 7 sites.** C# 15 lets a collection expression pass a comparer (`[with(StringComparer.Ordinal), …]`), and
Meziantou.Analyzer 3.0.317 now flags a `HashSet<string>` or `Dictionary<string, …>` that `[]` builds without one. C# 14
has no `with(...)`; the constructor given `StringComparer.Ordinal` — what `[]` used, the default comparer of `string` —
compiles on both and changes no answer.
- **CA2026, 1 site** (a rule the 11 SDK's analyzers add): `JsonDocument.Parse(…).RootElement` leaves the document
undisposed; `JsonElement.Parse`, in .NET 10 too, does not (a test's payload).
**What did not happen**, against the table: no compiler error from C# 15's breaking changes; no NU1510 (the repository
references none of the nine `Microsoft.Extensions.*` libraries .NET 11 moved into the shared framework — `Hosting`, the
one it references, stays a package); no test changed its answer, so `Math.Round`'s and the decimal conversions' corrected
rounding, the saturating float-to-small-integer casts, `Environment.TickCount`, DI's aggregated disposal and the ZIP CRC
check moved no expectation of this suite; no test pins the Agent's exit after a failed `BackgroundService`, so .NET 11's
rethrow from `IHost.RunAsync` — the Agent's crash path, with its minidump, where .NET 10 exited 0 — is the alpha line's
behaviour; no timing flake in the one run.
**Not measured here:** an installed alpha on real hardware with a real title, and an alpha updating to the next alpha —
the owner's run of the first alpha.
+151
View File
@@ -0,0 +1,151 @@
## 25 · Xbox app / Microsoft Store (GDK) titles — the layout, the launch chain, the image paths *(2026-11-03, beta.33, owner decisions D77–D82)*
**Why this was measured.** The owner asked for the games the Xbox app and the Microsoft Store install (PC Game Pass
included) to be handled, evaluated and analysed. FrameLedger had no source for them — the import read Steam, GOG, Epic
and itch, and the owner's log of 2026-11-01 lists exactly those four — and `02_SPEC` put "Microsoft Store/UWP/Game Pass
titles (packaged-app injection constraints)" out of scope for v1 without any document saying what the constraints were.
What follows is read from the owner's own installs: first read-only (the layout), then a launch probe the owner allowed
(D77): each game started through its package with nothing of FrameLedger in it, its processes recorded, and closed by
its window.
**Where.** The dev box of §Environment (Windows 11 Pro build 29648, i7-14700KF, RTX 5080), the Agent there running
elevated (D34). Gaming Services and GamingServicesNet running; its drivers `gameflt.sys` and `xvdd.sys` running.
| Title | Package family name | Version | Engine | Executables in `Content` |
|---|---|---|---|---|
| A Game About Digging A Hole (on C:) | `rokapublish.AGameAboutDiggingAHole_6q4vfhsywtz4j` | 1.2.1.0 | Unreal, `Binaries\WinGDK` | `DiggingGame.exe` (233,984 bytes), `DiggingGame\Binaries\WinGDK\DiggingGame-WinGDK-Shipping.exe` (126.1 MB) |
| Ascend to ZERO | `FlywayGames.AscendtoZERO_sey8peye7nc36` | 1.2.1.0 | Unreal, `Binaries\WinGDK` | `AscendtoZERO.exe` (339,968), `MementoMori\Binaries\WinGDK\AscendtoZERO-WinGDK-Shipping.exe` (160.7 MB) |
| Valor Mortis | `LyricalGamesLLC.ValorMortis_72fag5ekhk96y` | 1.3.5124.0 | Unreal, `Binaries\Win64` | `ValorMortisMSG.exe` (297,984), `ValorMortis\Binaries\Win64\ValorMortisMSG-Win64-Shipping.exe` (184.1 MB) |
| FINAL FANTASY I–VI (Pixel Remaster) | `39EA002F.FF1DF_n746a19ndrrjg` … `FF6DF` | 1.2.1.0–1.2.3.0 | Unity IL2CPP | `FINAL FANTASY*.exe` (664,336 each), `UnityCrashHandler64.exe` |
| inKONBINI | `BeepJapan.inKONBINI_h2va14as5wpxj` | 1.0.209.0 | Unity, D3D12 Agility SDK | `inKONBINI.exe` (672,256), `UnityCrashHandler64.exe` |
| Microsoft Jewel | `Microsoft.MicrosoftJewel_8wekyb3d8bbwe` | 1.1.8131.0 | Unity, D3D12 Agility SDK | `Microsoft Jewel.exe` (239,936) |
Every one also has `gamelaunchhelper.exe` (100,808–113,096 bytes) at the root of `Content`.
### Read-only, before any launch
- **The layout.** Each drive the Xbox app installs to holds `.GamingRoot` at its root: the bytes `RGBX`, a 32-bit count,
then that many NUL-terminated UTF-16 folder names relative to the drive (C: `XboxGames`, 28 bytes; D: `xbox`, 18
bytes). Under each folder, one folder per game: `Content\` (the game's files), a `Shaders\` folder and GUID-named
package files beside it; `C:\XboxGames\GameSave` is not a game and has no `Content`.
- **The package's own description**, in `Content`: `MicrosoftGame.config` (the FINAL FANTASY titles spell it
`MicrosoftGame.Config`) — `Identity` Name/Publisher/Version, `ShellVisuals` (DefaultDisplayName,
Square480x480Logo 480×480, Square150x150Logo, StoreLogo, SplashScreenImage 1920×1080, BackgroundColor),
`ExecutableList` (the launch executable: the Unreal root stub, the Unity player), TitleId, StoreId,
`DesktopRegistration/ProcessorArchitecture` x64 — and `appxmanifest.xml`: one `Application` whose Executable is
`GameLaunchHelper.exe` with `EntryPoint="Windows.FullTrustApplication"`, `runFullTrust`, `appLicensing`,
`unvirtualizedResources`, and on all 11 `desktop6:FileSystemWriteVirtualization` and
`desktop6:RegistryWriteVirtualization` set to `disabled`. Exactly one `MicrosoftGame.config` per game, at the root of
`Content`; no reparse point anywhere inside `Content`; no `.sys` file and no anti-cheat folder in any tree; no
`Content` tree holds more than 2,633 entries in all (check 4's budget is 4,096 per walk). Each FINAL FANTASY title
ships `FINAL FANTASY*_Data\Plugins\x86_64\steam_api64.dll`.
- **Three spellings of one file.** Windows registers each package's InstallLocation as
`C:\Program Files\WindowsApps\<PackageFullName>` — a junction to `D:\WindowsApps\<PackageFullName>` (the D: games),
itself a junction to `D:\xbox\<Game>\Content\`; for the C: game, straight to `C:\XboxGames\<Game>\Content\`.
`D:\WindowsApps` cannot be listed by the user; a path through it can still be opened. .NET's
`Directory.ResolveLinkTarget` on the WindowsApps junction: access denied. A `FILE_READ_ATTRIBUTES` handle and
`GetFinalPathNameByHandleW` resolve the whole chain, unelevated:
`C:\Program Files\WindowsApps\LyricalGamesLLC.ValorMortis_1.3.5124.0_x64__72fag5ekhk96y\ValorMortis\Binaries\Win64\ValorMortisMSG-Win64-Shipping.exe`
→ `\\?\D:\xbox\Valor Mortis\Content\ValorMortis\Binaries\Win64\ValorMortisMSG-Win64-Shipping.exe`.
- **The executables refuse to be read or run by anything outside their package.** Every game `.exe` under `Content`
(the stubs, the shipping executables, the Unity players, `UnityCrashHandler64.exe`) answers `CreateFileW` with error 5
for `FILE_READ_DATA` and for `FILE_EXECUTE`, from a standard user's process, although its DACL grants Users read: its
first ACE is `(XA;;0x1200a9;;;BU;(WIN://SYSAPPID Contains "<family name>"))`, then `(A;;FR;;;BU)`, and
`READ_ATTRIBUTES` and `READ_CONTROL` work (size, times and security descriptor read). `gamelaunchhelper.exe` (which
carries an extra explicit Users ACE), every `.dll`, the images and the XML files read. What refuses — most likely the
Gaming Services file-system filter — is not established. Consequences: ~~no `CreateProcess` of a GDK game from outside
its package~~ *(corrected the same day by the run below: `CreateProcess` of one does start a process — never the game
in its package, so it is still not how FrameLedger starts one)*, and nothing of FrameLedger may need an executable's
bytes (its PE header, version resource, imports or strings) — `PeImports` already answers `unknown` for a file it
cannot open, without throwing.
- **Windows' own names for them.** `PackageFamilyNameFromId(Name, Publisher)` computes the family name;
`GetPackagesByPackageFamily` lists the installed full name; `GetPackagePathByFullName` answers the WindowsApps path —
all unelevated, documented `appmodel.h` calls. `<family name>!<the appxmanifest Application Id>` is exactly the
AppUserModelID Windows' Start menu lists for each of the 11 (`Get-StartApps`), e.g.
`LyricalGamesLLC.ValorMortis_72fag5ekhk96y!AppValorMortisShipping` and `39EA002F.FF1DF_n746a19ndrrjg!Game`.
### The probe (D77)
PowerShell with inline C#, from the scratchpad, as the standard user, with no FrameLedger hook enabled for any of these
titles (none is in the library). Six titles, one of each kind: A Game About Digging A Hole, Ascend to ZERO, Valor
Mortis, FINAL FANTASY, inKONBINI, Microsoft Jewel. For each:
1. `IApplicationActivationManager::ActivateApplication(<AUMID>, null, AO_NONE)` — the pid it returns, its HRESULT.
2. Every 100 ms for 30 s, each process that was not there before: pid, parent pid, image name, creation time,
`QueryFullProcessImageNameW` (what the watcher and the guard's `ImageDirectory` read) **and**
`GetModuleFileNameExW(handle, NULL)` (the loader's main-module path — what `TargetResolver` compares through
`MainModule.FileName`), `GetPackageFullName`, `TokenIsAppContainer`, the integrity level, elevation,
`GetProcessMitigationPolicy` (signature, dynamic code, user shadow stack, control flow guard, image load), whether
`OpenProcess(PROCESS_QUERY_LIMITED_INFORMATION | PROCESS_VM_READ)` — the guard's module-scan rights — opens it, and
the first poll at which `dxgi.dll`, `d3d11.dll`, `d3d12.dll`, `D3D12Core.dll` and `vulkan-1.dll` are in its module
list.
3. The ancestors of the game's process up to the first name on the guard's launcher list, each with the same
openability test, and every chain member's module names checked against the rules' fuzzy name fragments.
4. `CloseMainWindow` on the game's window, then up to 20 s for it to exit. A game that stays open is left open and
named to the owner, never killed.
Plus, once each: `explorer.exe shell:AppsFolder\<AUMID>` for FINAL FANTASY (the command Play will use), and one
`CreateProcess` of `FINAL FANTASY.exe` by its path (expected: error 5 — if it starts, it is closed the same way).
### The decision table, written before the run
| Measured | Outcome | Then |
|---|---|---|
| The game process's image path (`QueryFullProcessImageNameW`) | `<root>\<Game>\Content\…`, the final path | the library entry is that path, and the watcher matches it as today |
| | `C:\Program Files\WindowsApps\<Full>\…` | a path under a `WindowsApps` segment is resolved with a read-attributes handle and `GetFinalPathNameByHandleW`, in the watcher's key and in the guard's `ImageDirectory` — only such paths, so no existing entry's key moves |
| The loader's main-module path against the image path | the same | `TargetResolver` moves to `QueryFullProcessImageNameW` all the same: one source of the image path for the watcher, the resolver and the guard |
| | different | that move is what makes a hooked session of a packaged game possible at all |
| The chain | GameLaunchHelper → the game (→ the shipping executable), parents alive | nothing to add: the entry is the process that presents, and the watcher sees it |
| | GameLaunchHelper exits first | the same — the watcher matches by path; no election is needed |
| GameLaunchHelper's parent | `svchost.exe` or `explorer.exe` | the guard's scan set stops there; the launcher list is unchanged |
| | `GamingServices.exe` or another SYSTEM process | it joins the hardcoded launcher list, with this row as the reason — else an unelevated Agent's scan cannot open it and refuses every session |
| A chain member the guard's rights cannot open | none | nothing to add |
| | one | named here; a platform process → the launcher list, anything else → the owner, mid-train |
| A chain member's module with a fuzzy fragment in its name | none | nothing to add |
| | one | recorded with its signature kind; the guard refuses (fail closed) and the owner decides — never relaxed here |
| The token | full trust, the user, medium integrity | the Tier-1 path; a token that is not an AppContainer uses the session's object namespace, so the ring and `Local\FrameLedger.Tolerate.<pid>` work unchanged (the ring itself is first seen in the owner's hooked session) |
| | an AppContainer | refused with a reason of its own (D78) |
| Mitigations | none of: signed-only images, prohibited dynamic code, strict shadow stack, strict CFG | inject |
| | any of them | refused before injecting, the policy named (the refusal is built either way: today each ends as a failed injection, no hooks, or a crash risk) |
| The graphics runtime mapped before a 1 Hz watcher can see the process | yes | the session is `late_attach`, as for a game Steam starts; `dxgiPresentsBeforeHook` says how much |
| `CreateProcess` of a game executable by path | error 5 | D80 stands: Play activates the package in both modes |
### What the run found *(2026-11-03, 03:57–04:09 UTC)*
Every activation answered `S_OK` with the pid of `gamelaunchhelper.exe`. The chain, each time: `gamelaunchhelper.exe`
(in the package; its parent the activating process) → `gamingservicesui.exe` (Gaming Services' own UI, no package,
appearing 0.1–0.8 s after the press and gone again) → `XboxPcTray.exe` (the Xbox app's tray, when not already running)
→ the package's launch executable 6.2–14.4 s after the press → for Unreal, the shipping executable 0.25–0.37 s later as
its child.
`gamelaunchhelper.exe` had exited before the 30 s were up in every run, while the game ran on.
| Title | Launch executable at | Process that presents | Graphics runtime mapped |
|---|---|---|---|
| A Game About Digging A Hole | `DiggingGame.exe` +14.4 s | `DiggingGame-WinGDK-Shipping.exe` +14.7 s | `dxgi` + `opengl32` at its first poll, `d3d11` 2.4 s later |
| Ascend to ZERO | `AscendtoZERO.exe` +8.7 s | `AscendtoZERO-WinGDK-Shipping.exe` +8.9 s | `dxgi` + `opengl32` at once, `d3d12` + `D3D12Core` 2.7 s later |
| Valor Mortis | `ValorMortisMSG.exe` +6.8 s | `ValorMortisMSG-Win64-Shipping.exe` +7.2 s | `dxgi` + `opengl32` at once, `d3d12` + `D3D12Core` 3.1 s later, `d3d11` 3.7 s |
| FINAL FANTASY | `FINAL FANTASY.exe` +8.8 s | the same (+ `UnityCrashHandler64.exe`) | `opengl32` 0.4 s, `d3d11` + `dxgi` 1.2 s |
| inKONBINI | `inKONBINI.exe` +6.8 s | the same (+ `UnityCrashHandler64.exe`) | `dxgi` + `d3d11` + `opengl32` at its first poll |
| Microsoft Jewel | `Microsoft Jewel.exe` +6.6 s | the same (+ six `msedgewebview2.exe` children in its package) | `dxgi` + `d3d11` at once, `d3d12` + `D3D12Core` 0.6 s later |
Against the table above:
| Measured | Outcome | So |
|---|---|---|
| The game process's image path | **`<root>\<Game>\Content\…`** for all six, the C: game included (`C:\XboxGames\…\Content\…`) | the entry is that path; the watcher matches as today |
| The loader's main-module path | **the same string** as the image path, for every process of every chain | no mismatch on these titles; `TargetResolver` still moves to `QueryFullProcessImageNameW` (one source) |
| The chain | GameLaunchHelper → the game (→ the shipping executable); GameLaunchHelper gone before the game is | nothing to add: the watcher matches the entry by path |
| GameLaunchHelper's parent | the activating process: `pwsh.exe` (the probe's `ActivateApplication`), `explorer.exe` (`explorer.exe shell:AppsFolder\<AUMID>`), `dllhost.exe` (below). From the Xbox app itself: not measured | started as Play starts it, the scan set stops at `explorer.exe`; the launcher list is unchanged |
| Chain members the guard's rights cannot open | **none**: every process of every chain — GameLaunchHelper while it lived, the stubs, the shipping executables, the Unity players and crash handlers, Jewel's WebView2 children (two of them at low and untrusted integrity) — opened with `QUERY_LIMITED_INFORMATION \| VM_READ` as the standard user | nothing to add |
| Fuzzy-fragment module names in a chain member | **none** (the Unreal games load `xgameruntime.dll`, `XCurl.dll`, `libHttpClient.GDK.dll`, `GameChat2.dll`, `gameplatformservices.dll`, `gamingservicesproxy_17.dll`, `XblAuthManagerProxy.dll`) | nothing to add |
| The token | every game process: in its package, **not an AppContainer**, medium integrity | the Tier-1 path; the session's object namespace |
| Mitigations | none of the four on any game process: signature `0x0`, dynamic code `0x0`, user shadow stack `0x100` (only `CetDynamicApisOutOfProcOnly`), CFG `0x0`/`0x1` (no strict mode), image load `0x0`. Jewel's WebView2 sandboxes carry signed-only `0x5` and dynamic code `0x1` — children, never a target | inject; the `TargetMitigation` refusal is built for the titles that do |
| The graphics runtime before a 1 Hz watcher sees the process | the Unreal shipping executables import `dxgi.dll` statically and create their D3D device 2.4–3.7 s later; the Unity players have it within 0.1–1.2 s | an attach within the watcher's second is before the Unreal device and around the Unity one: `late_attach`, as for a game Steam starts |
| `CreateProcess` by path | **not error 5.** `FINAL FANTASY.exe` (the package's launch executable): Windows started **`gamelaunchhelper.exe`, outside the package, in its place** (that process's image path and main module both `gamelaunchhelper.exe`), which activated the package — a second, packaged `gamelaunchhelper.exe` (its parent `dllhost.exe`) started `FINAL FANTASY.exe` 6.2 s after the press; the process the caller holds is never the game, and the game is not its descendant. `DiggingGame-WinGDK-Shipping.exe` (not a launch executable): ran **as itself, outside its package** (`GetPackageFullName`: no package), its window up, until closed | D80 stands on two measured grounds instead of the one assumed: a start by path either hands itself to the package within seconds (an early exit the crash safety counts, and a launch whose game it never sees) or runs the game outside its package — which FrameLedger must never cause. The Agent refuses to start an executable under a GDK package root |
**Closing.** Five of the six closed on `CloseMainWindow`; Valor Mortis' window went at once and its two processes
about 40 s later, by themselves. Microsoft Jewel ignored it and was left open for the owner, as agreed.
**Not measured:** a start from inside the Xbox app (GameLaunchHelper's parent there); a package that keeps write
virtualization on (all 11 turn it off), so where the Overlay's log would land in one; any GDK title with anti-cheat;
any Vulkan GDK title; the ring from a packaged process (first seen in the owner's hooked session).
@@ -0,0 +1,85 @@
## 26 · DLSS 5 on Hogwarts Legacy, Dynamic frame generation on Phantom Blade Zero, and Streamline 2.12 → 2.14.16 *(2026-11-06, beta.34, owner decisions D83, D84)*
**Why this was measured.** The owner asked, on 2026-11-06, how FrameLedger detects DLSS 5's Neural Rendering on
Hogwarts Legacy — turned on in the game — and why Phantom Blade Zero under the NVIDIA App's *Dynamic* multi frame
generation, up to ×3, read "DLSS 4" when Dynamic and ×6 exist only in DLSS 4.5; then, while the plan was written,
what had changed in Streamline since the copy the Overlay is built against.
**Where, and how.** The owner's ledger was read **read-only** — Python's `sqlite3` with `mode=ro`, no FrameLedger
binary, the Agent of `0.1.0-alpha.2` running beside it — on the dev box of §Environment (Windows 11 Pro build 29648,
i7-14700KF, RTX 5080, 2560×1440 at 240 Hz; NVIDIA driver 32.0.16.2101, then 32.0.16.2114 from 2026-11-05 18:29).
Streamline's headers were compared with the upstream repository's tags through GitHub's API, byte for byte.
### The NVIDIA App's frame-generation settings against the driver's report
`driver_profile` is the game's profile as the Agent read it at the session's start; the FG word and `frameGenerationMode`
are `NvAPI_NGX_GetNGXOverrideState`'s, from `ngx_driver_words`. Bits: `0x1F` initialised … selected, `0x20` preset,
`0x200`/`0x400` created/evaluated, `0x2000` `FG_MODE`, `0x8000` `FG_MULTI_FRAME`.
| Sessions | The App's setting (profile) | FG word | `frameGenerationMode` | Frames counted |
|---|---|---|---|---|
| Phantom Blade Zero 111, 112, 114 (11-01 → 11-02) | `NGX_DLSSG_MODE` 4 *dynamic*, ceiling 5, target `0x01000000` | `0x263F` | 3 | states ×3.0 … ×4.0, ×5.2, ×6.0 |
| Phantom Blade Zero 116 → 129 (11-03 → 11-05), the eight hooked sessions the driver answered (130 was recovered without its report) | `NGX_DLSSG_MODE` 4 *dynamic*, **ceiling 2**, target `0x01000000` | `0x263F` (`0x203F` once) | 3 | ×2.0 and ×3.0 only; ×3.0 held 75–94 % of each session longer than an hour |
| SILENT HILL 2 60, 71 (10-19, 10-20) | `NGX_DLSSG_MODE` 4 *dynamic*, ceiling 5 | `0xA03F` | 3 | ×2.0, ×3.0, ×6.1 |
| Clair Obscur: Expedition 33 64, The Witcher 3 68, SILENT HILL 2 36 | `NGX_DLSSG_MODE` 2 *on*, multi-frame count 5 (*Fixed ×6*) | `0xA03F` | 1 | ×6.0; Witcher 3 ×2.0 |
| Cyberpunk 2077 69 (multiplier chosen in the game) | none set | `0x5` | 0 | ×1.9, ×3.0, ×4.0 |
So the driver reports `FG_MODE` applied under both of the App's modes and its own mode number tells them apart — 3 under
Dynamic, 1 under Fixed, on all sixteen sessions — but NVIDIA's header names neither number. **What D83 reads is the
profile's value, which the header does name (4, `NGX_DLSSG_MODE_DYNAMIC`), with the report's `FG_MODE` bit as proof the
driver applied it**, and DLSS Frame Generation identified in the session (`fg_mode = dlssg`, whether or not its factor
was counted). The ceiling's decode (frames generated per
rendered frame, `03_METRICS` §The mix) held: a ceiling of 5 reached ×6.0, a ceiling of 2 never passed ×3.0.
**Decided (D83):** a session the driver reports running the App's Dynamic mode is **DLSS 4.5**, below a measured ×5 and
above every DLSS 4 row; *Fixed* stays the frames' to name (`05_DETECTION` §DLSS generation).
### DLSS 5 on Hogwarts Legacy
Session 132 (2026-11-06 13:56, hooked, attached, 141 s, Neural Rendering on in the game): `runtime_modules` holds
**`nvngx_dlssnr.dll` 310.9.16.0, loaded from the game's folder** — the name `CensusNames` carried from community sources
(owner-only item 20(d)) seen on a real game for the first time — beside `nvngx_dlss.dll`, `nvngx_dlssd.dll`,
`nvngx_dlssg.dll` 310.9.16.0 and Streamline 2.14.16 (`sl.interposer.dll`, `sl.common.dll`, `sl.dlss_g.dll`,
`sl.reflex.dll`). The install ships the matching Streamline plugin, `Engine\Plugins\Runtime\Nvidia\StreamlineCore\
Binaries\ThirdParty\Win64\sl.dlss_nr.dll` (402,048 bytes; `nvngx_dlssnr.dll` is 266,424,944), which no list asked about.
The driver's super-resolution word read `0x80605` (created and evaluated, no override); the session identified DLSS Frame
Generation but refused a factor (non-uniform, ×1.97 overall); 140.2 FPS presented.
What the App made of it: *DLSS · Super Resolution 310.9.16, from the game · … · DLSS 5 runtime loaded* — loaded, never
whether it ran. Nothing measured that: an evaluation of a Streamline feature the Overlay does not decode lights
`FL_FEAT_SL_UNDECODED`, which the Agent does not store, and the session's `sl_tag_census` (`0x20E00`) shows only that
the game tags a buffer type the census does not name, per frame (bit 17) — which Streamline 2.14 names, below.
### Streamline: the vendored copy against the releases
The vendored closure (`src/native/third_party/streamline`, "main, 2026-08-09") is **byte-identical to tag `v2.12.0`**,
all eleven files. Releases since: `v2.14.1` (2026-09-08: V-Sync and frame-rate limiters in Dynamic multi frame
generation, `VK_NV_low_latency2`) and `v2.14.16` (2026-10-16: fixes) — the version Hogwarts Legacy ships and the NVIDIA
App's override loads (`1B0_E658700.dll` 2.14.16.0). From `v2.12.0` to `v2.14.16` three of the eleven change:
- `sl_core_types.h`: **`kFeatureDLSS_NR = 1004`**; buffer types 70–72, reserved until then, become
`kBufferTypeUpliftInputColor`, `kBufferTypeUpliftOutputColor` and `kBufferTypeUpliftControlMask` — "neural-net
uplift passes", DLSS 5's inputs; `Resource::reserved` (32 bits) becomes `internalFlags` + `reserved` (16 each, the
struct's size unchanged).
- `sl_struct.h`: `kStructVersion7`.
- `sl_version.h`: 2.14.16.
`sl_core_api.h` (`PFun_slEvaluateFeature`), `sl_dlss.h`, `sl.h` and `license.txt` are unchanged, and nothing of
FrameLedger reads `Resource::reserved`. **Decided:** re-vendor at `v2.14.16` (the owner: "check what changed … and fix it
if really needed") so the Overlay decodes DLSS 5's evaluations by the vendor's own constant (D84).
### What beta.34 builds on it, and owner-only item 30(a)'s decision table — written before the run
Built (D84): the Overlay decodes `kFeatureDLSS_NR` into `FL_FEAT_SL_NEURAL_RENDERING` and publishes
`FL_HOOK_SL_NEURAL_RENDERING` with the detour; the Agent stores `dlss_nr_pct` — the share of the Streamline batches that
carried it — only from a writer that published the family. The harness drives the id through an injected Overlay
(`guard_test`, *DLSS 5's neural rendering is its own fact*). What no fixture can say is whether Hogwarts Legacy evaluates
neural rendering through `slEvaluateFeature` at all; one short hooked session each:
| Neural Rendering in the game | `dlss_nr_pct` | What it means, and what follows |
|---|---|---|
| On | above 0 | the game evaluates it through Streamline: *DLSS 5 (neural rendering on N % of rendered frames)* — D84 holds as built |
| On | 0 | Streamline batches drained and none carried 1004: neural rendering runs another way (NGX directly, or another id). The line reads *runtime loaded, not seen running*; record the session's `sl_tag_census`, and the decode is revisited before anything is named |
| On | NULL | no Streamline batch drained, or the family is missing from `hooks_installed_mask` (bit 12): the detour never installed — record which |
| Off | 0, the runtime loaded | the runtime loads with the feature off: "loaded" never meant "on", which is why D84 waits for the evaluation |
| Off | NULL, the runtime not loaded | the game loads it only when on — recorded, nothing changes |
@@ -0,0 +1,41 @@
## 27 · Switching to Games, and a language change that lands elsewhere *(2026-11-06, beta.34)*
**Why this was measured.** The owner, 2026-11-06: switching from any page to Games stalls about 0.5–1.5 s before the
page appears; and changing the language in Settings brings back the last content page (a game's detail) instead of
Settings. §21 (beta.23) had measured the library at 275 ms for 48 games and left it, the grid non-virtualizing by the
owner's decision (2026-10-15); the library has 65 games now.
**What the code showed** (read, then measured): every page is transient and rebuilt per visit; `GamesViewModel` read the
settings, the games and the per-game session summary on the UI thread (Microsoft.Data.Sqlite completes its asynchronous
calls synchronously), then asked for every executable's file **and showed no card until all had answered** — 39 of the
owner's 41 Steam games are on the USB drive D:, which sleeps — and cleared and re-added every card on each read; the list
view's `DataGrid` had no height bound and built every row. WPF UI's `NavigationCacheMode` would not have helped: 4.3.0
reads it only when the NavigationView has neither a service provider nor a page provider, and this App sets one. The
language: `ShellHost` remembered only pages opened from code (`PageNavigator`), never a pane click.
**The decision table, written before the runs:** fix what keeps the first card from appearing, what rebuilds a page on
every visit, and what blocks the UI thread ≥ 50 ms; leave the grid non-virtualizing (the owner's decision); record the
rest.
**How.** A scratch xUnit test over the App's own `GamesViewModel` and `GamesPage` (not committed — it times, and a timing
assertion in CI is a flake), Release, on the dev PC of §21: a scratch ledger shaped like the owner's — 65 games, a third
with a session — with the first executable check held **800 ms** (a USB drive waking) and every later one answering at
once. Seven iterations a run, the median; three runs a side, the code before this change (PR-3's tree) and after it.
*First cards*: from the view model's construction to all 65 cards listed. *Build*: a new page laid out at 1200×900 with
its 65 cards. *Revisit*: before, a new page again (every visit built one); after, the kept page laid out again.
| | before (three runs) | after (three runs) |
|---|---|---|
| First cards | 822 – 830 ms | 10 – 15 ms |
| Build (first visit) | 165 – 197 ms | 164 – 223 ms — the same work, run-to-run noise |
| Revisit | 181 – 215 ms | 15 – 16 ms |
**Built** (beta.34): the window keeps the library page it built (`Services.WindowPageCache`, the window's own page
provider, set after `INavigationService.SetNavigationControl`) and the page reads the library again each time it is shown
(`GamesViewModel.Attach`); the library is read on the thread pool; the cards are listed first and the executable checks
follow, each card getting its *Not installed* pill when its check answers; a read keeps every card that would look the
same (`GameCardViewModel.LooksLike`, `GamesViewModel.Sync` — no `Clear`); the list view is bounded (`MaxHeight` 640).
`ShellHost` notes every page the live window shows, so a rebuild opens on Settings after a change made there.
**Left as it was:** the first visit's build (≈ 2.5–3.4 ms a card at 65) — the non-virtualizing grid's cost, unchanged by
decision; a page kept per window holds its 65 cards' visuals for the window's life.
+46
View File
@@ -0,0 +1,46 @@
## 28 · The main line on .NET 11's release — the whole gate, and what the analyses read *(2026-11-11, beta.37, owner decisions D94–D96)*
**Why this was measured.** The owner moved the main line to .NET 11 the day after it shipped (D94), setting aside the
condition `20_OPEN_QUESTIONS` §G had written for it — two alphas on the released runtime. §24 measured Release Candidate
3 on a throwaway branch; nothing had measured the release, and three things had never met .NET 11 at all: CodeQL's C#
analysis (a required check, main-only), SonarCloud's scanner, and a Velopack delta across two runtime majors. This note
is what stood in for the condition that was set aside.
**Where.** The dev box of §Environment (Windows 11 Pro build 29648, i7-14700KF, RTX 5080). SDK `11.0.100`, runtime and
Windows Desktop `11.0.0` (released 2026-11-10), installed beside the 10.0 SDKs. The hosted runner: image
`windows-2025-vs2026`, Visual Studio 18 Enterprise, MSVC 14.51.
**The switch, on main this time** (branch `beta37/pr1-net11`): `global.json` → `11.0.100`, `allowPrerelease` false;
`Directory.Build.props` → `net11.0-windows10.0.22621.0`; `Microsoft.Extensions.Hosting`, `Microsoft.Data.Sqlite`,
`System.Diagnostics.EventLog` → `11.0.0`; `legal/licenses/nuget/` regenerated (78 packages → 69, the alpha's set at
released versions). Nothing else in the build.
**What the release asked of the source that RC3 had not.** Two sites, both in tests written after the last alpha was
cut (beta.35's `ContrastThemeTests.Drawn.cs`): CA1307 on `string.StartsWith(char)` and `string.EndsWith(char)`, which
.NET 11 gives a `StringComparison` overload. They take that overload now — the main line compiles against .NET 11, so
§24's rule (a form .NET 10 also compiles) no longer binds. The 21 sites §24 fixed stayed quiet.
**`IHost.RunAsync`, observed for the first time.** §24 read Microsoft's note that a failed `BackgroundService` now fails
`RunAsync` and recorded that no test pinned it. `HostBackgroundFailureTests` does: a host with one service that throws
fails `RunAsync` with that exception on 11.0.0. The Agent's `--serve` therefore leaves through its crash report
(`10_LOGGING` §Crash handling) where it exited 0 on .NET 10; it was accepted, not wrapped.
**The gate, on the dev box (`./build.ps1 check`, 338 s, all gates passed).** Native: 32 of 32 suites. Managed: the build
with warnings as errors, 0 warnings; `dotnet format` clean; 2,561 tests passed and 2 skipped in the six projects (Domain
429, Infrastructure 578 and the 2 skipped, Application 568, CaptureHost 137 with its end-to-end cases, App 816, Agent
33), every one on `net11.0`; the coverage floors held (12 reports); `license-check` green on the regenerated texts. No
test changed its answer between .NET 10 and .NET 11.
**The pull request's own runs (#376, 2026-11-11), which were the first of each on .NET 11:**
| Run | What it showed |
|---|---|
| `check` (42916490997) | green in 12 min 22 s on the hosted runner, SDK 11.0.100 installed by `setup-dotnet` from `global.json` |
| `analyze (csharp, none)` (42916491104, CodeQL 2.27.4) | green in 4 min 5 s. Build mode `none` used the runner's 11.0.100 SDK for references (on .NET 10 it downloaded 10.0.100 itself): 1,221 source files found, 363 references resolved and none unresolved, 9 types unresolved (main's last run on .NET 10: 23 in three `Windows.Win32` namespaces), and "CodeQL scanned 1220 out of 1220 C# files" — the same line as main's last run. CodeQL's documentation lists C# up to 14 and .NET up to 10; *(Corrected the same day: this was an **overlay** analysis — the changed files, on top of `main`'s cached database — and its "1220 out of 1220" was `main`'s baseline. The whole source was read by `main`'s run after the merge, 42921492229: "Overlay mode not enabled", 1,221 files found and "CodeQL scanned 1221 out of 1221 C# files", 363 references resolved, none unresolved, 23 types unresolved as on .NET 10, 4 min 45 s.)* `net11.0` with source that uses no C# 15 construct is read whole |
| `analyze (cpp, manual)` | green, 7 min 7 s — the native layer did not change |
| `sonarcloud` | green, the gate passed: the SonarScanner for .NET 12.0.0 (a `netcoreapp3.1` tool that rolls forward to the newest major) ran on the 11.0 runtime |
| Qodana (42916491047), the Community linter with the interim | the `bootstrap` line installed SDK 11.0.100 into the container, InspectCode 2026.2.3.1 loaded all thirteen `net11.0-windows` projects, and it reported **1 problem**: a redundant `!` in the new test, fixed in the same pull request |
| `release.yml` rehearsal on the branch (42916488083, `0.1.0-beta.37`) | green. `setup-dotnet` installed SDK 11.0.100 and, for `vpk` 1.2.161, the .NET 10 line (SDK 10.0.404, runtime 10.0.15). **The first delta across two runtime majors**: "Delta processed 0443 files. 0372 patched, 0071 unchanged, 0009 new, 0017 removed" — 72,604,898 bytes, against a full package of 110,314,263 (beta.36's: 107,902,117) and a `Setup.exe` of 117,828,375 |
**Not measured here.** An installed build on real hardware and a hooked title on .NET 11.0.0 (owner-only item 34);
Windows 10 22H2, which no version of FrameLedger has been run on; a processor without x86-64-v2.
+61
View File
@@ -0,0 +1,61 @@
## 29 · C# 15 against the checks — the canary, and where its constructs would go *(2026-11-11, beta.37, owner decision D96)*
**Why this was measured.** The owner asked for C# 15 on the main line in the same release that moved it to .NET 11 (D96).
The plan's rule, approved with it: a construct is used only where (1) the build, its analyzers and `dotnet format` take
it without an analyzer being switched off, (2) CodeQL extracts its file without an error, and (3) Qodana does not report
errors that are only its engine not knowing the syntax. So each construct was written once, in a file of its own, and
shown to each tool before any product code used it.
**The canary** (branch `probe/csharp15-canary`, draft pull request #377, closed unmerged): four files under
`tests/FrameLedger.Domain.Tests/Canary/`, one construct each, each with a test that runs —
```csharp
HashSet<string> set = [with(StringComparer.OrdinalIgnoreCase), "a", "A"]; // collection expression arguments
private closed record State; private sealed record Idle : State; // a closed hierarchy, switched over
private union Pet(Cat, Dog); // a union, switched over
outer: foreach (int[] row in rows) { foreach (int cell in row) { if (cell < 0) { continue outer; } } } // a labeled jump
```
**What each tool made of them.**
| Construct | SDK 11.0.100's compiler, its analyzers (`latest-all`), Roslynator 5.0.1, Meziantou 3.0.319, VS Threading 18.12.1 | `dotnet format` | ReSharper's engine: InspectCode 2026.2.3.1 (what Qodana 2026.2 runs) | InspectCode 2026.3.0 (the newest released) |
|---|---|---|---|---|
| Collection expression arguments, `[with(…), …]` | builds, 0 warnings | clean | **error** — "Feature 'collection expression arguments' is not available. Please use language version 'preview'." | the same error |
| Closed hierarchy, `closed record` | builds, 0 warnings; the switch needs no default arm | clean | **not parsed** — "Cannot resolve symbol 'closed'", "Unexpected token", then CS8509 on the switch it reads as open | the same |
| Union, `union Pet(Cat, Dog)` | builds **only with CA1815 silenced**: the SDK's own rule asks every union — a struct — to override `Equals` and the equality operators | clean | **not parsed** — "Cannot resolve symbol 'union'", "Identifier expected" | the same |
| Labeled `continue` / `break` | builds, 0 warnings | **moves the label one indent to the left** (`csharp_indent_labels`), the statement staying on its line | **not parsed** — "; expected", "Cannot resolve symbol 'outer'", and the loop's tail read as unreachable | **error** — "Feature 'labeled break and continue' is not available. Please use language version 'preview'." |
The four tests passed. No analyzer threw on a syntax node it did not know (an `AD0001` would have been an error here).
InspectCode was run on the dev box with `--toolset-path` at SDK 11.0.100's `MSBuild.dll`, a fresh caches folder each
time; 2026.2.3.1 reported 29 results in the four files, 2026.3.0 24.
**CodeQL (2.27.4): not established, and why a pull request cannot establish it.** `analyze (csharp, none)` was green on
the canary's pull request in 3 min 10 s, and its log says "Reading overlay changes": on a pull request the C# analysis is
an **overlay** — it extracts the files the pull request changed on top of the database cached from `main` — and its log
prints no per-file extraction result. "CodeQL scanned 1220 out of 1220 C# files" is `main`'s baseline figure, printed
unchanged on a pull request that had added eight files. The SARIF the code-scanning API returns carries no extraction
notification. CodeQL's documentation lists C# up to 14. So this run neither shows that CodeQL reads these constructs nor
that it does not; a full analysis needs a run that is not a pull request's (`codeql.yml` takes `workflow_dispatch`
since this pull request, for that).
**The conclusion, by the rule.** No C# 15 construct is used on the main line in 0.1.0-beta.37: every one of the four
fails condition (3) — Qodana's engine would report errors in each file that used one, on a gate of zero — and the union
fails (1) as well. What the main line takes from .NET 11 in this release is **API, not syntax**: the
`string.StartsWith` / `EndsWith` / `LastIndexOf(char, StringComparison)` overloads (sixteen call sites that §24's rule had
written as spans, or that §28 fixed), and `Process.TryGetProcessById` in place of a caught `ArgumentException`.
**What unblocks each, and where it would go** — the survey of 2026-11-11 over the thirteen projects, kept so the next
attempt starts from it:
| Construct | Waits for | Where it would go |
|---|---|---|
| `[with(comparer), …]` | a ReSharper engine that reads C# 15 as released, in the Qodana linter | the seven sites §24 wrote with explicit `StringComparer.Ordinal` constructors for MA0002, and about fifteen more local `HashSet`/`SortedSet` constructions (`GameFileProbe`, `CaptureOrchestrator`, `LibraryImporter`, `GameTitleGuess`, …). Not the `IReadOnlySet`-typed statics (not a collection-expression target) nor `ConcurrentDictionary` |
| `closed` | the same; and CodeQL's reading, measured by a dispatched run | `Application/Watch/WatchEvent` (the one abstract record in `src/`); and, as closed record hierarchies rather than unions, the hand-written "one of" shapes: `Domain/Detection/EngineMatch` (with `RuleEvaluator.MatchPlatform`), `Application/Recording/FgVerdict` with the identity and the withheld reason it travels with, `Application/Telemetry/GameProcess`, the Agent's private `ElevationDecision` |
| `union` | the same, **and** CA1815 settled — a union that must hand-write its equality is not shorter than what it replaces | only a value that is one of several *existing* types: `IRingAttacher.TryAttach`'s `(ICaptureSink?, ShmAttachRefusal)` |
| Labeled `continue` | the same | one site: `Infrastructure/Detection/InstallRoot.cs`, the `hit` flag |
| Extension indexers | — | nowhere: the six extension methods in `src/` are not index-like |
**Left as they are, whatever the tools read:** the enums whose names are stored or cross a wire
(`SessionEndReason`, `AntiCheatRefusalReason`, `ShmAttachRefusal`, `Tri`), and `AntiCheatVerdict` (it mirrors a native
result, and "zeroed means not evaluated" is a rule of the guard). And the two preview features — runtime-async and the
updated memory-safety rules — which D76's "no preview feature" still excludes.
+2 -2
View File
@@ -1,7 +1,7 @@
{
"$comment": "Pins the SDK band. Without this, dotnet picks the newest installed SDK — on a machine with a .NET 11 preview present that silently changes analyzer behaviour under TreatWarningsAsErrors and makes local and CI disagree for reasons invisible in a diff. See docs/12_BUILD.md.",
"$comment": "Pins the SDK band: .NET 11 since 0.1.0-beta.37 (owner decision D94, 2026-11-11). Without this, dotnet picks the newest installed SDK — on a machine with a .NET 12 preview present that silently changes analyzer behaviour under TreatWarningsAsErrors and makes local and CI disagree for reasons invisible in a diff. The alpha branch carries this same file while its line rests. See docs/12_BUILD.md.",
"sdk": {
"version": "10.0.100",
"version": "11.0.100",
"rollForward": "latestFeature",
"allowPrerelease": false
}
+7 -1
View File
@@ -2,7 +2,10 @@
## What you need
- **Windows 10 (22H2) or Windows 11, 64-bit.**
- **Windows 11, 64-bit.** FrameLedger may also run on Windows 10 (22H2), but it has not been tested there and nobody
supports it: it is built on .NET 11, which Microsoft supports on Windows 11.
- **A processor Windows 11 accepts.** On an older one, without the SSE4.2 and POPCNT instructions, FrameLedger does
not start.
- Games FrameLedger can measure: **64-bit DirectX 11, DirectX 12 and OpenGL games.** Other games — 32-bit games,
DirectX 9 games, and Vulkan games you start yourself — are still recorded (how long you played, your PC's sensors,
the game's memory use), but not measured. [Limitations](../LIMITATIONS.md) has the full list.
@@ -44,6 +47,9 @@ startup**, and check by hand with Help ▸ Check for updates.
far) looks for test versions, a release looks for releases. Choose *Stable* or *Beta* to decide yourself. Before
0.1.0-beta.14 the channel was *Stable* by default and found no version at all — on an older copy, choose *Beta* to update.
An **alpha** — an experimental build on a new .NET — updates only to newer alphas, and its channel is locked; a beta
never updates to an alpha. Installing one, and going back: [Alpha builds](11-alpha-builds.md).
## Uninstall
Uninstall FrameLedger from Windows Settings ▸ Apps. It asks before it deletes your recordings folder.
+4 -2
View File
@@ -3,8 +3,8 @@
## 1. Add the game
- **File ▸ Add game…** — pick the game's `.exe` file.
- **File ▸ Import library…** — FrameLedger lists the games installed through Steam, GOG, Epic and itch.io, and you
tick the ones to add.
- **File ▸ Import library…** — FrameLedger lists the games installed through Steam, GOG, Epic, itch.io and the Xbox app
(or the Microsoft Store — PC Game Pass games included), and you tick the ones to add.
Every game is added with **hooking off**.
@@ -33,6 +33,8 @@ why it was not measured.
- **It found anti-cheat.** FrameLedger then turns hooking off for that game and says why on the game's page.
- **The game is 32-bit or uses DirectX 9.**
- **It is a Vulkan game** you started yourself.
- **It is an older Microsoft Store app (UWP)**, or Windows runs the game under code protection the component cannot
live under.
- **The game runs as administrator.** Settings ▸ Capture agent ▸ *Run the agent as administrator* can help (off by
default; Windows asks every time the agent starts). Read its risk in [Limitations](../LIMITATIONS.md) first.
- **The game was already running when FrameLedger was updated** — restart the game once.
+10 -5
View File
@@ -19,9 +19,11 @@ A value FrameLedger could not measure reads **N/A** — never 0, and never an es
settled. For FSR it is the mode the game asked AMD's library about and then rendered at; at a dynamic resolution
none is shown.
- **The DLSS line** names the DLSS the game ran: *DLSS 4.5* or *DLSS 4* only when the session showed it (the model
preset the NVIDIA driver reports, or a frame-generation multiplier of ×3 and above), each DLSS library's version and
whether it came from the game or from the graphics driver (the NVIDIA App can swap in the driver's copy), and *DLSS 5
runtime loaded* when it was.
preset the NVIDIA driver reports, a frame-generation multiplier of ×3 and above, or the NVIDIA App's *Dynamic* frame
generation, which is DLSS 4.5's), each DLSS library's version and
whether it came from the game or from the graphics driver (the NVIDIA App can swap in the driver's copy). *DLSS 5*
heads the line when the game was seen running its neural rendering — with the share of the frames it rendered —; its
library loaded and nothing seen reads *DLSS 5 runtime loaded* (*not seen running* when FrameLedger looked). With nothing to add to the header's *DLSS*, it is not shown.
- **Frame generation in this session** (sessions recorded with 0.1.0-beta.24 or later) lists every frame-generation
state the session held — `×2.0`, `×4.0`… — each with its own frame rates and its share of the time, then the time
without frame generation, and *Not classified* for time in no state that lasted at least 10 seconds: switching,
@@ -65,10 +67,13 @@ correct it by hand — your correction is labelled as yours.
- **Sensors** — temperatures, load and power; video memory; memory; and the card's clocks and fan, with the moments it
was held back shaded. The game's own line and the whole card's or the whole PC's are drawn separately.
- **Trend** (on the game's page) — one point per session over time, for example before and after a driver update.
Changes to your hardware or driver are marked on it.
Each day your graphics driver, graphics card, processor, display or Windows changed is a dashed line with a number
above the chart, 1 for the oldest; the list under the chart says what changed that day, and pointing at the line
shows the same. *Sessions at a glance* numbers the same days the same way.
- **Compare** (in the navigation on the left) — pick sessions, even of different games, and see them side by side.
To look closer, hold **Ctrl** and turn the mouse wheel over a chart to zoom, drag to pan, and double-click to reset. The
To look closer, hold **Ctrl** and turn the mouse wheel over a chart to zoom, drag to pan, and double-click to see all of
it again — or Tab to the chart and use the arrow keys, **Ctrl** with an arrow to zoom, and **A**. The
wheel alone scrolls the page.
## Export
+2 -1
View File
@@ -12,7 +12,8 @@ nothing is uploaded. The only network requests are the update check and the upda
Your game library; your sessions — frame times when a game was measured, the statistics, your PC's sensors, the game's
own memory use, how the game's window was shown; a short description of your hardware for each session; your tags and
notes; your settings; and, in the `covers` folder, a copy of each picture you chose for a game. The pictures the Steam and
GOG GALAXY apps keep for your games are shown from where those apps keep them, never copied. The
GOG GALAXY apps keep for your games, and those an Xbox game ships in its own folder, are shown from where they are, never
copied. The
[Privacy Policy](../legal/PRIVACY_POLICY.md) lists all of it.
## How much is kept
+2 -1
View File
@@ -8,7 +8,8 @@ FrameLedger cannot measure. The session's summary says which. See [Record a game
## I switched hooking on, and the game is still not measured.
FrameLedger refuses a game where it finds anti-cheat, and cannot measure 32-bit games, DirectX 9 games, Vulkan games you
start yourself, or a game that runs as administrator (unless the agent does too). A game that was already running when
start yourself, or a game that runs as administrator (unless the agent does too). A game from the Xbox app is measured from a few
seconds after it starts, because Windows starts it. A game that was already running when
FrameLedger updated needs one restart. The game's page and the session's summary say what happened.
## Why "Presented FPS" and not the game's own frame rate?
+42 -27
View File
@@ -27,27 +27,29 @@ stopped, hooking turned off — each with one button that only says you have rea
| Menu | Item | What it does |
|---|---|---|
| **File** | **Add game…** | Pick a game's `.exe` file. It is added with hooking off, and its page opens. |
| | **Import library…** | A checklist of the games installed through Steam, GOG Galaxy, Epic and itch.io. |
| | **Export** ▸ **Session CSV** · **Session JSON** · **Chart PNG** | Saves the session you last selected or opened. Read [Your data](05-your-data.md) before you share a file. |
| | **Exit** | Quits FrameLedger, even when *Minimize to tray on close* is on. |
| **File** | **Import library…** | A checklist of the games installed through Steam, GOG Galaxy, Epic, itch.io and the Xbox app (or the Microsoft Store). |
| **File** | **Export** ▸ **Session CSV** · **Session JSON** · **Chart PNG** | Saves the session you last selected or opened. Read [Your data](05-your-data.md) before you share a file. |
| **File** | **Exit** | Quits FrameLedger, even when *Minimize to tray on close* is on. |
| **Tools** | **Agent status…** | Opens the Dashboard, where the agent's card is. |
| | **Update detection rules** | The agent reads its detection rules again and checks your games again. |
| | **Vulkan layer registration…** | Opens Settings, where the Vulkan layer is. |
| | **Open data folder** | Opens `%LOCALAPPDATA%\FrameLedger` in Explorer. |
| | **Database maintenance…** | **Check**, **Back up…**, **Sweep…** and **Compact** your database ([When something goes wrong](09-troubleshooting.md#the-database)). |
| **Tools** | **Update detection rules** | The agent reads its detection rules again and checks your games again. |
| **Tools** | **Vulkan layer registration…** | Opens Settings, where the Vulkan layer is. |
| **Tools** | **Open data folder** | Opens `%LOCALAPPDATA%\FrameLedger` in Explorer. |
| **Tools** | **Database maintenance…** | **Check**, **Back up…**, **Sweep…** and **Compact** your database ([When something goes wrong](09-troubleshooting.md#the-database)). |
| **Help** | **User guide** | This guide. |
| | **Check for updates** | Asks GitHub now. |
| | **Report a bug…** | Builds a report on your PC ([When something goes wrong](09-troubleshooting.md#report-a-problem)). |
| | **Online documentation** | The project's page on GitHub. |
| | **Limitations** | What FrameLedger cannot do. |
| | **About FrameLedger** | The version, the licences and the notices. |
| **Help** | **Check for updates** | Asks GitHub now. |
| **Help** | **Report a bug…** | Builds a report on your PC ([When something goes wrong](09-troubleshooting.md#report-a-problem)). |
| **Help** | **Online documentation** | The project's page on GitHub. |
| **Help** | **Limitations** | What FrameLedger cannot do. |
| **Help** | **Accessibility** | What works with the keyboard alone, a screen reader or a contrast theme, what does not yet, and how to report a problem. |
| **Help** | **About FrameLedger** | The version, the licences and the notices. |
## Dashboard
- **Live capture** — the game being recorded right now: its name, **T1** (measured) or **T2** (recorded only), and the
time so far. While it is measured: the frame rate, the resolution, the upscaler, frame generation, ray tracing, the GPU
and CPU temperatures and the game's memory. *Attached — waiting for the first frames…* means hooking worked and the
first frames are on their way.
- **Live capture** — each game being recorded right now, one card per game (two games side by side, and *2 games
recording* beside the title): its name, **T1** (measured) or **T2** (recorded only), and the time so far. While it is
measured: the frame rate, the resolution, the upscaler, frame generation, ray tracing, the GPU and CPU temperatures and
the game's memory. *Attached — waiting for the first frames…* means hooking worked and the first frames are on their
way.
- **Games tracked**, **Total playtime**, **Sessions this week**.
- **Capture agent** — *State*, *Agent version*, *Telemetry source* (which sensor readers work on this PC: `l1` is
Windows itself, `lhm` is LibreHardwareMonitor, `nvapi` is NVIDIA's own and only on NVIDIA cards), *Overlay build* (the
@@ -58,6 +60,9 @@ stopped, hooking turned off — each with one button that only says you have rea
## Games
- **Search games**; sort by **Name**, **Last played** or **Playtime**; **Show as a list** or **Show as a grid**.
- **Filters** (since 0.1.0-beta.34): by **store**, **engine**, **state** (Hooking on, Hooking off, Anti-cheat, Exception,
Not recorded), **installed** and **played**; the title then says how many of your games are shown. **Clear filters**
shows them all again.
- **Refresh** reads your library again: it offers games newly installed through a store, and marks a game whose `.exe`
is gone as *Not installed*. The agent removes such a game by itself after ten minutes when it has no sessions and its
drive is connected — never one where anti-cheat was found (**Settings ▸ Data ▸ Remove uninstalled games** turns this
@@ -70,23 +75,26 @@ stopped, hooking turned off — each with one button that only says you have rea
## A game's page
- **At the top:** the game's picture — a banner and its cover, from the Steam or GOG GALAXY app on your PC or the image
you chose — in a band that takes the picture's colour; then the name, publisher, version, store and engine, the `.exe`
- **At the top:** the game's picture — a banner and its cover, from the Steam or GOG GALAXY app on your PC, the logo and
splash image an Xbox game ships in its own folder, or the image you chose — in a band that takes the picture's colour; then the name, publisher, version, store and engine, the `.exe`
path, the last session, the last measured session's frame rate and its ray-tracing chips. A game with no picture shows
none (**Settings ▸ Games** turns the picture and its colour off). **Play** starts the game: through the store that
installed it, or directly — **Settings ▸ Games ▸ Play button** chooses. **Edit…** changes the name, publisher, version
installed it, or directly — **Settings ▸ Games ▸ Play button** chooses; a game from the Xbox app always starts through
Windows. **Edit…** changes the name, publisher, version
and notes, and the picture: **Choose image…** (kept as a copy once you save) or **Use the store's image**. **Change
executable…** points the entry at another `.exe` and turns hooking back off; its file dialog opens in the game's own
folder. **Remove…** asks whether to keep the game's sessions.
- **Recording** — off, FrameLedger ignores the program completely: for a launcher or a tool that is not a game.
- **Hooking** — on, the game is measured. A warning comes first, and you type `I ACCEPT THE INJECTION RISK` to go on.
- **Hooking** — on, the game is measured. A warning comes first: type `I ACCEPT THE INJECTION RISK` exactly, then press
**Enable hooking** or Enter.
Read [Anti-cheat and safety](04-anti-cheat-and-safety.md) before you do.
- **Anti-cheat** — shown in its place when anti-cheat was found: what was found, and where. **User-mode exception**
appears when the game qualifies for the one exception.
- **Supports** and **Details** — what the game's own files contain, as far as FrameLedger can tell.
- **Tabs:** **Sessions** (every session: double-click a row or press **Open**; **Delete all sessions…** at the top),
**Frametime**, **Distribution**, **Trend** (one point per session for a figure you choose, with changes to your
hardware or driver marked), **Sensors**, and **Latency** when the game reported it.
**Frametime**, **Distribution**, **Trend** (one point per session for a figure you choose; each day your hardware,
driver, display or Windows changed is numbered on the chart and listed under it), **Sensors**, and **Latency** when
the game reported it.
## A session's summary
@@ -104,7 +112,8 @@ It opens from a session row, from the Dashboard, and from the notice when a sess
Tick **2 to 5 sessions**, from any of your games, and press **Compare**: one frame-rate curve per measured session, and
a table with the best value of each row in bold. Comparing a measured session with an unmeasured one asks first,
because they measured different things.
because they measured different things. The list holds every session; narrow it by **game**, **tier** (measured or
not) and **frame generation** — a session you ticked stays in the list. **Clear selection** unticks them all.
## Logs
@@ -124,8 +133,14 @@ is ready.
## Keyboard and mouse
- **Ctrl+1** … **Ctrl+5** open Dashboard, Games, Compare, Logs and Settings.
- **Alt** or **F10** moves to the menus.
- **Ctrl+1** … **Ctrl+5** open Dashboard, Games, Compare, Logs and Settings, and put the keyboard in that page.
- **Alt** or **F10** moves to the menus; **Alt** with a menu's underlined letter opens it (**Alt+F**, **Alt+T** and
**Alt+H** for File, Tools and Help in English).
- **Esc** closes a dialog the way its Close or Cancel button does.
- Over a chart, **Ctrl** and the mouse wheel zoom, dragging pans, and a double-click resets. The wheel alone scrolls the
page.
- Over a chart, **Ctrl** and the mouse wheel zoom, dragging pans, and a double-click shows all of it again. The wheel
alone scrolls the page.
- **Tab** reaches a chart; then the **arrow keys** move its view, **Ctrl** with an arrow zooms, and **A** shows all of it
again.
What works with the keyboard alone, a screen reader or a contrast theme — and what does not yet — is on its own page:
[Accessibility](../ACCESSIBILITY.md) (Help ▸ Accessibility).
+4 -4
View File
@@ -41,16 +41,16 @@ The link under them, *Read what the hook does and does not do*, opens the safety
| Setting | What it does | Default |
|---|---|---|
| **Theme** | Follow system, Light or Dark. Applies at once. | Follow system |
| **Language** | English, Tiếng Việt or 日本語. The window is rebuilt in the new language at once. | English |
| **Theme** | Follow system, Light or Dark. Applies at once. While a Windows contrast theme is on, FrameLedger uses that theme's colours whatever you choose here, and says so under the box. | Follow system |
| **Language** | English, Tiếng Việt or 日本語. The window is rebuilt in the new language at once, and stays on Settings (since 0.1.0-beta.34; before, it could open on the last game you looked at). | English |
## Games
| Setting | What it does | Default |
|---|---|---|
| **Show game artwork** | A game's page shows a picture of the game: the image you chose for it (**Edit…**), or else the cover and banner the Steam or GOG GALAXY app already keeps on your PC. Nothing is downloaded; a game from another store shows a picture only once you choose one. | On |
| **Show game artwork** | A game's page shows a picture of the game: the image you chose for it (**Edit…**), or else the cover and banner the Steam or GOG GALAXY app already keeps on your PC, or the logo and splash image an Xbox game ships in its own folder. Nothing is downloaded; a game from another store shows a picture only once you choose one. | On |
| **Colour the game page from its artwork** | The band at the top of a game's page takes the picture's main colour — never so strongly that a text on it gets hard to read. Off, the band keeps the plain card colour. | On |
| **Play button** | What **Play** does, on a game's page and on each game in the library. *Through the store*: Steam or the Epic Games Launcher starts the game, GOG GALAXY runs it, and the itch app asks which copy to launch — each store's app does what it does when you start a game from it. A game no store installed, and a GOG game without GOG GALAXY, is started by FrameLedger instead; so is every game while FrameLedger itself runs as administrator, so that the game does not. *Start directly*: FrameLedger's agent starts the game, recorded from its first frame, with your standard rights; it does not start a game whose recording is off, or one that asks to run as administrator. | Through the store |
| **Play button** | What **Play** does, on a game's page and on each game in the library. *Through the store*: Steam or the Epic Games Launcher starts the game, GOG GALAXY runs it, and the itch app asks which copy to launch — each store's app does what it does when you start a game from it. A game no store installed, and a GOG game without GOG GALAXY, is started by FrameLedger instead; so is every game while FrameLedger itself runs as administrator, so that the game does not. *Start directly*: FrameLedger's agent starts the game, recorded from its first frame, with your standard rights; it does not start a game whose recording is off, or one that asks to run as administrator. Some Steam games hand themselves to Steam when started directly — the game Steam then starts is recorded — and a few will not start outside Steam at all: start those through the store. A game from the Xbox app or the Microsoft Store always starts through Windows, as its Start-menu tile does, in either mode. | Through the store |
## Window
+2
View File
@@ -29,9 +29,11 @@ While the game runs, a notice may say *hooking refused*.
| FrameLedger could not check the game's files. | It checks again by itself; Tools ▸ Update detection rules checks now. |
| The game runs as administrator. | Settings ▸ Capture agent ▸ *Run the agent as administrator* — read its risk in [Limitations](../LIMITATIONS.md#running-the-agent-as-administrator) first. A game protected by an anti-cheat driver cannot be measured either way. |
| The game is 32-bit, uses DirectX 9, or uses Vulkan. | Nothing: these are recorded, not measured ([Limitations](../LIMITATIONS.md#games-it-will-not-measure)). |
| The game runs in an app container, or Windows protects it in a way the component can neither load into nor hook. | Nothing: an older Microsoft Store app (UWP), or a game under code protection, is recorded, not measured ([Limitations](../LIMITATIONS.md#xbox-app-and-microsoft-store-games)). |
| **Disable all hooking** is on. | Switch it off in Settings ▸ Capture. |
| The game was already running when FrameLedger was updated. | Close the game and start it again. |
| Hooking was switched off after the game crashed twice soon after it started. | Switch it on again in the game's page if the cause may be gone — after a driver update, for example. |
| Hooking was switched off after **Play** started the game directly twice, and each time the game handed itself to Steam or closed at once. | Switch it on again, and set Settings ▸ Games ▸ **Play button** to *Through the store*: some Steam games will not start any other way. |
| The game's file is gone. | If only its drive letter changed, FrameLedger follows it within about 15 seconds; otherwise **Change executable…** on the game's page. |
| The component could not be loaded into the game. | [Report a problem](#report-a-problem). |
+3 -1
View File
@@ -16,7 +16,9 @@ What the words on FrameLedger's screens mean, in alphabetical order. How each fi
says. Sessions are still recorded.
- **Displayed FPS** — the frames you saw, generated frames included.
- **DLSS 4, DLSS 4.5** — NVIDIA's DLSS generations. FrameLedger names one only when the session shows it: the model
preset the NVIDIA driver reports, or a frame-generation multiplier of ×3 and above.
preset the NVIDIA driver reports, a frame-generation multiplier of ×3 and above, or the NVIDIA App's *Dynamic*
frame generation (DLSS 4.5 only).
- **DLSS 5** — NVIDIA's neural rendering. Named only when the game was seen running it (since 0.1.0-beta.34).
- **FG factor** — Displayed FPS divided by Native FPS, shown as `×1.9 FG`.
- **FPS** — frames per second over the time measured.
- **Frame generation** — the technology (DLSS Frame Generation, FSR Frame Generation) that inserts frames the game did
+65
View File
@@ -0,0 +1,65 @@
# Alpha builds
## What an alpha is
Besides the betas, FrameLedger publishes **alphas**: the same program as a beta, built to try a newer version of .NET —
sometimes one Microsoft has not finished yet. They exist so that a new .NET can be tried before the betas rely on it. An
alpha's version ends in `-alpha.N` (`0.1.0-alpha.1`), its page on GitHub says *experimental alpha*, and its installer is
`FrameLedger.App-alpha-Setup.exe`.
**If you want results you can rely on, use the beta.** An alpha can crash, record wrongly or fail to update in ways no
beta has. The part of FrameLedger that goes into a game is the beta's own and does not use .NET; everything that starts
it, reads it and stores what it measured runs on the alpha's .NET.
## Right now: the alphas are paused
The alphas tried .NET 11. Since 0.1.0-beta.37 the betas run on .NET 11 too, so **0.1.0-alpha.4 is the last alpha for
now**: it brings an installed alpha onto the finished .NET 11, and after it no alpha is published until there is a newer
.NET to try.
A paused alpha gets **no updates** — no fixes, and not the list of anti-cheat software FrameLedger refuses to touch, which
only arrives inside an update. Its banner tells you so. **Install the latest beta over it** (below); your data stays.
One more thing: once ten betas have been published after 0.1.0-alpha.4, an older alpha can no longer find it as an
update, and installing the beta by hand is the only way forward.
## Before it runs
The first time an alpha starts, the terms window shows the **Alpha notice** beside the other documents, with a box to
tick: *I understand that this is an experimental build and I use it at my own risk.* Accept stays off until it is ticked.
Until you accept, the alpha's capture agent does not run at all. The notice is shown again whenever its text changes.
While an alpha runs, the title bar carries an **ALPHA** badge (hover it to see the .NET version), and a yellow banner
above every page says what it is each time it starts — while the alphas are paused, that they are, and to install the
beta; you can close the banner for that run. **Help ▸ About** names the
.NET it runs on.
## Your data
An alpha **replaces** the beta on your PC — only one of them is installed at a time — and uses the **same data folder**
and the same database ([Your data](05-your-data.md)). Before an alpha opens your database for the first time, it copies it
to the `backups` folder inside the data folder, as `ledger-before-<version>.db`; the newest three copies are kept. If the
copy cannot be made — the disk is full, say — the alpha does not open the database and tells you why.
Sessions an alpha records stay in the database when you go back to the beta, and the beta shows them.
## Installing one, and going back
There is no switch inside FrameLedger: an alpha never arrives as an update to a beta, and a beta never as an update to an
alpha.
- **To try an alpha:** download `FrameLedger.App-alpha-Setup.exe` from the alpha's page on GitHub Releases, check its hash
against `SHA256SUMS.txt`, and run it. Windows' installer asks whether to replace the FrameLedger already installed;
say yes.
- **Updates:** an alpha updates only to newer alphas. In **Settings ▸ Updates** the channel is locked on an alpha, and
says so.
- **To go back:** install the newest beta's `FrameLedger.App-win-Setup.exe` the same way. Your database stays where it
is.
## Windows and your PC
An alpha needs what a beta needs since 0.1.0-beta.37 ([Install](01-install.md)): Microsoft supports .NET 11 on
Windows 11; on Windows 10 (22H2) FrameLedger may run, but it is not tested there and nobody supports it; and on a
processor without SSE4.2 and POPCNT it does not start at all.
When an alpha runs on a .NET Microsoft has not finished, Microsoft stops supporting that version when the finished one
ships, and the next alpha moves to the finished one.
+5 -3
View File
@@ -4,7 +4,7 @@ FrameLedger records how your games run on this PC — frame rate, frame times, t
with, temperatures, and how much memory the game uses — and keeps every session so you can compare them later.
Everything stays on your PC.
Each page below takes a minute or two to read. The first six are the guide; the next four are there to look things up.
Each page below takes a minute or two to read. The first six are the guide; the next five are there to look things up.
1. [Install and first start](01-install.md)
2. [Record a game](02-record-a-game.md)
@@ -16,10 +16,12 @@ Each page below takes a minute or two to read. The first six are the guide; the
8. [Every setting](08-settings.md)
9. [When something goes wrong](09-troubleshooting.md)
10. [Words FrameLedger uses](10-glossary.md)
11. [The terms, in plain words](terms-in-plain-words.md)
11. [Alpha builds](11-alpha-builds.md) — the experimental builds on a new .NET, and how to go back
12. [The terms, in plain words](terms-in-plain-words.md)
What FrameLedger cannot do is listed on its own page: [Limitations](../LIMITATIONS.md) (in the app: Help ▸
Limitations).
Limitations). How it works with the keyboard alone, a screen reader or a contrast theme, and how to report a problem:
[Accessibility](../ACCESSIBILITY.md) (Help ▸ Accessibility).
**FrameLedger is beta software.** It certainly still has bugs. If something goes wrong, Help ▸ Report a bug… builds a
report on your PC that you can look at before you decide to share it.
+2 -1
View File
@@ -10,7 +10,8 @@ Legal documents**.
- It records performance data **on your PC**.
- It hooks a game **only if you switch that on for that game**, after a warning. If anti-cheat bans your account for
it, **that risk is yours**, and the developer cannot undo a ban.
- It is **beta** software, provided **without warranty**, and the developer is not liable for damage it causes — as
- It is **pre-release** software — a beta, or an [alpha](11-alpha-builds.md) on a new .NET, which carries more risk and
asks you to accept that first — provided **without warranty**, and the developer is not liable for damage it causes — as
far as the law allows. Rights the law gives you as a consumer, which no agreement can take away, stay yours.
- Read it: [EULA](../legal/EULA.md).
+6 -4
View File
@@ -11,9 +11,9 @@
that changes what FrameLedger.Overlay or the capture host does; date the change.
HTML comments are not part of the block.
-->
> ⚠ **What FrameLedger actually measures today — 2026-10-19.** The software is a beta; its latest
> **pre-release is `0.1.0-beta.24`** (2026-10-19), an unsigned installer built from that tag with its
> checksums published beside it. The source holds the desktop app
> ⚠ **What FrameLedger actually measures today — 2026-11-06.** The software is a beta; its latest
> **beta is `0.1.0-beta.37`** (2026-11-11), an unsigned installer built from that tag with its
> checksums published beside it (alphas — experimental builds that try a newer .NET — are published apart). The source holds the desktop app
> (library, store import, charts, settings) and the background Agent, which records a session when a
> game in the library runs (unless you switched its recording off), injects only into games you enabled
> and only past the safety guard, and
@@ -44,7 +44,9 @@
> every other case — FSR at a dynamic resolution among them — no mode is shown.
> - **DLSS version:** the version of each DLSS library the game loaded and whether it came from the game or from
> the NVIDIA driver; "DLSS 4" or "DLSS 4.5" only when the session shows it (the model preset the driver reports,
> or a measured multi-frame factor); DLSS 5 only as "runtime loaded".
> a measured multi-frame factor, or the NVIDIA App's Dynamic frame generation that the driver reports applied);
> "DLSS 5" only when the game was seen running its neural rendering, otherwise "runtime loaded" when its library was
> loaded.
> - **Render → output resolution:** measured where the vendor's own per-frame call carries the render
> size (AMD FidelityFX dispatches, and Streamline titles whose resource tags state it); `N/A` where it
> does not: DLSS titles that bypass Streamline, Streamline titles whose tags carry no size, and Vulkan
Loaded 100 of 604 files, more files were not shown because too many files have changed in this diff. Show more