Functional correctness
How fully the public summary displays the required normalized status.
This test measures whether a model can explore an unfamiliar module layout, trace a public renderer to the correct implementation file, and make a small integrated change.
Nomination prepared · results pendingTest assignment
The model starts from the public renderAccountSummary(account) API and repository documentation. It must follow the rendering flow, locate the nested status-label implementation, and repair it without moving the API or editing tests.
Each criterion receives 0–10. Public and objective checks remain separate from the manual score.
How fully the public summary displays the required normalized status.
How safely it handles arbitrary accounts, separators, whitespace, empty values, and numbers.
How clear and idiomatic the formatter is within the existing module design.
Whether the model found the correct nested file and avoided workaround changes elsewhere.
Overall is the arithmetic mean of the four scores.
This page defines the test before model execution. The future table will show public and objective results, four review scores, time, cost, and runtime route.