Repository navigation
Preserve and reproduce real TinyDev evidence - #29
Conversation
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
Important Review available on request
Reviews should be triggered manually for repositories with fewer than 10 stars. Select Trigger review above or comment ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Reproduction check completed successfully. Real TinyDev workflow run 32085695308 used the exact pinned Torch 2.13.0 install and produced artifact 9306822005. The ZIP container digest differs because Actions ZIP metadata is run-specific, but the canonical |
Preserves the first successful real TinyDev generation as a compact, self-hashed source-grounded evidence manifest instead of committing generated model text.
The manifest binds workflow run 32084697518 and artifact 9306497613 to the generator commit, merged main commit, artifact ZIP/JSON digests, corpus/artifact/manifest hashes, prompt/sample counts, model/tokenizer revisions, DEV key condition, runtime versions, deterministic retry counts, and independently recomputed integrity checks.
It explicitly scopes this evidence as a DEV_KEYS TinyDev generation prerequisite, not M6 readiness and not a confirmatory result.
This PR also pins the TinyDev CPU Torch install from a floating >=2.4,<3 range to the exact 2.13.0 runtime observed in the successful source run. The real-generation check is expected to rerun and reproduce the same content-addressed corpus artifact.