feat(persona): add linear-dispatcher and repo-router persona packs

[khaliqgant]

Summary

Two new persona packs following the persona-slack-comms structure:

@agentworkforce/persona-linear-dispatcher v0.1.0

Autonomous Linear issue dispatcher: watches for ready-for-agent issues, triages them, dispatches codex implementer + claude reviewer agent teams in batches of 5, posts comments, and updates state to Agent Implementing. Releases agents on completion and kicks off the next batch.

@agentworkforce/persona-repo-router v0.1.0

Codebase navigator and issue-to-repo dispatcher: maps all sibling repos in ../, determines which repo(s) an issue requires changes in (including multi-repo issues), and spawns codex implementers + claude reviewer agents pointed at the correct repos. Can be used standalone or called by linear-dispatcher as a routing subroutine.

Key behaviors

linear-dispatcher:

• Batch limit of 5 issues in flight at once
• Codex implementers + claude reviewers per issue
• Canonical AR-{id}__{uuid}.json/comments/ writeback paths
• Repo routing by label: cloud → cloud, pear → pear, agents → agents
• No-auto-merge policy enforced on all spawned agents

repo-router:

• Dynamically scans ../ repos (README, package.json, CLAUDE.md) to build routing map
• Matches issue keywords/labels/surface areas to repos
• Splits multi-repo issues across parallel implementers
• Escalates to broker when routing is ambiguous
• Reasoning: high (needs to reason carefully about repo boundaries)

Files

packages/persona-linear-dispatcher/
├── package.json
├── index.js + index.d.ts
└── personas/linear-dispatcher.{json,md}

packages/persona-repo-router/
├── package.json
├── index.js + index.d.ts
└── personas/repo-router.{json,md}

🤖 Generated with Claude Code

[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

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

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

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ 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.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

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: 904330be-1259-4699-a60b-c30f82670aa0

📥 Commits

Reviewing files that changed from the base of the PR and between a5d4e83 and f5cbac7.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (19)

• packages/cli/src/persona-install.test.ts
• packages/cli/src/persona-install.ts
• packages/persona-linear-dispatcher/index.d.ts
• packages/persona-linear-dispatcher/index.js
• packages/persona-linear-dispatcher/package.json
• packages/persona-linear-dispatcher/personas/linear-dispatcher.json
• packages/persona-linear-dispatcher/personas/linear-dispatcher.md
• packages/persona-linear-dispatcher/skills/persona-relayfile-mount.md
• packages/persona-linear-dispatcher/test/persona.test.mjs
• packages/persona-nango-integrations/personas/nango-integrations.json
• packages/persona-nango-integrations/test/persona.test.mjs
• packages/persona-repo-router/index.d.ts
• packages/persona-repo-router/index.js
• packages/persona-repo-router/package.json
• packages/persona-repo-router/personas/repo-router.json
• packages/persona-repo-router/personas/repo-router.md
• packages/persona-repo-router/skills/agentworkforce-repo-map.md
• packages/persona-repo-router/skills/persona-relayfile-mount.md
• packages/persona-repo-router/test/persona.test.mjs

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/persona-linear-dispatcher

---

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.}

[agent-relay-code]

Fixed two PR-scoped issues:

• Added missing persona package tests for linear-dispatcher and repo-router, since both new packages declared node --test test/persona.test.mjs.
• Changed repo-router’s local markdown skill source to the package-style source expected by the existing persona-pack pattern in repo-router.json.
• Updated pnpm-lock.yaml to include the two new workspace importers at pnpm-lock.yaml.

Addressed comments

• No bot or reviewer comments were present in the local .workforce artifacts. I checked .workforce/context.json, .workforce/pr.diff, and .workforce/changed-files.txt; there were no review-comment payloads to validate.

Advisory Notes

None.

Verification run locally using the CI workflow order from .github/workflows/ci.yml:

pnpm install --frozen-lockfile
pnpm -r run build && pnpm run lint && pnpm run typecheck && pnpm run test

That sequence completed successfully.

[agent-relay-code]

Reviewed PR #223 against .workforce/pr.diff, changed files, and repo callers/tests. I did not find a demonstrated breakage that required code edits.

Addressed comments

• No bot/reviewer comment metadata was present under .workforce/, so there were no external comments to validate or fix.

Advisory Notes

• I did not verify live GitHub CI status, mergeability, or merge conflicts because the task explicitly forbids gh/git usage here. Because of that, I am not marking this READY.

Validation

Passed locally:

• corepack pnpm install --frozen-lockfile
• corepack pnpm -r run build
• corepack pnpm -r lint
• corepack pnpm -r typecheck
• corepack pnpm run typecheck:examples
• corepack pnpm -r test
• New package tests for both persona packages
• npm pack --dry-run --json for both new persona packages
• Installer smoke test for both new persona packages, confirming sidecar Markdown is copied and JSON paths are rewritten

Note: corepack pnpm run lint failed only because this sandbox lacks a plain pnpm executable on PATH inside lifecycle scripts; CI installs pnpm on PATH. The equivalent underlying command, corepack pnpm -r lint, passed.