installation_sequencing

End-to-end first-run story ( typical editor user ):
1. User installs the extension from Marketplace / Open VSX / VSIX ( extension_installation ).
2. Host fires an activation_events match ( usually `onStartupFinished` ).
3. activation_sequence synchronously registers contributions and schedules background_startup; onboarding_check may open installation_event ( Welcome to Reqlan webview ) without blocking activation.
4. If no `.reqlan` exists under workspace folders, surfaces offer create-base ( create_base_onboarding ) — user-driven, never auto-created on extension install.
5. base_installation seeds config / ignore / marker; index activate / sync follows ( application_memory ).
6. Optionally, user runs Install Cursor Skills ( workspace_agent_files ) — copies rq- * skills and may update `.cursor/mcp.json`; independent of `.reqlan` seeding.
Ordering constraint: steps 1 – 3 are extension-scoped; steps 4 – 5 are base-scoped; step 6 is workspace agent tooling scoped to the open folder, not the `.reqlan` directory.

Interactive page: installation_sequencing