Record corrected one-node and RF3 functional gate passes

Both native cases pass on e292c1c with matching source, executable and image-input cohorts: one node10302 successful SDK/MCP/SQL operations, RF3 10306. Each completes41waves, three-resource event/queue/topic/blob rotation, current persisted authorization, cross-client replay and original owned cleanup.

Bind original TRX, stdout, image and terminal evaluator hashes. Preserve previous scenarios and failed originals. Record39/39 selected whole-operation Unit cases,3/3 selected recovery cases and the separate actual RF3 all-node cold authorization pass. This updates local working-base evidence only; original KL acceptance remains20/105 and DROP/full SQL/Linux/endurance/performance/release remain open.

Author: KSemenenko

README.md

@@ -92,9 +92,9 @@ flowchart LR
 
 [KL-105](docs/Features/BenchmarkComparisons/DotnetProfiling.md) adds .NET profiling with `dotnet-diagnostics-mcp`, measured bottleneck repairs and matched verification; its acceptance remains open.
 
-The [working database functional gates](docs/Features/DatabaseComposition/FunctionalDatabaseGates.md) passed locally on the recorded `86834e8a` cohort: **one Aspire instance completed 10,302 successful operations; three RF3 nodes completed 10,306** on the same source, executable and image-input cohort. Both scenarios use the real SDK, official MCP SDK and selected T-SQL, with three configured resources per supported catalog model, eight workload users, one queue operator and the server-side queue → graph → queue roundtrip. Original native results include owned shutdown and released-storage checks. Time-series analytics uses the persisted series sets; native operational analytics is separate derived node-local history with one engine per node. A subsequently identified scheduler/resource-selection correlation leaves complete repeated event/queue/topic/blob lifecycle coverage on all three resources open; see the linked gate specification.
+The corrected [working database functional gates](docs/Features/DatabaseComposition/FunctionalDatabaseGates.md) passed locally on the recorded `e292c1c1` cohort: **one Aspire instance completed 10,302 successful operations; three RF3 nodes completed 10,306** on the same source, executable and image-input cohort. Both scenarios use the real SDK, official MCP SDK and selected T-SQL, with eight workload users, one queue operator and complete event/queue/topic/blob rotation across all three configured resources. Every model, the server-side queue → graph → queue roundtrip, cross-client replay, owned shutdown and released-storage checks passed. Time-series analytics uses three persisted series sets; native operational analytics is one separate derived engine per node.
 
-The current resource-lifetime and analytics-root repair checkpoint passes its strict solution build, all **39 selected native whole-operation tests**, all **three selected process/native recovery tests**, and the actual SDK/MCP RF3 authorization scenario through all-three-node same-root cold restart. The corrected functional scenario now rotates repeated event, queue/topic and blob flows across all three resources; its fresh one-node then RF3 pair remains open. Earlier gate results retain their original source scope.
+The resource-lifetime and analytics-root repair checkpoint also passes its strict solution build, all **39 selected native whole-operation tests**, all **three selected process/native recovery tests**, and the actual SDK/MCP RF3 authorization scenario through all-three-node same-root cold restart. These are local development proofs. Earlier scenarios and failures retain their original source scope; whole-product and Linux qualification remain open.
 
 `DROP TABLE` remains open. Local functional proof does not complete unified SQL, failover/endurance, security, performance or release qualification. This working-base priority precedes the broader [foundation-first plan](docs/Features/RepositoryGovernance/FoundationDelivery.md); original [task acceptance](docs/implementation/status.json) remains **20 accepted / 85 in progress**.
 

docs/Features/DatabaseComposition/FunctionalDatabaseGates.md

@@ -107,6 +107,41 @@ defects while the other modules continue.
 
 ## Current local execution evidence
 
+Both corrected native cases passed on commit
+`e292c1c1585bc0bc402d3be4f97165ca6b29ac25`:
+
+| Gate | Genuine nodes | Successful SDK operations | Successful MCP operations | Total | Native result |
+| --- | --- | --- | --- | --- | --- |
+| R477 single instance | 1 | 5,315 | 4,987 | 10,302 | 1 passed, 0 failed, 0 skipped |
+| R478 RF3 | 3 | 5,317 | 4,989 | 10,306 | 1 passed, 0 failed, 0 skipped |
+
+Each completed 41 joined waves with the corrected independent resource index,
+covering all three event, queue/topic and blob resources. Both retained eight
+workload users, one queue operator, actual selected T-SQL composition and full
+SDK/MCP result, replay and authorization oracles. Original native cleanup passed
+before terminal acceptance. Source, executable and image-input cohort bindings
+match exactly; drift is zero. Elapsed owned-runner times were 228.364 seconds
+and 385.538 seconds, respectively; these are functional test durations, not
+comparable performance measurements.
+
+Original terminal evaluators under `TestResults/stage61-native-join/` are
+`root-r477-gate1-terminal-evaluation.original.json`, SHA-256
+`d3f05f6737201980432ba493351a0617bd9d0c7622b6239e2c7baa35c5c744c1`,
+and `root-r478-gate2-terminal-evaluation.original.json`, SHA-256
+`8e4e942842e91440c289e18a806baadd51950e9f606bb47949dbac1499e093dd`.
+They bind original TRX, stdout, joined runner, native fixture lifecycle and exact
+image identity checks. The complete identities are recorded in
+`docs/implementation/status.json`. This local proof does not qualify complete
+SQL, DROP, Linux, endurance, power-loss durability or release readiness.
+
+The associated strict full solution build passed with zero warnings/errors;
+all 39 selected native whole-operation tests and all three selected recovery
+cases passed. The separate real SDK/MCP persisted-authorization RF3 case also
+passed through all-three-node same-root cold restart. Production sources and
+binaries were unchanged between that cold proof and this corrected pair.
+
+## Previous local execution evidence
+
 Both original native cases passed on commit
 `86834e8a68d54c8c749221a373bb38b94b5d8436`:
 
@@ -138,11 +173,11 @@ four new deadline flows; R467 passed all three selected process/native recovery
 cases. At that historical R465/R466 checkpoint, the default fixture correction
 changed one nullable-key expression only; product and public functional-test
 source remained unchanged from the recorded local pair. The later resource-index
-correction below changes the functional scenario and requires a fresh matched
-Gate1/Gate2 pair, which remains open. R466 collected production coverage for its
+correction below changed the functional scenario; its fresh matched R477/R478
+pair now passes as recorded above. R466 collected production coverage for its
 nine cases only, not a full-product coverage result.
 
-## Current source coverage limitation
+## Resource rotation correction
 
 Source inspection found that the wave scheduler and iteration-based resource
 selection correlate: `model = (wave + worker) % 9` and
@@ -156,9 +191,9 @@ requires at least 27 complete waves before the successful-operation threshold ca
 end execution. In the unchanged four-worker schedule this schedules four full
 visits to each model/resource combination. A failed original visit still fails
 the gate; scheduled visits do not increment successful-operation counters. The
-corrected scenario requires a fresh matched gate pair. Original recorded PASS
-reports and operation counts remain historical facts; they do not prove complete
-lifecycle coverage of all three resources for these models.
+corrected scenario passed the fresh matched R477/R478 gate pair above. Original
+recorded PASS reports and operation counts remain historical facts with their
+narrower scenario; the corrected pair supplies all-three-resource lifecycle proof.
 
 ## Historical repair evidence