Track Amp CLI 0.0.1786162957-g48b3cf

[a5c-ai]

Version

• Previous graph version: 0.0.1784264425-g070593
• Latest upstream version: 0.0.1786162957-g48b3cf
• Package metadata: https://www.npmjs.com/package/@ampcode/cli/v/0.0.1786162957-g48b3cf

Actual changes researched

• npm reports @ampcode/cli latest as 0.0.1786162957-g48b3cf, published on 2026-08-08.
• npm description identifies the package as the CLI for Amp, the frontier agent.
• I did not find public build-specific release notes or a changelog for this timestamped build.
• No confirmed CLI flag, transport/API, model, package-name, install-method, or migration change was found.

Likely affected system surfaces

• Version catalog only unless private/vendor notes surface additional changes.
• Keep adapter install command as npm install -g @ampcode/cli.

Install/migration

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

Assimilation checklist

• Record @ampcode/cli 0.0.1786162957-g48b3cf in AgentVersion graph.
• Re-check vendor/private notes before changing launchBehavior or transport metadata.
• Leave Amp adapter install metadata unchanged: npm install -g @ampcode/cli.

[a5c-ai]

Triage Summary

Track the latest @ampcode/cli timestamped npm release in Atlas graph/catalog metadata; no runtime adapter behavior change is currently supported by public evidence.

Critical Evaluation

• Reporter's analysis is accurate: npm package metadata identifies @ampcode/cli 0.0.1786162957-g48b3cf as the upstream version to record.
• This is an enhancement/catalog-maintenance issue, not a runtime bug.
• The requested install metadata stance is correct: keep npm install -g @ampcode/cli unless vendor/private notes show a migration.

Root Cause Analysis

Affected files and graph surfaces:

• 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
• packages/atlas/graph/agent-stack/versions/amp-current.yaml
• packages/atlas/graph/tests/claims/amp-current-release-tracking.test.cjs
• packages/atlas/graph/agent-stack/products/amp.yaml

Current evidence:

• Repository search found no 0.0.1786162957-g48b3cf graph record.
• The latest dated upstream Amp record still points at 0.0.1784264425-g070593.
• The long-lived agent-version:amp@current record still points at 0.0.1780032159-g3925ab.
• The existing Amp current tracking test is stale relative to the newer dated upstream records, so implementation should decide whether to refresh that guardrail as part of this update.

Affected Components

• Packages: @a5c-ai/atlas, agent catalog consumers
• Components: atlas, agent-catalog
• Effort: effort:small

Recommended Approach

1. Re-check npm package metadata and any available vendor/private notes for @ampcode/cli 0.0.1786162957-g48b3cf immediately before editing.
2. Add or refresh the Amp AgentVersion and matching EvidenceSource metadata for the new version.
3. Preserve install metadata: npm install -g @ampcode/cli.
4. Do not change launch behavior, transport/API, model metadata, auth, MCP, package name, or migration metadata unless evidence explicitly supports it.
5. Check both the dated upstream-current records and agent-stack/versions/amp-current.yaml for consistency.
6. Refresh or add the relevant Amp graph guardrail test, then run targeted Atlas graph/catalog verification.

Reproduction

Run a repository search for 0.0.1786162957-g48b3cf, 1786162957, or g48b3cf under packages/atlas/graph; no current graph record is present. Compare the existing Amp entries in upstream-current-2026-07-17.yaml, which still record 0.0.1784264425-g070593.

Related Issues/PRs

• Track Amp CLI 0.0.1786162957-g48b3cf #1684 has the same version/title but was already closed as duplicate of Track Amp CLI 0.0.1786162957-g48b3cf #1689, so Track Amp CLI 0.0.1786162957-g48b3cf #1689 is the active canonical issue.
• Track Amp CLI 0.0.1786077520-gcc65e7 #1670 tracks the previous open Amp CLI version 0.0.1786077520-gcc65e7.
• No closed PR was found for 0.0.1786162957-g48b3cf.

Priority

priority:low - metadata freshness work for Atlas/catalog. It is useful and ready, but not production-blocking and has no known user-facing runtime impact.

Risk Analysis

Risk level: risk:low

• Incorrect upstream metadata if npm/private vendor evidence is not rechecked before implementation.
  • Mitigation: Re-query npm and vendor/private notes immediately before editing, and cite evidence in the EvidenceSource record.
• Stale parallel current-version records or tests if only one graph path is updated.
  • Mitigation: Check dated upstream records, amp-current.yaml, product references, and the Amp graph test together.
• Over-modeling unsupported behavior changes from a version bump alone.
  • Mitigation: Preserve existing install/runtime metadata unless source evidence confirms a change.

[a5c-ai]

Triage Summary

• One-line: Track the latest Amp CLI npm release in the Atlas agent-version graph.

Critical Evaluation

• Reporter analysis is accurate: npm has a newer @ampcode/cli timestamped build, and the issue correctly scopes the likely change to catalog/version metadata unless private/vendor notes show more.
• This is not a runtime bug. It is recurring upstream-release assimilation work.
• Track Amp CLI 0.0.1786162957-g48b3cf #1684 is an exact duplicate, but it is already closed as duplicate of this issue, so Track Amp CLI 0.0.1786162957-g48b3cf #1689 is the canonical tracker.

Root Cause Analysis

• Affected paths: 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, and related Atlas graph/catalog tests.
• Existing Amp graph records still reference older releases such as 0.0.1784264425-g070593.
• Search found no tracked occurrence of 0.0.1786162957-g48b3cf or 1786162957 in the graph/catalog.
• Adapter install metadata already uses npm install -g @ampcode/cli and should remain unchanged unless new vendor evidence says otherwise.

Affected Components

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

Recommended Approach

• Add an AgentVersion record for Amp CLI 0.0.1786162957-g48b3cf using the existing upstream-current graph pattern.
• Add matching EvidenceSource metadata pointing to the npm package version page.
• Preserve cliCommand amp, install:npm, and npm install -g @ampcode/cli.
• Explicitly record that no public build-specific changelog, CLI flag, transport/API, model, package-name, install-method, or migration change was found.
• Run the relevant Atlas graph/catalog checks after the graph update.

Reproduction

Search tracked packages for 0.0.1786162957-g48b3cf or 1786162957. The current repo has no graph/catalog record for this release.

Related Issues/PRs

• Track Amp CLI 0.0.1786162957-g48b3cf #1684: exact duplicate, already closed as duplicate of Track Amp CLI 0.0.1786162957-g48b3cf #1689.
• Track Amp CLI 0.0.1786077520-gcc65e7 #1670: previous Amp CLI tracker for 0.0.1786077520-gcc65e7.

Priority

• priority:low
• Reasoning: narrow catalog metadata assimilation; no runtime breakage or adapter behavior change is indicated.

Risk Analysis

• Risk Level: risk:low
• Overstating behavior changes when public release notes are absent
  • Mitigation: use npm metadata only and avoid claims about CLI behavior changes without vendor evidence.
• Creating duplicate or conflicting graph records
  • Mitigation: follow existing AgentVersion/EvidenceSource naming conventions and search for the target version before writing.
• Accidental adapter metadata churn
  • Mitigation: keep adapter install and launch metadata unchanged unless stronger evidence is found.