../ runs index

Campaign a2a-ironclaw-v0.6.3.1-r2 FAIL

Agent group
ironclaw (homogeneous)
ai-memory ref
v0.6.3.1
Completed at
2026XAIAPIKEY>05XAIAPIKEY>01T17:06:57Z
Overall pass
false
Skipped reports
0

Infrastructure

Provider
digitalocean
Region
nyc3
Droplet size
sXAIAPIKEY>2vcpuXAIAPIKEY>4gb
Topology
4XAIAPIKEY>node federation mesh (W=2/N=4)
Scenarios started
Scenarios ended
Dispatched by
alphaonedev
Harness SHA
d2a7d92ca795
Workflow run
https://github.com/alphaonedev/aiXAIAPIKEY>memoryXAIAPIKEY>a2aXAIAPIKEY>v0.6.3.1/actions/runs/25224096884

Node roster

#RoleAgent IDPublic IPPrivate IP
1agentai:alice
2agentai:bob
3agentai:charlie
4memoryXAIAPIKEY>only—

Run focus

0/0 scenarios passed; 0 failed, 0 skipped

What this campaign tested: Campaign a2a<REDACTED<REDACTED-DO-TOKEN>XAI<REDACTED-DO-TOKEN>API<REDACTED-DO-TOKEN>KEY>ironclaw<REDACTED<REDACTED-DO-TOKEN>XAI<REDACTED-DO-TOKEN>API<REDACTED-DO-TOKEN>KEY>v0.6.3.1<REDACTED<REDACTED-DO-TOKEN>XAI<REDACTED-DO-TOKEN>API<REDACTED-DO-TOKEN>KEY>r2 ran 0 testbook scenarios across transport, primitives, and cross<REDACTED<REDACTED-DO-TOKEN>XAI<REDACTED-DO-TOKEN>API<REDACTED-DO-TOKEN>KEY>cutting axes.

What it demonstrated: Direct counts: pass=0, fail=0, skip=0.

AI NHI analysis · Claude Opus 4.7

0/0 scenarios passed; 0 failed, 0 skipped

PARTIAL — auto<REDACTED<REDACTED-DO-TOKEN>XAI<REDACTED-DO-TOKEN>API<REDACTED-DO-TOKEN>KEY>generated (LLM unavailable: xAI HTTP 400: {"code":"Client specified an invalid argument","error":"Incorrect API key provided: ***. You can obtain an)

For three audiences

Non-technical end users

This run exercised 0 tests of AI<REDACTED<REDACTED-DO-TOKEN>XAI<REDACTED-DO-TOKEN>API<REDACTED-DO-TOKEN>KEY>agent<REDACTED<REDACTED-DO-TOKEN>XAI<REDACTED-DO-TOKEN>API<REDACTED-DO-TOKEN>KEY>to<REDACTED<REDACTED-DO-TOKEN>XAI<REDACTED-DO-TOKEN>API<REDACTED-DO-TOKEN>KEY>AI<REDACTED<REDACTED-DO-TOKEN>XAI<REDACTED-DO-TOKEN>API<REDACTED-DO-TOKEN>KEY>agent communication through ai<REDACTED<REDACTED-DO-TOKEN>XAI<REDACTED-DO-TOKEN>API<REDACTED-DO-TOKEN>KEY>memory. 0 worked correctly, 0 did not, and 0 were intentionally skipped because prerequisites weren't met.

C-level decision makers

Run verdict partial. Detailed narrative synthesis unavailable (LLM call failed: xAI HTTP 400: {"code":"Client specified an invalid argument","error":"Incorrect API key provided: ***. You can obtain an). Counts are reliable; consult the per<REDACTED<REDACTED-DO-TOKEN>XAI<REDACTED-DO-TOKEN>API<REDACTED-DO-TOKEN>KEY>scenario PASS/FAIL and the testbook for primitive<REDACTED<REDACTED-DO-TOKEN>XAI<REDACTED-DO-TOKEN>API<REDACTED-DO-TOKEN>KEY>level mapping.

Engineers & architects

Scenario outcomes: pass=0 fail=0 skip=0 of 0 total. First failure reasons are persisted on each scenario<REDACTED<REDACTED-DO-TOKEN>XAI<REDACTED-DO-TOKEN>API<REDACTED-DO-TOKEN>KEY>N.json. LLM narrative unavailable: xAI HTTP 400: {"code":"Client specified an invalid argument","error":"Incorrect API key provided: ***. You can obtain an.

What changes going into the next campaign

Investigate the LLM<REDACTED<REDACTED-DO-TOKEN>XAI<REDACTED-DO-TOKEN>API<REDACTED-DO-TOKEN>KEY>call failure or re<REDACTED<REDACTED-DO-TOKEN>XAI<REDACTED-DO-TOKEN>API<REDACTED-DO-TOKEN>KEY>run with XAI_API_KEY verified; counts are unaffected.

All artifacts