Skip to content

ci(conformance): grade TR-ANC-002 against a pinned anchor corpus - #550

Closed
astrogilda wants to merge 2 commits into
agentrust-io:mainfrom
astrogilda-forks:ci/anchor-corpus-check
Closed

astrogilda wants to merge 2 commits into
agentrust-io:mainfrom
astrogilda-forks:ci/anchor-corpus-check

Conversation

@astrogilda

Copy link
Copy Markdown
Contributor

What this changes

@lywinged, .github/workflows/anchor-corpus.yml grades a 27-case registry anchor corpus with TR-ANC-002, checking each file against its SHA-256 in pin.json. As @imran-siddique asked on #469, it installs and runs nothing from the corpus repository, and a disagreement not listed in pin.json fails the job. No corpus release has these cases yet, so pin.json names a commit; when a verdict moves, I'd open a pin.json bump for you to merge. I'll fold in comments made until October 30, such as a preference to vendor the cases byte-identical, as #548 did.

Type of change

Conformance tooling, with no normative effect.

Spec section

At main TR-ANC-002 agrees on 19 of 27 and pin.json lists the other eight; on #533, seven of those eight agree and print a notice.

Tests for a fix

This job's run on my fork is green.

Checklist

  • DCO sign-off on all commits (git commit -s)

Add a workflow that downloads an external registry anchor corpus at a
commit pinned in conformance/interop/trace-anchor/pin.json, checks every
file against its SHA-256, and answers each case with this suite's own
TR-ANC-002. The corpus is read as data and nothing from it is installed.

The job fails on a disagreement that pin.json does not list. At main it
agrees on 19 of 27 cases; the 8 listed disagreements are the ones
spec/registry-anchor-v1.md and the open entry-binding change address.

Signed-off-by: Sankalp Gilda <23521054+astrogilda@users.noreply.github.com>
Add a short section to the TR-ANC module page saying what the Anchor
corpus workflow checks, when it fails, and how its pin moves.

Signed-off-by: Sankalp Gilda <23521054+astrogilda@users.noreply.github.com>
@astrogilda
astrogilda requested review from a team, lywinged and rajnisht7 as code owners October 16, 2026 22:29
@github-actions

github-actions Bot commented Oct 16, 2026 •

Copy link
Copy Markdown
Contributor

❔ Contributor Check: UNKNOWN

Check Result
Profile UNKNOWN
Credential LOW
Overall UNKNOWN

Automated check by AgenTrust Contributor Check.

@github-actions github-actions Bot added the needs-review:UNKNOWN Contributor check flagged UNKNOWN risk label Oct 16, 2026
@imran-siddique

Copy link
Copy Markdown
Member

@astrogilda take your own offer: vendor the 27 cases byte-identical under conformance/interop/trace-anchor/, as #548 did, and drop anchor-corpus.yml. A job that fetches from another organisation's repository can turn our CI red when that repository moves, and #469 settled that the grading lives with the cases, not in a workflow here. Keep grade.py and pin.json so a reader can check the vendored bytes against your commit.

@astrogilda astrogilda closed this Oct 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

needs-review:UNKNOWN Contributor check flagged UNKNOWN risk

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants