Remove manual wake subscription sequence from agent startup

Context The A2A Wake Substrate stability checks have introduced an auto-subscription mechanism for the bridge daemon using SQL idempotency checks within the Memory Core.

The Problem Current startup documentation or scripts might still instruct developers/agents to manually subscribe to wake events when starting a new session. This creates unnecessary cognitive load and adds redundant steps to the session initiation flow.

The Architectural Reality The memory-core MCP server automatically executes WakeSubscriptionService.bootstrap() on initialization (Server.initAsync). This process is self-healing, utilizing raw SQL queries to ensure status: 'existing' and prevents duplicate subscriptions across restarts. The bridge-daemon dynamically polls the graph log and does not require explicit manual subscription setup.

The Fix Audit .agents/AGENTS_STARTUP.md, other .agents/skills/* guides, and package.json to remove instructions for manually subscribing to wake events.

Acceptance Criteria

• Remove any steps mandating manual manage_wake_subscription or bootstrap tool usage from agent startup guides.
• Ensure any onboarding guides reflect the automated nature of the wake substrate.

Out of Scope

• Modifying the underlying bridge-daemon.mjs logic or WakeSubscriptionService.mjs implementation.
• Refactoring memory-core initialization.

Avoided Traps

• Do not remove the mcp_neo-mjs-memory-core_manage_wake_subscription tool from the MCP server entirely, as it may still be needed for debugging or advanced custom subscription scenarios.

Related

• PR #10510
• #10437

Origin Session ID Origin Session ID: 0a897c00-bbdb-4e05-9012-93fc0c9c26f0

Handoff Retrieval Hints Retrieval Hint: "remove manual wake subscription"