Implement Harness Registry and fresh session terminal booting

Context

Currently, the Auto-Wakeup Substrate (resumeHarness.mjs) relies on an unvalidated free-text appName inside harnessTargetMetadata, and hardcodes an identity map targeting only Antigravity via osascript. If an agent is sunsetted, the shell script should be capable of starting any agent app (Antigravity, Claude Desktop, Codex). Furthermore, waking an agent isn't just about bringing the app to the foreground; it requires booting a true fresh session by injecting a first prompt via the terminal.

The Problem

• Free-Text Vulnerability: harnessTargetMetadata.appName is free text, making it fragile across different OS configurations or naming conventions.
• Hardcoded Scope: resumeHarness.mjs only knows how to wake Antigravity.
• Missing Fresh Session Boot: The current wakeup substrate brings the window forward but doesn't explicitly start a fresh terminal session with a context-primed prompt for the other agent types.

The Architectural Reality

The wakeup substrate needs to evolve from a hardcoded map in ai/scripts/resumeHarness.mjs to a formal "Harness Registry". This registry must define how to start different agents (e.g., antigravity, claude-desktop, codex-desktop) using precise enums rather than free-text names, and execute the specific terminal commands or AppleScript sequences to deliver the initial payload.

The Fix

1. Define Harness Registry Enum: Standardize harness targets into an enum (e.g., antigravity-ide, claude-desktop, codex-desktop) replacing the free-text appName.
2. Update Schema & Memory Core: Enforce this enum in the Memory Core manage_wake_subscription tool parameter schema.
3. Refactor resumeHarness.mjs: Implement the Harness Registry logic to resolve the enum to specific executable paths/scripts.
4. Implement Fresh Session Booting: Extend the execution logic for each registry entry to not only open the app but also inject the initial payload via terminal commands to guarantee a fresh session.

Acceptance Criteria

• appName in harnessTargetMetadata is replaced by an enumerated appIdentifier.
• Memory Core schema is updated to validate the new enum.
• resumeHarness.mjs dynamically resolves execution strategies based on the registry.
• The recovery payload successfully triggers a fresh session with the provided prompt for at least two different agent targets.

Out of Scope

• Modifying the SQLite GraphLog schemas beyond the appName enum validation.
• Rewriting the core heartbeat timer logic in swarm-heartbeat.sh.

Origin Session ID

Origin Session ID: 68862ab8-619c-496e-8ba2-8a75ddd73059