Repository navigation
Re-pin to registry v1.4.0 — the drift detector's first real firing - #212
Merged
Merged
Conversation
…l firing S6 (#187) built a check that fails when views-appwrite's coordinate registry moves without this repo re-verifying against it. It fired on 2026-08-03, naming the version and the action: the Appwrite Seam Contract's registry moved to v1.4.0; this repo declares v1.3.0. Re-verify appwrite_env's declaration against v1.4.0, then bump SEAM_CONTRACT_VERSION and SEAM_CONTRACT_COMMIT together. A true positive on its first firing, and it turned development red rather than letting the divergence sit unnoticed — which is the whole point. The upstream change graduates four CRAFD coordinates from reserved to real and records the CRAFD caller key as issued. Its own header says the bump "imposes no new obligation on any consumer". Re-verified rather than taken on trust, because a bumped pin ASSERTS that someone checked: all 13 names this repo declares are present at v1.4.0 with unchanged class, and nothing was added or removed across connection/target/secret. The claim holds for us mechanically. Pin bumped as a pair — version and commit together, never one alone — to 20dfd0f, confirmed an ancestor of views-appwrite main with both cited files present at it. That reachability check is the one #196 taught us to make: the withdrawn b54928f existed, its files existed at it, and it had never reached main. ADR-013 §7d's two URLs follow the pin, with a dated erratum recording that the detector worked. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Two erratum entries still read "both links now pin 47172af". They pin 20dfd0f as of this change, so the record was asserting a superseded pin as current — the exact stale-claim class ADR-014 exists for, in the document that records the last time it happened. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Polichinel
added a commit
that referenced
this pull request
Aug 3, 2026
Same procedure as #212, same outcome: our 13 declared names are unchanged in class and membership at v1.4.1, verified rather than assumed before the pair was bumped. The upstream change is a register reframing that imposes nothing on consumers. Noted in ADR-013 rather than acted on: the registry moved twice today, and a pin chased per-PR is a real cost. If views-appwrite stays this active, the check may want a MAJOR/MINOR floor rather than an exact match. That is a decision, not a fix, so it is recorded where the next person re-pinning will read it. Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
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
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.
developmentis red. This fixes it, and the failure was a true positive on its first firing.What happened
S6 (#187) built a check that fails when views-appwrite's registry moves without this repo re-verifying. It fired:
The registry moved to v1.4.0 on 2026-08-02, hours after S6 merged. Without the check, this repo would have gone on citing a superseded edition indefinitely — which is exactly register C-57, the concern S6 closed.
Re-verified, not just bumped
A bumped pin asserts that someone re-checked, so I checked rather than trusting the upstream note:
The upstream change graduates four CRAFD coordinates from reserved to real and records the CRAFD caller key as issued. Its header says the bump "imposes no new obligation on any consumer" — that now holds for us mechanically, not by assertion.
Note the CRAFD connection: those coordinates landing upstream is directly relevant to the
feat/crafd-producerbranch waiting to be reviewed.Pinned as a pair
v1.3.0 @ 47172af→v1.4.0 @ 20dfd0f, version and commit together.20dfd0fconfirmed an ancestor of views-appwritemain, with both cited files present at it. That reachability check is the one #196 taught us to make — the withdrawnb54928fexisted, its files existed at it, and it had never reachedmain.ADR-013 §7d's two URLs follow the pin, with a dated erratum recording that the detector worked.
Scope
Deliberately its own change rather than folded into the S4 PR it was blocking. It is a different concern, and the reason should be legible later.
🤖 Generated with Claude Code