Document how the local AgentV Dashboard and GitHub-backed run artifacts fit together after the 2026-06-20 decision that AgentV does not need AgentV-to-Phoenix export/projection. Make the package and frontend-stack boundaries explicit: keep apps/dashboard as the private workspace dashboard package, keep the current Vite/React/TanStack Router/Query SPA stack, and do not split/publish a separate npm package or migrate to TanStack Start until there is a concrete second runtime consumer or SSR/full-stack requirement. Document the allowed Phoenix correlation path: if Codex/Arize hooks already emit spans to Phoenix, AgentV may store safe external_trace metadata and optionally read the linked Phoenix session through GraphQL/API, but does not export AgentV artifacts to Phoenix.
Document how the local AgentV Dashboard and GitHub-backed run artifacts fit together after the 2026-06-20 decision that AgentV does not need AgentV-to-Phoenix export/projection. Make the package and frontend-stack boundaries explicit: keep apps/dashboard as the private workspace dashboard package, keep the current Vite/React/TanStack Router/Query SPA stack, and do not split/publish a separate npm package or migrate to TanStack Start until there is a concrete second runtime consumer or SSR/full-stack requirement. Document the allowed Phoenix correlation path: if Codex/Arize hooks already emit spans to Phoenix, AgentV may store safe external_trace metadata and optionally read the linked Phoenix session through GraphQL/API, but does not export AgentV artifacts to Phoenix.