2025-09 progress

[Matistjati]

I think it's high time we start implementing the new format.

This was based off asking claude to generate a list of differences and what is currently implemented. I cut out a lot of noise. So I might have missed something.

Changes needed to be 2025-09-compliant

problem.yaml

• Change 2023-07 to 2025-09
• rights_owner required if license is not unknown or public domain; must not be set for public domain. Defaults to credits.authors → source (2025-09 specifies fallback chain more precisely)
• Implement constants and constant variants

---

Input Visualizer/generators

• I think we don't have to do anything here? Double-check this assumption. (Of course, typo checking still applies here)

---

Problem Statements

• Support .svg for md
• Support .pdf for md (Markdown can support .pdf problem-package-format#577)
• Some extra polish to make sure it looks good (in particular, tables are quite fragily currently. Probably more)
• Double-check that we support the supported subset of LaTeX
• Multi-pass sample rendering (Multipass sample rendering #352 )
• .in.statement logic and similar

---

Included Files

• include/default/ directory for language-agnostic included files (legacy only had per-language include/<language>/)
• Code limit checked before copying included files

---

Test Data

• test_group.yaml
• <testcase>.yaml
• New test data structure
• Forbid graders from 2025-09
• Implement new score aggregation system (score_multiplier.txt, new keys, etc.)
• New extensions .in.statement, .out, etc. Also hints
• .files directory

---

Input Validators

• New input validator input (validating args, .files)

---

Submissions

• submissions.yaml
• Warn for directories that will not be run (In 2025-09, add warnings for directories that are not run because they are not configured in submissions.yaml #406)

---

Working directory

• Implement new working directory contents

---

Output Validator

• Double-check default validator is compatible with the spec w.r.t. whitespaces (LF, CR, HT, VT)

---

Submit-answer

• Specify them (see Submit-answer is underspecified problem-package-format#578)
• Create some testing problem packages
• Figure out non-specced implementation details
• Implement

---

Static Validators

• Are we happy with the spec?
• Create some testing problem packages
• Figure out non-specced implementation details
• Implement

---

Output Visualizer

• Are we happy with the spec?
• Create some testing problem packages
• Decide how/when they are run.
• Implement.

---

Multi-pass

• Verify current implementation

---

Miscellaneous

• Floats. They are now explicitly specified. We might already be compliant, but check.
• File size recommendation: no file should exceed 100 MiB
• attachments/templates/ subdirectory for code templates per language
• Check for typo'd directories. Warnings for directories that no longer exist in new version (Warn for typo'd folders #399)

---