migrate-application-operation

Inventory every entry point, freeze legacy observable behavior with characterization tests, define one semantic operation in the domain registry, then implement an authorized workspace use case that each surface adapter calls. Preserve each surface's own contract and presenter.

Create one domain-level Copilot application adapter with createCopilotApplicationAdapter that builds the delegated Principal from trusted server-authored context and calls the exact application use case. Never construct delegation from model-provided workspace IDs, operation IDs, or permission tags.

Yes, both surfaces must call the same application use case so authorization and business behavior stay identical, while authentication, rate limiting, contracts, and response presenters remain surface-specific. Never create internal- or public-specific versions of the same semantic operation.

Upload or multipart lifecycles, large bodies, binary or streaming responses, bulk or recursive operations, polymorphic tools, and multi-resource transactions require explicit special-case handling. Stop and report a missing design rather than weakening identity, authorization, limits, or error behavior.

Moving legacy steps under a shared wrapper can change authorization order, audit timing, error mapping, or partial-failure state even when individual calls are reused. Characterization tests pin down exact inputs, statuses, side effects, and response shapes before editing.