Complete legacy capability expansion

[adrianwebb]

Outcome

All legacy activity profiles can participate in standardized capability routing during the v4-to-v5 migration, not only chat profiles.

Work authority

• Work item / Issue: User-directed capability marketplace completion audit
• Proposal / decision: Capability-Driven Capacity Marketplace implementation plan in the active TreeSeed task
• Assignment / checkpoint: SDK architect send send-ab88274fd8fc83ed0ef886d2d8ccfd09
• Actor: Codex /root
• Human authority: @adrian
• Agent / capacity provider: Codex / local development capacity provider
• Exact base ref: staging c277e83
• Exact head ref: codex/complete-legacy-capability-expansion c74a94f

Contributor mode (select one):

• Human-authored
• Agent-assisted under human authority
• Agent-authored under human authority

Plan

Audit every activity-derived legacy capability, expand provider supply through the SDK canonical translation for all activity types, and retain exact v5 identities unchanged.

Changes and commits

Commit c74a94f expands generic agent-execution into conversation, planning, estimation, review, code-change, and reporting identities and preserves repository-work dual semantics during migration.

Verification

• I ran the narrowest relevant package verification and documented any checks that could not be run.
• npm run verify: 64 test files and 198 tests passed; distribution build and architecture checks passed.

Risk and rollback

Expansion applies only to values recognized by the centralized SDK legacy resolver and only supports the explicitly temporary no-offer bridge. Revert c74a94f to restore rc55 behavior.

Completion summary

The legacy supply bridge now covers all activity-derived standardized capabilities. Terminal conversation runs without assignments now fail their invocation and publish a visible lifecycle event instead of hanging send. Native v5 providers still require negotiated offers.

AGPL committer authorization

The base-owned workflow checks the authenticated pull-request author.

Submission checklist

• The change is bounded to the stated work item and target repository.
• Exact base and head refs are recorded and the branch is ready for review.
• Verification and compatibility evidence are recorded above.
• No plaintext secrets, credentials, machine state, or unrelated residue are included.
• Plan, status, commits, and completion summary form a complete durable record.
• Rollback or recovery steps are documented and executable.