Track upstream agent CLI versions

.a5c/processes/agent-version-daily-tracker.inputs.json

@@ -1,5 +1,5 @@
 {
   "userRequest": "You are an agent version tracker. Check for new releases of the ORIGINAL upstream agent CLI products - NOT our babysitter plugin packages.\n\nSTEP 1: Build atlas.\n```\nnpm run build --workspace=@a5c-ai/atlas\n```\n\nSTEP 2: Get the target list using the SAME logic as\n`scripts/sync-external-plugin-repos.mjs` uses in `buildTargetsFromCatalog()`.\nRead that file to understand the pattern, then run:\n```\nnode -e \"\n  import(new URL('file://' + process.cwd() + '/packages/atlas/dist/catalog/sdk.js').href)\n    .then(m => {\n      const targets = m.listPluginTargetDescriptors()\n        .filter(t => t.externalRepo)\n        .map(t => ({\n          id: t.adapterName || t.targetId,\n          displayName: t.displayName,\n          cliCommand: t.cliCommand,\n          externalPackageName: t.externalPackageName,\n          externalRepo: t.externalRepo,\n        }));\n      console.log(JSON.stringify(targets, null, 2));\n    });\n\"\n```\nThis gives you every agent that has an external repo - these are the\nupstream host agents. The `externalPackageName` is the npm package to\ncheck (if set). For agents without an npm package, search the web.\n\nAlso check adapter source for additional install commands:\n```\ngrep -r 'npm install -g' packages/adapters/codecs/src/ | grep -v node_modules | grep -v test\n```\nMerge both lists. EXCLUDE all @a5c-ai/* packages.\n\nSTEP 3: For EACH upstream agent, check the latest published version.\n`npm view <package>@latest version` for npm packages.\nSearch the web for agents distributed differently (pip, binary, etc.).\n\nSTEP 4: Compare against AgentVersion records in the graph.\nRead files in `packages/atlas/graph/agent-stack/agent-versions/` and\n`packages/atlas/graph/agent-stack/products/` to see what versions\nare already recorded.\n\nSTEP 5: For new versions not in the graph:\n- Search the web for release notes, changelog, blog posts\n- Create or update the AgentVersion YAML\n- Note capability changes, new CLI flags, breaking changes, transport/API changes\n\nSTEP 6: If graph files changed:\n- Rebuild: `npm run build --workspace=@a5c-ai/atlas`\n- Branch: `agent-versions/daily-$(date +%Y-%m-%d)`\n- Commit all changes, create ONE PR against staging\n\nSTEP 7: For each new agent+version pair, check for existing issue:\n`gh issue list --label \"agent-version-update\" --search \"<agent> <version>\"`\n\nIf none exists, create an issue. The issue body must NOT be a static\ntemplate - fill it with the ACTUAL research you did. Include:\n\n- The exact version numbers (old and new)\n- Links to the actual release notes / changelog / blog post you found\n- A summary of REAL changes you read from those release notes -\n  new features, breaking changes, new CLI flags, deprecated flags,\n  API/transport changes, new tool capabilities, new supported models\n- Which parts of our system are likely affected based on what changed\n  (be specific: \"new --foo flag means launchBehavior needs updating\",\n  \"switched from REST to WebSocket means transport-adapter proxy affected\")\n- Whether the new version changes install method or package name\n- Any migration steps mentioned in the release notes\n\nEnd the issue body with the assimilation checklist - but make the\nchecklist items SPECIFIC to what actually changed, not generic.\nFor example, if the release notes mention a new CLI flag, the\nchecklist should say \"Update launchBehavior: add --newFlag to\npromptExtraFlags\" not just \"Update launchBehavior if changed\".\n\nUse label `agent-version-update,graph-update`.\n\nSTEP 8: Print a summary table with ALL agents checked.\n\nIMPORTANT: Cover every upstream agent systematically. Do not stop after one.\nOne PR for all changes in this run.",
-  "branchName": "agent-versions/daily-2026-07-17",
+  "branchName": "agent-versions/daily-2026-08-05",
   "baseBranch": "staging"
 }