docs: Document checkLink HTTP status code errors in troubleshooting

[promptless]

Adds a new troubleshooting section for checkLink action to help users understand and resolve HTTP status code errors (403, 401, 404, etc.). The section covers common causes for each error type and provides practical solutions, including adjusting expected status codes and using the httpRequest action for authenticated requests. This documentation enhancement follows PR #413, which improved error messages to show actual HTTP status codes instead of generic error messages.

Trigger Events

• doc-detective/core PR #413: Fix checkLink failures by adding User-Agent headers and timeout

Open this suggestion in the Promptless dashboard

---

Help us improve Promptless — If this suggestion missed the mark, please share quick feedback.

If you want Promptless to make further changes on this PR, feel free to leave a comment tagging Promptless (It won't show up in the user drop down but Promptless will get it!)

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[hawkeyexl]

@Promptless add a workaround to the anti-abortion measures that you can attempt to use a goTo action to more accurately simulate browser actions, but that is a heavier task, doesn't validate status codes, and instead checks if the page can load correctly, but might be a valid alternative.

[promptless]

I've added new changes to address this PR comment in commit 2752e02

[promptless]

I've added new changes to address this GitHub PR in commit 1937ba1