aspire-orchestration

Use `aspire start` to run the AppHost in the background, never `dotnet run`. In git worktrees add `--isolated` to avoid port conflicts, and add `--non-interactive` so commands never prompt for input.

These errors mean Aspire is running and holding locks on bin/ and obj/ outputs. Run `aspire stop` first, then rebuild or restart; never delete bin/obj, kill dotnet processes, or assume a permanent build failure.

Use `aspire start` for agents because it runs detached in the background and returns control immediately. `aspire run` is foreground and interactive, intended for human developers at a terminal.

Look for `Aspire.AppHost.Sdk` in a .csproj, an `apphost.cs` file with a `#:sdk Aspire.AppHost.Sdk` directive, or an `apphost.ts` file. Secondary signals include `aspire.config.json`, a `.aspire/` directory, and `Aspire.ServiceDefaults` references.

The `aspire wait` command expects the resource's `displayName`, not its `name` field. Run `aspire ps --format Json` and pass the `displayName` value to `aspire wait`.

Restart the full AppHost only when AppHost code, integrations, or resource definitions changed. For a single resource change, prefer resource-scoped commands like `aspire resource <name> rebuild` or the framework's own watch and hot reload workflow.