BotBuilderJS to Agents SDK migration

Target AgentApplication and preserve observable behavior. Always assess and report before editing. Use migration-map.md as the primary reference; search it for each detected package, class, method, property, or handler.

Workflow

1. Inspect the bot's packages, imports, entry points, handlers, state, middleware, hosting, authentication, tests, and deployment files.
2. Inventory every Bot Framework symbol and behavior. Classify each item with the migration map:
   • Direct: replace the package or API while preserving the design.
   • Rewrite: implement the supported AgentApplication pattern.
   • Decision: verified SDK-supported choices exist, but the user must select one.
   • Unsupported: no verified stable Agents SDK for JavaScript equivalent exists.
3. Produce the migration plan in the format below. Do not edit project code during this assessment phase.
4. Stop and ask which numbered Direct and Rewrite items to implement and which Decision choices to make. Exclude Unsupported items from implementation.
5. After explicit selection, confirm the assessed files, dependencies, and scope have not changed. If they changed, refresh the plan and obtain a new selection. Otherwise, implement only the selected items and update the lockfile.
6. Run the project's build/type-check, lint, and tests. Start the service and exercise the message endpoint and affected custom, invoke, storage, and proactive paths when possible.
7. Report migrated items, decisions still required, unsupported behavior left unchanged, and validation results.

If multiple bots are present and scope is unclear, ask which bot to assess before step 2.