[tt-a1i]

Problem

Closes #328 on merge. The required minimum and latest Pi host jobs landed in #719. Decision 0006 still describes a proposal. Main has now exercised the policy with distinct minimum, locked and latest versions, which was the outstanding evidence requested by the issue.

Value

Publish a reviewed statement of what the open-ended peer range means and who reruns the compatibility checks when Pi changes.

Approach

Adopt the existing Decision when this PR merges and update the index. Preserve the dated proposal history and append the evidence for adoption. This PR adds no job and changes no peer range or development pin.

Validation

• Main CI at ffc9c624 passed the minimum (Pi 0.99.1) and then-latest (Pi 1.5.0) checks, Node suites and installation smokes. Locked Pi was 1.2.0.
• On November 14 a separate isolated probe resolved the eight-package Pi 1.5.2 cohort. The installed OpenPI tarball had no local Pi peers. Its sole registered package source loaded extensions over offline RPC, and the packed Web CLI served HTML, JavaScript, CSS and favicon using the separate Pi host. This probe covered startup. The full 1.5.2 Linux endpoint is exercised when CI resolves that version.
• The documentation branch passed bun run check and the existing host selector and workflow tests. Its executable sources and artifacts match the tested main revision.

Impact

The support policy takes effect through maintainer review and merge. The verification duties use the current CI. No change to installed software, model tools, configuration, or source/build distribution.