Compare commits

...
Author SHA1 Message Date
poli0981andClaude Opus 5.5 773bee1089 release: [Unreleased] empty again after merging main into the release branch - its beta.28 entries are docs/changelog/0.1.0-beta.28.md's (beta.28 PR-2)
Merging main into this branch (8c0fcb6) took the merge base 94120d3: main had added the beta.28
entries to [Unreleased] (#332, squashed), this branch had added and then moved them into
docs/changelog/0.1.0-beta.28.md, so the merge put them back under [Unreleased] - the release would
have shipped them as released and unreleased at once. CHANGELOG.md is the release commit's again;
the tree equals the one the release.yml dry run built (21355428, run 39369768443).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-20 11:55:43 +07:00
poli0981 8c0fcb65ab Merge branch 'main' into beta28/pr2-release 2026-10-20 11:49:00 +07:00
poli0981andClaude Opus 5.5 21355428d0 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)
- 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 11:28:34 +07:00
poli0981andClaude Opus 5.5 6379f24d91 test: 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 11:28:22 +07:00
poli0981andClaude Opus 5.5 5e96681969 feat: the Dashboard shows every game being recorded - one live card per running session, hooked first, two to a row, the games counted (beta.28 PR-1)
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.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-20 11:13:33 +07:00
8 changed files with 107 additions and 58 deletions

No files matched your search

+1 -15
View File
@@ -35,27 +35,13 @@ numeric core and does not move; the heading is the full version — corrected 20
## [Unreleased]
### 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.
## Releases
Newest first. Each file holds that release's section exactly as it stood here.
| Version | Date | Notes |
|---|---|---|
| `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) |
+1 -1
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.27.*
*Beta software: this page describes version 0.1.0-beta.28.*
## Games it will not measure
+2 -2
View File
@@ -12,7 +12,7 @@ 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.27`** (2026-10-20), an unsigned installer built from that tag with its
> **pre-release is `0.1.0-beta.28`** (2026-10-20), an unsigned installer built from that tag with its
> checksums published beside it. 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
@@ -174,7 +174,7 @@ Elevation is **optional — for everything.** Hooked capture is the normal path
## Install
> **The latest pre-release is `v0.1.0-beta.27` (2026-10-20); before it `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`.
> **The latest pre-release is `v0.1.0-beta.28` (2026-10-20); before it `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**.
+26 -38
View File
@@ -66,6 +66,7 @@ owner-only items stay below; the history of every train, the passed owner-only i
| `§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) |
| `§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) |
@@ -73,51 +74,33 @@ owner-only items stay below; the history of every train, the passed owner-only i
---
## **START HERE** — 2026-10-20, 0.1.0-beta.27: the owner's eight sessions of 2026-10-20
## **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.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.
*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.** 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.
**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).
**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.
**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:**
- **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.
- **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:** items 20 and 21 annotated (§23); item 22 added.
**Owner-only:** item 23 added; beta.27's item 22 and the crash-safety question stand.
## Owner-only — no PR can close these
@@ -264,6 +247,11 @@ Dark Souls III sessions stored no window size.
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`.)
**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 —
+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.
+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.
+1 -1
View File
@@ -12,7 +12,7 @@
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.27`** (2026-10-20), an unsigned installer built from that tag with its
> **pre-release is `0.1.0-beta.28`** (2026-10-20), an unsigned installer built from that tag with its
> checksums published beside it. 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
+1 -1
View File
@@ -114,7 +114,7 @@ Frame timing is derived from high-resolution timestamps taken at the moment the
<!-- 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.27`** (2026-10-20), an unsigned installer built from that tag with its
> **pre-release is `0.1.0-beta.28`** (2026-10-20), an unsigned installer built from that tag with its
> checksums published beside it. 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