fix(factory): propagate relay workspace to agents

[miyaontherelay]

Summary

• resolve the active Agent Relay workspace key from env or the persisted SDK/CLI workspace store during broker startup
• thread the resolved workspace key into internal fleet agents so their injected agent-relay MCP can reach .integrations
• spawn direct factory agents with relay task-exit lifecycle fields from feat(spawn): add task-exit mode relay#1129 (spawnMode: task_exit, exitAfterTask: true)
• tolerate live Linear writeback propagation latency by extending read-back confirmation retries
• parse Markdown GitHub mirror Source: links so mirrored Linear issues route to the source repo even before labels sync

Operational notes

• Current AR-311 agents were spawned before this branch, so they do not have task-exit set. New factory dispatches will.
• factory-node/@agent-relay/fleet does not expose task-exit fields yet; this PR applies task-exit to the direct internal factory spawn path used by factory start / factory dispatch.

Verification

• npm run build
• npm test

[gemini-code-assist]

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

[coderabbitai]

Warning

Review limit reached

@miyaontherelay, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 22 minutes and 54 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 32f565d5-fd23-4bca-b698-089ca05ad108

📥 Commits

Reviewing files that changed from the base of the PR and between 2e01101 and 4e85f0d.

📒 Files selected for processing (11)

• src/cli/fleet.ts
• src/fleet/create-fleet.ts
• src/fleet/ensure-relay-broker.test.ts
• src/fleet/ensure-relay-broker.ts
• src/fleet/internal-fleet-client.test.ts
• src/fleet/internal-fleet-client.ts
• src/fleet/relay-workspace-key.ts
• src/orchestrator/factory.test.ts
• src/orchestrator/factory.ts
• src/writeback/linear.ts
• src/writeback/writeback.test.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/relay-workspace-key-propagation

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}