wdk-op-policy's provenance note describes the state the fix removed - #5
Merged
Conversation
…fix removed Measured 2026-08-09. Two false statements, both at the URL a consumer checking provenance lands on, and both created by the work that was supposed to make provenance checkable. 1. "0.2.0, 0.3.0, 0.3.1, 0.3.2 and 0.4.0 resolve only in a private repository and cannot be fetched from outside the organisation." All five resolve in the PUBLIC observer-protocol/wdk-op-policy on the unmerged provenance/pre-monorepo branch, and each is reachable from a tag named for its version. Confirmed from a mirror clone taken with no authentication beyond public read. That is exactly what the 2026-08-08 provenance pass accomplished, and this sentence is its own description of the state it removed. 2. "(archived, read-only)". The repository reports archived=false. The pattern is the one already corrected twice this week at op-legacy-deployment: a true sentence becomes false because the state it describes was FIXED, and nobody re-reads the sentence because the fix felt like the end of the work. The block now says every published version resolves publicly, names which branch each sits on and why the divergent ones are tagged, and records both retired claims beside the correction. Swept the other six READMEs for the same shape: every remaining "(archived, read-only)" claim matches the measured archive state of the repository it names.
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.
Found while re-verifying section 3 of the 2026-08-09 handover, which claims provenance was closed for these exact versions.
Two false statements, both at the URL a consumer following
repository.urllands on:0.2.0–0.4.0"resolve only in a private repository and cannot be fetched from outside the organisation"observer-protocol/wdk-op-policyonprovenance/pre-monorepo, each reachable from a tag named for its version. Confirmed from a mirror clone with no auth beyond public readarchived=falseThe first one is the interesting one. Making those five publicly resolvable is precisely what the 2026-08-08 provenance pass did and what the handover lists as landed. The sentence is that pass's own description of the state it removed, left in place because the fix felt like the end of the work.
Same shape corrected twice already at
op-legacy-deployment. Both retired claims are recorded beside the correction rather than quietly replaced.Swept the other six READMEs: every remaining
(archived, read-only)claim matches the measured archive state of the repo it names.Docs only. No package, tag or dist-tag touched.