From 23bcbcfed16dd2d37afc65ad83a71a0a43882c7e Mon Sep 17 00:00:00 2001
From: Oleks <oleks.kuksenko@gmail.com>
Date: Tue, 7 Jul 2026 18:32:59 +0300
Subject: [PATCH] docs: complete consumer enumeration (Class B hosts + Class C
 standalone repos)

---
 README.md | 53 ++++++++++++++++++++++++++++++++++++++++++++---------
 1 file changed, 44 insertions(+), 9 deletions(-)

diff --git a/README.md b/README.md
index 8c35b98..7a14b75 100644
--- a/README.md
+++ b/README.md
@@ -76,9 +76,17 @@ exported packages, so they only need a re-lock **when you want that host to
 move to the new pin** — typically as part of its deploy. Each host is
 independent; re-locking one does not affect the others.
 
-`servers/emmett`, `servers/armer`, `servers/howard`, `servers/bim`,
-`servers/micron`, `servers/mermaid-gpu`, `servers/kotkan`, plus non-fleet
-NixOS flakes that pin here (`gvisor`, `gvisor-s390x/test-services`).
+Full list (input name in parentheses):
+
+- `servers/emmett` (`fleet-pins`)
+- `servers/armer` (`fleet-pins`)
+- `servers/howard` (`fleet-pins`)
+- `servers/bim` (`fleet-pins`)
+- `servers/micron` (`fleet-pins`)
+- `servers/mermaid-gpu` (`fleet-pins`)
+- `servers/kotkan` (`fleet-pins`)
+- `gvisor` (`fleet`)
+- `gvisor-s390x/test-services` (`fleet`)
 
 > A host will not fully align until **all** the Class-A exporters it depends on
 > are re-locked and pushed first. Verify with a transitive check — every
@@ -86,10 +94,37 @@ NixOS flakes that pin here (`gvisor`, `gvisor-s390x/test-services`).
 > except the intentional standalone pins (e.g. emmett's `nixpkgs-hyprland`,
 > `nixpkgs-gemini`, `nixpkgs-opencode`).
 
-### Everything else (package repos, ~51 parity repos)
+### Class C — standalone package repos (independent, self-paced)
 
-Many standalone package repos pin here purely for cache alignment of their own
-builds (`browser-automation`, `mcp-chrome`, `builder-arbitrage`, the parity
-repos, the `helms/*` charts, etc.). Re-lock these when you next build/republish
-them — they are not in any host's runtime closure, so they don't block a fleet
-deploy.
+These pin here purely for binary-cache alignment of their **own** builds. They
+are not in any host's runtime closure, so they never block a fleet deploy —
+re-lock each one whenever you next build/republish it. Input is `fleet` unless
+noted.
+
+- `alertmanager-gotify-bridge`
+- `antigravity-plugin-registry`
+- `audio-to-audio`
+- `BitNet`
+- `browser-automation`
+- `builder-arbitrage`
+- `building/caddy-with-replace`
+- `ci/temporal-based-ci`
+- `claude-plugin-registry`
+- `cmux/linux`
+- `ComfyUI-Docker/cu130-megapak-pt210-py314-nix`
+- `containerd-snapshot-healer`
+- `helms/imagegen-bot`
+- `helms/infra-cache`
+- `helms/voicebox`
+- `ii/ii-agent`
+- `ii/ii-researcher`
+- `mcp-chrome`
+- `mermaid-gpu-dashboard`
+- `moonlight-android`
+- `nix-customs/nixos-ci`
+- `overlay-xonsh` (`fleet-pins`)
+
+> This list is generated — regenerate with:
+> `grep -rl fleet-pins ~/projects/*/flake.nix ~/projects/*/*/flake.nix`.
+> The ~51 per-archetype **parity repos** also consume the pin transitively via
+> `parity-lib`; re-lock them on their own republish cadence.