Task Ladder: label each rung's heading budget as a default Each per-rung heading read as e.g. "L1_migration_entity - budget 45 min, denominator 11" - easy to misread as a fixed/hardcoded value, when it's actually just the rung's own default (a per-job parameter, already called out in the page's own intro note). Headings now say "default budget" explicitly; every internal/cross-page anchor link into these headings is updated to match the new slug.
Add Check Registry: detailed reference for every oracle check (#490) A new page covering all 30 checks in oracle/CheckId.java (S1-S9, P1-P3, M1-M4, B1-B3, C1-C2, F1-F9) - what each one actually verifies and how, grounded directly in its own checker implementation (StructureChecks/MoneySafetyChecks/BuildChecks/ComposeChecks/ BlackboxScenarios), not just the one-line description. Task Ladder now cross-references it directly: every check id in each rung's own Checks: line links to its entry here. Also corrects Task Ladder's own framing of rung budgets - they are per-job DEFAULTS (JobCfgFactory only sets them from an explicit flag; left blank, RunBench falls back to the rung's own budget_sec), not hardcoded caps, which the budget column/table could previously be read as implying.
Add Task Ladder: detailed reference for every task rung (#490) A new page (linked from Home, Features, and User Manual: Jobs) covering each rung in tasks/ladder.json in detail: what it actually asks the agent to build, its budget, denominator, and exact check-id list, and what's new compared to the rung before it - grounded directly in each rung's own PROMPT.md and ladder.json's own description/checks fields. User Manual: Jobs' existing short mention of the Task field now links to it, per the issue's own request for 'a shorter version of this information with a link to a full one.'