UTTORI ASM · IN DEVELOPMENT

Core API entry points

Integrate core api entry points through supported Uttori ASM APIs.

Entry point	Intended use
`@uttori/asm-core`	`Assembler`, file providers, diagnostics, architecture/decoder types, syntax, source maps, and tooling
`@uttori/asm-core/plugin`	Plugin definitions, contribution contracts, `PluginManager`, environments, state, and structured errors
`@uttori/asm-core/debug-map`	Debug-map serialization, validation, source mapping, and binary identity
`@uttori/asm-plugin-loader-node`	Configuration validation/discovery and trusted Node plugin loading
`@uttori/asm-plugin-loader-node/asm-config.schema.json`	Editor JSON schema

The browser condition selects the portable core entry point. Supply an in-memory file provider; filesystem-backed defaults belong to Node hosts. Portable target encoders can call parseExpressionNode() at runtime as well as parseOperandSyntax().

The core root also exposes pluginApi and the main plugin runtime classes/functions. Import plugin types from /plugin. Front-end/lowering services, ProgramModelBuilder, IR types, LSP helpers, OwnedContribution, and PluginSessionStateStore remain available for advanced hosts. They require the same stage, target, and ownership invariants as Assembler. Most integrations should use the assembler and manager. Package-internal src/ and dist/ paths are not entry points.