ci: run MyHOME's golden corpus and test suite against every OWNd change

[GreenGrassBlueOcean]

Follows from @Interstellar0verdrive's review note on #36: a change to the parser or the connection "needs someone who can run the conformance corpus". This makes CI that someone.

What

.github/workflows/myhome-conformance.yml, two jobs on every push and PR, each with this checkout installed in place of the OWNd release MyHOME pins:

job	runs	time	catches
corpus	MyHOME's scripts/run_ownd_smoke.py --target dev --skip-install: 255-vector golden corpus (parser extraction + builder parity), platform imports, mock-gateway TCP loopback	~1 min incl. install	a parse that shifts, a builder that emits a different frame, a removed symbol
suite	MyHOME's full test suite, core 2026.x / Python 3.14	~4 min	behavioural coupling — this is the run that flagged #35 against tests/test_connection.py and led to the send() retry flap fix (54f61e9)

workflow_dispatch takes a myhome_ref, so a release candidate can be proven against any MyHOME branch before either side tags.

Why both are required checks

An OWNd release is opt-in for users — MyHOME pins OWNd== exactly — so the only thing a release can break is the next MyHOME pin bump. A red suite here is the same red that pin bump would produce, learned before the release exists instead of after.

Verified locally

Same steps by hand on the current stack (#35 fix + #36): corpus 4/4 gates, suite 1599 passed. MyHOME-side changes that keep it green under both b6 and the new stack: OpenWebNet-HA/MyHOME#372.

🤖 Generated with Claude Code

[codecov-commenter]

⚠️ Please install the to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[GreenGrassBlueOcean]

@Interstellar0verdrive can you approve this test only pr please?

[xtimmy86x]

The workflow looks sound: I verified that both jobs install the local OWNd checkout, and the corpus, smoke gates, and full MyHOME suite all complete successfully.

Before approving, could you please sync this branch with the current master (0340902, including #35 and #39) and let the two MyHOME jobs run again? The existing checks were completed while this branch was still four commits behind master, so they do not yet validate the strict-typing changes now present there.

If the refreshed checks remain green, I have no further blockers.

[GreenGrassBlueOcean]

I have rebased the PR on the latest master. It should be good to go!