[sorccu]

Affected Components

• CLI
• Create CLI
• Test
• Docs
• Examples
• Other

checkly validate, test and deploy (and every other command that validates the project, such as pw-test and import plan) now fail for a SlackAppAlertChannel with Slack destinations when the account has no Checkly Slack app connected:

SlackAppAlertChannel 'ops-slack' needs the Checkly Slack app, which is not connected to this account, so its alerts cannot be delivered.

Hint: Connect the Checkly Slack app at https://app.checklyhq.com/accounts/<id>/settings/account/integrations, or remove the channel.

It's an error rather than a warning on purpose. A Slack App channel without the app delivers nothing, and that includes a channel deployed before the app was disconnected. A warning printed in CI output goes unseen.

How it works

• The account the CLI already loads at startup reports a new field, integrations: [{ type, connected }], listing every integration type the API reports. AuthCommand now keeps the whole account on Session.account, so the check reads integrations and the account ID for the link from there.
• SlackAppAlertChannel.validate() adds the error when the SLACK entry says connected: false. When the API doesn't send the field, or lists no SLACK entry, the check is skipped, so the CLI never refuses an integration the API doesn't report.
• The advanced project templates no longer construct a Slack App channel; it's commented out with a note that it needs the app. Without this, a freshly created project would fail checkly test on any account without the app.
• The AI-context guidance that recommends SlackAppAlertChannel now says it needs the app.

Other changes

• Session.accountFeatures is gone; the response time limits read Session.account?.features instead. The behaviour is unchanged: no account, or no features, means the standard limits.

Notes for the Reviewer

• Depends on a backend change (RED-1289) that adds integrations to the account routes. It isn't merged or deployed yet. Merging this first is safe, because the check stays off until the backend sends the field. In practice it takes effect once both the backend deploy and a CLI release are out.
• Behaviour change for existing projects. A project with a Slack App channel on an account whose app is disconnected starts failing test and deploy, including a deploy that leaves the channel unchanged, which Checkly itself would accept. This PR doesn't use the ! marker that previous changes like this used in 10.0.0. Decide whether it should be marked breaking.
• Stored credentials, not a live check. SLACK reflects what Checkly has stored. An app uninstalled on the Slack side still reads as connected.

Testing

src/constructs/__tests__/slack-app-alert-channel.spec.ts covers five cases:

• refused, with the message and link;
• accepted when connected;
• skipped when the field is absent;
• skipped when no SLACK entry is listed;
• accepted without Slack destinations.

The construct, command and REST suites pass (1,785 tests) and tsc -p tsconfig.json --noEmit is clean. No test covers the wiring from AuthCommand into Session.account.

🤖 Generated with Claude Code