This guide is the hosted route ladder from first install to realistic host proof. It has one unambiguous intake handoff from defended route to bounded intake record: step 3 hands off to Beta Support Bundle for the attachment note, then to Adoption Feedback Loop for the bounded intake record. Use it when you are evaluating AsterGraph as an SDK, not when you are maintaining release infrastructure.
If you are evaluating plugin trust, treat AsterGraph.ConsumerSample.Avalonia as the defended hosted trust hop. Read Plugin Manifest and Trust Policy Contract v1 and Plugin And Custom Node Recipe before you stop at the route ladder.
If you need reviewable local evidence while you follow the defended route, keep Beta Support Bundle close to step 3.
- stay on the shipped Avalonia path or the canonical runtime/session path
- treat
WPFas validation-only adapter-2 coverage, not a second onboarding path or a parity promise - treat retained
GraphEditorViewModel/GraphEditorViewas migration-only - keep
Demoand release harnesses for later visual inspection or maintainer validation, not for first evaluation
Follow this ladder in order. Each step answers one question and hands off to the next one.
The hosted route ladder is Starter.Avalonia -> HelloWorld.Avalonia -> ConsumerSample.Avalonia.
| Step | Run this | Why it comes now | Proof handoff |
|---|---|---|---|
| 1 | AsterGraph.Starter.Avalonia |
confirms the first hosted end-to-end route with the smallest scaffold | once the shell opens, move to the smallest stock sample |
| 2 | AsterGraph.HelloWorld.Avalonia |
confirms the shipped Avalonia surface without extra host wiring | once this is clear, move to the realistic hosted proof |
| 3 | AsterGraph.ConsumerSample.Avalonia -- --proof |
proves host-owned actions, trusted-plugin flow, parameter editing, command projection, and hosted accessibility semantics on the defended route | expect CONSUMER_SAMPLE_OK:True, COMMAND_SURFACE_OK:True, HOSTED_ACCESSIBILITY_OK:True, HOSTED_ACCESSIBILITY_AUTOMATION_NAVIGATION_OK:True, HOSTED_ACCESSIBILITY_AUTHORING_DIAGNOSTICS_OK:True, HOSTED_ACCESSIBILITY_AUTOMATION_OK:True, and HOST_NATIVE_METRIC:*; this is the proof handoff only, and the bounded intake record lives in Beta Support Bundle, Hosted Accessibility Recipe, and Adoption Feedback Loop |
| 4 | AsterGraph.HostSample |
validates the proof harness after the realistic host sample is already understood | expect HOST_SAMPLE_OK:True, HOST_SAMPLE_AUTOMATION_OK:True, HOST_SAMPLE_ACCESSIBILITY_BASELINE_OK:True, and HOST_SAMPLE_ACCESSIBILITY_AUTOMATION_OK:True; use this only after ConsumerSample.Avalonia |
If you are intentionally evaluating the runtime-only path, run AsterGraph.HelloWorld after step 1 instead of step 2, then return to the same realistic hosted proof at step 3.
If CONSUMER_SAMPLE_PARAMETER_OK or CONSUMER_SAMPLE_METADATA_PROJECTION_OK fail, keep the failed proof-marker lines together with the support bundle's parameterSnapshots rows on the same bounded intake record.
For one screen-reader-ready local evaluation path, keep the step-3 support bundle plus the step-4 HostSample proof lines on that same bounded intake record. This remains local evidence only and does not widen support promises.
If you need bounded adapter-2 follow-up after the defended Avalonia proof, run AsterGraph.HelloWorld.Wpf -- --proof after step 4 and keep HOSTED_ACCESSIBILITY_BASELINE_OK:True, HOSTED_ACCESSIBILITY_FOCUS_OK:True, HOSTED_ACCESSIBILITY_COMMAND_SURFACE_OK:True, HOSTED_ACCESSIBILITY_AUTHORING_SURFACE_OK:True, HOSTED_ACCESSIBILITY_OK:True, ADAPTER2_PERFORMANCE_BASELINE_OK:True, ADAPTER2_PROJECTION_BUDGET_OK:True:none, ADAPTER2_COMMAND_BUDGET_OK:True:none, ADAPTER2_SCENE_BUDGET_OK:True:none, ADAPTER2_WPF_SAMPLE_PROOF_OK:True, ADAPTER2_CANONICAL_ROUTE_OK:True, ADAPTER2_SAMPLE_SCOPE_BOUNDARY_OK:True, and HELLOWORLD_WPF_OK:True on that same local record; see Adapter-2 Accessibility Recipe and Adapter-2 Performance Recipe.
# first hosted confirmation
dotnet run --project tools/AsterGraph.Starter.Avalonia/AsterGraph.Starter.Avalonia.csproj --nologo
# smallest shipped Avalonia surface
dotnet run --project tools/AsterGraph.HelloWorld.Avalonia/AsterGraph.HelloWorld.Avalonia.csproj --nologo
# realistic hosted proof on the defended beta path
dotnet run --project tools/AsterGraph.ConsumerSample.Avalonia/AsterGraph.ConsumerSample.Avalonia.csproj --nologo -- --proof
# proof harness only after the realistic hosted sample
dotnet run --project tools/AsterGraph.HostSample/AsterGraph.HostSample.csproj --nologo
# bounded adapter-2 accessibility validation only after the defended Avalonia proof
dotnet run --project tools/AsterGraph.HelloWorld.Wpf/AsterGraph.HelloWorld.Wpf.csproj --nologo -- --proof- step 3 is the realistic hosted proof gate for most evaluators
ConsumerSample.Avaloniashould emitCONSUMER_SAMPLE_OK:True- the same run should emit
COMMAND_SURFACE_OK:True - the same run should emit
HOSTED_ACCESSIBILITY_OK:True,HOSTED_ACCESSIBILITY_AUTOMATION_NAVIGATION_OK:True,HOSTED_ACCESSIBILITY_AUTHORING_DIAGNOSTICS_OK:True, andHOSTED_ACCESSIBILITY_AUTOMATION_OK:True - the same run should emit the four
HOST_NATIVE_METRIC:*lines HostSampleshould emitHOST_SAMPLE_OK:True,HOST_SAMPLE_AUTOMATION_OK:True,HOST_SAMPLE_ACCESSIBILITY_BASELINE_OK:True, andHOST_SAMPLE_ACCESSIBILITY_AUTOMATION_OK:TrueAsterGraph.HelloWorld.Wpf -- --proofshould emitHOSTED_ACCESSIBILITY_BASELINE_OK:True,HOSTED_ACCESSIBILITY_FOCUS_OK:True,HOSTED_ACCESSIBILITY_COMMAND_SURFACE_OK:True,HOSTED_ACCESSIBILITY_AUTHORING_SURFACE_OK:True,HOSTED_ACCESSIBILITY_OK:True,ADAPTER2_PERFORMANCE_BASELINE_OK:True,ADAPTER2_PROJECTION_BUDGET_OK:True:none,ADAPTER2_COMMAND_BUDGET_OK:True:none,ADAPTER2_SCENE_BUDGET_OK:True:none,ADAPTER2_WPF_SAMPLE_PROOF_OK:True,ADAPTER2_CANONICAL_ROUTE_OK:True,ADAPTER2_SAMPLE_SCOPE_BOUNDARY_OK:True, andHELLOWORLD_WPF_OK:Trueon the validation-only adapter-2 lane
WPFcoverage is validation-only; it does not widen the supported hosted adapter boundary- retained MVVM is migration-only; it is not the recommended evaluator route
HostSampleis a proof harness, not the first product-like experienceDemois useful only after the route and proof expectations are already clear