Add native component lifecycle foundations

[shanerbaner82]

Why this exists

Four things a native component does — invoking a method from a template, binding a route model, mutating state, and firing an event — are four unrelated code paths on main. Nothing shares a contract, so every capability got bolted on where it happened to be needed.

The concrete result is that main invokes template-bound callbacks as $this->$method(...$args) with no callability check at all. @tap="deleteAccount" will happily call a protected method, a lifecycle hook, or anything else that exists on the class. There is no seam to hang DI, binding, or validation off, because there is no single place where invocation happens.

That is the actual problem. Everything below follows from fixing it.

What you can't do today

	main	after
Type-hint a model or service in mount()	not injected	container-resolved
Type-hint a routable model on an action	you fetch it by hand	implicitly bound (incl. soft-deletes and child bindings)
Protect a property from client mutation	nothing stops it	#[Locked]
React to a property changing	no hook	updating* / updated*
Hit a route whose binding fails	isNativeRoute() can throw	stays inside the screen error lifecycle
Bind native:model inside a nested Blade partial	doesn't resolve	resolves against view data

This does not add a form or validation API, and it does not include skipRender() / #[Renderless].

Breaking changes

Four patterns that work on main fail after this lands. All four fail loudly at runtime, on screens that previously worked, so they are worth a CHANGELOG entry.

ComponentMethodInvoker::ensureCallable() is the new check, and that tightening is the source of (1) and (2).

#	Pattern on main	After this PR	Fix
1	protected / private method bound to @tap	ComponentMethodNotFoundException	make the method public
2	public function updatedFilters() bound to a callback	DirectlyCallingLifecycleHooksNotAllowedException	rename off the updating* / updated* / hydrate* / dehydrate* prefix
3	parent::mount() inside a component's mount()	fatal — NativeComponent::mount() no longer exists	delete the parent::mount() call
4	overriding or calling protected function dispatch(array $event)	fatal — now public dispatch(string $event, mixed ...$params): ComponentEvent	the old UI-event method is dispatchUiEvent(); dispatch() is the component-event API

Note that (3) breaks in both directions: a component written against this branch — mount() with arguments — is a fatal declaration error on a pre-343 package:

Declaration of App\NativeComponents\CounterWithClick::mount(Click $click, ParityDemoService $service, string $section = 'overview'): void
must be compatible with Native\Mobile\Edge\NativeComponent::mount(): void

Overriding mount() with any signature is otherwise fine and strictly more permissive than main, since there is no longer a base declaration to match.

Measured blast radius

Scanned every NativePHP app on hand — native, demo, xclone, tesla, flighty — matching method names referenced from @tap / onPress / @change against protected and lifecycle-prefixed declarations:

App	Components	(1)	(2)	(3)
native	129	0	0	0
demo	33	0	0	0
xclone	6	0	0	0
tesla	3	0	0	0
flighty	6	0	0	0

177 components, zero hits. Ordinary public actions — what nearly everyone writes — are unaffected.

One open question for review

(1) is the one most likely to exist in the wild, and it is the least deliberate part of the tightening: rejecting a non-public method is a different intent from rejecting a lifecycle name. Restricting the guard to lifecycle names only would keep the intent and remove most of the upgrade risk. Flagging it as a design call rather than changing it unilaterally.

What's here

Area	Change
ComponentMethodInvoker	Single DI-backed invocation path. Implicit binding for routable models and backed enums; lifecycle hooks protected from direct invocation.
ComponentRouteBinder	Implicit route-model binding, including soft-deletable and child bindings.
ComponentEvent	dispatch() with #[On] listeners, self-targeting and class-targeted delivery.
ComponentState	Shared property-sync pipeline with #[Locked] and updating* / updated* hooks.
NativeRouter	Match/resolve split so isNativeRoute() cannot throw; binding failures stay in the screen error lifecycle.
Mount DI	Container injection into mount().
native:model	Resolves against view data so nested Blade partials bind.

Hardening on this branch

• Empty string binds as null for nullable parameters (cleared select/radio vs backed enums).
• #[On] delivery no longer runs the lifecycle-name guard, so a listener named updated* / mount can actually run.
• Native::test()->call('navigate') (and emit / back / replace) matches the device path.
• A throwing poll fails once instead of re-painting the error overlay every tick.

Not in this PR

#[Renderless] and skipRender(). They are new relative to main, so omitting them drops no existing capability. The flag is still a screen-wide one-shot boolean (mount can eat the first frame, one renderless poll can skip a sibling, a child can skip the root). That needs per-invocation provenance; it should come back as a small follow-up, not ride this branch.

Attribution

Portions of the invoker, state hooks, event targeting, and the lifecycle-hook exception are derived from Livewire (MIT, Copyright © Caleb Porzio). See THIRD-PARTY.md and the file headers.

Verification

CI at 99a777b: Tests PHP 8.4, Static Analysis, and Code Style all passed.

Follow-ups after this lands

• native:model compiles every path through data_get(get_defined_vars(), …) (full symbol-table copy per bound input; typos become silent null). Prefer $prop for single-segment paths.
• Cache class_uses_recursive() instead of reflecting on every tap.
• fix: deliver native events to nested child components #344 (native events to nested children) rebases onto this.
• Make optional route segments resolvable #351 (optional {slug?}) becomes redundant once this is on main.

[simonhamp]

A bit too big, separate these kinds of things into distinct PRs in future. I agree that the breaking changes shouldn't affect anyone