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
P11 project night orchestrator. New git-backed suite setup now defaults to
one lock-owning project coordinator that runs producer, integration, cleanup,
and reflection lanes inside a single scheduled job. This addresses live-fleet
contention where separate same-project jobs woke up inside each other's
workspace-lock windows and produced blocked/noisy runs.
profile_project.py profile --classic-suite and lifecycle.py setup --classic-suite keep the prior separate P1-P10 job shape
available for projects that intentionally want it.
Changed
profile_project.py now proposes P11 by default for git-backed projects and
records capability-backed lanes inside the orchestrator params.
lifecycle.py add can still add individual classic patterns; explicit P11
adds resolve through the orchestrated proposal path.
Fleet validation, materialization, docs, and lifecycle tests now recognize
P11 as a first-class known template.