Context profiles and actual models
The legacy full bootstrap accepts mixed, strict and lean. mixed is the default; mixed and strict include the execution scaffold, while lean omits it. The v4 layout instead renders layered rules and does not use these legacy variants. Inspect the selected layout before assuming a profile changed resident context.
A profile is instructional copy, not a model route, budget setting or inference result. Record the actual models and native harness controls for the project. Do not infer model capability, price or instruction adherence from a family name or a historical benchmark. Measure representative real tasks only at the completed-production integration boundary.
The legacy verifier checks consistency between its managed profile marker and scaffold, and requires a measured fleet entry for lean. That is a source diagnostic with a bounded predicate; it cannot establish that every model performs better or that a declared measurement is independent acceptance.
Use the team model policy and task model assignment reference for explicit discovery, fallback, reasoning, price ceilings and configured-versus-run evidence. A same-family critic in fresh context does not count as a distinct-model QA route.