Context
The helixir and helix teams are working in parallel on CEM fidelity tonight. This issue coordinates overnight work between teams.
What helixir is building
We're building 3 new health scoring dimensions + a cross-library benchmark suite (epic on board):
-
CEM-Source Fidelity analyzer (in progress, Opus agent) — cross-references CEM declarations against actual component source code. Detects phantom events (CEM declares, source doesn't dispatch — the carousel bug pattern), missing events, property/attribute drift. This would have caught the hx-slide-change vs hx-slide bug automatically.
-
Slot Architecture analyzer — scores slot documentation quality, default slot presence, slot-property coherence.
-
Naming Convention Consistency analyzer — library-wide naming pattern scoring (event prefixes, CSS custom property prefixes, attribute-property naming coherence).
-
Cross-Library Benchmark Suite — validates the full 14-dimension scorer against 11 real WC libraries + helix. Will generate a helix-specific report with actionable issues.
What we need from the helix team
Once the CEM-Source Fidelity analyzer lands, we'll run it against all 88 helix components and report back with specific discrepancies found. The carousel event was just the first — there are likely more.
Action items for helix team:
PR status — needs your attention
| PR |
Title |
CI Status |
What's needed |
| #80 |
HxSkeleton/HxSpinner drift |
changeset + format failing |
Ava is fixing — changeset + format push incoming |
| #81 |
HxTabs drift |
lint + test failures |
Needs helix team — lint errors + test failures on Node 20 and 22. Please investigate. |
| #82 |
CEM sync CI gate |
changeset only |
Ava is fixing — changeset push incoming |
| #83 |
validate_type_definitions tool |
lint + test failures |
Needs helix team — lint errors + test failures on Node 20 and 22. Please investigate. |
PRs #80 and #82 will be green shortly (Ava is pushing fixes now).
PRs #81 and #83 have deeper issues (lint + tests) that need the helix team to investigate.
How to collaborate
- Comment on this issue with findings, questions, or requests
- File new bugs on helixir board if you find CEM issues — Ava will triage and auto-mode will pick them up
- Once our benchmark suite lands, we'll post the full helix scorecard here
Timeline
- Now: CEM-Source Fidelity analyzer building (Opus agent)
- Next: Slot Architecture + Naming Consistency (parallel, after F1 merges)
- Then: Cross-Library Benchmark with helix report
- Morning: Full scorecard posted to this issue for helix team review
Ava is monitoring hourly. Auto-mode is running. Go time.
Context
The helixir and helix teams are working in parallel on CEM fidelity tonight. This issue coordinates overnight work between teams.
What helixir is building
We're building 3 new health scoring dimensions + a cross-library benchmark suite (epic on board):
CEM-Source Fidelity analyzer (in progress, Opus agent) — cross-references CEM declarations against actual component source code. Detects phantom events (CEM declares, source doesn't dispatch — the carousel bug pattern), missing events, property/attribute drift. This would have caught the
hx-slide-changevshx-slidebug automatically.Slot Architecture analyzer — scores slot documentation quality, default slot presence, slot-property coherence.
Naming Convention Consistency analyzer — library-wide naming pattern scoring (event prefixes, CSS custom property prefixes, attribute-property naming coherence).
Cross-Library Benchmark Suite — validates the full 14-dimension scorer against 11 real WC libraries + helix. Will generate a helix-specific report with actionable issues.
What we need from the helix team
Once the CEM-Source Fidelity analyzer lands, we'll run it against all 88 helix components and report back with specific discrepancies found. The carousel event was just the first — there are likely more.
Action items for helix team:
validate_type_definitionstool you built (PR feat: add validate_type_definitions MCP tool to catch CEM-to-types drift #83) is complementary — let's make sure it covers the same groundPR status — needs your attention
PRs #80 and #82 will be green shortly (Ava is pushing fixes now).
PRs #81 and #83 have deeper issues (lint + tests) that need the helix team to investigate.
How to collaborate
Timeline
Ava is monitoring hourly. Auto-mode is running. Go time.