Match renderer link routing and keep browser callbacks self-contained

Prefix only parsed issue references, preserve ordinary root-relative anchors, and avoid tsx name helpers inside the serialized DOM callback. Verify with the exact QA Node24/tsx path and positive/negative browser cases.

Co-Authored-By: Paperclip <noreply@paperclip.ing>

tests/runner-e2e/native-task-reply.test.ts

@@ -78,7 +78,7 @@ it("binds complete Markdown content and the exact link destination despite a dec
   const body = "I **couldn't retrieve** the pages. See [Connection outcome](/QA/issues/QA-123#document-outcome).";
   const comment = { id: "selected", authorAgentId: "owned-agent", createdByRunId: "final-run", body };
   const published = { ...run, resultJson: { presentationDecision: { commentId: "selected" } } };
-  const bubble: TaskReplyObservation = { ...observed, anchor: "selected", origin: "https://fixture.test",
+  const bubble: TaskReplyObservation = { ...observed, anchor: "selected", origin: "https://fixture.test", pageUrl: "https://fixture.test/QA/issues/QA-123",
     body: "I couldn't retrieve the pages. See QA-123.",
     content: [{ text: "I couldn't retrieve the pages. See " }, { href: "https://fixture.test/QA/issues/QA-123#document-outcome", label: "QA-123", decorated: true }, { text: "." }] };
   expect(taskReplyBelongsToRun(bubble, published, "owned-agent", [comment])).toBe(true);