port-upstream-issues-cc

# /port-upstream-issues — Resolve upstream-reported bugs in OmniRoute ## ⚠️ CONFIDENTIAL — this command is `.gitignored` and must NEVER be committed. Full reference: `.agents/workflows/port-upstream-issues-ag.md`. Sibling command (PR tracker, not issues): `/port-upstream-features`. > **NOT THE SAME AS `/resolve-issues`.** `/resolve-issues` works on > **OmniRoute's own** issue tracker. This command reads issues filed on > **`decolua/9router`** (upstream) and lands fixes here, without ever > touching the upstream tracker. ## Inputs Arguments: `$ARGUMENTS` (optional). Accepts a space-separated list of upstream issue identifiers — bare numbers (`1317 1320`), full URLs (`https://github.com/decolua/9router/issues/1317`), or a mix. If empty, the command harvests ALL open upstream issues and triages before any code change. ## 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: `_tasks/features-v${VERSION}/port-upstream-issues/` - Dedupe ledger: `_tasks/features-v${VERSION}/port-upstream-issues/_resolved.jsonl` - Upstream sources mirror (read-only): `_references/9router/` - We NEVER comment, close, or react on `decolua/9router`'s issue tracker. ## Architecture mapping (upstream → OmniRoute) Use this table when reproducing each bug and planning the fix. OmniRoute has layers that don't exist upstream (a2a, memory, cloudA...