fix: pass all shadow options through daemon spawn path

Shadow options (shadowMode, shadowAgent, shadowTriggers) were silently
dropped when spawning via the daemon socket path. The HTTP API fallback
passed all fields via JSON.stringify, but the SDK path used explicit
field listing that missed these three fields.

Thread shadowMode, shadowAgent, and shadowTriggers through:
- Protocol SpawnPayload type
- SDK client.spawn() options and envelope payload
- Daemon SpawnManager.handleSpawn() pass-through
- CLI client.spawn() call

Add SDK test verifying shadow options appear in sent envelope.
Add sdk-daemon-parity Claude rule to prevent future field omissions.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

Author: Agent Relay

.claude/rules/sdk-daemon-parity.md

@@ -0,0 +1,42 @@
+---
+paths:
+  - "packages/sdk/src/**/*.ts"
+  - "packages/daemon/src/**/*.ts"
+  - "packages/protocol/src/types.ts"
+  - "src/cli/index.ts"
+---
+
+# SDK-Daemon Parity
+
+## Principle
+
+The SDK (`RelayClient`) is the canonical interface for daemon communication. All spawn/release fields supported by the spawner and bridge must be threaded through:
+
+1. **Protocol types** (`SpawnPayload` in `packages/protocol/src/types.ts`)
+2. **SDK client** (`client.spawn()` options and envelope payload in `packages/sdk/src/client.ts`)
+3. **Daemon SpawnManager** (`handleSpawn` pass-through in `packages/daemon/src/spawn-manager.ts`)
+4. **CLI** (the `client.spawn()` call in `src/cli/index.ts`)
+
+## Adding New Spawn Fields
+
+When adding a field to `SpawnRequest` in `packages/spawner/src/types.ts` or `packages/bridge/src/types.ts`:
+
+- Add to `SpawnPayload` in `packages/protocol/src/types.ts`
+- Add to `client.spawn()` options type in `packages/sdk/src/client.ts`
+- Include in the envelope payload construction in `client.spawn()`
+- Pass through in `SpawnManager.handleSpawn()` to `this.spawner.spawn()`
+- Include in the CLI `client.spawn()` call in `src/cli/index.ts`
+- Add a test verifying the field appears in the sent envelope
+
+## Daemon vs HTTP API Parity
+
+The daemon socket path and HTTP API fallback must produce identical behavior. The HTTP fallback passes the entire `spawnRequest` via `JSON.stringify()`, so it gets all fields automatically. The daemon path uses explicit field listing, which requires manual updates when new fields are added.
+
+## SDK Over Direct Protocol
+
+Always use `RelayClient` methods (`spawn`, `release`, `sendMessage`) rather than constructing raw protocol envelopes in CLI commands. The SDK handles:
+
+- Connection lifecycle and reconnection
+- Envelope construction with correct protocol version
+- Timeout management and cleanup
+- Correlation ID tracking for responses

.trajectories/completed/2026-02/traj_itn5hyej5mi6.json

