Repository navigation
facts: release 1.6.2 measured facts (release_tag baseline at the tag pair) - #96
Merged
Merged
Conversation
…pair) releases["1.6.2"]: registry baseline pineforge-parity-baseline-20261021-release-tag-653c94df, the release_tag re-measurement (7989/7989) at engine v1.6.2 dfe5f367e8935ef549ee7a8a38c1d437d1e8e42e / codegen v1.6.2 f0786eab355b4c1811a03d2644fef0c8cda544dd, HPO v1.6.2 7493a2bd32c7cc5b802710c7287a5bfd27e18f42, snapshot 653c94dfdbb2..., measured by exp-release-v1-6-2-20261021 (134/134 succeeded). The active scoreboard identity moves to the same baseline; the counts are unchanged against 1.6.1 (graded 7989, excellent 7983, strong 6, belowStrong 0, engineErrors 0, anomaliesExcluded 17, closedProbes 7680, corpusProbes 309). facts.schema.json allows only "source" and "scoreboard" under a release and no note or status field, so the hub image status is recorded here instead: there is NO 1.6.2 hub image and no hub release for v1.6.2 (the hub tag v1.6.2 exists, its publish run failed and was not re-run; owner decision HUB-TAGMOVE = B), so this change does not trigger release-finalize for a stored candidate. The baseline was activated by the Cloud Run job pineforge-initiate-baseline (execution pineforge-initiate-baseline-7lf5f), which re-derived the release_tag row from the registry and the evidence bucket and logged: release_tag: pineforge-parity-baseline-20261021-release-tag-653c94df supersedes pineforge-parity-baseline-20261020-engine-34f9b3a3 (v1.6.2); exp-release-v1-6-2-20261021 attempt 2 (7989 probes), population cf857209574e (7989 declared, 0 engine-error), snapshot 653c94dfdbb2 rebuilt from case_results. Checks: `lab facts check --repo . --facts facts/facts.json` passes offline (0 fact markers, 0 files drifted); the inventory and every previously published release entry are unchanged against main (compared by jq). NOT run before this PR: scripts/facts_validate.py, scripts/repo_descriptions.py render and the facts unit tests (no Python environment on the preparing machine); the PR's CI runs all of them. The descriptions gate (belowStrong == 0 and excellent + strong == graded) holds on these counts (7983 + 6 == 7989). Co-Authored-By: Claude Sonnet 5.5 <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
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.
releases["1.6.2"]: registry baseline
pineforge-parity-baseline-20261021-release-tag-653c94df, the release_tag
re-measurement (7989/7989) at engine v1.6.2
dfe5f367e8935ef549ee7a8a38c1d437d1e8e42e / codegen v1.6.2
f0786eab355b4c1811a03d2644fef0c8cda544dd, HPO v1.6.2
7493a2bd32c7cc5b802710c7287a5bfd27e18f42, snapshot 653c94dfdbb2...,
measured by exp-release-v1-6-2-20261021 (134/134 succeeded).
The active scoreboard identity moves to the same baseline; the counts are
unchanged against 1.6.1 (graded 7989, excellent 7983, strong 6, belowStrong 0,
engineErrors 0, anomaliesExcluded 17, closedProbes 7680, corpusProbes 309).
facts.schema.json allows only "source" and "scoreboard" under a release and no
note or status field, so the hub image status is recorded here instead: there
is NO 1.6.2 hub image and no hub release for v1.6.2 (the hub tag v1.6.2 exists,
its publish run failed and was not re-run; owner decision HUB-TAGMOVE = B), so
this change does not trigger release-finalize for a stored candidate.
The baseline was activated by the Cloud Run job pineforge-initiate-baseline
(execution pineforge-initiate-baseline-7lf5f), which re-derived the release_tag
row from the registry and the evidence bucket and logged:
release_tag: pineforge-parity-baseline-20261021-release-tag-653c94df supersedes
pineforge-parity-baseline-20261020-engine-34f9b3a3 (v1.6.2); exp-release-v1-6-2-20261021
attempt 2 (7989 probes), population cf857209574e (7989 declared, 0 engine-error),
snapshot 653c94dfdbb2 rebuilt from case_results.
Checks:
lab facts check --repo . --facts facts/facts.jsonpasses offline(0 fact markers, 0 files drifted); the inventory and every previously published
release entry are unchanged against main (compared by jq). NOT run before this
PR: scripts/facts_validate.py, scripts/repo_descriptions.py render and the facts
unit tests (no Python environment on the preparing machine); the PR's CI runs
all of them. The descriptions gate (belowStrong == 0 and excellent + strong ==
graded) holds on these counts (7983 + 6 == 7989).
🤖 Generated with Claude Code