fix: update reference docs in checkly.rules.md

Author: stefanjudis

packages/cli/src/rules/checkly.rules.template.md

@@ -2,9 +2,9 @@
 
 - Refer to docs for Checkly CLI v6.0.0 and above.
 - Check the Checkly CLI output to figure out into which folder the setup was generated.
-- Use the [Checkly CLI reference documentation](https://www.checklyhq.com/docs/cli/command-line-reference).
-- Use the [Checkly construct reference documentation](https://www.checklyhq.com/docs/cli/constructs-reference).
-- Import and / or require any constructs you need in your code, such as `ApiCheck`, `BrowserCheck` from the `checkly/constructs` package.
+- Use the [Checkly CLI reference documentation](https://www.checklyhq.com/docs/cli/overview/).
+- Use the [Checkly construct reference documentation](https://www.checklyhq.com/docs/constructs/overview/).
+- Import and / or require any constructs you need in your code, such as `ApiCheck`, `BrowserCheck`, or `PlaywrightCheck` from the `checkly/constructs` package.
 - Always ground generated code and CLI commands against the official documentation and examples in this file.
 
 ## Installing the Checkly CLI
@@ -38,8 +38,8 @@ The `checkly.config.ts` at the root of your project defines a range of defaults
 ### API Check
 
 - Import the `ApiCheck` construct from `checkly/constructs`.
-- Reference [the docs for API checks](https://www.checklyhq.com/docs/cli/constructs-reference/#apicheck) before generating any code.
-- When adding `assertions`, always use `AssertionBuilder` class for API Checks which are [documented here](https://www.checklyhq.com/docs/cli/constructs-reference/#assertionbuilder).
+- Reference [the docs for API checks](https://www.checklyhq.com/docs/constructs/api-check/) before generating any code.
+- When adding `assertions`, always use `AssertionBuilder` class for API Checks.
 - When referencing environment variables always use the handlebar syntax `{{MY_ENV_VAR}}`.
 - When referencing secrets always use the handlebar syntax `{{MY_SECRET}}`.
 - If endpoints require authentication ask the user which authentication method to use and then generate a setupScript to authenticate the given requests.
@@ -60,7 +60,7 @@ The `checkly.config.ts` at the root of your project defines a range of defaults
 ### Browser Check
 
 - Import the `BrowserCheck` construct from `checkly/constructs`.
-- Reference [the docs for Browser checks](https://www.checklyhq.com/docs/cli/constructs-reference/#browsercheck) before generating any code.
+- Reference [the docs for Browser checks](https://www.checklyhq.com/docs/constructs/browser-check/) before generating any code.
 - Generate a separate `.spec.ts` file for the Playwright code referenced in the `BrowserCheck` construct.
 - Use the `code.entrypoint` property to specify the path to your Playwright test file.
 
@@ -71,7 +71,7 @@ The `checkly.config.ts` at the root of your project defines a range of defaults
 ### MultiStep Check
 
 - Import the `MultiStepCheck` construct from `checkly/constructs`.
-- Reference [the docs for Multistep checks](https://www.checklyhq.com/docs/cli/constructs-reference/#multistepcheck) before generating any code.
+- Reference [the docs for Multistep checks](https://www.checklyhq.com/docs/constructs/multistep-check/) before generating any code.
 - Generate a separate `.spec.ts` file for the Playwright code referenced in the `MultiStepCheck` construct.
 - Use the `code.entrypoint` property to specify the path to your Playwright test file.
 
@@ -82,8 +82,8 @@ The `checkly.config.ts` at the root of your project defines a range of defaults
 ### TCP Monitor
 
 - Import the `TcpMonitor` construct from `checkly/constructs`.
-- Reference [the docs for TCP monitors](https://www.checklyhq.com/docs/cli/constructs-reference/#tcpmonitor) before generating any code.
-- When adding `assertions`, always use `TcpAssertionBuilder` class for TCP monitors which is [documented here](https://www.checklyhq.com/docs/cli/constructs-reference/#tcpassertionbuilder)
+- Reference [the docs for TCP monitors](https://www.checklyhq.com/docs/constructs/tcp-monitor/) before generating any code.
+- When adding `assertions`, always use `TcpAssertionBuilder` class for TCP monitors.
 
 ```typescript
 // INSERT TCP MONITOR EXAMPLE HERE //
@@ -92,8 +92,8 @@ The `checkly.config.ts` at the root of your project defines a range of defaults
 ### URL Monitor
 
 - Import the `UrlMonitor` construct from `checkly/constructs`.
-- Reference [the docs for URL monitors](https://www.checklyhq.com/docs/cli/constructs-reference/#urlmonitor) before generating any code.
-- When adding `assertions`, always use `UrlAssertionBuilder` class which is [documented here](https://www.checklyhq.com/docs/cli/constructs-reference/#urlassertionbuilder)
+- Reference [the docs for URL monitors](https://www.checklyhq.com/docs/constructs/url-monitor/) before generating any code.
+- When adding `assertions`, always use `UrlAssertionBuilder`.
 
 ```typescript
 // INSERT URL MONITOR EXAMPLE HERE //
@@ -102,8 +102,8 @@ The `checkly.config.ts` at the root of your project defines a range of defaults
 ### DNS Monitor
 
 - Import the `DnsMonitor` construct from `checkly/constructs`.
-- Reference [the docs for DNS monitors](https://www.checklyhq.com/docs/cli/constructs-reference/#dnsmonitor) before generating any code.
-- When adding `assertions`, always use `DnsAssertionBuilder` class which is [documented here](https://www.checklyhq.com/docs/cli/constructs-reference/#dnsassertionbuilder)
+- Reference [the docs for DNS monitors](https://www.checklyhq.com/docs/constructs/dns-monitor/) before generating any code.
+- When adding `assertions`, always use `DnsAssertionBuilder` class.
 
 ```typescript
 // INSERT DNS MONITOR EXAMPLE HERE //
@@ -112,7 +112,7 @@ The `checkly.config.ts` at the root of your project defines a range of defaults
 ### Heartbeat Monitor
 
 - Import the `HeartbeatMonitor` construct from `checkly/constructs`.
-- Reference [the docs for Heartbeat monitor](https://www.checklyhq.com/docs/cli/constructs-reference/#heartbeatmonitor) before generating any code.
+- Reference [the docs for Heartbeat monitor](https://www.checklyhq.com/docs/constructs/heartbeat-monitor/) before generating any code.
 
 ```typescript
 // INSERT HEARTBEAT MONITOR EXAMPLE HERE //
@@ -121,7 +121,7 @@ The `checkly.config.ts` at the root of your project defines a range of defaults
 ### Check Group
 
 - Import the `CheckGroupV2` construct from `checkly/constructs`.
-- Reference [the docs for Check Groups](https://www.checklyhq.com/docs/cli/constructs-reference/#checkgroupv2) before generating any code.
+- Reference [the docs for Check Groups](https://www.checklyhq.com/docs/constructs/check-group-v2/) before generating any code.
 - Check Groups are used to group checks together for easier management and organization.
 - Checks are added to Check Groups by referencing the group in the `group` property of a check.
 
@@ -134,24 +134,30 @@ The `checkly.config.ts` at the root of your project defines a range of defaults
 - Alert channels are used to send notifications when checks and monitors fail or recover.
 - Alert channels are added to checks, monitors, and check groups constructs by adding them to the `alertChannels` array property.
 
-Here are some examples of how to create different types of alert channels. All alert are described in the [Checkly docs](https://www.checklyhq.com/docs/cli/constructs-reference/#alertchannel).
+Here are some examples of how to create different types of alert channels. All alert are described in the [Checkly docs](https://www.checklyhq.com/docs/constructs/overview/).
 
 ### Email Alert Channel
 
+- Reference [the docs for Email Alert Channels](https://www.checklyhq.com/docs/constructs/email-alert-channel/) before generating any code.
+
 ```typescript
 // INSERT EMAIL ALERT CHANNEL EXAMPLE HERE //
 ```
 
 
 ### Phone Call Alert Channel
 
+- Reference [the docs for Phone Call Alert Channels](https://www.checklyhq.com/docs/constructs/phone-call-alert-channel/) before generating any code.
+
 ```typescript
 // INSERT PHONE CALL ALERT CHANNEL EXAMPLE HERE //
 ```
 
 
 ### Slack Alert Channel
 
+- Reference [the docs for Slack Alert Channels](https://www.checklyhq.com/docs/constructs/slack-alert-channel/) before generating any code.
+
 ```typescript
 // INSERT SLACK ALERT CHANNEL EXAMPLE HERE //
 ```
@@ -162,7 +168,7 @@ Here are some examples of how to create different types of alert channels. All a
 ### Status Page
 
 - Import the `StatusPage` construct from `checkly/constructs`.
-- Reference [the docs for StatusPages](https://www.checklyhq.com/docs/cli/constructs-reference/#statuspage) before generating any code.
+- Reference [the docs for StatusPages](https://www.checklyhq.com/docs/constructs/status-page/) before generating any code.
 - Status pages are used to display the status of your services to your users.
 - A Status Page consists of cards which include Status Page Services.
 
@@ -173,7 +179,7 @@ Here are some examples of how to create different types of alert channels. All a
 ### Status Page Service
 
 - Import the `StatusPageService` construct from `checkly/constructs`.
-- Reference [the docs for Status Page Services](https://www.checklyhq.com/docs/cli/constructs-reference/#statuspageservice) before generating any code.
+- Reference [the docs for Status Page Services](https://www.checklyhq.com/docs/constructs/status-page-service/) before generating any code.
 - Status Page Services are used to represent individual services on a Status Page.
 
 ```typescript
@@ -183,7 +189,7 @@ Here are some examples of how to create different types of alert channels. All a
 ### Dashboard
 
 - Import the `Dashboard` construct from `checkly/constructs`.
-- Reference [the docs for Dashboards](https://www.checklyhq.com/docs/cli/constructs-reference/#dashboard) before generating any code.
+- Reference [the docs for Dashboards](https://www.checklyhq.com/docs/constructs/dashboard/) before generating any code.
 - Dashboards are used to display the results of your checks on screens external to Checkly.
 
 ```typescript
@@ -193,7 +199,7 @@ Here are some examples of how to create different types of alert channels. All a
 ### Maintenance Window
 
 - Import the `MaintenanceWindow` construct from `checkly/constructs`.
-- Reference [the docs for Maintenance Windows](https://www.checklyhq.com/docs/cli/constructs-reference/#maintenancewindow) before generating any code.
+- Reference [the docs for Maintenance Windows](https://www.checklyhq.com/docs/constructs/maintenance-window/) before generating any code.
 - Maintenance windows are used to pause checks during maintenance periods so no alerts are sent.
 - Checks are referenced by their tags in the `tags` property.
 
@@ -204,7 +210,7 @@ Here are some examples of how to create different types of alert channels. All a
 ### Private Location
 
 - Import the `PrivateLocation` construct from `checkly/constructs`.
-- Reference [the docs for Private Locations](https://www.checklyhq.com/docs/cli/constructs-reference/#privatelocation) before generating any code.
+- Reference [the docs for Private Locations](https://www.checklyhq.com/docs/constructs/private-location/) before generating any code.
 - Private locations are used to run checks from your own infrastructure with the Checkly Agent, an OCI compatible container.
 
 ```typescript