Rename the package to Browser Loop

[rgarcia]

Summary

Prepare the project for the new Browser Loop name before the first npm publish and GitHub repository rename:

• rename the publishable package from @onkernel/loop to @onkernel/browser-loop and its workspace directory to packages/browser-loop
• prepare package metadata for kernel/browser-loop (repository, homepage, issues), rename the private root workspace to browser-loop, and update the lockfile/project references
• update README imports/install commands and product prose to Browser Loop; preserve the public loop namespace, Loop* TypeScript symbols, and kloop.*.v1 tool identities
• rename the release workflow to release-browser-loop.yml, tags to browser-loop/v*, tarball smokes to onkernel-browser-loop-*.tgz, and all CI workspace targets
• update the release/docs skills and first-publish runbook for the exact tested tarball, kernel/browser-loop, and the new trusted-publisher tuple

The historical @onkernel/cua-* names remain unchanged in the changelog.

Verification

• npm install
• npm run typecheck
• npm run build --workspace @onkernel/browser-loop
• npm test --workspace @onkernel/browser-loop — 34 files, 429 tests
• packed onkernel-browser-loop-0.11.0.tgz, installed it in a clean project, and imported both @onkernel/browser-loop and @onkernel/browser-loop/pi

---

Note

Medium Risk
Wide rename across lockfile, workflows, and every import alias risks a missed @onkernel/loop reference or broken release tag/workflow pairing until the repo rename and first npm publish are completed.

Overview
Rebrands the project from Loop / @onkernel/loop to Browser Loop and @onkernel/browser-loop, aligning the workspace directory (packages/browser-loop), root package name (browser-loop), and planned GitHub repo (kernel/browser-loop) before the first npm publish.

Consumer-facing API stays stable: the loop namespace, Loop* TypeScript types, and kloop.*.v1 tool identities are unchanged; only npm package names, install/import paths (@onkernel/browser-loop, @onkernel/browser-loop/pi), and user-facing prose move to Browser Loop. The tool spec kind string updates to @onkernel/browser-loop-tool-spec/v1.

Release and CI switch to release-browser-loop.yml, tags browser-loop/v*, tarball onkernel-browser-loop-*.tgz, and workspace-scoped npm commands across CI and agent skills. Docs and runbooks (docs/npm-releases.md, release/update-docs skills) describe manual first publish, trusted publishing for the new repo/workflow pair, and avoiding republishing 0.11.0 after a manual release.

Internal pi-extension and test aliases, tsconfig paths, and vitest resolves now point at @onkernel/browser-loop so jiti-loaded extension code matches the published package name.

^{Reviewed by Cursor Bugbot for commit f72a0f2. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

Bugbot Autofix prepared a fix for the issue found in the latest run.

• ✅ Fixed: Stale screenshot path after rename
  • Updated the fallback fixture lookup path in native-action-probe to packages/browser-loop/examples/screenshot.png so root-invoked probes find the screenshot after the rename.

Or push these changes by commenting:

@cursor push c82dce3134

Preview (c82dce3134)

diff --git a/packages/browser-loop/scripts/native-action-probe.ts b/packages/browser-loop/scripts/native-action-probe.ts
--- a/packages/browser-loop/scripts/native-action-probe.ts
+++ b/packages/browser-loop/scripts/native-action-probe.ts
@@ -246,7 +246,7 @@
 async function readFixtureScreenshot(): Promise<Buffer> {
 	const path = [
 		join(process.cwd(), "examples", "screenshot.png"),
-		join(process.cwd(), "packages", "loop", "examples", "screenshot.png"),
+		join(process.cwd(), "packages", "browser-loop", "examples", "screenshot.png"),
 	].find(existsSync);
 	if (!path) throw new Error("could not find packages/browser-loop/examples/screenshot.png");
 	return readFile(path);

_{You can send follow-ups to the cloud agent here.}

^{Reviewed by Cursor Bugbot for commit 7b1ecf3. Configure here.}