test: Bonk issue triage capability test [DO NOT MERGE]

[marciocloudflare]

This is a throwaway PR to test whether Bonk can classify GitHub issues for the automated triage bot (PCX-21514). It contains no content changes — empty commit only. Will be closed after testing.

Test: Posting two /bigbonk prompts to evaluate Opus's ability to classify the relationship between a GitHub issue and candidate docs pages.

[github-actions]

This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:

Pattern	Owners

[marciocloudflare]

/bigbonk You are a documentation triage bot. Given a GitHub issue and a candidate documentation page, classify the relationship:

(A) The docs page directly answers the reporter's question — the reporter likely missed existing content. Respond with a helpful comment linking to the specific section.
(B) The docs page exists and covers the topic, but the reporter is pointing out a real problem with the docs (outdated content, incorrect instructions, missing information). Route as a content edit.
(C) No relevant docs page covers this topic. Route as a content gap.

ISSUE: "Updating linux package"
Body: "When I try to install cloudflare-warp via terminal it always kept saying unable to locate packages. I tried updating my packages but still does not work."
URL referenced by reporter: https://developers.cloudflare.com/warp-client/get-started/linux/

CANDIDATE PAGE: /warp-client/get-started/linux/
Content summary: The page provides Linux installation instructions for WARP. It tells users to install via "sudo apt install cloudflare-warp" (for apt-based OS) or "sudo yum install cloudflare-warp" (for yum-based OS). HOWEVER, this only works AFTER adding the Cloudflare package signing key and apt repository source — steps which are documented on the page but easy to miss. The page also includes a Note: "If you get an error message when trying to install via the terminal, download the package that suits your distro from the package repository." The package repository link goes to https://pkg.cloudflareclient.com/.

Classify as A, B, or C. Explain your reasoning in 2-3 sentences. This is TEST 1 — expected answer is (A).

[marciocloudflare]

/bigbonk You are a documentation triage bot. Given a GitHub issue and a candidate documentation page, classify the relationship:

(A) The docs page directly answers the reporter's question — the reporter likely missed existing content. Respond with a helpful comment linking to the specific section.
(B) The docs page exists and covers the topic, but the reporter is pointing out a real problem with the docs (outdated content, incorrect instructions, missing information). Route as a content edit.
(C) No relevant docs page covers this topic. Route as a content gap.

ISSUE: "Technical Report: Deprecated HuggingFace API Endpoint in Cloudflare AI Gateway"
Body: "The Cloudflare AI Gateway documentation for HuggingFace providers appears to be outdated. The documentation does not reflect that HuggingFace has deprecated api-inference.huggingface.co in favor of router.huggingface.co. As a result, users attempting to use HuggingFace models through the AI Gateway encounter errors indicating the old endpoint is no longer supported, even though the gateway URL format (https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/huggingface/{model}) remains correct. Error from dashboard: {"error": "https://api-inference.huggingface.co is no longer supported. Please use https://router.huggingface.co instead."}"
URL referenced by reporter: https://developers.cloudflare.com/ai-gateway/usage/providers/huggingface/

CANDIDATE PAGE: /ai-gateway/usage/providers/huggingface/
Content summary: The page documents how to use HuggingFace models through Cloudflare AI Gateway. It shows the gateway URL format and explains how requests are proxied to HuggingFace's API endpoint. The page currently references api-inference.huggingface.co as the underlying endpoint.

Classify as A, B, or C. Explain your reasoning in 2-3 sentences. This is TEST 2 — expected answer is (B).

[ask-bonk]

Triage Classification — TEST 1

Classification: (A) — The docs page directly answers the reporter's question.

Reasoning: The Linux installation page at /warp-client/get-started/linux/ documents two installation paths: using apt install cloudflare-warp / yum install cloudflare-warp, or downloading directly from the package repository. The reporter's "unable to locate packages" error is a classic symptom of not having added the Cloudflare package signing key and apt repository source first — a prerequisite that must be completed before apt install will find the package. The page also explicitly includes a note: "If you get an error message when trying to install via the terminal, download the package that suits your distro from the package repository."

Suggested comment to reporter: The WARP Linux installation instructions at /warp-client/get-started/linux/ cover this — the sudo apt install cloudflare-warp command requires the Cloudflare package repository to be configured on your system first. If you continue to see "unable to locate packages", the page recommends downloading the .deb/.rpm package directly from the Cloudflare package repository.

[ask-bonk]

Triage Classification — TEST 2

Classification: (B) — The docs page exists and covers the topic, but the reporter is pointing out a real problem (outdated content).

Reasoning: The candidate page at /ai-gateway/usage/providers/huggingface/ explicitly tells users to replace https://api-inference.huggingface.co/models/ in their URLs (line 16 of the source file). HuggingFace has since deprecated api-inference.huggingface.co in favor of router.huggingface.co, meaning the documentation now references a defunct endpoint. This is a legitimate content edit — the page needs to be updated to reflect the new HuggingFace endpoint so the AI Gateway proxy routes requests correctly.

Recommended action: Update src/content/docs/ai-gateway/usage/providers/huggingface.mdx to replace references to api-inference.huggingface.co with router.huggingface.co (pending confirmation that the AI Gateway backend has also been updated to proxy to the new endpoint).

[ask-bonk]

Posted both triage classification responses to PR #29664:

• TEST 1 — Classified as (A): The Linux WARP installation page already answers the reporter's question. The "unable to locate packages" error stems from not adding the Cloudflare apt repository first, and the page includes an explicit note about downloading from the package repository as a fallback.

• TEST 2 — Classified as (B): The HuggingFace AI Gateway page contains outdated content. It references the deprecated api-inference.huggingface.co endpoint, which HuggingFace has replaced with router.huggingface.co. This is a real docs problem that needs a content edit.

Both match the expected answers from the test prompts.

github run

[github-actions]

Preview URL: https://e1364abe.preview.developers.cloudflare.com
Preview Branch URL: https://marcio-bonk-triage-test.preview.developers.cloudflare.com