Compare commits

...
Author SHA1 Message Date
poli0981andClaude Opus 5.5 1b6a4f79ca 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)
- 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:19:45 +07:00
9 changed files with 119 additions and 65 deletions

No files matched your search

+1 -24
View File
@@ -35,36 +35,13 @@ numeric core and does not move; the heading is the full version — corrected 20
## [Unreleased]
### 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.
## Releases
Newest first. Each file holds that release's section exactly as it stood here.
| Version | Date | Notes |
|---|---|---|
| `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) |
+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.25.*
*Beta software: this page describes version 0.1.0-beta.26.*
## 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.25`** (2026-10-19), an unsigned installer built from that tag with its
> **pre-release is `0.1.0-beta.26`** (2026-10-19), 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.25` (2026-10-19); before it `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.26` (2026-10-19); before it `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**.
+6 -2
View File
@@ -285,9 +285,13 @@ 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; not marked yet | as above |
| `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 | **Fixed** in beta.26 | `wiki.yml` checks out `workflow_run.head_sha` only after a successful Release run started by a pushed `v*` tag, and now also only when `workflow_run.head_repository` is this repository. If the analysis still raises it, mark it *Safe* with that sentence. |
| `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*,
+30 -34
View File
@@ -64,6 +64,7 @@ owner-only items stay below; the history of every train, the passed owner-only i
| `§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) |
| `§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) |
@@ -71,44 +72,39 @@ owner-only items stay below; the history of every train, the passed owner-only i
---
## **START HERE** — 2026-10-19, 0.1.0-beta.25: FSR's quality mode
## **START HERE** — 2026-10-19, 0.1.0-beta.26: a ×1336 frame-generation state, fixed
*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.
*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.
**Decisions:**
**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.
- **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.
**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:**
- **`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.
- **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, added to the list below:** item 21.
**Owner-only:** items 20 and 21 annotated (`spike-notes` §22); nothing added.
## Owner-only — no PR can close these
@@ -219,8 +215,8 @@ case): 7.6–8.2 ns per UPSCALE dispatch, 1.6 ns per query beside the trampoline
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) most issues marked — the six left open on `main` are triaged in `13_CI_CD` §SonarCloud (beta.26). The rest is
not run yet.)*
(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.)*
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
@@ -311,7 +307,7 @@ Where each owner decision is recorded — the file and its section, and a label
| 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 | this file, §START HERE | FSR's quality mode through ffxQuery — deferred from beta.24, built in beta.25; none at a dynamic resolution |
| 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 |
+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.
+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.
+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.25`** (2026-10-19), an unsigned installer built from that tag with its
> **pre-release is `0.1.0-beta.26`** (2026-10-19), 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.25`** (2026-10-19), an unsigned installer built from that tag with its
> **pre-release is `0.1.0-beta.26`** (2026-10-19), 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