…ts-import-dependencies-ryan

updates to `feat custom elements import dependencies`

Add WDIO tests rendering all <prop-…> components plus behavior checks for reflect=true/false (string/number/boolean)
Prop overlay: emit stable caseIds (#1 primitives, #2 complex, #3 reflect=true primitives, stenciljs#4 reflect=false primitives); 100% detection via JSX scan
@Prop.mdx: switch Test Cases to single-row-per-case (#1–stenciljs#4), drive “Tested By” from caseIds
Add placeholder rows for stenciljs#5 (mutable=true primitives) and stenciljs#6 (mutable=false primitives); show neutral status until implemented
Status logic: avoid checkmarks for unimplemented cases (render em dash)
AGENT_PROMPTS: replace with concise, copy-paste prompts to “Implement Test Case stenciljs#5/stenciljs#6 for the @prop decorator”; clarify “re-run Prop test-coverage.js” wording

Wrap @State specs into describe blocks:
Test Case #1 – Primitive mutation
Test Case #2 – Complex static render
Move/rename file from components.test.tsx to tests.tsx
Update State coverage script to scan test/wdio/state (folder root)
Extend test source collector to include a root-level tests.tsx (in addition to .test.)
Update @State docs note to reference test/wdio/state
Keep JSX render with targeted ts-ignore for WDIO browser-runner compatibility

…to AI memories

- Add test-case-conventions.md documenting AI-friendly structured test patterns
- Document @State test cases: #1 Primitive mutation, #2 Complex static render
- Document @prop test cases: #1-5 covering runtime, complex render, reflect/mutable behaviors
- Include complete matrix rendering patterns with WebDriver IO assertion examples
- Add component tag naming conventions and predictable DOM structure expectations
- Update memory-sync.js to include test case conventions in synchronization (high priority)
- Update README.md structure to include test-case-conventions.md file
- Update conventions.md with references to structured test case patterns
- Sync all memories to IDE including new test case conventions documentation

This completes the AI context system by documenting the existing sophisticated test case
patterns that enable easy test generation, extension, and maintenance across the 289-component
testing framework.

…ate tests

- **Structure**: Move components from matrix/ to components/ with bubbles/no-bubbles subdirs
- **File organization**: Create data/ subdirectory for rules.json, components.json, test-coverage.json
- **Scripts**:
  - Update generate-components.js to integrate runVerifier and add --force flag support
  - Rename coverage.js → test-coverage.js with proper test file analysis and caseIds assignment
  - Remove obsolete verify-matrix.js and coverage-overlay.json files
- **Tests**:
  - Move and rename tests/cmp.test.tsx → tests.tsx for WDIO pattern compliance
  - Organize into logical test cases: "Bubbling events" vs "Non-bubbling events"
  - Integrate 8 @event tests into main test suite (now 40/40 tests passing)
- **Documentation**:
  - Update @Event.mdx to use shared TestCasesTable and GeneratedComponentsTable
  - Fix test cases table to show implemented status with proper coverage data
  - Populate "Tested By" column with case numbers (#1, #2) in components table
- **NPM scripts**: Add event:generate-components:force and event:test-coverage patterns

- Add WDIO tests for Scoped mode covering light DOM rendering, scoped styles, styleUrl/styleUrls, formAssociated, and assetsDirs
- Include all 48 scoped mode components in test template
- Update test-coverage.json to mark Test Case #2 as implemented with 9 passing tests

* Add a test demonstrating how you can use extends to directly manage state as part of your baseClass

* Extend Tests for @method decorator inheritance, super() calls, method override, and method composition.

* Extend Tests for @prop and @State inheritance from base classes.

* Extend Tests for extending Stencil-decorated classes with render() method inheritance.

* Demonstrates base classes triggering host component updates via requestUpdate

* Tests demonstrating lifecycle hooks living on the base class

* Tests for multi-level lifecycle inheritance

* Tests for ReactiveControllerHost pattern - composition based controllers with automatic lifecycle hooking

* Run prettier

* Tests for decorator conflicts - duplicate decorator names of the same type in inheritance chains

Test Case #13 - Decorator Conflicts
Features:
- Duplicate @prop names (component overrides base)
- Duplicate @State names (component overrides base)
- Duplicate @method names (component overrides base)
- Compiler precedence rules (component decorators take precedence)

* Tests for event handling inheritance - @listen decorator inheritance

Test Case #10 - Event Handling Inheritance
Features:
- Inherits base class window/document/host listeners
- Handles child class window/document/host listeners
- Child override event handler takes precedence over base
- Handles event bubbling correctly
- Tracks events in combined event log

* Tests for @watch decorator inheritance

Test Case #11 - Watch Decorator Inheritance
Features:
- Inherits base class @watch decorators
- Handles child class @watch decorators
- Executes watch handlers in correct order (base first, then child)
- Child override watch handler takes precedence over base
- Reactive property chains work correctly
- Tracks watch calls in combined watch log

* Tests for mixed decorator types - different decorator types with same name

Test Case #18 - Mixed Decorator Types
Features:
- @prop in Base, @State in Component (same name)
- @State in Base, @prop in Component (same name)
- @method in Base, @prop in Component (same name)
- Component decorator type takes precedence
- Runtime behavior verification

* Tests for inheritance-based scaling with multiple components and controllers

Test Case #15 - Inheritance-Based Scaling
Features:
- 3 components (TextInput, RadioGroup, CheckboxGroup) using inheritance
- 2 controllers (ValidationController, FocusController) via inheritance
- Lifecycle methods called correctly
- Validation triggers on blur
- Focus tracking works
- Controllers use inheritance pattern

* Tests for composition-based scaling with multiple components and controllers

Test Case #16 - Composition-Based Scaling
Features:
- 3 components (TextInput, RadioGroup, CheckboxGroup) using composition
- 2 controllers (ValidationController, FocusController) via composition
- Lifecycle methods called automatically via ReactiveControllerHost
- Validation triggers on blur
- Focus tracking works
- Controllers are properly composed (not inherited)

* Apply prettier formatting & tweak test case #s

* Remove the duplicate method as it was causing types error

---------

Co-authored-by: Paul Visciano <paul.visciano@outsystems.com>