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>
69 lines
3.7 KiB
XML
69 lines
3.7 KiB
XML
<Project>
|
|
|
|
<!--
|
|
Stages the two native binaries the drain integration test drives:
|
|
FrameLedger.Overlay.dll (the payload) and hook-harness.exe (the target).
|
|
|
|
WHY BOTH, AND WHY BESIDE THE TEST BINARY.
|
|
|
|
§S22(a) requires the injection payload to resolve into the directory the
|
|
GUARD's own code was loaded from, compared by file id. FrameLedger.Guard.targets
|
|
already puts FrameLedger.Guard.dll beside this test, so "the guard's directory"
|
|
IS the test's output directory — and the Overlay has to be there too or every
|
|
injection refuses with PayloadNotOurs. src/native/tests does exactly the same
|
|
thing for fl_guard_test, for exactly the same reason.
|
|
|
|
THE HARNESS IS A FIXTURE, NOT A PRODUCT ARTIFACT. It is our own dummy D3D app.
|
|
Injecting into it raises no consent question — no game, no account, no terms of
|
|
service — which is precisely why the drain is exercised against it rather than
|
|
behind a flag on the shipped Agent. See ShmDrainIntegrationTests for the rule
|
|
that keeps it that way.
|
|
|
|
Neither file reaches out/app through this: it is imported by the test project
|
|
only, and FrameLedger.Overlay.targets remains the Agent's own route for the
|
|
payload it ships.
|
|
-->
|
|
<PropertyGroup>
|
|
<FlOverlayDir>$(MSBuildThisFileDirectory)build\native\x64-release\FrameLedger.Overlay\</FlOverlayDir>
|
|
<FlHarnessDir>$(MSBuildThisFileDirectory)build\native\x64-release\tools\hook-harness\</FlHarnessDir>
|
|
</PropertyGroup>
|
|
|
|
<ItemGroup>
|
|
<None Include="$(FlOverlayDir)FrameLedger.Overlay.dll" Condition="Exists('$(FlOverlayDir)FrameLedger.Overlay.dll')">
|
|
<Link>FrameLedger.Overlay.dll</Link>
|
|
<CopyToOutputDirectory>PreserveNewest</CopyToOutputDirectory>
|
|
</None>
|
|
<None Include="$(FlHarnessDir)hook-harness.exe" Condition="Exists('$(FlHarnessDir)hook-harness.exe')">
|
|
<Link>hook-harness.exe</Link>
|
|
<CopyToOutputDirectory>PreserveNewest</CopyToOutputDirectory>
|
|
</None>
|
|
</ItemGroup>
|
|
|
|
<!--
|
|
THE HARNESS'S LOGS LEAVE WITH THE ASSEMBLY THAT CAUSED THEM. The Overlay logs to the real
|
|
%LOCALAPPDATA%\FrameLedger\logs by design (§S21), so every TEST project that stages hook-harness
|
|
compiles tests/Shared/HarnessOverlayLogSweep.cs, an xUnit assembly fixture that removes, when the
|
|
assembly finishes, the overlay logs of the harness copies it owns (17_HOOK_ENGINE §Native logging).
|
|
The CaptureHost imports this file too and is not a test project, so it does not get the sweep.
|
|
tools/test-artifacts-check.ps1 is what makes a missing sweep red.
|
|
-->
|
|
<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>
|
|
|
|
<!--
|
|
Warn at build, fail at test. build.ps1 runs the native build first, so by the
|
|
time this evaluates both exist; a hard error here would break `dotnet build` on
|
|
a fresh clone for a reason unrelated to managed code. The test itself refuses to
|
|
skip: an integration test that quietly does nothing when its fixtures are absent
|
|
is a gate that cannot fail.
|
|
-->
|
|
<Target Name="FlWarnOnMissingDrainFixtures" AfterTargets="Build"
|
|
Condition="!Exists('$(FlOverlayDir)FrameLedger.Overlay.dll') Or !Exists('$(FlHarnessDir)hook-harness.exe')">
|
|
<Warning Text="FrameLedger.Overlay.dll or hook-harness.exe is missing from the native build tree. Run build.ps1 native first; ShmDrainIntegrationTests will fail without them." />
|
|
</Target>
|
|
|
|
</Project>
|