Summary

AgentV no longer carries the private Phoenix adapter experiment as a workspace package. The package was private, unpublished, absent from the release publish list, and conflicted with the current Phoenix boundary: AgentV artifacts stay local/Git-backed, while Phoenix is only optional link-out context for independently emitted traces.

This removes packages/phoenix-adapter, drops the adapter from root build/typecheck/test scripts and CI smoke coverage, and refreshes bun.lock so the Phoenix/Arize dependency chain is no longer installed. It also updates stale ADR/plan language so future work does not revive Phoenix as an AgentV dataset, experiment, result, trace, or storage projection path.

Verification

• bun install
• bun run build
• bun run typecheck
• bun run lint
• bun run test
• bun scripts/validate-eval-dirs.ts
• bun apps/cli/dist/cli.js validate 'examples/features/**/evals/**/*.eval.yaml' 'examples/features/**/*.EVAL.yaml'
• git diff --check
• bun install --frozen-lockfile --dry-run
• rg checks for stale @agentv/phoenix-adapter, packages/phoenix-adapter, root Phoenix smoke script, and package export symbols
• Read-only review agents checked dependency/workspace safety, CI/release/testing risk, and Phoenix product-boundary docs; docs findings were addressed before commit

Risk

The supported Phoenix link-out path remains intact through external_trace metadata and Dashboard URL sanitization. The main residual risk is a private internal workflow that imported the deleted workspace package by path; that package was marked private: true, was not published to npm, and was not in the release package list.

Post-Deploy Monitoring & Validation

No additional production monitoring required because this removes an unpublished private workspace package and CI-only smoke path. Validate through GitHub Actions on the PR:

• Logs to watch: CI Install dependencies, Build packages, Typecheck packages, Run tests, and Validate Evals for missing @agentv/phoenix-adapter workspace/filter errors.
• Healthy signals: frozen install succeeds, root build/typecheck/test scripts do not reference the deleted workspace, eval schema validation remains green.
• Failure signals: bun --filter @agentv/phoenix-adapter errors, lockfile frozen-install failures, or imports resolving to the deleted package.
• Mitigation trigger: if CI or review identifies a still-supported consumer, revert this deletion and replace it with a deprecation/removal plan.
• Validation window/owner: PR author watches initial PR CI run through completion.