ZOA Extensions

IFoundryExtension is the umbrella. ExtensionId is a stable identifier used both to de-duplicate registrations across domain reloads and to correlate a runtime integrator with a curated catalogue row. DisplayName, Description and Category drive the browser row. IsAvailable says whether the underlying package is detected. DiagnosticSummary is the short status line, something like five tree prefabs and three grass billboards detected, or Blaze AI runtime detected with the perception bridge inactive. Refresh re-runs detection, and SupportsSetup plus RunSetup provide the one-click action.

IFoundryScriptingSymbolExtension adds the define-symbol layer for integrations gated behind a compile symbol. Detection runs in two stages: reflect across AppDomain for any of RequiredTypeNames to decide the package is present, then declare ScriptingDefineSymbol in Player Settings when the user runs Setup so the gated code starts compiling. IsScriptingSymbolActive backs the DEFINE ON and DEFINE OFF pill in the browser.

IFoundryExtensionWithDemo adds a runnable demo. An extension can return a DemoScenePath for a scene already on disk, or override GenerateAndOpenDemo to author one first. The browser only shows the button when the extension is also detected, because every demo expects its package's runtime types to resolve.

FoundryExtensionRegistry is a static list. Extensions register themselves at editor load from an [InitializeOnLoadMethod]; the browser iterates All to render rows and pipeline-specific consumers cast entries to the capability they care about.

Register de-duplicates by ExtensionId and replaces the stored reference rather than appending, so a domain reload leaves the registry holding the fresh instance instead of a stale one plus a duplicate row. Changed fires on register and unregister, which is how the browser repaints as integrators stream in after a reload.

TerrainIntegratorAdapter wraps a terrain IExtensionIntegrator, forwarding its properties verbatim and reporting the Terrain category by default, with a constructor override for integrators that belong elsewhere such as Cinemachine landing under PlayerRig. It is presentation only: the legacy ExtensionIntegratorRegistry still drives the demo scene generator's apply pass unchanged.

NucleonIntegrationAdapter wraps a player-rig IntegrationDefinition and implements IFoundryScriptingSymbolExtension, so the browser can show the gating symbol state and offer a one-click add. It discovers every concrete IntegrationDefinition subclass by reflection at editor load. The player wizard keeps its own discovery loop; this adapter is purely additive.

CuratedEntryAdapter wraps an ExtensionEntryDefinition, the curated catalogue asset that still lives in com.zoa.terrain. Detection rides the shared ExtensionDetectionService with its UPM probe, asset-path scan and folder fuzzy match. Setup handles all three install paths: FreeUnity adds by UPM id, FreeOSS adds by pinned git URL, Paid opens the Asset Store page.

A package such as ProBuilder can appear twice: once as a live terrain integrator and once as a curated catalogue entry with a normalised id like curated.ProBuilder. The browser renders only one row.

The integrator wins, because its detection is canonical, resolved synchronously through the UPM package probe, and its setup hook does the real scene-side wiring. The curated entry is kept as an install fallback: when the integrator reports missing, the row's Install button delegates to the curated entry's setup hook so the user still gets a one-click install.

Extensions sits well below demo in the package graph, so it cannot reference com.zoa.demo to open a demo scene. FoundryExtensionDemoRegistry inverts that: com.zoa.demo registers a handler per extension id from an [InitializeOnLoadMethod], and the browser is a passive consumer that surfaces an Open Demo button when both a handler exists and the extension is detected.

A handler is an extension id, a callable, an optional button label and a description. The demo package's bindings map ProBuilder and Splines to the AI Encounters generator and Cinemachine to the Full Showcase generator, so opening a demo from the browser regenerates a scene that actually exercises the integration.

Adding a demo therefore never touches com.zoa.extensions; the registry is the only seam between the two packages.

The runtime bridges compile without their targets. BlazeAiAgentDamageBridge, EmeraldAiAgentDamageBridge and BehaviorDesignerAgentDamageBridge each sit on the same GameObject as the third-party agent and implement Foundry's IAiDamageReceiver, forwarding a DamageContext into the vendor's damage method through cached reflection. When the player's hitscan walks up from a hitbox collider looking for IAiDamageReceiver, it resolves to the bridge.

FinalIkAgentRig adds aim and look-at solvers to an agent rig at runtime through reflection, no-opping entirely when Final IK is absent. PuppetMasterDeathBridge converts an agent's death into an active-ragdoll state so a body falls and keeps responding to hits instead of freezing on a T-pose. ZOAEnviroDayNightDriver either pushes the configured ZOA time of day into Enviro on Awake or pulls Enviro's current time every frame so the HUD clock, AI senses and vegetation read one clock.

Editor-side bridges follow the same rule. The AI bridges cover Blaze AI, Emerald AI 2025, Behavior Designer and Sensor Toolkit 2, plus a set of detect-only entries for RAIN AI, Behavior Bricks, Polarith AI Free, Apex Path and Utility AI, and Sensor Toolkit v1 that probe for types and report presence without wiring anything. The engine bridges cover DOTween, Easy Save 3, Enviro 3, Final IK and PuppetMaster.