L4 0.2.11

Owner setup can recover after losing the original tab. Task execution has an explicit start, and reports identify the work they belong to.

• The Cloudflare installer can recover an owner setup link after its original tab or installer session was lost. Reconnect Cloudflare and choose Finish setup on your Server or Recover setup link. The installer verifies the authorized account and exact Worker origin, then atomically renews only a pending D1 claim while the Server has no Owner or login Accounts. It cannot reset an existing Owner. Replacement links stay in the encrypted installer session, outside Shell bookmarks and localStorage.
• Owner setup keeps its claim through a tab reload. Successful owner creation displays Signing you in while the session refreshes, avoiding a misleading missing-claim warning after the claim has been consumed.
• Assigning an Agent remains organizational and does not queue a Run. Tasks explain the manual start; Create and run creates an assigned Task and starts it through the same authorized admission path as Run assigned agent. Creating a Task alone still leaves it ready for a later explicit start.
• Conversation reports include the Task number, title, current status and a link to its board/detail, with the result below. Report retries reuse the saved computation and remain authorized. The separately reported Discussion Loading problem was not reproduced in Docker/Chrome for fresh or existing Tasks and remains open in #243.

Validation includes 927 tests, setup claim recovery through a real SQLite/HTTP fixture, denial for wrong accounts/origins/expired grants and owned Servers, UI handoff and explicit-start tests, type/lint/migration checks, Docker local-stack and self-host restore, and Git-built Web/Server Previews. Chrome on the native Server Preview verified owner setup after reload and successful login. A real customer Cloudflare OAuth claim recovery and live external inference remain separate acceptance gaps.

There are no new schema migrations. The official web, Shell, installer, standalone Server, portable amd64 runtime and version-pinned Docs share version 0.2.11. Customer Servers remain pinned until their operators complete the backup/update flow. Native iOS/macOS publication remains frozen.