You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Critic applicability — a critic in .tenet/critics.json can now declare "applicable_jobs": ["F2", "F3"] (decomposition job ids) and will only run on the jobs it declares. Domain critics (migrations, auth, ledgers, a11y) no longer re-run on every job's eval — cost scales with applicability instead of roster size.
Critic retry safeguard — tenet_retry_job now enforces when a critic may be retried in place: only infra-failure retries (the critic produced no verdict) and only while no dev/integration_test job completed since its eval round dispatched. No more re-rolling a red verdict hoping for a green, and no more "greening" an old round against code that changed after it was dispatched.
Changes
applicable_jobs (TASK-007): critics whose list excludes the source job's dag_id are skipped at dispatch and reported under skipped_inapplicable. Omitted or empty list = applies to every job; ad-hoc jobs (no dag_id) always get the full roster. The round's expected_eval_stages stamps from what actually dispatched, so the resume gate waits on exactly the critics that ran. A declared id no registered job carries surfaces as a non-fatal stale_dag_id_warnings entry at dispatch. Honored on built-ins too.
Critic retry safeguard (TASK-056): any parsed verdict — red or green — is refused, with the error naming the legal path (fix loop / fresh tenet_start_eval round). Unstamped/legacy critic rows fail closed. The three-way classifier's documented no-verdict retry still works exactly as before and is now server-enforced rather than advisory. Dev and non-critic retries are unchanged.
Skill and tool docs updated: the execution loop's classifier bullet notes the enforcement, and tenet_retry_job's description states the legality conditions up front.
Breaking changes
Behavior change: retrying a critic that already produced a verdict (red or green) via tenet_retry_job was previously accepted and is now refused. Orchestrators following the documented three-way classifier are unaffected — the legal no-verdict retry still works; red verdicts go through the fix loop as prescribed.