feat(bindx-react): createComponent().use() + crash-proof static selection analysis

[matej21]

Fixes #57.

Problem

createComponent(...).render(...) crashed implicit-selection collection whenever the render body used a scalar (.props<>()) prop value — e.g. calling a translator t(key) or reading labels.heading. The collection pass fed undefined for every scalar prop and ran the render unguarded, so the call/dereference threw.

Worse than the crash itself: when triggered through a fetching <Entity>'s walk, the throw was swallowed by a coarse try/catch in useSelectionCollection, silently dropping the whole JSX-derived selection (including sibling components' fields) from the fetch plan — a real data-loss (noindex and friends never fetched, downstream shipped collectionSafeT workarounds).

Design

Implicit collection is an abstract interpretation of the render body. This PR makes it total (never crashes out) and confines it to the static-analysis phase:

1. Tolerant scalar stand-ins — during collection, scalar props resolve to an inert value that absorbs calls, property access, primitive coercion and iteration. Scalar content can never affect field selection, so the analysis must not need real values. (Known, accepted hole: indexing a real object with a mocked key — handled by 2 & 3.)
2. Collection only from the static surface — ComponentImpl no longer triggers it; it runs solely from getSelection, $propName fragment getters, and the interfaces proxy. Render bodies are pure runtime code. Components whose selection nobody statically consumes are never collected (no dead work, no spurious dev errors). The guard is tri-state (collecting terminates self-recursive components).
3. Graceful, loud degradation — scopes capture field accesses eagerly, so a mid-body throw now finalizes the partial selection instead of losing everything, and logs a console.error with component attribution (displayName). analyzeJsx catches per node — one broken component no longer costs its siblings their selection.
4. .use(fn) — runtime-only values, hooks allowed:

const PageForm = createComponent()
	.entity('entity', schema.WebsitePageRevision)
	.use(() => ({ t: useT() }))
	.render(({ entity, t }) => (
		<InputField field={entity.page.title} label={t('wb.forms.page.titleLabel')} />
	))

Runs inside the React render (hooks, context all work) and merges into render props; chainable — later use() fns see earlier values. Static analysis skips it entirely; its outputs fall through to the scalar stand-ins. Type-wise the values exist only in render props, not on the public component props. This removes the thin wrapper components that existed only to thread hook-derived values in as props — wrappers that also broke selection discovery, since the JSX walk cannot see through plain components.

Verification

• Repro test from the issue branch (createComponentScalarPropCollection.test.tsx) now passes.
• New createComponentUse.test.tsx: analysis skips use() while still collecting fields; hooks inside use(); chaining; sibling isolation on analysis crash; partial capture before a throw.
• Full suite: 1616 pass. Pre-existing failures unchanged (browser suite fails identically on main with the playground running; bindx-form formRelations dirty-tracking fails on main too).
• Wired into the NPI admin via source sync: both collectionSafeT workarounds and the PageForm wrapper removed, full admin suite 288/288 green (companion PR in that repo).

🤖 Generated with Claude Code

https://claude.ai/code/session_016eijo87HdS4vA6D2ZcS6KL