port-upstream-features-cc

# /port-upstream-features — Port upstream PRs into OmniRoute ## ⚠️ CONFIDENTIAL — this command is `.gitignored` and must NEVER be committed. Full reference: `.agents/workflows/port-upstream-features-ag.md`. Sibling command (issue tracker, not PRs): `/port-upstream-issues`. ## Inputs Arguments: `$ARGUMENTS` (optional). Accepts a space-separated list of upstream PR identifiers — bare numbers (`1317 1320`), full URLs (`https://github.com/decolua/9router/pull/1317`), or a mix. If empty, the command MUST list candidate open upstream PRs first and ask the user which to port before doing anything else. ## Constants (hard-coded — do not infer) - Upstream: `decolua/9router` (JavaScript, Next.js 16) - Fork (origin): `diegosouzapw/OmniRoute` (TypeScript, Next.js 16) - Worktree root: `.claude/worktrees/` - Task notes dir: `_tasks/features-v${VERSION}/port-tasks/` - Dedupe ledger: `_tasks/features-v${VERSION}/port-tasks/_ported.jsonl` - Upstream sources mirror (read-only): `_references/9router/` ## Architecture mapping (upstream → OmniRoute) Use this table when planning each port. OmniRoute has layers that don't exist upstream (a2a, memory, cloudAgent, guardrails, evals, services bootstrap); when an upstream change touches functionality that lives in those layers downstream, MAP IT and note it in the task note. | Upstream (9router, JS) | OmniRoute (TS) ...