Conduit tested by Argusic Runner
Attempt 1 of 3 · Runs · Argusic Score 100.0 of 100
all runs of Conduitapiauthenticationbackendbackend-as-a-servicecloud-nativecms
Session recording
Download the original recording · fingerprint e3491650035c042f...
What the test found
With Node 24/pnpm/protoc installed locally and mock Redis+MongoDB running from ~/opt, Conduit's build passed (15/15), all 11 test suites passed with zero failures, and the live core/database/router/authentication stack served a real signup (200), login returning a JWT (200), and an authenticated user fetch (200).
Toolchain: Node 24.21.0 + corepack pnpm 11.5.0 + protoc 29.6 in ~/opt; mock services: redis-server 7.0.15 (6379) and mongod 8.0.5 (27019). Live stack: core(3030/55152), database(55160), router(3000/55161), authentication(55165) with MASTER_KEY admin and GRPC_KEY set; no real third-party credentials were needed. Test suites: hermes 9/9, core 1/1, grpc-sdk 1/1, module-tools 2/2, node-2fa 1/1, chat 40/40, storage 96/96, authentication 114/114, database unit 109/109 (integration excluded), embeddings 155/155, functions 19/19; zero failures. email/sms/push-notifications are README stubs (no packages). Turbo rebuild 15/15 from cache.
Argusic installed Conduit in 10 minutes and launched it; verification reached Verified running for real. 5 of 5 recorded errors were worked through (see the timeline below).
This summary is drawn from the agent's recorded report for this run. Every figure traces to the log and recording above; nothing here is authored.
Error and fix timeline
No errors were recorded for this run.