This package owns the complete caller-port Forms lifecycle implementation: management, immutable publication, submission, assurance, consent, deterministic navigation, scoped idempotency, locale fallback and PII-safe CSV. It owns the whole document model, compiler, validation and relation helpers used by these services. Concrete authority, storage, clocks, IDs, tokens, digest and event delivery remain supplied through the original complete ports.
Compatibility intent is an ownership relocation with unchanged bodies, defaults, callback order, nominal error and function identity. ModuleForms keeps its UI and server composition and forwards the old runtime/model/helper leaves to the same canonical objects. RuntimeCore forwards its eight supported Forms leaves here. Product, OPA destination and renderer literals remain complete.
The ./contracts/platform-* leaves own the Forms operation/event catalog, capability and milestone features, product composition, portable serialization, registry registration. Compatibility Forms paths forward the same objects. Registration returns the supplied registry unchanged, retaining its concrete host context and subtype without importing RuntimeCore. Decision-graph conversion lives in DecisionRuntime's ./form-decision-graph
entry, which consumes these portable Forms document types. FormsRuntime has no dependency on DecisionRuntime or its workflow/runtime composition.
The narrow service entry deliberately defers unrelated allocations and scalar cache warming from the old ModuleForms contracts aggregate. That aggregate keeps its original ordered exports and canonical Growth/Catalog fixture identities. Schema retains its single scalar factory cache; no schemas, factories, registry or error constructors are duplicated.
The relation helper uses the complete canonical Kernel predicate evaluator. Its original callback order and indexed-path resolver remain unchanged. The actual held Kernel supplier must be joined and qualified; this Source staging does not claim that every other workspace dependency cycle is closed.
Task-bound adoption, producer declarations, physical resolution, identity and initialization tests, affected consumers and full qualification remain required before integration. Generated artifacts are awaiting owning-workflow regeneration.
