QA report: external/aether-dapp-simulator.expo.app at hosted
The Bedrock agent backend is broken. Direct macro dispatch could not be exercised in this sandbox.
Testing covered 11 scenarios across the dApp simulator, evaluating onboarding modal flows, Sui testnet wallet connection and persistence, prompt validation, quick prompt helpers, direct macro dispatch, and telemetry inspection.
One high-severity functional issue was confirmed: prompting the Bedrock agent results in an immediate 'Agent error' without generating tool calls or rendering the dispatch transaction button (F1).
A second finding, that direct macro dispatch fails with an HTTP 402 payment rejection, was withdrawn after a hand check. Every macro command costs a small amount of Testnet USDC per the app's own onboarding text, which names its "Open Faucet" link as the way to get it. Following that exact link opens the official Sui faucet, which only offers "Request Testnet SUI," no USDC option anywhere. So the app's own documented path to the required token never actually provides it, and our wallet was never going to be able to fund this flow through anything the app itself offers. Environment limitation, not an app defect.
While wallet connection persistence, UI state handling, and onboarding dialogs passed validation, the application's primary agentic dispatch path is broken, and its direct-control dispatch path remains untested rather than confirmed broken.
Run summary
| Metric | Count |
|---|
| Scenarios executed | 11 |
| Passed | 9 |
| Failed | 2 |
| Blocked | 0 |
| Findings raised | 1 |
| Issues after the audit | 1 |
| Withdrawn by the audit | 1 |
| Critical / high / medium / low | 0 / 1 / 0 / 0 |
Target: https://aether-dapp-simulator.expo.app/ · Testing level: deep_feature · Stack: unknown
Issues
High severity
F1 · Agent fails to generate tool calls and returns 'Agent error' on prompt dispatch
Severity: high · Type: functional · Verdict: confirmed · Scenario: S4
The console shows a 500 Internal Server Error when the prompt is sent, confirming the application's backend failed and returned an 'Agent error' message. The live replay was inconclusive: The replay ran out of tool calls before it reached the reported state. The page reported 2 console errors during the scenario.
Expected: The agent should interpret the sequential motion prompt, propose the corresponding tool calls, and provide the 'Transact & Dispatch via x402' button for execution.
Actual: The Bedrock agent layer responds with 'Agent error' upon sending a prompt, failing to generate tool calls or display the 'Transact & Dispatch via x402' button.
Steps to reproduce:
- Navigate to https://aether-dapp-simulator.expo.app/
- Click the 'Agent' navigation tab
- Click the '✨Try Prompt: \"Sequential Motion\"' button to populate the prompt
- Click the 'Send' button
Evidence: screenshots/S4-8.png
Environment limitations
These failures came from the test environment, not from the application: a credential the sandbox does not hold, a demo nobody may write to, a resource it cannot reach. They are not counted as issues. They record what this run could not exercise.
- Macro dispatch needs Testnet USDC the app's own faucet link never provides (S8, high): Surfaced by the audit of S8, which the Tester passed, and reproduced live: I clicked the 'HOME' button on the Direct Control tab. After a brief wait, a status message appeared on the page stating 'Transaction Failed: Could not fulfill any payment requirements provided by the server.', reproducing the reported behavior. The page reported 2 console errors during the scenario. Hand check, 2026-09-27: the app's own onboarding modal names an 'Open Faucet' link under 'Fund with Testnet USDC' as the way to get the USDC each command costs. Followed that exact link and it opens the official Sui faucet at faucet.sui.io, which only has a 'Request Testnet SUI' button, no USDC option anywhere. So the app's own in-app path to the required token does not actually provide it, our wallet was never going to be able to fund this flow through anything the app offers. Environment limitation, not an app defect, the same class as round 1's Bluefin collateral gap.
Scenario results
| Scenario | Priority | Result | Issues |
|---|
| S1 Dismiss the onboarding modal | high | pass | none |
| S2 Connect Sui testnet wallet | high | pass | none |
| S3 Dispatch Front High macro via Direct Control | high | fail | none |
| S4 Dispatch a populated Agent command | high | fail | F1 |
| S5 Validate empty Agent command | medium | pass | none |
| S6 Validate whitespace Agent command | medium | pass | none |
| S7 Populate Agent input via quick prompt | medium | pass | none |
| S8 Dispatch HOME macro via Direct Control | medium | pass | none |
| S9 Open and inspect the Telemetry Drawer | medium | pass | none |
| S10 View Onboarding Instructions | low | pass | none |
| S11 Verify wallet connection persistence on reload | low | pass | none |
The audit
The Critic reviewed 1 finding and ran 3 live replays in the browser, each on a fresh page.
- Scenarios S3 and S8 contradict each other: S3 failed due to missing Testnet USDC causing a 402 error, while S8 observed the exact same failure but marked the scenario as passed.
- The wallet activity correctly shows zero transactions sent because the x402 payment requirement triggered an HTTP 402 rejection before any on-chain transaction could be requested from the wallet.
- A possible defect in S8 was called an environment limitation, and nothing that scenario recorded names an environment cause, so it was audited as a candidate.
- A possible defect in S2 ("React hydration mismatch error on load") was not promoted: the live replay came back not-reproduced.
- Hand correction, 2026-09-27: F2 was re-classified as an environment limitation and withdrawn after confirming the app's own faucet link never provides the Testnet USDC the paywall requires, only SUI.
What to fix first
- Resolve the Bedrock agent integration failure causing 'Agent error' responses upon prompt dispatch (F1).
Coverage and caveats
In scope: Onboarding modal dismissal; Wallet connection and state persistence; Direct Control macro dispatch; Agent natural language command validation and dispatch; Telemetry drawer interactions; Instructions and Help views.
Not covered: Physical robotic arm verification (hardware actions are out of scope for browser testing); Mainnet transactions (environment is restricted to Sui Testnet); Other wallet providers (only the injected DeepQA Test Wallet is tested).
- The 'Open the Simulator' button successfully dismisses the onboarding modal, despite the explorer noting it remained open; the test relies on this dismissal to access the main UI.
- The injected DeepQA test wallet automatically handles transaction signing prompts without requiring explicit browser window switching.
- The 402 console error observed on load does not outright break the client application rendering.
By the numbers
| Metric | Value |
|---|
| Scenarios | 9 passed, 2 failed, 0 blocked of 11 (25 planned steps) |
| Browser actions | 161 (47 clicks, 9 inputs, 17 navigations, 88 snapshots) |
| Screenshots | 39 (4 explore, 32 scenario, 3 critic), 32 captioned |
| Coverage | 1 pages, 1 forms, 4 flows, 1 console errors |
| Audit | 1 findings, 3 re-verified live, 1 confirmed, 0 promoted, 1 withdrawn |
| Model calls | 151 |
| Tokens | 744,057 input, 7,771 output, 18,019 thinking |
| Time | 10 min |
| Wallet | 0 transactions, 0 signatures, 0 refusals on chain sui:testnet |
| Stage | Calls | Input | Output | Thinking | Seconds |
|---|
| explore | 19 | 95,224 | 1,539 | 1,297 | 63 |
| plan | 1 | 3,741 | 1,684 | 3,395 | 37 |
| test | 113 | 589,965 | 3,339 | 6,321 | 372 |
| critique | 17 | 53,439 | 950 | 6,523 | 102 |
| report | 1 | 1,688 | 259 | 483 | 7 |
