Skip to content

Certify Amp adapter against the v1 approval contract #276

Description

@gongahkia

Decision

Retain Amp and raise it from its current installed integration to the same evidence-backed certified-adapter standard as Claude, Codex, and Pi.

Current state

Amp already has an Onibi plugin with lifecycle events and blocking tool.call approvals, including allow, deny, expiry, and JSON-object edit mapping. It is not represented by the v1 certified adapter contract.

Certification requirements

  • Verify the current official Amp plugin/hook API and supported versions before changing product claims.
  • Add a versioned adapter contract/capability report with managed idempotent install/uninstall, backups/integrity/drift reporting, approval semantics, lifecycle/recovery limits, and audit/redaction behavior.
  • Demonstrate approve, deny, expiry, edit, daemon-unavailable, timeout, restart, and session-replacement behavior using provider-shaped fixtures; add a secret-gated live evidence path.
  • Ensure onibi adapters --json, hooks --show, and doctor accurately report the supported version and any limitations.

Promotion gate

Do not mark Amp certified until every contract claim has local tests, a documented live verification result, and review. Do not hide unsupported provider behavior behind a generic parity claim.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions