The pin moves to rc.21, and the four Group 2 expectations move with it

[BTCBoyd]

One commit, because they cannot land separately. Measured: with the expectations changed and the lockfile still at rc.12, verify-published-credentials returns 1, because rc.12 cannot verify the four. An expectation is a statement about the version being run, so it moves when the version does.

The four

	before	after
allow	false	true
reasonContains	(op.evaluation.verdict.v3); the record states construction op.evaluation.verdict.v4	signature verifies over the payload this build rebuilds (op.evaluation.verdict.v4)
knownIssue	VERDICT-PAYLOAD-VERSION-PIN	removed

ppp-verdict-released, ppp-verdict-denied-ceiling, ppp-probe-a-verdict-release-above-escalation, ppp-probe-b-verdict-release-above-ceiling.

The expectations changed because the version at latest changed, not because the engine changed. The records are signed under v4 and were always sound. rc.12 rebuilds v3 and cannot verify them; rc.21 rebuilds v4 and does. Nothing about the artifacts moved.

The reasonContains strings named both version tokens deliberately so the pin could not move in either direction without turning this check red. It moved, the check went red, and this is the answer — the control working, not a finding about the engine.

Population searched

Every tracked file, dist/ excluded, grepped for the package name adjacent to a semver, plus every data-engine-version="current" span in tracked HTML.

scripts/package.json	rc.12 → rc.21
scripts/package-lock.json	rc.12 → rc.21
eight current spans	verify.html 3, index.html 2, docs.html 2, check.html 1

Eight, not the five the earlier survey found. That survey excluded verify.html's three as parked; they are on master now, so the population grew by exactly those three. Not a correction to the earlier count — the same method over a population that changed underneath it.

A ninth thing, which no instrument found

verify-samples/README.md said "scripts/package.json still pins 1.0.0-rc.12 … and credential-expectations.json still records the four allow:false outcomes." This commit falsifies that paragraph. Rewritten here.

sentences-at-risk.mjs was run before committing and found nothing — correctly and uselessly. It keys off results/ values, and this change moves a pin and eight spans, touching no results/ file. The README paragraph is Markdown, which it does not read at all. Its scope is one class of change and this is a different one.

Verified, not predicted

13/13 checks green with this branch merged into #101's content locally. sync-engine-version goes from 1 to 0 — it was the only thing failing on #101.

This branch alone leaves check-measured-figures red, for #101's reasons: the stale npmLatest in results/ and the two section-02 markers. Those are #101's to fix and it does.

The pre-push hook caught this

It refused the first push: four pages moved their git dates and the sitemap was stale. Regenerated in its own commit. First time that hook has stopped a real push rather than a probe.

[netlify]

✅ Deploy Preview for observerprotocol ready!

Name	Link
🔨 Latest commit	a095b13
🔍 Latest deploy log	https://app.netlify.com/projects/observerprotocol/deploys/6a8b8857e1c1c20008ee98d2
😎 Deploy Preview	https://deploy-preview-103--observerprotocol.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
🤖 Make changes	Run an agent on this branch

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[BTCBoyd]

Closing in favour of #104, which carries this branch's commits unchanged.

Ruling from Boyd: #101 and #103 are combined because they are one change to the world. A repository state with one landed and not the other is a state that should not exist, so they land together or not at all. The branch protection is correct and was not relaxed.

The measurement that forced it: each was red for the other's reasons.

combination	result
#103 alone	RED — stale npmLatest, two section-02 markers
#101 alone	RED — the pin drift
#103 + #101	13/13 GREEN

Neither could go green first, so neither could merge first. Combined, the merge is clean and the suite passes.

Nothing from this branch is dropped; its commits are in #104's history.