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>
This commit is contained in:
poli0981andClaude Opus 5.5 authored and GitHub committed 2026-11-03 07:37:51 +00:00
1 parent 249c02be56
commit 405449283b
3 files changed
+55

No files matched your search

+1
View File
@@ -41,6 +41,7 @@ Newest first. Each file holds that release's section exactly as it stood here.
| Version | Date | Notes |
|---|---|---|
| `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) |
+21
View File
@@ -146,6 +146,21 @@ refuses `FILE_READ_DATA`/`FILE_EXECUTE` outside its package, so no Unreal versio
**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.
## Owner-only — no PR can close these
@@ -347,6 +362,12 @@ refuses `FILE_READ_DATA`/`FILE_EXECUTE` outside its package, so no Unreal versio
`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.
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.
**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 —
+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.