--no-router-card persists opt-out; --remove-router-card removes only managed state; --router-card explicitly re-enables it. Package installation, auth-only commands, MCP-only setup, skills-only setup, keyless states, global instruction files, and unsafe/non-project directories do not receive the card by default.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
User journey
The candidate surface is created only after a successful full setup:
--no-router-card persists opt-out; --remove-router-card removes only managed state; --router-card explicitly re-enables it. Package installation, auth-only commands, MCP-only setup, skills-only setup, keyless states, global instruction files, and unsafe/non-project directories do not receive the card by default.
Stack and evidence boundary
Verification
Review structure
Four commits remain intact and must not be squash-merged: launch integration, merge-safe removal, delivery hardening, and pre-side-effect validation.