From b9eedd8973f764afc91326fdc475c23cdea12e82 Mon Sep 17 00:00:00 2001
From: cndgrr <59120057+cndgrr@users.noreply.github.com>
Date: Tue, 4 Aug 2026 10:05:04 +0000
Subject: [PATCH] docs(consumers): cite the manifest availability to the tag
 that shipped it

0.5.0 availability is actions/docs-sync own arrival (#19); #251 is the
guidance and the guarantee, not the file date.

Refs #251
---
 docs/CONSUMERS.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/CONSUMERS.md b/docs/CONSUMERS.md
index b684e12..17cbc13 100644
--- a/docs/CONSUMERS.md
+++ b/docs/CONSUMERS.md
@@ -604,8 +604,8 @@ Anything on the consumer's side that needs to know *which* documents are
 vendored — a re-vendor script, a `docs-sync` equivalent, the task list of a
 conversion issue — reads **the pin's `docs/VENDORED.txt`** and never names
 the files itself. The manifest is available at the pinned ref from `0.5.0`
-and later (ceremony#251); it is one path per line, relative to ceremony's
-root, and blank lines are ignored:
+and later — it shipped with `actions/docs-sync` itself (ceremony#19) — and
+it is one path per line, relative to ceremony's root, blank lines ignored:
 
 ```sh
 # the vendored doc set at the ref this repo is pinned to