[pamelachia]

I moved plan-gate handling out of each command into shared code. Since #7271, mapHttpError attaches entitlement from the Management API's entitlement_required body, so the upgrade hint, the cli_upgrade_suggested event and the plan_limit classification now all come from that one field, with no per-command wiring and no extra requests.

Changed:

• One hint and one event per gated denial, wired or not: the text error renderer prints the upgrade hint before the error message, and withCommandTelemetry captures cli_upgrade_suggested (same name, same {feature_key, org_slug} payload) after the command, just before cli_command_executed. Commands that never had wiring, such as branches unpause, now get both. vanity-subdomains check-availability now fires the event too; its no-event exception only existed for parity with the removed Go CLI.
• No per-command gate code or follow-up lookups: I deleted the gateMapError/suggestUpgrade wrapping at branches create/update, the four domains commands and the three vanity-subdomains commands. branches update no longer fetches the project and org entitlements after a 4xx, since the persistent-branch 402 carries the envelope. Only the SSO commands keep the entitlements lookup.
• plan_limit from the envelope: an error carrying entitlement classifies as plan_limit whatever its class declares, so gated denials from branches unpause, domains get/create/activate/reverify and vanity-subdomains get move from api_status to plan_limit (fingerprint suffix :api_status becomes :plan_limit).

Note: the event moved from mid-handler to post-run. Payload and identity stay the same; it uses the same capture context as cli_command_executed.

Linear

• part of GROWTH-1050

[pamelachia]

Manual check from source against a Free-plan project (<ref>, org <org>), run on the earlier head that also added a source param to the link. That change is now dropped; the request count, the hint and the entitlement field don't depend on it.

• branches create gate-probe --project-ref <ref> --yes --debug: one POST /v1/projects/<ref>/branches (402), then the hint printed once with the org's billing URL. Passed.
• Same command with --output-format json: error.entitlement is {"feature":"branching_limit","upgrade_url":".../org/<org>/billing..."}. Passed.
• branches update <branch> --persistent not run live: Pro and Team orgs have the persistent-branch entitlement and Free orgs can't create branches, so only a Free org that still has a branch reaches this 402, and no test org is in that state. update.integration.test.ts covers one PATCH carrying the 402 envelope.