docs: Document resolver repository and LLM-powered analyzer feature

[promptless]

Adds documentation for the resolver repository in the repos section. Documents that the resolver package detects and resolves documentation into Doc Detective tests, including its new AI-powered analyzer feature that can automatically extract action steps from plain documentation text. The analyzer supports multiple LLM providers (Anthropic, Google, OpenAI) and includes a local testing solution using llama.cpp.

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.}

[promptless]

I've added new changes to address this GitHub PR in commit 2516ea8

[promptless]

🔧 I noticed that some CI checks failed for this PR. I'm investigating the failures and will work on fixing them.

[promptless]

Promptless escalated the following message to you. If you respond, please remember to tag Promptless:

I've investigated the CI failure and found that the branch accidentally had some unintended file deletions/modifications that could have affected the CI environment:

Fixed:

• Restored .devcontainer/devcontainer.json
• Restored .github/dependabot.yml
• Restored package.json (with the --host 0.0.0.0 flag)
• Restored .long_term_context/screenshot_workflow/instructions.md

About the test failure: The failing test was testing the Docker installation steps in docs/get-started/installation/index.mdx, which I didn't modify in this PR. The timeout was likely caused by the missing CI configuration files, which I've now restored.

The branch now contains only the intended documentation changes for the resolver repository. CI should re-run automatically and should pass now that the environment files are restored.

[promptless]

I've added new changes to address this CI failure in commit 165ae22