Track Amp CLI 0.0.1783414941-g212a2a upstream release

[a5c-ai]

Upstream version check

• Agent: Amp CLI
• Package: @ampcode/cli
• Previously recorded in graph: 0.0.1783069983-gce9c8b
• Latest checked version: 0.0.1783414941-g212a2a
• Release/package metadata: https://www.npmjs.com/package/@ampcode/cli/v/0.0.1783414941-g212a2a

Research notes

I checked the adapter install commands and npm metadata. The latest npm dist-tag is 0.0.1783414941-g212a2a, published July 7, 2026. The package README still documents npm install -g @ampcode/cli and says the prior @sourcegraph/amp package name remains available for backwards compatibility. I did not find public build-specific release notes, a GitHub release, or a public changelog for this timestamped build.

Changes found

• New timestamped npm package build only.
• No confirmed new CLI flags.
• No confirmed transport/API changes.
• No confirmed new model/tool capability changes.
• No install method or package-name migration; install remains npm install -g @ampcode/cli.

Likely affected system surfaces

• Atlas AgentVersion graph should record the new package version and evidence source.
• Adapter launchBehavior does not need a flag update based on available public metadata.
• Install metadata should remain @ampcode/cli, with awareness that @sourcegraph/amp is still mentioned as backwards-compatible.

Migration notes

No migration steps were published.

Assimilation checklist

• Update Atlas AgentVersion record for Amp CLI 0.0.1783414941-g212a2a.
• Keep install command as npm install -g @ampcode/cli; do not rename to @sourcegraph/amp.
• Verify no launchBehavior changes are needed because no new flags were published.
• Record package-metadata evidence instead of release-notes evidence because no changelog was found.

[a5c-ai]

Triage Summary

• One-line: Track the new @ampcode/cli timestamped npm build 0.0.1783414941-g212a2a in the Atlas graph with npm package evidence.

Critical Evaluation

• Reporter's analysis is accurate.
• This is valid graph/version-tracking work, not an adapter behavior bug.
• The issue should stay narrowly scoped: npm metadata confirms the package version, but no public evidence confirms new CLI flags, transport/API changes, MCP changes, model/tool capability changes, package-name migration, or launch behavior changes.

Root Cause Analysis

• npm view @ampcode/cli@0.0.1783414941-g212a2a version time dist-tags homepage --json confirms 0.0.1783414941-g212a2a is published and is the current npm latest dist-tag.
• packages/atlas/graph/agent-stack/agent-versions/upstream-current-2026-07-03.yaml currently records Amp CLI 0.0.1783069983-gce9c8b with sourcePackage: "@ampcode/cli" and npm evidence.
• packages/atlas/graph/agent-stack/versions/amp-current.yaml still records an older agent-version:amp@current baseline, including unchanged install metadata and no-public-changelog notes.
• Adapter metadata already uses npm install -g @ampcode/cli, so no adapter install command change is indicated.

Affected Components

• Packages: packages/atlas, agent catalog graph consumers
• Effort: effort:small

Recommended Approach

• Add/update Atlas AgentVersion metadata for Amp CLI 0.0.1783414941-g212a2a.
• Add npm package evidence for https://www.npmjs.com/package/@ampcode/cli/v/0.0.1783414941-g212a2a.
• Preserve install metadata as npm install -g @ampcode/cli.
• Explicitly record that no public build-specific changelog was found for CLI flags, transport/API, model/tool capability, MCP, launch behavior, auth, package-name, or migration changes.
• Prefer additive issue-scoped files if shared upstream-current files are hot or conflict-prone.
• Update or add a focused graph claim test that checks the new version, npm URL, source package, install command, and no-public-release-notes finding.

Reproduction

npm view @ampcode/cli@0.0.1783414941-g212a2a version time dist-tags homepage --json
rg -n '1783414941|1783069983|@ampcode/cli' packages/atlas/graph

Expected: npm reports the target version as available/latest, while the graph currently lacks 0.0.1783414941-g212a2a.

Related Issues/PRs

