main
7
Commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
|
|
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> |
||
|
|
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> |
||
|
|
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> |
||
|
|
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>
|
||
|
|
d565760830 |
feat(build): every managed binary names FrameLedger and carries the native copyright line; versioninfo-check reads both kinds (beta.14 PR-6, D50) (#269)
Owner request 2026-10-05 ("Thêm Assembly metadata"); D50: company and product "FrameLedger", the copyright the
native FL_COPYRIGHT word for word.
Measured before the change, from the built binaries: FrameLedger.Agent.exe/.dll read Company and Product
"FrameLedger.Agent" and FileDescription "FrameLedger.Agent" (what Task Manager lists); each library its own assembly
name; every managed LegalCopyright was one space; the apphost's OriginalFilename is its assembly's (FrameLedger.dll).
tools/versioninfo-check.ps1 read the five native binaries and nothing else.
- Directory.Build.props: Company, Product, Authors, Copyright, Description (the native blocks' sentence, the Comments
field), RepositoryUrl (stamped as AssemblyMetadata by the SDK); the FrameLedgerSourceRef metadata moved here from the
App csproj, and release.yml passes the same ref to the Agent's publish.
- App: AssemblyTitle "FrameLedger" and a Description. Agent: AssemblyTitle "FrameLedger Agent" and a Description.
- versioninfo-check.ps1: the rules in one function over a block, a managed half (-ManagedDir, -ExpectedProductVersion -
required, -ManagedOnly), one LegalCopyright across every binary read, the apphost carrying its assembly's block,
Company as well as Product = FrameLedger, and -SelfTest: ten cases, nine RED, each for the reason it names (four
mutations of the rules each turn the self-test red). build.ps1 runs the self-test and both halves (the managed half
alone under -SkipNative); release.yml reads out/app with the tag's version.
- AssemblyIdentityTests (App, Agent): company, product, copyright = FL_COPYRIGHT parsed from CMakeLists.txt,
description, RepositoryUrl = IssueLink.Repository, and the Win32 block Explorer shows. Red on the source before.
Docs: 12_BUILD (Identity table, the gate, the publish lines), 13_CI_CD, 19_SAFETY, FORKING (what a fork changes),
CHANGELOG.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
||
|
|
1776a22907 |
feat(app): Velopack, the updater with FR-12 as its shape, release.yml, and one VERSION source (P4 PR-5) (#174)
* feat(app): Velopack, the updater with FR-12 as its shape, release.yml, and one VERSION source (P4 PR-5)
The updater of 11_UPDATER behind an IUpdateClient port (VelopackUpdateClient over Velopack 1.2.0's
GitHub source; stable = releases GitHub does not mark pre-release, beta adds them): the startup silent
check 5 s after start for an installed copy with update.auto_check on, Help > Check for updates with
the dialogs and the six error rows, the background download (a checksum failure retried once), and the
apply -- refused while any session runs, Deferred until the last SessionCompleted, then Shutdown to the
Agent, the connection's relaunch held, the pipe watched until it drops, WaitExitThenApplyUpdates, the
host ended. Program.Main runs VelopackApp first; the uninstall hook stops the Agent, unregisters the
layer, removes the logon task and asks about the data folder.
The package id is FrameLedger.App, not FrameLedger: Velopack installs into and deletes
%LOCALAPPDATA%\<packId>, which with the documented id is the data folder holding ledger.db.
VERSION at the root feeds Directory.Build.props and the native CMake project; versioninfo-check
compares every binary against it. release.yml gates the tag against VERSION and CHANGELOG
(tools/release-notes.ps1), substitutes {{RELEASE_DATE}}, runs the identical gate, publishes, asserts
the published tree, packs, checksums and releases.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
* fix(app): the private constant's name, Velopack's copyright as its package states it, and the measured pack
- UpdateService: _idleState (IDE1006, the repository's private-field rule; dotnet format caught it).
- legal/licenses/velopack-MIT.txt and THIRD_PARTY_NOTICES: the copyright line is the package's own
<copyright> field ("Velopack Ltd."), not a name written from memory.
- 12_BUILD / 13_CI_CD / CHANGELOG: vpk pack 1.2.0 run by hand over the published tree -- Setup 104 MB,
VelopackApp.Run() verified in Program.Main.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
|
||
|
|
5b61a20482 |
build: scaffold the repository the docs assume
Takes the project from docs-only to a state where the P0 spike can begin.
Everything here was verified to run, not just written.
Managed
global.json pins the SDK band. Without it `dotnet --version` on this
machine resolved to an 11.0 preview, which silently changes analyzer
behaviour under TreatWarningsAsErrors and makes local and CI disagree
for reasons invisible in a diff. Not mentioned in any doc; added to
12_BUILD.
TargetFramework net10.0-windows10.0.22621.0 with
SupportedOSPlatformVersion 10.0.19045.0. The plan called for a 19041
target, but the SDK rejects SupportedOSPlatformVersion above
TargetPlatformVersion (NETSDK1135), and 19045 is not a targeting-pack
version — the packs are cut at 19041/20348/22000/22621/26100.
12_BUILD already requires the Windows 11 SDK >= 22621, so targeting it
costs nothing while CA1416 still enforces the 22H2 floor from NFR-8.
Solution is FrameLedger.slnx: the XML format is what `dotnet new sln`
produces on .NET 10, and it diffs far better than the classic format.
Six projects plus three test projects, wired to the dependency
direction CLAUDE.md specifies. Builds warning-free under
TreatWarningsAsErrors + AnalysisLevel=latest-all; the only analyzer
suppressions are three WPF codegen constraints, scoped to
src/FrameLedger.App and each explained in .editorconfig.
Pinned SQLitePCLRaw forward: Microsoft.Data.Sqlite 10.0.10 resolves
lib.e_sqlite3 2.1.11, which carries GHSA-2m69-gcr7-jv3q. The build
failed on it, correctly.
Pinned FluentAssertions to the 7.x line. 8.0.0 moved from Apache-2.0
to Xceed's Community Licence, which is not OSI and carries
field-of-use restrictions — exactly what 18_GPU_VENDOR_APIS's vendor
checklist rejects. Dependabot is configured not to major-bump it.
Native
fl_shm.h is the valuable artifact: the corrected four-region layout,
with static_asserts on every size and offset. Compile-verified — all
four structs are exactly 64 bytes with no implicit holes, and the
mapping is 512 KiB + 192 B of header. fl-layout-dump emits those
offsets as JSON for the C# mirror test to consume.
/guard:cf and -D_HAS_EXCEPTIONS=0 are deliberately NOT applied to the
Overlay target yet. Both are unresolved (20_OPEN_QUESTIONS H1, H3);
applying them now would mean meeting the problem as a crash in a real
game rather than as a decision.
Not compiled: this machine has no MSVC C++ workload, so the CMake
targets are unverified. The headers were checked with g++ instead.
Gates
build.ps1 check runs the nine gates, and CI runs that same script.
Gates skip loudly — the run ends "PASSED WITH N SKIPPED GATE(S)"
rather than a clean pass, because a gate that silently passes because
its tool is missing reads as "checked" when nothing was checked.
license-check and rules-validate are real, and were proven red-green
before being wired in: a planted IGCL header fails the licence gate,
and an emptied anticheat.modules list (or a dropped BattlEye entry, or
malformed JSON) fails the rules gate. A safety gate only ever observed
passing has not been tested.
Added a placeholder guard: any {{ token other than {{RELEASE_DATE}}
surviving in README.md or legal/*.md fails the build. Those documents
are displayed for acceptance under FR-11.
rules/detection-rules.json is seeded with a non-empty anticheat block.
An empty one is a fail-closed fixture, not a ship state.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|