Split capability taxonomy so every user-facing command has its own dashboard wedge (main-ca)

[amilandi]

Ports PR #259 (which targets main) to main-ca so CEA-agent installations get the same split-per-command adk_capability taxonomy.

Cherry-picked commits from amilandin/split-capability-taxonomy-per-command:

• de7c946 — original split
• 6818aaf — update taxonomy header comment for the new not in <blank> dashboard filter
• fd89c19 — review-round-2 fixes: reverse capability check + fix wired comment group

Changes

Before	After
evaluations	evaluation_create, evaluation_update, evaluation_delete, evaluation_validate
publishing (push + publish)	push (push.py) + publishing (publish.py)
(no wedge)	onboarding, topic_review, topic_test, workflow_test

Conflict resolved during cherry-pick

src/skills/evaluations/update/SKILL.md — kept main-ca''s "workspace-only updates, do not require an agent checkpoint" note and the separate telemetry code block, applied the new evaluation_update label from #259.

Dashboard follow-up (already applied in prod)

The Aria "Capability Usage by Type" and "Capability Usage by Type Trend" tiles were switched from an explicit in {value-list} filter to not in <blank> on 2026-09-22 (all four tiles: ADK Platform + ADK Platform External, donut + trend). New capabilities from this PR — including push — auto-appear on the donut; verified with real emits from a maker environment.

Still to double-check: any Build Outcomes / Agent Deploy tile that filters specifically on adk_capability="publishing" should be extended to include "push" (or switched to not in <blank> too), since push.py events are now stamped "push" instead of "publishing".

Tests

• New tests/test_adk_telemetry.py::test_every_canonical_capability_is_actually_emitted — reverse-direction check: fails on any canonical value with no emit site anywhere in the kit. Passes on main-ca (all values, including onboarding, are wired).
• Existing test_wired_capabilities_are_in_canonical_list — updated comment groups to reflect that publish.py emits via the shim, not via emit_build_*.
• pytest tests/test_adk_telemetry.py tests/scripts/test_push_scope.py -> 169 passed.

Companion PR on main

#259

ADO

https://o365exchange.visualstudio.com/O365%20Core/_workitems/edit/7830948

[Dawn Jeong (daeunJe0ng)]

[copilot-review]

Approve. Clean taxonomy split, and I verified it on the target branch: checked out the head (6818aaf) and ran pytest tests/test_adk_telemetry.py tests/scripts/test_push_scope.py, 168 passed. Confirmed publish.py emits publishing and push.py emits push on main-ca, so both wedges are populated and nothing is orphaned. Every canonical capability has a real emitter.

One follow-up to make sure doesn't get lost, since it lives outside this diff. Your commit message calls it out, but the PR description doesn't: the not in <blank> change only covers the Capability Usage donut. The Aria Build Outcomes and Agent Deploy tiles that filter on adk_capability = "publishing" still need updating, because push.py's emit_build_start / emit_build_complete / emit_agent_deploy events are now stamped push, not publishing. Until those tiles include push (or split into push vs publish), push build/deploy activity will silently drop off them. Worth adding to the PR description so a reviewer or dashboard owner picks it up.

Two optional nits, neither blocking:

• In test_wired_capabilities_are_in_canonical_list, publishing is grouped under the emit_build_*/flightcheck_* comment, but after this change publishing only comes from publish.py's emit_capability.py shim. Moving it next to the shim group keeps the comment accurate.
• The wired test asserts wired is a subset of canonical, so it won't catch a canonical value that no code emits. The #254 shim guard already covers arg drift, so this is just belt-and-suspenders.

[amilandi]

Addressed the two nits in fd89c19:

• Comment placement — moved publishing from the emit_build_*/flightcheck_* group to the shim group in the wired set; publish.py invokes the emit_capability.py shim via subprocess (publish.py:367-368), it doesn't call emit_build_* directly. Also added the same reverse-direction test as Split capability taxonomy so every user-facing command has its own dashboard wedge #259.
• PR body — added a callout that any Build Outcomes / Agent Deploy tile filtering specifically on adk_capability="publishing" still needs "push" added (or the not in <blank> swap).

pytest tests/test_adk_telemetry.py tests/scripts/test_push_scope.py -> 169 passed.

[Dawn Jeong (daeunJe0ng)]

[copilot-review] Approve.

Re-reviewed at current head. Clean port of #259 to main-ca. Both prior nits (publishing comment grouping, reverse-direction test) are resolved in-diff. No code-side blockers.

Same operational follow-up as #259: reconcile any Aria Build Outcomes / Agent Deploy tile filtered on adk_capability="publishing" to include "push". Tracked separately since CI can't catch it.