• Related prior Amp tracking issues: Track Amp CLI 0.0.1783329373-gb3eec2 upstream release #1196, Track Amp CLI 0.0.1783228622-g9b591b upstream release #1183, Track Amp CLI 0.0.1783155105-g3e26cc upstream release #1172, Track Amp CLI 0.0.1783069983-gce9c8b upstream release #1127, Track Amp CLI 0.0.1782969322-gf53f17 #1104.
• Exact version duplicate search found only this issue.
• No matching commits or closed PRs were found for 0.0.1783414941-g212a2a.

Priority: low

Routine upstream version tracking. It improves graph freshness and catalog accuracy but is not a production outage, security issue, data-loss bug, or user-blocking adapter failure.

Risk Analysis

• Risk Level: risk:low
• Graph churn/conflict: Multiple agent-version updates can touch shared upstream-current files.
  • Mitigation: use additive issue-scoped graph/evidence files where appropriate, rebase before merge, and run metadata verification.
• Overclaiming: npm metadata confirms the package build but not behavior changes.
  • Mitigation: limit claims to package version evidence and unchanged install metadata unless additional public sources are found.
• Test drift: Existing Amp release-tracking tests may guard an older target version.
  • Mitigation: update or add a focused claim test for this target version.

[a5c-ai]

Triage Summary

• One-line: Track the latest @ampcode/cli timestamped npm build in Atlas AgentVersion graph records.

Critical Evaluation

• Reporter's analysis is accurate: npm metadata confirms @ampcode/cli latest is 0.0.1783414941-g212a2a.
• This is an enhancement/catalog maintenance issue, not a runtime bug.
• No public build-specific changelog or release notes were found, so implementation should avoid inventing adapter behavior changes.

Root Cause Analysis

• Affected files:
  • packages/atlas/graph/agent-stack/agent-versions/upstream-current-2026-07-03.yaml
  • packages/atlas/graph/agent-stack/versions/amp-current.yaml
  • packages/atlas/graph/agent-stack/products/amp.yaml
  • packages/adapters/codecs/src/amp-adapter.ts
  • packages/adapters/codecs/tests/amp-adapter.test.ts
• Actual root cause: upstream @ampcode/cli moved to 0.0.1783414941-g212a2a, but committed Atlas Amp records only cover older versions. The latest additive Amp record is 0.0.1783069983-gce9c8b, and amp-current.yaml is older still at 0.0.1780032159-g3925ab.
• Code evidence: npm view @ampcode/cli reports version and dist-tags.latest as 0.0.1783414941-g212a2a, with publish time 2026-07-07T09:10:15.001Z. Repository search found no committed 1783414941 or g212a2a record.

Affected Components

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

Recommended Approach

Treat this as an Atlas AgentVersion graph/catalog update:

• Add an Amp AgentVersion record for @ampcode/cli 0.0.1783414941-g212a2a with npm metadata evidence.
• Keep install command as npm install -g @ampcode/cli.
• Record that no confirmed CLI flag, transport, MCP, model, package-name, or migration change was published for this timestamped build.
• Update product/current links only where consistent with existing Atlas conventions.
• Run the Atlas graph validator or repo metadata verification after the YAML change.

Reproduction

Run:

npm view @ampcode/cli version dist-tags.latest time.0.0.1783414941-g212a2a --json
rg '1783414941|g212a2a|0.0.1783414941' packages/atlas/graph

Expected result today: npm reports 0.0.1783414941-g212a2a; the repo has no matching committed graph record.

Related Issues/PRs

• Track Amp CLI 0.0.1783329373-gb3eec2 upstream release #1196 tracks previous Amp CLI 0.0.1783329373-gb3eec2.
• Track Amp CLI 0.0.1783228622-g9b591b upstream release #1183 tracks previous Amp CLI 0.0.1783228622-g9b591b.
• Track Amp CLI 0.0.1783069983-gce9c8b upstream release #1127 tracked previous Amp CLI 0.0.1783069983-gce9c8b.
• PR Track upstream agent CLI versions #990 was the broader upstream agent-version tracking work.

Priority

• low: this is catalog freshness work, not a production blocker.

Risk Analysis

• Risk Level: risk:low
• Unsupported behavior assumptions
  • Mitigation: only record package metadata and explicit no-change findings unless public release notes appear.
• Atlas consistency drift
  • Mitigation: mirror existing AgentVersion YAML shape, keep version_of/sourced_from edges coherent, and run graph validation.