From 75703d7fd6a3ef92a2b11eea8889a8e1cf74702b Mon Sep 17 00:00:00 2001 From: Kyle Sexton <153232337+kyle-sexton@users.noreply.github.com> Date: Tue, 15 Sep 2026 10:08:11 -0400 Subject: [PATCH 1/4] docs(fleet): replace the stale fifteen-repo count in cloud-fleet-setup The bootstrap adoption paragraph claimed "all fifteen non-archived melodic-software repositories". `gh repo list melodic-software --no-archived --limit 100 --json name` returns 16 today, so the count had already rotted. Drop the hardcoded number and scope the claim to the date the pass was actually run (2026-08-16, the section's own heading date), so the sentence records a dated verification instead of asserting an ever-changing present-tense count. Name the gap class the date introduces -- a repository created after that pass is not covered by it -- rather than enumerating repos, which the paragraph's closing sentence already rules out. Also tighten the cited query to `--no-archived --json name`, which returns exactly the set the sentence describes. Co-Authored-By: Claude Fable 5.1 Claude-Session: https://claude.ai/code/session_011mbb3nkTfMrT9vDmoUnQuj --- docs/cloud-fleet-setup.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/docs/cloud-fleet-setup.md b/docs/cloud-fleet-setup.md index 3e1ed0cf1..f785d5258 100644 --- a/docs/cloud-fleet-setup.md +++ b/docs/cloud-fleet-setup.md @@ -74,10 +74,11 @@ Pinned toolchains found: ## Bootstrap adoption (2026-08-16) -Adoption is complete and no longer a per-repo decision surface: all fifteen non-archived -melodic-software repositories (`gh repo list melodic-software --json name,isArchived`) carry -`.claude/cloud-bootstrap.sh`, register it as a `startup|resume` SessionStart hook, and declare the -`melodic-software` marketplace. Enabling the catalog is not among the per-repo steps: the standards +Adoption is no longer a per-repo decision surface: as of 2026-08-16, every non-archived +melodic-software repository (`gh repo list melodic-software --no-archived --json name`) carried +`.claude/cloud-bootstrap.sh`, registered it as a `startup|resume` SessionStart hook, and declared +the `melodic-software` marketplace; a repository created after that pass is not covered by it. +Enabling the catalog is not among the per-repo steps: the standards fleet list does that for every repo, and a repo's own block carries only deltas ([Step 2](#step-2-per-repo-wiring)). Read adoption state from the repos rather than from a table here; a per-repo enumeration in this doc can only lag them. From 27ef3f27016c37f43b456a8d0e9a4a9b18f1fbbe Mon Sep 17 00:00:00 2001 From: Kyle Sexton <153232337+kyle-sexton@users.noreply.github.com> Date: Tue, 15 Sep 2026 10:15:35 -0400 Subject: [PATCH 2/4] docs(fleet): pin --limit on the cited gh repo list query Codex review raised a valid P2 on the query this PR cites: `gh repo list` returns only 30 repositories by default (`gh repo list --help`: "-L, --limit int Maximum number of repositories to list (default 30)"). At 16 non-archived repos it does not bite today, but a reader who runs the cited command once the org passes 30 would silently enumerate a truncated fleet while the prose claims fleet-wide coverage. That is the same rot class this PR exists to remove, so pin `--limit 100` in the doc to match the command the verification actually ran, and say in one clause why the flag is there. Co-Authored-By: Claude Fable 5.1 Claude-Session: https://claude.ai/code/session_011mbb3nkTfMrT9vDmoUnQuj --- docs/cloud-fleet-setup.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/docs/cloud-fleet-setup.md b/docs/cloud-fleet-setup.md index f785d5258..99c4b4ef0 100644 --- a/docs/cloud-fleet-setup.md +++ b/docs/cloud-fleet-setup.md @@ -75,11 +75,12 @@ Pinned toolchains found: ## Bootstrap adoption (2026-08-16) Adoption is no longer a per-repo decision surface: as of 2026-08-16, every non-archived -melodic-software repository (`gh repo list melodic-software --no-archived --json name`) carried +melodic-software repository (`gh repo list melodic-software --no-archived --limit 100 --json name`; +the `--limit` matters, since `gh repo list` returns only 30 by default) carried `.claude/cloud-bootstrap.sh`, registered it as a `startup|resume` SessionStart hook, and declared the `melodic-software` marketplace; a repository created after that pass is not covered by it. -Enabling the catalog is not among the per-repo steps: the standards -fleet list does that for every repo, and a repo's own block carries only deltas +Enabling the catalog is not among the per-repo steps: the standards fleet list does that for every +repo, and a repo's own block carries only deltas ([Step 2](#step-2-per-repo-wiring)). Read adoption state from the repos rather than from a table here; a per-repo enumeration in this doc can only lag them. From 988dd4ed21ef3561f40bde67cdf603b38c0166de Mon Sep 17 00:00:00 2001 From: Kyle Sexton <153232337+kyle-sexton@users.noreply.github.com> Date: Tue, 15 Sep 2026 10:24:10 -0400 Subject: [PATCH 3/4] docs(fleet): update the standards fallback-list value after standards #572 DOTNET_FALLBACK_VERSIONS in components/cloud-environment/setup.sh moved from 10.0.302 10.0.400 to 10.0.400 10.0.401 (standards PR #572, merged 2026-09-15). The fallback list now matches the fleet's pinned .NET versions instead of trailing them. Co-Authored-By: Claude Sonnet 5 Claude-Session: https://claude.ai/code/session_011mbb3nkTfMrT9vDmoUnQuj --- docs/cloud-fleet-setup.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/cloud-fleet-setup.md b/docs/cloud-fleet-setup.md index 99c4b4ef0..a6d46a109 100644 --- a/docs/cloud-fleet-setup.md +++ b/docs/cloud-fleet-setup.md @@ -59,8 +59,8 @@ Pinned toolchains found: `rollForward: disable`, so the exact patch is required, and by ci-workflows without a `rollForward`. **10.0.401** (github-iac, also `rollForward: disable`) is in neither fallback slot, so that repo depends entirely on the per-repo-pin path reading its `global.json`. The - fallback list is still `10.0.302 10.0.400`, so **10.0.302** is installed even though no fleet - repo pins it any more. + fallback list now matches the fleet pins above, `10.0.400 10.0.401` (per + `components/cloud-environment/setup.sh` in standards, verified 2026-09-15). - **Node 24.20.0**, the fleet fallback the setup script installs when the checked-out repo pins no `.node-version`; nine repos pin that exact version and codex-plugins pins major 24. The cloud VM ships Node 20/21/22 only, so this is always an install. From 1b8be5e288fbf66f50baf5d5ae3f106d3cb98f68 Mon Sep 17 00:00:00 2001 From: Kyle Sexton <153232337+kyle-sexton@users.noreply.github.com> Date: Tue, 15 Sep 2026 10:30:24 -0400 Subject: [PATCH 4/4] docs(fleet): make the .NET SDK bullet consistent with the new fallback list The bullet still said 10.0.401 was in neither fallback slot after standards #572 added it to DOTNET_FALLBACK_VERSIONS, contradicting the sentence right below it. Rewrite to state github-iac's 10.0.401 (rollForward: disable) is now covered by the fallback list, matching the rest of the bullet. Co-Authored-By: Claude Sonnet 5 Claude-Session: https://claude.ai/code/session_011mbb3nkTfMrT9vDmoUnQuj --- docs/cloud-fleet-setup.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/docs/cloud-fleet-setup.md b/docs/cloud-fleet-setup.md index a6d46a109..786e324b8 100644 --- a/docs/cloud-fleet-setup.md +++ b/docs/cloud-fleet-setup.md @@ -57,9 +57,8 @@ Pinned toolchains found: - **.NET SDK 10.0.400**, pinned by medley and claude-code-account-rotation, which set `rollForward: disable`, so the exact patch is required, and by ci-workflows without a - `rollForward`. **10.0.401** (github-iac, also `rollForward: disable`) is in neither fallback - slot, so that repo depends entirely on the per-repo-pin path reading its `global.json`. The - fallback list now matches the fleet pins above, `10.0.400 10.0.401` (per + `rollForward`. **10.0.401** (github-iac, also `rollForward: disable`) is now in the fallback + list too. The fallback list matches the fleet pins above, `10.0.400 10.0.401` (per `components/cloud-environment/setup.sh` in standards, verified 2026-09-15). - **Node 24.20.0**, the fleet fallback the setup script installs when the checked-out repo pins no `.node-version`; nine repos pin that exact version and codex-plugins pins major 24. The cloud VM