solutions-tutorial

ICPC cross-validation generates a primary solution.cpp and an independently correct solution2.cpp to catch mistakes. It also produces a runnable solution.py when appropriate, ensuring both C++ implementations are independently correct.

Difficulty-controlled tutorial writing drafts docs/tutorial.md with the right level of detail for the problem's complexity. It ensures all claims about edge cases and complexity exactly match the generated C++ and Python implementations.

Yes, you can generate an editorial-style explanation that exactly matches your ICPC solution code. The tutorial aligns complexity and boundary claims with the primary solution and cross-check implementation for both normal and difficulty-controlled outputs.

The best way to ensure your ICPC solution tutorial matches the code is to generate them together. This cross-validates the solution implementations and enforces that tutorial claims on boundaries and complexity exactly match the code.

Yes, you need to provide a workspace path and target complexity. The generation uses the already confirmed problem core, target complexity, difficulty, and workspace path to write src/solution.cpp, src/solution2.cpp, and docs/tutorial.md.

You should not use a generated Python solution when it cannot be correct, runnable, and readable. The process strictly writes src/solution.py only when it can provide actual runnable code rather than pseudocode.