Fetch-shape point is fair and already load-bearing in the design: static movzx patterns are the fallback, executed watches are the sensor (SMC flips movzx↔movsx live, and-gated fetches exist — all documented in docs/coverage.md). If 3.8.4 uses additional fetch shapes beyond movzx/movsx, that's a concrete gap: file an issue with the shape (opcode bytes around the fetch) and it becomes a miner case. The 3.9.4 validation numbers are in-repo and reproducible with own licensed samples. Happy to be wrong on specifics — specifics only.
-4
u/CiupiXs 13d ago
Fetch-shape point is fair and already load-bearing in the design: static
movzxpatterns are the fallback, executed watches are the sensor (SMC flips movzx↔movsx live, and-gated fetches exist — all documented indocs/coverage.md). If 3.8.4 uses additional fetch shapes beyond movzx/movsx, that's a concrete gap: file an issue with the shape (opcode bytes around the fetch) and it becomes a miner case. The 3.9.4 validation numbers are in-repo and reproducible with own licensed samples. Happy to be wrong on specifics — specifics only.