[koculu]

Summary

Component discovery repeatedly builds selectors and calls Element.matches() during DOM traversal. Cache a matcher by parser context-array identity and global registry size, using tag-name lookups for plain component names and retaining selector matching for other names. Pass the matcher directly through traversal and preserve its scope while nested binding runs.

Changes

• Add coverage for name matching, registration changes, empty registries, and parent scope restoration.
• Add equivalent nested-component workloads to the Regor/Vue browser benchmarks, plus minidom scenarios for mounting, prop updates, and remounting.
• Validate rendered props, classes, order, and slots outside timed sections.
• Update benchmark mutations to use reactive element setters and array operations.
• Refresh performance baselines for 500, 1,000, and 2,000 rows.
• Add a benchmark TypeScript configuration with Node types.

Validation

132 relevant tests, library and benchmark type checks, lint, and benchmark builds pass. Browser output checks pass for both frameworks at 500 rows; minidom scenarios pass at 500 and 2,000 rows.