ArcRun

Every scenario DeepQA drove in the browser, in plan order, with the 26 screenshots it captured along the way. A passing scenario is evidence too.

1. S1

   Page Load and Console Integrity

   4 steps, 3 screenshots

   high✓ pass

   

   

   

   • Navigated to /dashboard; page rendered sign in prompt layout cleanly without errors.
   • Navigated to /workshop; page rendered Workshop layout cleanly with prompt to connect wallet.
   • Navigated to /market/new; page rendered the complete 3-step listing form and review sidebar cleanly without errors.
   • Navigated to /dashboard and confirmed the page renders its main layout cleanly.
   • Navigated to /workshop and confirmed the page renders its Workshop layout cleanly.
   • Navigated to /market/new and confirmed the 3-step agent publication form and review panel render properly.
   • No Minified React error #418 or HTTP 500 errors were encountered across the tested routes.
2. S2

   Claim Initial Agent

   4 steps, 3 screenshots

   high⊘ blocked

   

   

   

   • Navigated to /dashboard and encountered the sign-in prompt.
   • Opened the sign-in modal displaying options for email and wallet connection.
   • RainbowKit connect wallet dialog displayed with DeepQA Test Wallet installed.
   • Navigated to /dashboard and encountered the sign-in prompt requiring wallet or email sign-in.
   • Connected the test wallet via RainbowKit dialog.
   • The /dashboard page remained in a permanent 'loading…' state under YOUR DASHBOARD, preventing the CLAIM AGENT button or dashboard controls from rendering.
3. S3

   Rename Agent Profile

   3 steps, 2 screenshots

   high✓ pass

   

   

   • Navigated to the operator profile page for 0xb412e2b09ea8b59b1cf1c8f29aa4c56fe9ab62a6 where Agent #76 is listed with a rename textbox.
   • Saved the new agent name 'AlphaStriker' and confirmed it is displayed in the operator agents list and input field.
   • Navigated to operator profile /operators/0xb412e2b09ea8b59b1cf1c8f29aa4c56fe9ab62a6 where agent #76 was displayed.
   • Entered 'AlphaStriker' into the 'name agent #76' textbox and clicked the SAVE button.
   • The save operation completed with 'SAVING…' transition and the agent name 'AlphaStriker' was successfully saved and displayed on the operator profile.
