Add Jules connector (fire-and-forget coding task delegation)

[allocsys]

What

Adds a new connector for Jules — Google's async, autonomous coding agent — following the same client.js + tools.js pattern as the Context7 connector.

Why

Fills a real gap: delegate_agent is synchronous and read-only, delegate_designer is write-capable but fenced to frontend files only. Neither can autonomously write arbitrary code across a whole repo unsupervised. Jules can — you hand it a task, it works in its own sandboxed VM, and (by default here) opens a PR when done. Intended usage is fire-and-forget: kick off a task, check back later.

Tools added

• jules_list_sources — connected GitHub repos
• jules_create_session — start a task; defaults to automation_mode: AUTO_CREATE_PR with plans auto-approved (no gating step), matching the fire-and-forget use case
• jules_list_sessions / jules_get_session — check status, retrieve output PR URLs
• jules_get_activities — full event timeline for a session

Deliberately left out jules_approve_plan / jules_send_message for this first pass — those are for a supervised, gated workflow, which isn't the target use case right now. Easy follow-up if that's ever needed.

Other changes

• config.js — JULES_API_KEY / JULES_API (no unauthenticated tier, unlike Context7)
• server.js — registered, added to / configured-connectors report and startup warnings
• README.md — new Jules section under Connectors & tools, config table entry, badges
• docs/API_KEYS.md — key creation link
• test/jules-client.test.js — unit tests for the client (auth header, query params, error handling) and the three most load-bearing tools

Notes

• Jules's REST API is alpha (Google's own designation) — endpoint shapes may change without notice.
• JULES_API_KEY is optional at the server level, same as every other connector token — missing it just makes jules_* tools fail at call time, not at startup.