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
Dashboard relaunches on a kit-version skew. A long-lived dashboard server started before a consort-upgrade kept serving its OLD bundle, so an upgraded project was viewed through pre-fix UI (driver steps collapsing to one turn, deploy cards showing build content). The launcher now records the server's kit version and, when it differs from the project's pinned kit, stops the stale server and relaunches the current one (--status/--open report only the current-kit dashboard).
consort-upgrade moves the substrate pin in lockstep. It bumped only the consort kit, leaving .lakebase/scm-utils-ref at the scaffolded/seeded version — so ./scripts/lk kept resolving an OLD scm-utils locally (its CI-auth + pipeline.json-gitignore fixes absent). refreshSurface now dual-pins scm-utils-ref + .local to the version consort ships.
pipeline.json self-heal now covers .gitignore.writePipeline's untrack was undone by the drive's next git add when the file wasn't ignored (pre-0.2.47 substrate); it now also adds .consort/features/*/pipeline.json to .gitignore so the untrack holds and run-state can't collide at the promotion merge.
