Add MicroStack admin UI with request/resource APIs

[damianh]

Summary

• add a new Blazor WebAssembly admin client (MicroStack.UI.Client) and host (MicroStack.UI) served on a dedicated UI port
• add backend admin APIs for request logging and resource exploration
• implement resource providers for SQS, S3, and DynamoDB to expose names/ARNs and key attributes
• wire solution, container configuration, and docs for dual-port runtime (4566 API + 4567 UI)

Backend changes

• add RequestLog ring buffer + RequestLogMiddleware
• add GET /_microstack/requests and DELETE /_microstack/requests
• add IResourceProvider, ResourceSummary, ResourceItem
• add GET /_microstack/resources
• add MICROSTACK_UI_PORT option and startup logging
• register new AOT JSON types in MicroStackJsonContext

UI changes

• Dashboard page for health/service status/resource counts
• Request Log page with polling, pause/resume, row limits, and clear action
• Resource Explorer page grouped by service
• typed API client with configurable ApiBaseUrl

Validation

• dotnet build src/MicroStack/MicroStack.csproj
• dotnet build src/MicroStack.UI/MicroStack.UI.csproj
• dotnet test tests/MicroStack.Tests/MicroStack.Tests.csproj --filter-not-class MicroStack.Tests.ContainerSmokeTests

Notes

• full solution test restore still hits existing MessagePack vulnerability-as-error failures in Aspire projects
• container smoke test requires Linux NativeAOT toolchain support in the environment

[coldtea-pr-lens]

◈ PR Lens

🟢 +10 new · 🟠 ~13 changed · 🔴 -0 removed · 2 flows · 45 files · commit 34a8292

Architecture

23 components touched across 6 lanes.

Open the interactive canvas

Inside the changed components — 2 views

Component view — Admin API & Live Engine

Internal modules handling admin inspection routes, event streaming, request logging, and relationship resolution.

Component view — Resource Explorer UI

Blazor WebAssembly client architecture managing views, live event coordination, API client, and inspector components.

Data flow

Live change event streaming · Inspecting resource details and connections

Open the interactive canvas

The other flows — 1 sequence

Inspecting resource details and connections

View

• Architecture lens
• Data flow lens
• Expand every detail

Tip

The CLI's render reads .github/pr-lens.yml and applies your renames, exclusions and lane pins at draw time.

🪧 More tips

• Run npx skills add coldteadotai/pr-lens, then tell your coding agent: "Diagram the change you just made with PR Lens and attach it to the pull request."
• Run npx @coldtea/pr-lens-cli analyze --base origin/main on a branch, then npx @coldtea/pr-lens-cli render .pr-lens/graph.json. Same lenses, your own model key, before the pull request exists.
• Untick Architecture lens or Data flow lens under View to hide a diagram, or tick Expand every detail to open every section. The comment redraws in a few seconds.
• Click the link under each diagram to open it on a canvas you can zoom, pan and step through.
• The diagrams are links. Click one to open it on the canvas, then press W or click play to walk through the change.
• Open a diagram on the canvas, then press W or click play to walk through the change one step at a time.
• Set github.comment.collapsed: true in .github/pr-lens.yml to fold the comment behind one View architecture and data flow row. Drawing still runs on every push.
• Add .github/workflows/pr-lens.yml with coldteadotai/pr-lens/packages/action@v0 and your model provider's key as its api-key to run PR Lens from your own CI. Any /chat/completions endpoint works.
• Push a commit and the comment redraws for the new head. A slow older run never overwrites a newer one.
• Switch GitHub to dark mode and the diagrams follow. The moving dots are this pull request's data in motion.

---

Thanks for using PR Lens! It's built by Coldtea, free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn