05183ea2 · zzmq.dev@gmail.com/zz
Commit
05183ea2d2122a719a0bd2960d847c891280f335
Backend step 2: real Worker + Artifacts round trip, proven live Step 2 of site/content/remote-backend/index.md's build sequencing: stand up a Worker against the real Cloudflare account, with just enough implemented to clone a real repo into Artifacts and read it back -- proving the git side before the Lane/Ask side. Verified live, as a real deployed Worker (not a local simulation): created a real Artifacts repo via the native env.ARTIFACTS binding, wrote git objects (blob/tree/commit) via isomorphic-git against a from-scratch in-memory fs (app/worker/src/memFs.ts -- Workers have no node:fs at all), pushed over the real git smart-HTTP protocol, then read the exact same content back via the native binding's readCommit/readTree/readBlob -- no isomorphic-git, no clone needed for reads at all. This resolved every open question the doc had flagged: Artifacts access needed a Workers Paid plan (now active, confirmed working immediately, no propagation delay); isomorphic-git's push path, only proven locally before, now proven against Artifacts' real smart-HTTP endpoint, from inside real workerd; and the native binding's actual response shapes (commit.treeHash not commit.tree, tree entries as {name, hash} not {path, oid}, readBlob returning a web Blob needing .text()/.arrayBuffer()) are now all confirmed against the real API, not assumed from the docs' abbreviated examples. Also discovered and worked around: wrangler auto-loads app/.env from the exact cwd it's invoked in, which silently overrides OAuth credentials with the narrowly-scoped CLOUDFLARE_API_TOKEN set there for the Workers AI LLM backend (agent/cloudflareBackend.ts) -- that token lacks the account/workers/artifacts scopes wrangler itself needs. Running wrangler from app/worker/ (no local .env) avoids this entirely; .env itself is untouched. Next: Lane/Ask/Answer storage on the Worker/DO's own storage (step 3), then the tool-surface HTTP routes and a real CloudflareBackend implementing engine/backend.ts's interface (step 4).
Troy Howard <thoward37@gmail.com> -- 2026-10-11T10:44:26.000Z