Retrospective UTC work date 2026-11-10; prepared 2026-11-12 by Codex from retained engineering receipts and separately labelled dated reports. First published 2026-11-12. Source review does not establish current runtime health or owner editorial approval of each claim.
The standalone harness began with an isolated, read-only test connection to an actual historical ABL receipt. The loopback-only gateway refused public access and writes, preserved the original observation timestamps, and displayed current workers as unknown. Reusing a real receipt made the first view meaningful without pretending that old evidence was a live feed. This did not establish production login or a live worker connection.
Task, control and result handling was then joined to the owner backend. The local Workers runtime exercised durable queue state through a restart; repeating the same task key stayed stable without creating another queue item. Those tests used a synthetic owner identity and did not establish a real login or worker job.
The hosted upload succeeded even though the command later failed while looking up a subdomain. Provider readback confirmed the new version and full traffic allocation, so the code was not uploaded again blindly. That receipt still left routing and runtime identity unverified. A later same-day progress report recorded reaching protected sign-in, but application-session acceptance was still incomplete.
The new endpoint was therefore a hosted foundation, not a completed control center. The older Hub's bridge and capture problems were separate work and were not resolved by creating the standalone application.
What did not ship
No accepted end-to-end owner application session at this checkpoint, live worker dispatch, continuously current worker state, public chatbot or completed Hermes Desktop integration was established.
Next
Complete one authenticated owner session, save and reopen a task through the hosted store, then connect a bounded real worker without replaying an uncertain attempt.
Raw telemetry
- Local Cloudflare runtime: 11 checks, including restart persistence, stable same-key retries and no duplicate queue item.
- Hosted upload confirmed by provider readback; its CLI lookup error did not mean the upload failed. Routing and runtime identity were still unverified in that receipt.