[codex] Add ProofLoop Agent OS context reports#18
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Summary
src/contextReport.tssoproofloop targetwrites a deterministic dated context page at.proofloop/reports/latest.mdalongside target and runner receipts.docs/agent-os/and include it in the npm package files.proofloop.config.json, ProofLoop package aliases, and a CInode dist/cli.js gatestep.dist, and tests for the new context-report contract.Validation
npm run buildnpm test(13 files, 82 tests)node dist\\cli.js gatenode dist\\cli.js target --url https://www.proofloop.live --write-runner-plan --jsonnode dist\\cli.js manifest --dense->blockers=0for local ProofLoop setupnpm publish --dry-run-> includesdist/contextReport.*anddocs/agent-os/*Still Not Done
The generated target report still correctly records these broader blockers: benchmark adapters are not configured for the matched families, the live URL has no deterministic click-through script in this repo, and official scoring still needs upstream scorer/artifact contracts or recorded equivalent judge contracts.