API Coverage Index

This index maps the shipped AXSG package surface to the narrative docs and generated API reference.

Package groups

Group	Packages	Primary docs
Compiler host and contracts	`XamlToCSharpGenerator.Compiler`, `XamlToCSharpGenerator.Core`, `XamlToCSharpGenerator.Framework.Abstractions`	Compiler Host and Project Model, Compiler and Core Namespaces
Framework profiles and parsers	`XamlToCSharpGenerator.Avalonia`, `XamlToCSharpGenerator.NoUi`, `XamlToCSharpGenerator.ExpressionSemantics`, `XamlToCSharpGenerator.MiniLanguageParsing`, `XamlToCSharpGenerator.Generator`	Binding and Expression Model, Expression, Parsing, and Framework Namespaces
Runtime and editor	`XamlToCSharpGenerator.Runtime`, `XamlToCSharpGenerator.Runtime.Core`, `XamlToCSharpGenerator.Runtime.Avalonia`, `XamlToCSharpGenerator.Editor.Avalonia`	Generated Artifacts and Runtime, Runtime and Editor Namespaces
Tooling and integration	`XamlToCSharpGenerator.RemoteProtocol`, `XamlToCSharpGenerator.LanguageService`, `XamlToCSharpGenerator.LanguageServer.Tool`, `XamlToCSharpGenerator.McpServer.Tool`, `XamlToCSharpGenerator.Build`, `XamlToCSharpGenerator`	Tooling Surface, Language Service and Tooling Namespaces

Package and assembly mapping

Use Package and Assembly when you need the installation identity, shipped payload, and generated API status for each artifact. Use Assembly Catalog when you already know the assembly or shipped artifact name and want the direct generated API route plus the matching narrative guide. Use Feature Coverage Matrix when you know the feature area but need to map it to the right package and namespace entry point.

Package guide coverage

Every shipped package and editor/tool surface now has a dedicated narrative page:

Generated API scope

The Lunet api.dotnet build on this branch covers these projects:

XamlToCSharpGenerator.Compiler
XamlToCSharpGenerator.Core
XamlToCSharpGenerator.Framework.Abstractions
XamlToCSharpGenerator.Avalonia
XamlToCSharpGenerator.ExpressionSemantics
XamlToCSharpGenerator.MiniLanguageParsing
XamlToCSharpGenerator.NoUi
XamlToCSharpGenerator.Generator
XamlToCSharpGenerator.Runtime.Core
XamlToCSharpGenerator.Runtime.Avalonia
XamlToCSharpGenerator.RemoteProtocol
XamlToCSharpGenerator.LanguageService
XamlToCSharpGenerator.LanguageServer.Tool
XamlToCSharpGenerator.Editor.Avalonia

For a direct assembly-to-API route map, use Assembly Catalog.

Narrative-only shipped/internal artifacts are documented outside generated API when a package is primarily a package shell, MSBuild targets layer, or operational executable. The main examples are:

XamlToCSharpGenerator via Package Guides and Package and Assembly
XamlToCSharpGenerator.Build via Package Guides and Package and Assembly
XamlToCSharpGenerator.Runtime via Package Guides and Package and Assembly
XamlToCSharpGenerator.DotNetWatch.Proxy via Internal Support Components

These are intentionally excluded from generated API because they do not provide a stable, useful public namespace surface on their own.

Namespace entry points

Notes

Generated API pages remain the member-level authority.
Package guides and namespace pages provide the orientation missing from the raw generated API tree.