@@ -0,0 +1,70 @@
+{
+  "id": "traj_itn5hyej5mi6",
+  "version": 1,
+  "task": {
+    "title": "Fix @agent-relay/wrapper module resolution issues - 17 test failures",
+    "source": {
+      "system": "plain",
+      "id": "PR-357"
+    }
+  },
+  "status": "completed",
+  "startedAt": "2026-02-02T10:32:24.710Z",
+  "agents": [
+    {
+      "name": "default",
+      "role": "lead",
+      "joinedAt": "2026-02-02T15:13:33.203Z"
+    }
+  ],
+  "chapters": [
+    {
+      "id": "chap_g5zlcodg305k",
+      "title": "Work",
+      "agentName": "default",
+      "startedAt": "2026-02-02T15:13:33.203Z",
+      "events": [
+        {
+          "ts": 1770045213205,
+          "type": "decision",
+          "content": "Thread shadowMode, shadowAgent, shadowTriggers through protocol, SDK, daemon, and CLI layers: Thread shadowMode, shadowAgent, shadowTriggers through protocol, SDK, daemon, and CLI layers",
+          "raw": {
+            "question": "Thread shadowMode, shadowAgent, shadowTriggers through protocol, SDK, daemon, and CLI layers",
+            "chosen": "Thread shadowMode, shadowAgent, shadowTriggers through protocol, SDK, daemon, and CLI layers",
+            "alternatives": [],
+            "reasoning": "Devin review found these fields were silently dropped in daemon spawn path. Both the spawner and bridge packages already support them, but protocol SpawnPayload and SDK client.spawn() were missing them, creating silent data loss when using daemon-based spawning vs HTTP API fallback."
+          },
+          "significance": "high"
+        },
+        {
+          "ts": 1770045235751,
+          "type": "decision",
+          "content": "Created sdk-daemon-parity.md Claude rule: Created sdk-daemon-parity.md Claude rule",
+          "raw": {
+            "question": "Created sdk-daemon-parity.md Claude rule",
+            "chosen": "Created sdk-daemon-parity.md Claude rule",
+            "alternatives": [],
+            "reasoning": "Codifies the requirement that all spawn fields must be threaded through protocol, SDK, daemon, and CLI layers to prevent future silent data loss bugs."
+          },
+          "significance": "high"
+        }
+      ],
+      "endedAt": "2026-02-02T15:14:01.719Z"
+    }
+  ],
+  "commits": [],
+  "filesChanged": [],
+  "projectId": "/data/repos/relay",
+  "tags": [],
+  "_trace": {
+    "startRef": "2bf129eb8935904951b0aeb866ddba268611e009",
+    "endRef": "f637ba5a9d194aff545001bbe091c45fc0c3413d",
+    "traceId": "trace_17kspa6zdv77"
+  },
+  "completedAt": "2026-02-02T15:14:01.719Z",
+  "retrospective": {
+    "summary": "Fixed Devin review issue: threaded shadowMode, shadowAgent, shadowTriggers through protocol SpawnPayload, SDK client.spawn(), daemon SpawnManager, and CLI. Added SDK test for shadow options. Created sdk-daemon-parity Claude rule.",
+    "approach": "Standard approach",
+    "confidence": 0.9
+  }
+}

.trajectories/completed/2026-02/traj_itn5hyej5mi6.md

@@ -0,0 +1,37 @@
+# Trajectory: Fix @agent-relay/wrapper module resolution issues - 17 test failures
+
+> **Status:** ✅ Completed
+> **Task:** PR-357
+> **Confidence:** 90%
+> **Started:** February 2, 2026 at 10:32 AM
+> **Completed:** February 2, 2026 at 03:14 PM
+
+---
+
+## Summary
+
+Fixed Devin review issue: threaded shadowMode, shadowAgent, shadowTriggers through protocol SpawnPayload, SDK client.spawn(), daemon SpawnManager, and CLI. Added SDK test for shadow options. Created sdk-daemon-parity Claude rule.
+
+**Approach:** Standard approach
+
+---
+
+## Key Decisions
+
+### Thread shadowMode, shadowAgent, shadowTriggers through protocol, SDK, daemon, and CLI layers
+- **Chose:** Thread shadowMode, shadowAgent, shadowTriggers through protocol, SDK, daemon, and CLI layers
+- **Reasoning:** Devin review found these fields were silently dropped in daemon spawn path. Both the spawner and bridge packages already support them, but protocol SpawnPayload and SDK client.spawn() were missing them, creating silent data loss when using daemon-based spawning vs HTTP API fallback.
+
+### Created sdk-daemon-parity.md Claude rule
+- **Chose:** Created sdk-daemon-parity.md Claude rule
+- **Reasoning:** Codifies the requirement that all spawn fields must be threaded through protocol, SDK, daemon, and CLI layers to prevent future silent data loss bugs.
+
+---
+
+## Chapters
+
+### 1. Work
+*Agent: default*
+
+- Thread shadowMode, shadowAgent, shadowTriggers through protocol, SDK, daemon, and CLI layers: Thread shadowMode, shadowAgent, shadowTriggers through protocol, SDK, daemon, and CLI layers
+- Created sdk-daemon-parity.md Claude rule: Created sdk-daemon-parity.md Claude rule