Aomi Build - App & Plugin Builder

🔒 Constraints

When working inside aomi-sdk:

Scaffold with cargo run -p xtask -- new-app if starting from scratch, or copy sdk/examples/app-template-http.

Build the plugin with cargo run -p xtask -- build-aomi --app .

If build-aomi reports zero built plugins for a brand new app, check whether the new apps//Cargo.toml is still untracked. The current xtask prefers git ls-files discovery for app manifests.

For a direct compile signal on an untracked app, use cargo build --manifest-path apps//Cargo.toml.

If the app has meaningful branching or normalization logic, add unit tests with aomi_sdk::testing::{TestCtxBuilder, run_tool, run_async_tool}.

If a real target is available, validate the app with a short ladder:

- compile/build - connectivity check - one representative read flow - one representative write or submit flow when applicable - post-write verification such as status, receipt, or refreshed state

Prefer proving one end-to-end user scenario over checking many disconnected endpoints.

When the task also touches docs or demos in aomi-widget, update the relevant examples or guides to match the new app behavior.