feat: link PRs to Issues via Native Edge Graph RESOLVES edges; mandate PR body Fat Ticket summaries (#9851)

Author: tobiu

AGENTS.md

@@ -156,7 +156,7 @@ You **MUST** perform these steps in order before marking a task as complete:
 4.  **One PR per Ticket:** Enforce a strict 1-to-1 ratio between an Issue and a Pull Request. Do not bundle multiple unassociated issues into a single PR.
     - **Epic Exception:** An Epic may have a single overarching PR that resolves all of its associated Sub-Issues.
 5.  **Assign:** Ensure the Pull Request and the underlying Ticket are assigned to the current user to capture credit.
-6.  **Handoff:** Post a comment on the original issue and the PR if you deviated from the original plan. The agent's task is considered "Done" once the PR is opened and ready for human review. Do not merge it yourself.
+6.  **Handoff:** The PR body MUST contain a "Fat Ticket Style" summary of the changes made, explicitly highlighting any deviations from the original issue's scope, and clarifying what previous closing discussions or commits accomplished. The agent's task is considered "Done" once the PR is opened and ready for human review. Do not merge it yourself.
 
 ## 9. Preventing Context Corruption (State Management)
 

AGENTS_STARTUP.md

@@ -271,4 +271,4 @@ Without this context, sub-agents will hallucinate bugs where none exist (e.g., c
     -   **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:** Explain *why* you decided not to use alternative paths. Specifically highlight if you avoided a generic industry or LLM "Gold Standard" (e.g., standard React patterns, generic node workflows) because it acts as a trap within Neo.mjs's unique multi-threaded architecture.
 7.  **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.
-8.  **Pull Request Collaboration:** Once you begin actionable work, you are acting as an asynchronous contributor. All code changes MUST culminate in a Pull Request against the `dev` branch (see `AGENTS.md` Section 8). Direct commits to `main` or `dev` are forbidden, ensuring the team can review and critique the implementation before integration.
+8.  **Pull Request Collaboration:** Once you begin actionable work, you are acting as an asynchronous contributor. All code changes MUST culminate in a Pull Request against the `dev` branch (see `AGENTS.md` Section 8). The PR body MUST contain a "Fat Ticket" style summary detailing the execution and highlighting any scope deviations, alongside the `Resolves #[Issue Number]` keyword. Direct commits to `main` or `dev` are forbidden, ensuring the team can review and critique the implementation before integration.

ai/daemons/DreamService.mjs

@@ -910,6 +910,20 @@ ${topContent}
                                 logger.debug(`[DreamService] Ingested ${gapType} from ${prId}: ${gapNodeId}`);
                             }
                         }
+
+                        // Lexical scanning for Resolves/Closes/Fixes issue linkages
+                        const issueMatches = [...content.matchAll(/(?:(?:Resolves|Closes|Fixes)\s+#)(\d+)/gi)];
+                        for (const issueMatch of issueMatches) {
+                            const issueNumber = issueMatch[1];
+                            const issueNodeId = `issue-${issueNumber}`;
+
+                            // Create Hebbian edge for PR resolving Issue
+                            GraphService.linkNodes(prId, issueNodeId, 'RESOLVES', 1.0, {
+                                justification: `PR #${meta.number} explicitly resolves Issue #${issueNumber}.`
+                            });
+
+                            logger.debug(`[DreamService] Linked PR ${prId} as resolving ${issueNodeId}`);
+                        }
                     }
                 } catch (e) {
                     logger.warn(`[DreamService] Failed to process pull request feedback for ${file}`, e);