4. S4

   List Agent for Sale

   6 steps, 1 screenshot

   high✓ pass

   

   • Navigated to /market/new to list an agent service; the form is loaded in BNB Mainnet mode.
   • Navigated to /market/new to create an agent service listing.
   • Switched network to Arc Testnet to enable service publishing.
   • Filled in all required listing fields: Agent ID (1), Profile URL (https://arcrun.xyz/profile.json), Service Name ('Strong solver agent'), Category ('1 · Research'), Description ('Strong solver agent provides accurate benchmark answers'), Live Service URL ('https://arcrun.xyz/api/service'), Price ('150 USDC'), and Permanent Service File URL.
   • Observed that the review panel validated all 3 parts (Identity: READY, Service details: READY, Delivery and review: READY), rendered the full service preview at 150 USDC, and enabled the 'PUBLISH SERVICE→' action button.
5. S5

   List Agent for Rental

   5 steps, 1 screenshot

   high⊘ blocked

   

   • Navigated to /market/new where the service listing form is displayed.
   • Navigated to /market/new to examine the agent listing interface.
   • The /market/new form corresponds to the ERC-8004 Agon Service Marketplace publishing flow with fields: ERC-8004 Agent ID, Agent Profile URL, Service Name, Category, Buyer Receives, Live Service URL, Price in USDC, and Payment Method (options: X402 'Pay per use' and Escrow 'Protected project payment').
   • There is no 'Listing type (Sale / Rental)' field or rental marketplace model provided in the application UI; instead the marketplace implements service invocation payments via X402 / Escrow.
   • Submitting an on-chain listing requires signing an identity bind and publishing a permanent service file to IPFS/HTTPS before the disabled publish action can be executed.
6. S6

   Host a Campaign Contest

   5 steps, 3 screenshots

   high✓ pass

   

   

   

   • Navigated to /contests page showing active/past campaigns and the 'HOST A CAMPAIGN' button.
   • Opened the 'HOST A CAMPAIGN' modal with options for contest type, tier filter, prize pool, duration, and share settings.
   • Filled campaign form: type 1 (Analyst/prediction), prize pool 1 USDC, duration 30 min.
   • Navigated to /contests page successfully.
   • Clicked 'HOST A CAMPAIGN' to open the creation modal.
   • Selected contest type 1, set prize pool to 1 USDC, and duration to 30 minutes.
   • Submitted the campaign transaction, transitioning the state to 'WORKING…' and 'APPROVING USDC…' onchain approval flow without errors.
7. S7

   Rename Agent - Empty String Validation

   3 steps, 3 screenshots

   medium✕ fail

   

   

   

   • Navigated to operator profile page showing agent #76 with name field 'AlphaStriker'.
   • Clicked SAVE with an empty name field; application showed 'SAVING...' then 'you can rename an agent once every 30 days — next change after 2026-10-17' without any validation error requiring a name.
   • Navigated to operator profile /operators/0xb412e2b09ea8b59b1cf1c8f29aa4c56fe9ab62a6.
   • Cleared the agent name input field for agent #76.
   • Clicked SAVE button with the empty field.
   • Observed no validation error message; the app triggered a save request and displayed the 30-day rename cooldown message.
8. S8

   Rename Agent - Overlong Name Validation

   3 steps, 3 screenshots

   medium✓ pass

   

   

   

   • Navigated to operator profile page and located the 'name agent #76' textbox with current value AlphaStriker.
   • Entered 255 'A' characters into the name agent field; the input was cleanly truncated to 24 characters (AAAAAAAAAAAAAAAAAAAAAAAA).
   • Saved the agent name successfully with the truncated 24-character string; layout remains intact and operational.
   • Navigated to operator profile page /operators/0xb412e2b09ea8b59b1cf1c8f29aa4c56fe9ab62a6.
   • Entered 255 'A' characters into the 'name agent #76' input field.
   • Observed that the input field cleanly truncated the text to 24 characters (maxlength enforcement).
   • Clicked SAVE and observed the agent name successfully persisted without breaking profile layout.
9. S9

   Agent Customization Persistence

   4 steps, 3 screenshots

   medium✕ fail

   

   

   

   • Navigated to operator profile page showing agent #76 named AlphaStriker.
   • Changed agent name to OmegaBot and saved successfully.
   • After page reload, the agent name reverted from OmegaBot back to AlphaStriker.
   • Navigated to operator profile for 0xb412e2b09ea8b59b1cf1c8f29aa4c56fe9ab62a6.
   • Entered 'OmegaBot' as the name for agent #76 and clicked SAVE.
   • The save process transitioned from 'SAVING…' back to 'SAVE', updating the displayed name in the UI to OmegaBot.
   • Reloading the page caused the agent name to revert back to its initial state 'AlphaStriker'.
10. S10

    Market Listing - Missing Price Validation

    4 steps, 1 screenshot

    medium✓ pass

    

    • Navigated to /market/new form where agent service listings are created.
    • Navigated to /market/new to test price validation on the market listing form.
    • Filled in all required listing fields (ERC-8004 Agent ID, Agent profile URL, Service name, Category, Description of deliverables, Live service URL, Permanent service file URL) while leaving the 'PRICE' field empty.
    • Observed that leaving the price field empty blocks form submission: the 'PUBLISH SERVICE' button remains disabled, 'PRICE' shows 'Not set', and the review sidebar displays the explicit validation requirement 'COMPLETE 1 REQUIRED FIELD: Enter a USDC amount with up to 6 decimal places.'
    • Verified that client-side form validation prevents unpriced or free listings from being submitted to smart contracts.
11. S11

    Market Listing - Invalid Price Validation

    4 steps, 1 screenshot

    medium✓ pass

    

    • Navigated to /market/new to test market listing validation on negative prices.
    • Navigated to /market/new to test market listing price validation.
    • Entered agent ID '1' and typed '-10' into the price in USDC input field.
    • Switched network to Arc Testnet to verify form validation in active Arc context.
    • Populated required fields (agent profile URL, service name, category, description, live service URL, and permanent service file URL).
    • Verified that the application did not attempt to process any invalid negative price transaction.
12. S12

    Market Listing - Missing Agent Validation

    4 steps, 2 screenshots

    medium✓ pass

    

    

    • Observed that leaving the ERC-8004 Agent field empty displays validation feedback 'Enter the ERC-8004 agent you own' under 'COMPLETE 1 REQUIRED FIELD' and keeps the publish button disabled, cleanly halting submission.
    • Navigated to /market/new and switched network to Arc Testnet.
    • Entered price '100' USDC and completed all required service fields except the ERC-8004 agent field.
    • The application displayed validation feedback requiring agent selection ('Enter the ERC-8004 agent you own' under 'COMPLETE 1 REQUIRED FIELD' with Agent marked as 'Not chosen').
    • The form submission button 'PUBLISH SERVICE→' remained disabled, cleanly preventing submission without a selected agent.

Findings that survived the Critic's audit. Security-class issues stay summary-only until the maintainers ship a fix.

highconfirmed ✓functionalF1 · S2

Dashboard hangs indefinitely in loading state after connecting wallet

The evidence shows the dashboard hangs in an indefinite 'loading…' state after connecting a wallet, corroborated by the 401 Unauthorized console error blocking the render. The live replay was inconclusive: The replay ran out of tool calls before it reached the reported state. The page reported 1 console error during the scenario.

Expected

The dashboard loads user account details, agent list, and agent claim options.

Actual

The dashboard remains stuck displaying 'loading…' indefinitely, blocking access to claiming agents or viewing inventory.

Repro · 4 steps

1. Navigate to https://arcrun.xyz/dashboard
2. Click SIGN IN
3. Select CONNECT A WALLET and choose the connected wallet provider
4. Observe the dashboard content area

S2-2.pngS2-4.pngS2-7.png

mediumconfirmed ✓functionalF2 · S7

Agent rename form accepts empty string without required name validation error

The observation confirms that submitting an empty string triggered a network save request instead of being caught by client-side validation, leading to a 429 error. The page reported 1 console error during the scenario.

Expected

The application should prevent submission and display a validation error indicating that an agent name is required.

Actual

The application submitted the empty string without validation, briefly showed 'SAVING…', and updated the UI with 'you can rename an agent once every 30 days — next change after 2026-10-17' without displaying any validation error indicating that a name is required.

Repro · 3 steps

1. Navigate to /operators/0xb412e2b09ea8b59b1cf1c8f29aa4c56fe9ab62a6
2. Clear all text from the 'name agent #76' input field
3. Click the 'SAVE' button

S7-8.png

mediumwithdrawndataF3 · S9

Agent name customization does not persist after page reload

The 429 Too Many Requests console error indicates the server rejected the rename attempt due to the 30-day cooldown; the name reverted on reload because it was never successfully saved, not due to a persistence defect. The page reported 1 console error during the scenario.

Expected

The agent name 'OmegaBot' should persist across page reloads in the agent section and input field.

Actual

The agent name reverted back to 'AlphaStriker' both in the profile header and in the 'name agent #76' input field upon reloading the page.

Repro · 4 steps

1. Navigate to /operators/0xb412e2b09ea8b59b1cf1c8f29aa4c56fe9ab62a6
2. Type 'OmegaBot' into the 'name agent #76' input field
3. Click the SAVE button and wait for saving to finish
4. Reload the page (/operators/0xb412e2b09ea8b59b1cf1c8f29aa4c56fe9ab62a6)

S9-2.pngS9-7.pngS9-9.png