feat: Swarm Network Fat Ticket bootstrapping and autoGoldenPath (#9790)

Author: tobiu

AGENTS.md

@@ -25,7 +25,7 @@ For any actionable request that requires modifying the repository, you **MUST**
 
 **Gate 1: The Ticket Gate**
 1.  **Scoping:** Tickets force focus. A single ticket (and its subsequent commit) should address one discrete problem or feature. Never bundle unrelated fixes into a single ticket/commit.
-2.  **Problem-Focused:** When creating a ticket, focus the description on the *problem* or the *user story*.
+2.  **The "Fat Ticket" Protocol (MANDATORY):** You MUST adhere to the Swarm Architecture "Fat Ticket" protocol (defined in `AGENTS_STARTUP.md`). When creating a ticket, focus the description not just for human tracking, but as a rich A2A (Agent-to-Agent) memory bridge containing deep architectural context, rationale, and avoided pitfalls.
 3.  **Exploration is Allowed:** You are permitted to write code, modify files, and experiment locally to understand a complex problem ("Unknown Unknowns") *before* creating the ticket.
 4.  **The Hard Stop:** The absolute hard stop is `git commit`. You **MUST NEVER** execute a commit without referencing a valid, narrowly scoped ticket ID in the commit message. Use the `create_issue` tool and follow its workflow.
 

AGENTS_STARTUP.md

@@ -251,3 +251,20 @@ Without this context, sub-agents will hallucinate bugs where none exist (e.g., c
 3.  **Consult the Expert:** If tools are insufficient or the hierarchy is complex, **ASK THE USER**.
     -   *Template:* "I cannot see the parent container's computed styles. Could you please paste the computed `height` and `overflow` of the element wrapping `.my-component`?"
 4.  **Verify Assumptions:** Never assume a class like `neo-label` behaves standardly. Verify its computed style.
+
+## 9. Swarm Architecture: The "Fat Ticket" Protocol
+
+**Context:** The Neo.mjs project runs as a distributed agentic swarm. Multiple hardware instances (e.g., Mac 1, Mac 2) operate simultaneously, but their underlying SQLite `/neo-ai-data` repositories are entirely local to avoid cross-network database collisions.
+
+**The Boot Amnesia Problem:** This means that when a secondary agent drops into the network or pulls a new git sync, it has *zero* chronological memory vectors of what the primary agent discussed, discovered, or decided in the preceding sessions.
+
+**The Solution:** You MUST bridge the SQLite gap by converting GitHub Issues into your primary episodic memory carriers.
+
+**Mandatory Workflow:**
+1.  **Do Not Create Skeleton Tickets:** You are strictly forbidden from creating GitHub issues with one-sentence descriptions. A ticket is not just for human tracking; it is the **A2A (Agent-to-Agent)** data transport mechanism.
+2.  **Generate "Fat Tickets":** When you call `create_issue`, the `body` parameter MUST contain a highly detailed summary that functions as a structural graph node proxy.
+3.  **Required A2A Context:** The Fat Ticket MUST contain:
+    -   **The Problem:** Include deep background context or insights from your recent Memory Core explorations.
+    -   **The Architectural Reality:** Point out exactly *which* Neo.mjs patterns or class topologies this issue interacts with. Include specific paths to files discovered during your research.
+    -   **Avoided Gold Standards/Traps:** Summarize *why* you decided not to use alternative paths based on your prior queries.
+4.  **Handoff Realization:** On boot (`initAsync`), nodes like Mac 2 automatically synthesize the latest synced `.md` issues into their local SQLite matrix and build `sandman_handoff.md`. If your tickets are "Fat," the resulting "Golden Path" ranking will accurately bridge the distributed swarm without ever merging the raw SQLite files.

ai/mcp/server/memory-core/config.template.mjs

@@ -23,6 +23,12 @@ const defaultConfig = {
      * @type {boolean}
      */
     autoDream: process.env.AUTO_DREAM !== 'false',
+    /**
+     * Automatically trigger Golden Path Synthesis into the handoff file on startup.
+     * Crucial for headless swarm nodes (Mac 2) to physically generate sandman_handoff.md.
+     * @type {boolean}
+     */
+    autoGoldenPath: process.env.AUTO_GOLDEN_PATH !== 'false',
     /**
      * Immediately parse each incoming memory turn (add_memory) for Graph Injection.
      * @type {boolean}

ai/mcp/server/memory-core/services/DreamService.mjs

@@ -68,6 +68,11 @@ class DreamService extends Base {
             logger.info('[Startup] DreamService: Checking for undigested session memories...');
             this.processUndigestedSessions().catch(e => logger.error('[Startup] DreamService failed:', e));
         }
+
+        if (aiConfig.data.autoGoldenPath) {
+            logger.info('[Startup] DreamService: Synthesizing Golden Path into handoff file...');
+            this.synthesizeGoldenPath().catch(e => logger.error('[Startup] Golden Path generation failed:', e));
+        }
     }
 
     /**