Skip to content

Remigrate Frontier-CS P1 challenges faithfully#512

Merged
ifsheldon merged 12 commits into
mainfrom
codex/frontier-p1-faithful-remigrations
May 27, 2026
Merged

Remigrate Frontier-CS P1 challenges faithfully#512
ifsheldon merged 12 commits into
mainfrom
codex/frontier-p1-faithful-remigrations

Conversation

@ifsheldon

Copy link
Copy Markdown
Contributor

Summary

Faithfully reset and remigrate the Frontier-CS P1 migration breaks identified by the faithfulness QA pass.

This PR:

  • removes the previous unfaithful public bundles for 34 reset candidates;
  • remigrates 31 source-interactive algorithmic problems as piped_stdio with acknowledge_stdio_protocol_framing: true;
  • keeps Binary Slate 81 as the already-fixed piped_stdio reverify case;
  • remigrates the three research P1s with source-faithful public/private contracts;
  • adds meaningful non-cheating test solutions for the remigrated challenges;
  • records the faithfulness QA logs under migrations/.

Validation

  • python3 scripts/validate_challenges.py -> validated 247 challenge(s)
  • Private ZIP staging inspection found no traversal paths, symlinks, or public-file overwrites.
  • Algorithmic interactor copies were compared against Frontier-CS source interactors.

Production Notes

The private official overlays are staged locally under /tmp/frontier-p1-remigration and will be uploaded/backed up during the Agentics production publication lifecycle. Moltbook links are intentionally not committed in challenge files.

Related Issues

Refs #3, #244, #246, #248, #250, #252, #254, #256, #258, #260, #262, #266, #268, #270, #272, #274, #280, #282, #284, #286, #290, #292, #294, #300, #302, #304, #306, #308, #310, #312, #314, #316, #471, #498.

ifsheldon added 12 commits May 28, 2026 00:42
Remove the public challenge bundles and test solutions for the 34 P1 faithfulness breaks that still need full remigration. Keep binary-slate-machine-frontier-cs-algorithmic-81 because it already has the later piped_stdio remigration and is reverify-only.\n\nVerification: python3 scripts/validate_challenges.py
Remigrate algorithmic problems 3, 4, 10, 13, and 14 as piped_stdio challenges using the original Frontier-CS Testlib interactors and honest public smoke solutions.

Private official sessions remain staged outside Git under /tmp/frontier-p1-remigration/worker-a. Verification: python3 scripts/validate_challenges.py; byte-for-byte interactor comparison; private ZIP path inspection.
Remigrate algorithmic problems 16, 17, 25, 28, and 30 as faithful interactive Agentics challenges with meaningful smoke solutions.

Problem 30 keeps the original interactor source for audit and uses an adapter to preserve source behavior across Agentics session framing. Private official sessions remain staged outside Git under /tmp/frontier-p1-remigration/worker-b.

Verification: python3 scripts/validate_challenges.py; byte-for-byte interactor comparison; private ZIP path inspection.
Remigrate algorithmic problems 36, 40, 52, 53, and 54 as piped_stdio challenges using the original Frontier-CS interactors and honest smoke solutions.

Private official sessions remain staged outside Git under /tmp/frontier-p1-remigration/worker-c. Verification: python3 scripts/validate_challenges.py; byte-for-byte interactor comparison; private ZIP path inspection.
Remigrate algorithmic problems 60, 63, 68, 69, and 73 as piped_stdio challenges with original Frontier-CS interactor code and honest smoke solutions.

Private official sessions remain staged outside Git under /tmp/frontier-p1-remigration/worker-d. Verification: python3 scripts/validate_challenges.py; byte-for-byte interactor comparison; private ZIP path inspection.
Remigrate algorithmic problems 77, 79, 82, and 85 as piped_stdio challenges using original Frontier-CS interactors and honest smoke solutions.

Binary Slate 81 was reverified separately and intentionally left unchanged. Private official sessions remain staged outside Git under /tmp/frontier-p1-remigration/worker-e.

Verification: python3 scripts/validate_challenges.py; byte-for-byte interactor comparison; private ZIP path inspection.
Point Testlib interactor output streams at stdout so participant-facing replies are delivered correctly, and tighten the P1 smoke baselines that exposed official-session hangs. The modulo-collision interactor now preserves source scoring semantics with sparse residue counts so source-scale bucket IDs fit evaluator memory.\n\nVerification: python3 scripts/validate_challenges.py; local official piped_stdio sweep for the previously failing P1 sessions.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant