audit: registry snapshot remains intentionally unrefreshed after draft evidence #10

Status

OPEN / REGISTRY_FRESHNESS_LOCKED / NEW_DRAFT_EVIDENCE_AVAILABLE

Finding

The Evaluation Kit registry is a pinned profile snapshot and remains intentionally separate from current repository default branches and unmerged repair candidates.

The current registry entry for Riverbraid-Refusal-Gold points to:

edb2fb12879f016d0dd575903fef8d9f25ccfb81

The current Refusal-Gold main branch used as the base of draft PR #7 is:

3a587d068f5cd11d9d86579792b5c4c160db89ba

The evidence-producing draft head is:

a05c341af05fe9b5663c5dc8d6e85084e0118cdc

These are three distinct source subjects.

New execution evidence

Draft PR Riverbraid/Riverbraid-Refusal-Gold#7 passed GitHub Actions run 30288938156, job 90053623558.

The exact draft head executed:

• the real positive verifier path;
• an isolated missing-required-file negative path;
• exit-code-1 and bounded-output assertions.

Observed bounded markers:

REFUSAL_GOLD_POSITIVE_PASS
REFUSAL_GOLD_FAIL_CLOSED_NEGATIVE_PASS

This resolves the prior statement that no execution evidence existed for the patched behavior. It does not make the draft head an adopted registry subject.

Why the registry remains unchanged

No registry pin was changed because a registry freshness transition requires a separate exact decision and evidence set, including:

1. intended target source identity after merge/adoption disposition;
2. resulting exact current-line execution evidence;
3. verification-depth classification for the new command surface;
4. expected-result review and any required update;
5. source, configuration, environment, and dependency identities;
6. rollback and supersession path;
7. authority disposition explicitly authorizing the registry change;
8. full Evaluation Kit execution after the pin change.

A successful draft PR does not silently replace the current registry snapshot.

Current claim effect

• The registry remains a valid historical pinned profile subject under its existing claim ceiling.
• It is not automatically fresh relative to Refusal-Gold main or draft PR docs: align evaluator routing and claim terminology #7.
• Refusal-Gold fail-closed evidence now exists for the exact draft head only.
• A future pin change must be represented as a new registry/profile event, not a retroactive correction of the prior snapshot.

Boundary

This issue records registry freshness and source-subject separation.

It does not mutate registry pins, expected results, releases, tags, or repository settings. It does not merge Refusal-Gold PR #7, adopt its source, establish independent reproduction, or advance F0–F4.

It does not claim certification, production readiness, external audit, complete security assurance, or absence of defects.