{"version":"2.1.265","anchor":"design-removed-as-a-standalone-cli-action-while-design-con","canonical_anchor":"design-removed-as-a-standalone-cli-action-while-design-con","heading":"\"design\" removed as a standalone CLI action while design-consent\/revoke\/login remain","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/design-removed-as-a-standalone-cli-action-while-design-con","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### \"design\" removed as a standalone CLI action while design-consent\/revoke\/login remain\n\nPlain \"design\" CLI action removed while design-consent, design-revoke and design-login remain\n\n**Unclear.** What the standalone \"design\" action did, and whether it was actually reachable as a command, is not stated.\n\n**What**\n\nThe internal list of CLI command categories no longer includes a standalone `design` entry. The related `design-consent`, `design-revoke`, and `design-login` actions are still present and unaffected.\n\n**Why**\n\nThe finding does not explain what the plain `design` action did or why it was dropped, only that it is no longer in the category map while its related subcommands remain.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}