Printable idea sheet
extension_installation
reqlan rq/extension/installation.rq:31
Extension-level install covers packing, activation, and first-run host UX — not base filesystem state.
There is * * no * * VS Code `onInstall` API; install-time behaviour runs on the * * first * * activation after install ( activation_events ).
Sequencing inside `activate` is owned by activation_sequence:
- Sync register CodeLens / inlay config commands.
- Synchronously register analytical submodule contributions ( commands, activity bar, chat, webviews, AI commands, mutation hooks ) without starting the index ( analytical_submodule_activation ).
- Register import quick-fixes, then schedule index and language-client startup through first_paint_startup / background_startup; sync catalogs once the language client exists.
- Fire-and-forget onboarding_check → welcome_webview_install.
Failures in submodule or language client are logged and must not abort later phases or the welcome check.
Related command surfaces: Show Onboarding ( show_onboarding_command ), Install Cursor Skills ( cursor_skills_install ), Create Base ( create_base_onboarding ).
Interactive page: extension_installation