[prabowosd]

Adds agents (https://github.com/prabowosd/lerd-agents at e068573573bcd36efb00b0e13651ae2c252fc2bb), a plugin that shows the coding agents herdr and Orca run in each site and its worktrees, and opens any checkout in either tool. It works with whichever of the two is running and skips the other.

1. Adds a site tab and Overview card "Agents", site commands "Open in herdr" and "Open in Orca", commands agents:status and agents:watch, hooks on worktree.added and worktree.removed, an MCP tool agents_status with a skill, and two endpoints: status (GET) and open (POST, loopback_only, the folder checked against the site's own checkouts).
2. Reads Lerd's /api/sites, git worktree list in the site's folder, and the JSON output of the local herdr and orca commands. No .env, keys or secrets.
3. Changes only herdr workspaces and Orca terminals it is asked to open, the site's repository in Orca (added when missing, set to show worktrees Orca did not create), and herdr-workspaces.json in its data folder. The worktree.removed hook closes only a workspace the hook created, never one with a working or blocked agent. Lerd itself is never changed.
4. Sends nothing over the network. Notifications are declared and sent only by agents:watch, when an agent finishes or waits for input.
5. Needs git and Node, lerd: ">=1.38", Linux and macOS. herdr and Orca are optional, so they are not under requires.
6. The catalog has no fitting category yet, so the entry proposes AI; happy to change it.

• The repository is public and has an open source license.
• The README says what the plugin adds, reads, changes and sends.
• plugin.yaml declares lerd as a lower bound, and platforms if it runs on only one.
• Everything it runs is readable source in the commit, in shell, Python, Node or similar but not PHP: no binaries, no minified code without its source, nothing downloaded and run.
• It asks for no privilege and writes only to its own folder, its data folder and the sites it is run against, changing Lerd only through its API.
• It reads no secrets it has no stated need for, and a site's .env only when the README says why.
• Lerd's token never leaves the machine and is never written outside the plugin's data folder.
• Hooks finish quickly and fail without leaving a site, service or database half changed.
• Nothing leaves the machine without an opt-in the user turns on, and there are no analytics, tracking, ads or mining.
• Any notifications are declared in plugin.yaml and only tell the user something they need to know or act on.
• Pages bundle their own assets, nothing loads from third-party servers, and page scripts talk only to the plugin's own endpoints.
• No services, so no images to pin.
• No services or frameworks, so no name clashes.
• The name, description and images describe what it actually does.
• The images show the plugin itself, are mine to publish, and are at most 6, each a PNG, JPEG or WebP under 1 MB and at most 2560 px wide.