Repository navigation
feat(results): read the release list from the fedcourtsai manifest - #37
Draft
modelmirror-agent wants to merge 2 commits into
Draft
modelmirror-agent wants to merge 2 commits into
modelmirror-agent wants to merge 2 commits into
Conversation
scripts/fetch-results.mjs reads docs/releases.json from fedcourtsai main (at the commit main points to, stamped into index.json) in place of the site's interim src/lib/releases.js, which is removed. A manifest that cannot be fetched, does not parse, lists no releases or breaks the fields the pages read fails the build; each summary is still read at its own tag. RESULTS_REPO now comes from the fetched index. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DfjaLBEcsn9UBUSe33fpwE
Author
|
Generated by Claude Code |
Mirrors the fedcourtsai manifest rule: the page at /results/<slug> shows the documents read at the tag, so a mismatch fails the build. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DfjaLBEcsn9UBUSe33fpwE
Deploying fedcourtsai with
|
| Latest commit: |
a084bd7
|
| Status: | 🚫 Build failed. |
Merged
5 tasks done
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
2 participants
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.
Requested by ModelMirror · project thread
Before: the Results pages read the release list from
src/lib/releases.js, a hard-coded copy in this repo. Each new release needs a change here.After: the Results pages read fedcourtsai's
docs/releases.jsonfrommain. Each summary is still read at its own tag, and the build still fails closed. Release 1 renders exactly as it does today; thedist/output is byte-identical.How:
scripts/fetch-results.mjsfetches the manifest at the commitmainpoints to, and records that SHA inindex.json.schema_versionis wrong, the list is empty, or a field is bad.src/lib/results-data.jstakesRESULTS_REPOfrom the fetched index.src/lib/releases.jsand the README's interim note are removed.Merge order: this PR must merge only after ModelMirrorAI/fedcourtsai#2560 is promoted to
main. Until then, thebuildcheck fails closed with HTTP 404 on the manifest, which is the intended behaviour. I added no fallback, because a fallback would bring back the hard-coded list. Once the manifest is on fedcourtsaimain, re-runbuild, or push any change, and it should go green.Checked:
npm cipasses. With the fetch temporarily pointed at the fedcourtsai branch, the build passes and the output matches the current main build byte for byte.Can reach: no workflow, permission, or secret changes. The change makes one more read-only fetch from
raw.githubusercontent.com, which the build already uses.Preview pages:
/results,/results/ot2026-longconf. The preview will fail to build until the promotion lands.Closes #31
Generated by Claude Code