Repository navigation
test(compatibility): link opcode coverage to behavior evidence - #708
Merged
Merged
Conversation
This was referenced Oct 15, 2026
Mathih13
force-pushed
the
feat/hunter-pet-rename
branch
from
October 15, 2026 13:00
c507d97 to
dd4b462
Compare
Mathih13
force-pushed
the
feat/vanilla-compatibility-first-pass
branch
from
October 15, 2026 13:00
703da55 to
8d411c2
Compare
Mathih13
force-pushed
the
feat/vanilla-compatibility-first-pass
branch
from
October 15, 2026 13:27
8d411c2 to
4119728
Compare
Mathih13
force-pushed
the
feat/hunter-pet-rename
branch
from
October 15, 2026 13:27
dd4b462 to
980ad20
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Opcode dispatch coverage does not establish that gameplay works. The compatibility inventory now links message rows to nine curated behavior entries, each with prerequisites, test locations, evidence level and remaining work.
The scanner checks named Rust test declarations and records whether they are ignored. It explicitly reports that it did not execute them. Real-client status remains unverified.
What you verified
All nine applicable CI checks passed at
41197289, including the full durable suite. Retargeting tomainpreserved the tested base tree.Local checks ran on the combined Core tree at
5003aca5, based on9be23cd1. The reordered stack at8d411c26has the identical tree. The current stack at41197289adds only the three test-fixture repairs in #709; all other files are identical. The six affected durable tests passed separately on #709.cargo run --locked --quiet -p lyracore-gateway --example benilla_inventoryproduced the JSON inventory with nine behavior entries.Comment review passed for the inventory source and tests. Comments in scanner test strings remain fixture data.
What you did not verify
This is a curated starting set, not a complete gameplay audit. Test discovery does not prove a passing test or real-client behavior.
Merged Core changes: fixture timing → gossip Gates → Hunter pet rename → behavior evidence inventory. The Transfer correction #705 and the Deadmines tests have merged.
This PR targets
mainand contains its own change.Model: GPT-6 Astra, using Codex through T3 Code.