refactor(web_core): decouple GenericBinder and separate catalog-agnostic package entrypoints

[gspencergoog]

Summary

This PR completes the catalog agnosticism refactor by addressing the remaining architectural decoupling recommendations:

1. GenericBinder Decoupling & ValidationResult Support:

   • Replaced hardcoded property name checks (checks) in GenericBinder.getFieldBehavior with schema introspection via isCheckableField.
   • Updated GenericBinder check evaluation to natively support v1.0 ValidationResult objects ({ valid: boolean, message?: string }) in addition to boolean condition expressions.
   • Added unit tests in generic-binder.test.ts verifying dynamic validation messages and custom check property schemas.

2. Catalog-Agnostic Package Entrypoints:

   • Created root src/index.ts exporting only catalog-agnostic core modules (catalog, state, processing, rendering, validating, reactivity, expressions, errors, events).
   • Created dedicated module barrels (src/catalog/index.ts, src/state/index.ts, src/rendering/index.ts, src/expressions/index.ts, src/reactivity/index.ts).
   • Updated package.json main, types, and exports["."], plus subpath exports (./catalog, ./state, ./processing, ./rendering, ./validating, ./reactivity, ./expressions, ./adapters).
   • Decoupled src/v0_9/index.ts by removing transitive basic_catalog re-exports.
   • Updated renderer imports in renderers/markdown/markdown-it and renderers/lit that specifically required v0.8 styles/types to explicitly import from @a2ui/web_core/v0_8.

Testing

• All 364 web_core unit and integration tests pass.
• All renderer unit and integration tests (Angular, Lit, Markdown-It) pass.

[gemini-code-assist]

Code Review

This pull request restructures the @a2ui/web_core package to export multiple subpaths, introduces v1.0 features including bidirectional RPC handling via RpcHandler, system functions like @index, and validation functions. It also adds robust validators for component integrity, path syntax, and graph topology, and updates SurfaceModel and GenericBinder to support these new structures. A review comment points out a performance optimization in MessageProcessor.getRendererCapabilities to avoid redundant calls to generateInlineCatalog when generating inline catalogs.

I am having trouble creating individual review comments. Click here to see my feedback.

typescript/web_core/src/processing/message-processor.ts (177-193)

When options?.includeInlineCatalogs is enabled, generateInlineCatalog is called twice for each catalog: once to populate versionCaps.inlineCatalogs and once to populate the root-level inlineCatalogs property in the returned object. Since generateInlineCatalog performs relatively expensive Zod-to-JSON-schema conversions, we should generate the inline catalogs once and reuse the array to improve performance.

    let inlineCatalogs: Record<string, unknown>[] | undefined;
    if (options?.includeInlineCatalogs) {
      inlineCatalogs = this.catalogs.map(c =>
        this.generateInlineCatalog(c, options?.componentEnvelopeRef),
      );
      versionCaps.inlineCatalogs = inlineCatalogs;
    }

    return {
      supportedCatalogIds: this.catalogs.map(c => c.id),
      ...(inlineCatalogs
        ? {
            inlineCatalogs,
          }
        : {}),
      [version]: versionCaps,
    };