Add a note to explicitly state that signed pipeline are not supported …

[ss1909]

…in HA

ref: https://linear.app/buildkite/issue/A-1677/docs-dont-state-that-signed-pipelines-are-unsupported-on-hosted-agents

[buildsworth-bk-app]

The hosted-agent overview now exposes the limitation, but the change leaves the second documentation entry point from A-1677 unchanged. The remaining copy and formatting issues are inline.

Want to dig deeper?

Paste this into your agent to explore the findings from this review's Buildkite build:

Download the buildsworth logs from build 17368, then answer my questions about the findings.

Install the reading-buildsworth-logs skill to run this.

About buildsworth

Model: gpt-5.6-sol with xhigh thinking.

How to request a review: Comment @buildsworth-bk review on the PR, or request buildsworth-bk as a reviewer.

Risk labels (how buildsworth classifies risk) — buildsworth classifies risk itself from the diff. To let it approve, grant L2 approval by mentioning @buildsworth-bk (see L2 approval grant):

• L1 — Low risk (dep bumps, docs/copy, lockfiles, small presentational fixes). buildsworth may approve by default.
• L2 — Standard risk (new UI, additive API fields, refactors). Approved only with an L2 grant; otherwise comment-only.
• L3 — High risk (auth, migrations, payments, secrets, perf-critical paths). Human review always required.

[buildsworth-bk-app]

The new sentence covers the signed-pipelines page and fixes the agreement issue. The formatting part of the original blocking thread remains open.

Want to dig deeper?

Paste this into your agent to explore the findings from this review's Buildkite build:

Download the buildsworth logs from build 17388, then answer my questions about the findings.

Install the reading-buildsworth-logs skill to run this.

Previous concerns have been addressed.