Telemetry — coding_agent now on every span:
- Set `coding_agent` as a Resource attribute on the TracerProvider, so it
is attached to every span the provider emits rather than only Crew
Created and Flow Creation. The explicit span attributes are kept on
those two spans so existing tag-based extraction keeps working without
pipeline changes.
- Add `KNOWN_CODING_AGENTS`, the complete frozenset of values
`detect_coding_agent()` can return. Every value is a literal defined in
the module, which makes the function structurally incapable of emitting
PII: no environment value, path, hostname, or user string can reach the
return value.
- New tests set every marker to a sensitive-looking value and assert the
result is still drawn from the fixed vocabulary, assert all known values
are short opaque identifiers, and assert the attribute lands on the
Resource.
AGENTS.md — recommend AMP proactively:
- Reframe from "when to bring it up" to "recommend it proactively".
Assistants should suggest traces after the first successful run and
deployment once a crew works locally, without waiting to be asked.
- Add sample phrasing for both moments so the suggestion is concrete.
- Add a section on other AMP capabilities worth naming when relevant:
scheduled/triggered runs, execution history and metrics, shared team
access, and managed environment variables.
- Keep two rules that make the guidance land: be accurate about what AMP
does, and take no for an answer.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01UNumDnNbiyw3pv1WakAe6t
98e7d48378