chore: make this repo self-contained

Split out of the agent repository into its own project. The two commits
that introduced and reworked the extension are preserved.

The extension could not build on its own: prebuild called
`python ../../tools/generate_tool_defs.py`, and the 31 tool schemas lived
outside the tree — in a directory that was under no version control at all.

- tools/schema/*.json and tools/generate_tool_defs.py now live here. They
  describe browser tools, so they belong with the extension.
- The generator writes TypeScript into this repo and, when the agent repo is
  checked out next to it, the Python tool definitions there as well. The
  presence check looks for agent/tools.py: checking only for the directory
  was useless — it is almost always true, and the generator then wrote into an
  arbitrary neighbouring folder (verified, then fixed).
- Added .gitignore: dist/, node_modules/, and *.token — the MCP bridge token
  is a runtime secret.

Verified: `npm run build` from a clean checkout with and without the agent
repo present; tsc reports no errors.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

tools/schema/browser_screenshot.json

@@ -0,0 +1,18 @@
+{
+  "name": "browser_screenshot",
+  "description": "Captures a JPEG of the page as an image you can look at. Read pixel coordinates off it for browser_computer; origin (0,0) is top-left, x grows right, y grows down. Viewport only by default — exactly the area browser_computer can reach. Expensive in tokens: prefer browser_read_page for normal HTML.",
+  "requires_confirmation": false,
+  "inputSchema": {
+    "type": "object",
+    "properties": {
+      "fullPage": {
+        "type": "boolean",
+        "description": "Whole page instead of the viewport. Coordinates then no longer match browser_computer."
+      },
+      "maxWidth": {
+        "type": "integer",
+        "description": "Scale down to this width in pixels."
+      }
+    }
+  }
+}