[mkw432]

Adds official tools/strata_bench.py results from an RX 6700 XT 12 GB (gfx1031), Ryzen 5 5600X and 32 GB RAM: Qwen3.6-35B UD-Q4_K_XL, LFM2.5-24B UD-Q4_K_XL, Tiel Coder UD-Q3_K_XL and Gemma-4 26B-A4B QAT UD-Q4_K_XL at 32K and 64K contexts (nine runs, suite 1, --runs 3), a same-machine Qwen re-run at e97c8aa against the c54f0eaf originals, and a Gemma draft-pairing A/B. Every run has its per-request results.json; provenance.json carries model SHA-256s (all verified same-day), settings, and the reproduce commands.

Measured source: engine 0.1.45 built locally for gfx1031 (HIP, AMD's wheels); original suites at c54f0ea, Qwen re-runs at e97c8aa (the delta commits are CUDA-only, engine binary identical). Every profile reserves 1024 MiB VRAM; no memory fault in any of the nine runs including 64K contexts — consistent with the reserve-related fault discussed in #52.

Observations the report documents beyond the tables:

• Reproduction: the Qwen3.6 and LFM2.5 rows land within a few percent of the existing RX 6700 XT report (a Ryzen 5 3600 machine).
• Version delta: c54f0ea → e97c8aa changed nothing measurable on this card (16K prompt 999.7 = 999.7; 32K 775.0 vs 773.2; chat deltas inside the run range).
• Gemma draft pairing: the QAT-paired 252 MB draft gives 87.7 tok/s short-chat where the repo Q8_0 draft (the standard-model pairing) gives 81.4, prompt throughput unchanged — pairing matters for QAT users.
• GPU naming: this kernel's amdgpu sysfs has no product_name, so the tool reports the generic "AMD Radeon" and the generated folder names say unknown; folders were renamed to rx6700xt-5600x here (inner generated names untouched) and the card verified externally (PCI 1002:73DF, 12272 MiB). Same disclosure style as bench: RX 6700 XT 12 GB official PolyStrata results #52's cpu-named folders.
• PRACTICAL-EVALUATION.md is a separately labeled appendix (6 h / 483-check soak, blind agent screens) kept outside the speed claims.

Disclosures: the Oct-20 Qwen and LFM suites ran while a large download wrote to a second disk (the 4K/16K medians match the idle re-run, so no visible effect, but recorded); LFM's 32K agent stage did not complete (its tool-call format, same gap as the 10-19 report) and is listed as a skipped test; the LFM2.5 GGUF was deleted in a post-campaign disk cleanup, so its byte count is marked unavailable (SHA-256 recorded same-day).

Validation: files copied byte-for-byte from the campaign artifacts; report folder is 392 KB; no credentials or host names (the runner's own placeholder pass is intact). This PR contains only results and their metadata — no engine, setup, or benchmark-tool code changes, and no general accuracy claim.

[VecSzn]

Thanks, merged, and it has a line in COMMUNITY_BENCHMARKS.md right next to the first one for the RX 6700 XT. GPU tiles: setup wrote backend: hip for strata-poly only on Windows, fixed in v0.1.45-poly.3, running setup again will rewrite the config. Qwen3.6 Q6_K_XL illegal memory access on a 4.8K prompt, can you open an issue with the engine log?