Add @kody/rcon_agent + @kody/rcon_sdk_factory_agent

[kody-w]

Summary

Two new cartridges for the rCon platform — a locked agentic console built on top of the brainstem.py kernel (see kody-w/openrapp-desktop). Both ship under @kody/.

Cartridges

@kody/rcon_agent (rcon_agent.py, 275 KB)

The consolidated rCon expansion-pack. One file = one rapplication. Drop into a brainstem's agents/ and the locked console lights up with the full rCon experience; drop it out and the brainstem returns to the bare kernel set. Nine BasicAgent subclasses in one module:

• TwinAgent — local digital-twin lifecycle (boot / stop / list / inspect / soul updates / lay-egg / hatch / chat)
• HatchTwinEggAgent — hatch .egg cartridges into running twins from files, URLs, or GitHub repos
• FleetAgent — discover & manage Mac-mini peers over SSH; execute commands, read/write files, list ports/processes on remote machines
• NeighborhoodSnapshotAgent — snapshot the entire neighborhood (brainstem + all twins + peers) into one .egg
• NeighborhoodRunAgent — restore a neighborhood snapshot, full or partial, local or simulated
• SelfHealingCronAgent — cron-based health checks with auto-retry / repair / alerts
• LearnNewAgent — generate new agent.py files from natural-language descriptions
• RARRemoteAgent (@kody/rar_remote_agent v1.7.2) — the native RAR client (discover / search / install / vote / review / submit)
• (plus TwinIdentity helper class)

@kody/rcon_sdk_factory_agent (rcon_sdk_factory_agent.py)

The meta-cartridge that generates new rCon rapplications from a natural-language spec. Knows the rCon platform contract:

• Skin claims (TwinExpansion / iMessageSkin / ConsoleSkin_* naming → desktop client lights up its matching renderer)
• Side-loop hooks (CONSTITUTION §2.3 — headless brainstem-driven execution)
• .egg lifecycle declarations in __manifest__.requires_eggs
• Mom Test compliance (the cartridge must be drivable purely through chat)

Actions: spec → scaffold → validate → package_egg → submission.

Why two cartridges, not one

rcon_agent.py is the runtime — the user's installation surface. rcon_sdk_factory_agent.py is the authoring tool — the way new rapplications get written. Both ship under @kody/ so the rCon SDK story is self-contained inside the registry.

Test plan

• Drop rcon_agent.py into a fresh brainstem's agents/; verify /agents lists all 8 agents.
• Ask the brainstem to "hatch the grandma-rose egg from the public hub" — should drive HatchTwinEggAgent → twin appears.
• Drop rcon_sdk_factory_agent.py in alongside; ask the brainstem to "build me a weather cartridge for rCon" — should drive RConSDKFactoryAgent.scaffold → new .py lands in agents/.
• Drop rcon_agent.py back out; verify the brainstem returns to its kernel set with no agent-side errors.

🤖 Generated with Claude Code