Frontier-CS migration: Average Permutation
- Source path:
algorithmic/problems/124
- Challenge handle:
average-permutation-frontier-cs-algorithmic-124
- Execution mode:
piped_stdio
- Target:
linux-arm64-cpu
- Solution contract:
zip_project stdin/stdout
Public/private split
Public validation is a tiny synthetic interactive smoke session committed at v1/public/session.json. Official Frontier-CS-derived hidden input and answer files are packaged only in the private overlay at /home/maplespark/code/Agentics-private-overlays/average-permutation-frontier-cs-algorithmic-124/official-runs.zip under private-benchmark/session.json and private-benchmark/cases/.
Acceptance criteria
python3 scripts/validate_challenges.py passes in the challenge worktree.
- The smoke solution under
test-solutions/average-permutation-frontier-cs-algorithmic-124/ completes public piped_stdio validation locally.
- The private overlay ZIP contains no traversal or symlink entries.
- The public bundle contains no Frontier-CS official input or answer files.
Known risks
Agentics piped_stdio runs one participant process per evaluation, so official sessions chain the source testdata cases inside one stdin/stdout session while preserving each original Frontier-CS interactor protocol, hidden state, query limits, and scoring.
Frontier-CS migration: Average Permutation
algorithmic/problems/124average-permutation-frontier-cs-algorithmic-124piped_stdiolinux-arm64-cpuzip_projectstdin/stdoutPublic/private split
Public validation is a tiny synthetic interactive smoke session committed at
v1/public/session.json. Official Frontier-CS-derived hidden input and answer files are packaged only in the private overlay at/home/maplespark/code/Agentics-private-overlays/average-permutation-frontier-cs-algorithmic-124/official-runs.zipunderprivate-benchmark/session.jsonandprivate-benchmark/cases/.Acceptance criteria
python3 scripts/validate_challenges.pypasses in the challenge worktree.test-solutions/average-permutation-frontier-cs-algorithmic-124/completes publicpiped_stdiovalidation locally.Known risks
Agentics
piped_stdioruns one participant process per evaluation, so official sessions chain the source testdata cases inside one stdin/stdout session while preserving each original Frontier-CS interactor protocol, hidden state, query limits, and scoring.