Track Factory Droid CLI 0.190.0

[a5c-ai]

Version

• Previous graph version: 0.174.0
• Latest upstream version: 0.190.0
• Package metadata: https://www.npmjs.com/package/@factory/cli/v/0.190.0

Actual changes researched

• npm reports @factory/cli latest as 0.190.0, published on 2026-08-07.
• npm description identifies the package as Factory Droid CLI, an AI-powered software engineering agent.
• npm repository metadata points to Factory-AI/factory under apps/cli.
• I did not find public 0.190.0-specific release notes/changelog for CLI flags, transport/API, models, install method, or package-name changes.

Likely affected system surfaces

• Version catalog only unless Factory publishes release notes with behavioral details.
• Keep Droid adapter install command as npm install -g @factory/cli.

Install/migration

• Install remains npm install -g @factory/cli.
• No migration steps were published.

Assimilation checklist

• Record @factory/cli 0.190.0 in AgentVersion graph.
• Re-check Factory release notes before changing launchBehavior or transport metadata.
• Leave Droid adapter install metadata unchanged: npm install -g @factory/cli.

[a5c-ai]

Triage Summary

• One-line: Track the upstream Factory Droid CLI @factory/cli 0.190.0 release in the Atlas agent-version graph.

Critical Evaluation

• Reporter analysis is accurate.
• This is a valid graph/catalog update, not a runtime bug.
• The recommended scope is catalog-only unless fresh Factory release notes show concrete CLI flag, transport/API, model, package-name, install-method, or migration changes.

Root Cause Analysis

• The Atlas graph has not yet assimilated @factory/cli 0.190.0.
• The latest explicit Droid upstream AgentVersion entry found is agentVersion:droid:0-174-0 in packages/atlas/graph/agent-stack/agent-versions/upstream-current-2026-07-17.yaml.
• A targeted scan of packages/atlas/graph/agent-stack/agent-versions and packages/atlas/graph/agent-stack/versions found no 0.190.0 Droid entry.
• npm view @factory/cli confirms latest 0.190.0, package description Factory Droid CLI - AI-powered software engineering agent, repository Factory-AI/factory, droid binary, and Node >=20.0.0.

Affected Components

• Packages/components: @a5c-ai/atlas, Atlas catalog / agent-version graph
• Likely files: packages/atlas/graph/agent-stack/agent-versions/*, with validation through packages/atlas/src/catalog/catalog.test.ts and packages/atlas/scripts/graph-quality.mjs
• Effort: effort:small

Recommended Approach

• Add a dated AgentVersion record for Factory Droid CLI 0.190.0 using the existing upstream Droid record pattern.
• Use npm evidence: https://www.npmjs.com/package/@factory/cli/v/0.190.0.
• Keep sourcePackage: "@factory/cli", cliCommand: "droid", and install metadata as npm-based unless new release notes justify more.
• Do not change adapter launch behavior, transport/API metadata, model metadata, or install command without concrete upstream evidence.
• Run Atlas graph/catalog validation after editing.

Reproduction

• rg -n "0\\.190\\.0" packages/atlas/graph/agent-stack/agent-versions packages/atlas/graph/agent-stack/versions currently finds no Droid 0.190.0 graph record.
• npm view @factory/cli version --json reports 0.190.0.

Related Issues/PRs

• Track Factory Droid CLI 0.190.0 #1687 has the same title but is already closed as a duplicate of this issue, so Track Factory Droid CLI 0.190.0 #1692 is the canonical tracker.
• Prior Droid version tracking issues include Track Factory Droid CLI 0.189.0 #1650, Track Factory Droid CLI 0.188.0 #1634, and Track Factory Droid CLI 0.187.0 #1612.

Priority

• priority:low
• Reasoning: routine upstream-version catalog freshness work. No runtime crash, data loss, production blocker, or user-facing regression was identified.

Risk Analysis

• Risk Level: risk:low
• Graph metadata drift or stale copied notes
  • Mitigation: base the new record on fresh npm metadata and cite the 0.190.0 npm package URL.
• Over-scoping into runtime/adapter behavior without evidence
  • Mitigation: keep the implementation limited to the AgentVersion graph record unless release notes provide concrete changes.
• Duplicate tracking confusion with Track Factory Droid CLI 0.190.0 #1687
  • Mitigation: treat Track Factory Droid CLI 0.190.0 #1692 as canonical because Track Factory Droid CLI 0.190.0 #1687 was closed as duplicate of Track Factory Droid CLI 0.190.0 #1692.

Ready for development.

[a5c-ai]

Triage Summary

• One-line: Factory Droid CLI has upstream npm version 0.190.0, while the Atlas graph still records Droid through 0.174.0.

Critical Evaluation

• The report is valid and the reporter's analysis is accurate.
• This is a catalog freshness enhancement, not a runtime adapter bug.
• The suggested scope is correct: record the new upstream version and avoid behavior/adapter metadata changes unless release notes justify them.

Root Cause Analysis

• Affected graph files follow the current Droid precedent in:
  • packages/atlas/graph/agent-stack/agent-versions/upstream-current-2026-07-17.yaml
  • packages/atlas/graph/catalog-meta/evidence-sources/upstream-current-2026-07-17.yaml
• Current code evidence: the graph contains agentVersion:droid:0-174-0 and evidence:droid-0-174-0-2026-07-17, but no 0.190.0 Droid AgentVersion/EvidenceSource.
• Upstream npm metadata for @factory/cli@0.190.0 confirms:
  • version 0.190.0
  • published 2026-08-07T20:45:24.093Z
  • description: Factory Droid CLI
  • repository: Factory-AI/factory, directory apps/cli
  • binary: droid
  • engines: Node >=20.0.0

Affected Components

• Packages: atlas, agent-catalog
• Effort: effort:small

Recommended Approach

• Add a dated upstream-current AgentVersion entry for agentVersion:droid:0-190-0 modeled after the existing 0.174.0 entry.
• Add a matching EvidenceSource entry, likely evidence:droid-0-190-0-2026-08-07 or the repo's current date-shard convention.
• Preserve cliCommand: "droid", sourcePackage: "@factory/cli", and install method install:npm / npm install -g @factory/cli.
• Do not change launch behavior, transport/API metadata, model metadata, package name, or install method without specific upstream release-note evidence.

Reproduction

• rg "0\.190\.0|Factory Droid CLI|@factory/cli" packages/atlas/graph shows existing Droid records but no 0.190.0 graph entry.
• npm view @factory/cli@0.190.0 version description repository.url repository.directory bin engines --json verifies package identity and command metadata.
• npm view @factory/cli time --json verifies the 0.190.0 publish timestamp.

Related Issues/PRs

• #1687 had the same title/version but is already closed as a duplicate of this issue, so #1692 is the canonical tracking issue.
• Recent related upstream-version graph work includes commits such as e3b0a4ea8 and 4cf911509.

Priority: low

• This improves graph/catalog freshness for downstream consumers, but it does not block runtime behavior or adapter execution.

Risk Analysis

• Risk Level: risk:low
• Changing adapter runtime/install metadata without evidence
  • Mitigation: limit the change to AgentVersion/EvidenceSource metadata unless upstream release notes state otherwise.
• Duplicate or inconsistent graph/evidence ids
  • Mitigation: follow the existing Droid 0.174.0 pattern and dated shard conventions.
• YAML or graph reference validation failure
  • Mitigation: run Atlas catalog tests or repository metadata verification after updating the graph.