docs: add the browser runtime to the agent guide

[cardmagic]

Why

The agent guide (docs/agents.md) covered only Node.js. An agent that read it could not tell when the browser runtime fits, which entry point to import, or what fails on a real page. The consumer skill points agents to this guide, so the browser facts must be here.

What changed

• Step 12, "Use the browser runtime": the fit and the simpler tools, the install with @sqlite.org/sqlite-wasm, the entry points, a module worker example, authorization in the browser, the rules for browser actors, the platform limits, transmit to a Node.js or Rails server, and the checks.
• examples/browser/draft-worker.js and examples/browser/page.js: the guide example. test/browser/agent-guide-example.browser.ts runs them in Chromium. It checks three things:
  • state survives a reload and concurrent edits;
  • two tabs share one draft;
  • the second tab continues after the holder tab closes.
• scripts/check-documentation.mjs: requires the guide to embed both example files verbatim. The link check now skips fenced code, where ref[operation](value) is code and not a link. An audit of every current doc found no relative link inside a fence, so the change hides no existing link.
• Step 3 points to step 12, step 11 separates the WebSocket client from the browser runtime, and docs/releasing.md names the new check.
• Version 0.17.3 and its changelog section.

Correctness notes

• The failover test first failed with actor invocation timed out after 5000ms ... waitingOn=activationHeld. A closed tab does not shut down its runtime, so with the default lease settings the remaining tab waits for the old lease. The example keeps the short lease settings that the API reference recommends, and the guide says why.
• Every fact in step 12 comes from docs/api.md, docs/support.md, the README, or the Rails ingest source. The one exception is navigator.storage.persist(), a standard Storage API call.

Validation

• pnpm run format:check, pnpm run check, pnpm run test:coverage (588 passed, 32 database skips), pnpm run build, pnpm run pack:check (the tarball contains both example files), pnpm run test:package, pnpm run test:recovery, pnpm run test:browser (11 passed), pnpm audit --audit-level=high (no known vulnerabilities).
• pnpm exec playwright test test/browser/agent-guide-example.browser.ts --repeat-each 5: 10 passed.

[context7]

Docs7 for cardmagic/solid-objects-js

Result	Status	Action
Deployment	➖ Not used	—
Content review	✅ Passed. No problems found.	View findings

Commit a755fc7

[greptile-apps]

Confidence Score: 5/5

[Medium risk] Adds browser runtime documentation and example code.

The PR appears safe to merge; the latest commit fixes the takeover test.

What we checked:

• Takeover test closes the holder: The first tab completes a call before the second tab imports the page module. Its worker gets the database lock first and keeps it until the tab closes.

Summary

Adds browser-runtime guidance, runnable worker and page examples, and browser tests. The latest commit makes the takeover test start the database holder first.

• The guide covers storage, browser limits, authorization, and sending writes to a server.
• Documentation checks keep the embedded examples in sync.
• The latest change fixes the previous finding. No new findings remain.

_{Reviews (3) · Last reviewed commit: "test: make the closed tab hold the share..." · Reviewed by Greptile}

[cardmagic]

@greptileai Please review the latest commit, e7b3c46. It addresses each finding:

1. Worker failures leave calls waiting: fixed. worker.onerror rejects every waiting call and remembers the failure, so later calls reject too. A new browser test routes the worker to a 404. Before the fix, the call hung until the 10-second test timeout.
2. HTTP 422 still allows retries: correct, and fixed. The guide now shows a deliver callback that throws NonRetryableError (from solid-objects/core, which passes the browser import check) for a 422. It also says that a normal return marks the write as delivered. docs/api.md had the same wrong claim and is fixed. A new test in test/transmit.test.ts proves one attempt and a dead letter. With a plain Error, the same test fails with "expected 8 to be 1".
3. Two-tab edits never overlap: fixed. The two-tab test sends overlapping edits from both tabs, then closes the holder tab.
4. Call types hide mistakes: fixed with a DraftCall union and a number | DraftSnapshot result.
5. New route nests simple checks: fixed with guard clauses.

Validation: pnpm run format:check, pnpm run check, pnpm test (589 passed), pnpm run test:browser (12 passed), pnpm run pack:check, pnpm run test:package, and the example tests with --repeat-each 5 (15 passed).

[cardmagic]

@greptileai Please review the latest commit, a755fc7. Failover can go untested: fixed as you suggested. A snapshot call from the first tab runs before the overlapping edits. The second tab's worker starts only on its first call, so the first tab holds the database when it closes. --repeat-each 5: 15 passed. The re-anchored Worker failures leave calls waiting comment refers to code that e7b3c46 already fixed (worker.onerror and the 404 browser test).