Repository navigation
Conversation
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
This branch has not been deployed
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
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.
The companion previously required eight generated files to be committed: six
task-review-*.jsdata bundles and two Cost vs Score PNGs. They added about 18.7 MB of duplicate content to the working tree. A fresh Pages build now generates them from the tracked record, audit metadata, task catalog, answer marks, and model registry. The generated outputs were checked byte for byte against the former committed files.Removed in this PR
task-review-data.jsandtask-review-tasks.js: full and slim task catalogs generated from the pinned audit metadata and task catalog.task-review-audit.jsandtask-review-published.js: browser wrappers around tracked audit JSON.task-review-results.js: browser wrapper aroundresults/rerun.json.task-review-variants.js: derived box-scoring alternatives from tracked answer marks and the model registry.results/dataset/cost-vs-score*.png: rendered from the committed record and registry.Further cleanup opportunities, scoped separately
answers/*.json(~16 MB) are generated but are the only tracked per-question marks and responses used by Explore and the box-scoring review. Moving them out of Git requires a versioned external source plus a working Pages fetch/build path.results/audit/gold_metadata/andresults/audit/gold-distributions.jsoncontain the pinned question and reference material used to build the full task catalog. Removing them would require another reproducible, pinned source in CI.results/rerun.jsonis derived but cannot be rebuilt from a clean checkout: the raw sweep records live under ignoredresults/runs/. Keep it until the record build has a complete tracked or published source.results/archive/,scripts/archive/, and the audit paper snapshot are historical evidence rather than active site inputs. They can move to a release or research archive after their provenance links are reviewed.original/contains the released upstream code and visual assets, preserved with hashes; any size reduction requires a deliberate provenance policy and is outside this change.docs/reviews/anddocs/plans/package-layout.mdcontain historical review and design notes. A documentation pass could mark superseded findings or move them to an archive.Validation
uv run --group scripts vladbench build --steps site --site dist/pagessucceeds.uv run ruff check .,uv run ty check,uv run pytest -q(138 passed, 11 skipped), and push hooks pass.