chore: repin the kit's caller stubs to v1.11.0 - #28
Merged
Conversation
Step 2 of the release order for v1.11.0 (90f0d06). All six stubs move b394c6d (v1.10.0) -> 90f0d06 (v1.11.0). v1.10.0 tagged the reusable; v1.11.0 tags the caller stub, the DRIVER_AGENTS_REF bump and the Shopify tripwire. Pinning to v1.11.0 is what keeps fleet-pin-audit.sh meaningful — it compares deployed stub pins against the latest tag, so leaving them at v1.10.0 while the tag moved would report the whole fleet stale, and leaving the tag at v1.10.0 while waving v1.11.0 content would report it uniform over a gap. Docs: "latest tag" now v1.11.0 with all six stubs at 90f0d06; the conversion is described as spanning the two tags, since the reusable and its stub genuinely shipped in different ones. References to "the v1.10.0 repin" corrected to v1.11.0 across both scope docs and the kit README — the stub never shipped in a v1.10.0 tag. The canonical stub block in reusable-conversion-scope.md repinned to match the landed file. Wave references now name the v1.11.0 wave. Parity with driver-agents docs/agent-instructions-shopify.md re-checked at the tag per the new release-order step 1: 978 chars both sides, exact. actionlint clean; stub-pin and tokenization guards pass.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Step 2 of the release order for
v1.11.0(90f0d06, already tagged). All six stubs moveb394c6d(v1.10.0) →90f0d06(v1.11.0).Pinning to v1.11.0 is what keeps
fleet-pin-audit.shmeaningful: it compares deployed stub pins against the latest tag. Leaving the stubs at v1.10.0 while the tag moved would report the whole fleet stale; leaving the tag at v1.10.0 while waving v1.11.0 content would report it uniform over a gap.Docs updated: latest tag, and every "v1.10.0 repin" corrected to v1.11.0 — the stub never shipped in a v1.10.0 tag, only the reusable did. The canonical stub block in the scope doc is repinned to match the landed file.
Parity with driver-agents
docs/agent-instructions-shopify.md@4d63371re-verified at the tag per the new release-order step 1: 978 chars both sides, exact. actionlint clean; both kit guards pass.Next after this lands: pilot
foundrae-blackridge@staging, then the 18-pair wave.