Repository navigation
Release v7.60.1
The two shell evaluation tasks no longer depend on a model file the evaluation workspace does not have, and their navigation assertions say what a correct extends/overrides answer shows.
Changed
module-navigation-modes-and-slice-buttonsandblueprint-template-and-sample-datatell the agent there is no model file and to write the declarations from scratch. Before, the blueprint task ended with the agent asking for the repository (the skill was never loaded).- The two navigation assertions of the first task are worded as what the answer declares (Sales
extends, Supportoverrides, Reports nothing; each item targets its own module), not as "lists only its own item", which graders read both ways for anextendsregion.