Same component always gets the same rkey, so re-publishing updates
the existing record instead of creating duplicates.

👾 Generated with [Letta Code](https://letta.com)

Co-Authored-By: Letta Code <noreply@letta.com>

- Extract shared carry query, URL normalization, and component logic into island-shared.ts
- island:detect: simplified, uses shared utils
- island:discover: improved component reporting
- island:explore: enhanced carry-backed scoring
- Add island:publish stub

👾 Generated with [Letta Code](https://letta.com)

Co-Authored-By: Letta Code <noreply@letta.com>

Runs carry-backed analysis on connected components found by island:discover:
- Matches carry connections against island URLs to find bridge edges
- Extracts themes from island text corpus
- Flags hot edges connected to carry touchpoints
- Finds tensions from carry citations
- Generates synthesis and open questions
- Writes results to SQLite (not PDS — use island:publish for that)

Usage: bun island:analyze 1 | bun island:analyze --all

👾 Generated with [Letta Code](https://letta.com)

Co-Authored-By: Letta Code <noreply@letta.com>

Lexicon namespace, source files, and generated types all updated.
Fixed hyphenated def IDs (web-search → webSearch, etc.) and
invalid schema types (json → unknown, inline object → ref).

👾 Generated with [Letta Code](https://letta.com)

Co-Authored-By: Letta Code <noreply@letta.com>

- island:discover: BFS to find connected components in global network.cosmik.connection graph, caches in SQLite
- island:detect: match our carry graph against discovered components to find closest island
- island:explore: find fringe nodes and suggest bridge edges back into island
- connection:detect: compare our carry graph against individual DIDs' connection records
- vault:analyze: parse Obsidian vault notes into carry data via letta-code-sdk agent

Dependencies: @atproto/api, @letta-ai/letta-code-sdk, jsdom

👾 Generated with [Letta Code](https://letta.com)

Co-Authored-By: Letta Code <noreply@letta.com>