# Agent9 Provider Operation Parity

<!-- auto-oncall-optimization-record
{
  "schemaVersion": "auto-oncall-optimization-record-v1",
  "optimizationId": "agent9-provider-operation-parity-2026-08-18",
  "problems": [
    {
      "problemId": "agent9-managed-tools-lack-diagnostic-source-parity",
      "summary": "The first Agent9 Clinic Tool exposed only metadata, components, and metrics, while the Wetech Tool exposed only one fixed CPU query, so switching the diagnostic pipeline would remove load-bearing TopSQL, Slow Query, SQL, logs, activities, Statements, and general metric acquisition.",
      "status": "candidate",
      "applicability": "Agent9-managed Clinic or Wetech evidence acquisition for scenarios whose load-bearing question requires a source already supported by the legacy Provider Executor but absent from the first Managed Tool packages.",
      "issueKeys": [],
      "sourceRefs": [],
      "signalTextIncludesAny": [
        "agent9 managed tool operation unavailable",
        "agent9 provider source parity",
        "managed wetech query is unavailable"
      ],
      "observedThrough": "2026-08-18",
      "effectiveAt": null,
      "verifiedAt": null,
      "attemptedAction": "Expand Clinic to bounded TopSQL, read-only SQL, tier-aware Slow Query, logs, and activities; expand Wetech to bounded Agent-authored PromQL and TiDB Dashboard TopSQL, Statements, and Slow Query while preserving compact redacted output and exact target/window binding.",
      "evidenceUrl": null
    }
  ]
}
-->

- Owner: Evidence Agent Tool schemas and Agent9 Provider Executor packages
- Source: Agent9 auto-oncall migration readiness review
- Implementation status: in progress
- Effective status: `candidate`

## Bounded capability gap

Agent9 already provides the correct Evidence Agent and isolated Tool execution
boundary. The first Clinic and Wetech packages did not yet expose the provider
sources used by the existing diagnostic scenarios. A transport cutover would
therefore have been structurally valid but diagnostically narrower.

## Candidate change

- Clinic owns bounded metadata, components, PromQL, canonical TopSQL,
  partition-bounded read-only SQL, tier-aware Slow Query, Loki, and activities.
- Wetech owns bounded Agent-authored PromQL plus TiDB Dashboard TopSQL,
  Statements, and Slow Query.
- Raw SQL and Slow Query text do not cross the Tool boundary. Digests and
  provider identities are materialized as opaque references.
- Agent9 remains the generic package registry and isolated executor; it does
  not decide provider semantics or ticket policy.

## Verification status

Local package tests cover immutable package digests, exact operation schemas,
free bounded PromQL, canonical TopSQL construction, partition-bounded Slow
Query execution, and digest redaction. The change is not effective until the
packages are merged, published, loaded into Agent9 internal prod, installed on
the auto-oncall Agent with matching Auth, and exercised through live provider
smoke.

## Unresolved gaps

- The active Wetech Auth bundle does not yet include the two Dashboard secret
  keys required by the expanded package.
- Provider-specific live smoke and an Agent9-backed case replay have not run.

## Next validation action

Merge and publish the immutable packages, update the Agent-scoped Auth and
installation through the normal Agent9 API, then run one bounded Clinic,
Wetech metrics, Wetech Dashboard, and Manus smoke before enabling the passive
auto-oncall Agent9 runtime.