Cloudflare adapter returns 404 for Wrangler Container application endpoints

[realmroot]

Problem

Realmroot Cloudflare native command proxy returns HTTP 404 for the Container endpoint used by Wrangler 4.95.0. This makes wrangler containers list fail and causes a Worker deploy with [[containers]] to upload successfully but exit non-zero during the final Container application reconciliation.

Reproduction

realmroot exec cloudflare -- pnpm wrangler containers list

Wrangler debug output:

GET /client/v4/accounts/<account-id>/containers/dash/applications
HTTP 404 Not Found
There has been an error listing containers.

The authorized Realmroot Cloudflare Resource has both containers.read and containers.write. Toolbox discovery currently advertises /accounts/{account_id}/containers/applications/..., but not Wrangler’s /accounts/{account_id}/containers/dash/applications route.

Impact

• wrangler containers list cannot be used through the Agent identity.
• wrangler deploy --env staging for AMA uploads the Worker successfully, then exits 1 while reconciling the unchanged Container application.
• Automation cannot reliably distinguish a successful deployment from a failed one.

Expected behavior

The adapter should proxy the Container dashboard endpoints used by supported Wrangler versions, including listing and reconciling Container applications, under the existing containers.read / containers.write scopes.

Environment

• Wrangler: 4.95.0
• Realmroot Cloudflare native command: pnpm wrangler
• Observed: 2026-08-29

---

_{🤖 Created by Jarvis via Realmroot}

[realmroot]

Additional verification: upgrading Wrangler does not resolve this. Wrangler 4.127.1 still requests GET /client/v4/accounts/<account-id>/containers/dash/applications and receives the same adapter 404. This confirms the missing adapter route is not specific to AMA’s pinned Wrangler 4.95.0.

---

_{🤖 Created by Jarvis via Realmroot}

[realmroot]

PR #35 is merged at 700449b34417d1939bc097b7062fc01925f81d93, but the production adapter has not been deployed yet. A live verification after merge still fails:

• command: realmroot exec cloudflare -- pnpm wrangler containers list
• request path: /accounts/{account_id}/containers/dash/applications
• production result: HTTP 404 / Wrangler exits 1

Keep this issue open until adapters.realmroot.dev is deployed and both Container listing and the AMA staging Worker deployment complete successfully through the adapter.

---

_{🤖 Created by Jarvis via Realmroot}

[realmroot]

Verified the deployed Cloudflare adapter end to end on 2026-08-30: realmroot exec cloudflare -- wrangler containers list succeeds and lists both production and staging AMA container applications as ready. AMA staging was then built with CLOUDFLARE_ENV=staging vite build through the Cloudflare Vite plugin and deployed successfully as version b1384083-a73f-43be-a1cc-16bedfddaa44; /api/healthz and /api/readyz both return ok. Closing the adapter deployment issue.

---

_{🤖 Created by Jarvis via Realmroot}