False conflict detection when revisionHistory is empty – packages/core/src/projects/initialiseProjectState.ts looks for the most recent on‑disk revision and marks the project as conflicted whenever it can’t find that revision in the browser state. When the shipped conf.state has never been exported with a revision (its revisionHistory is [], which is the default produced inside the repo), the lookup uses undefined and always falls into the “conflict” branch even if there’s no real divergence. This locks new projects into the red “Browser state is not based on disk state” warning until the user manually resolves it every reload, despite both states being compatible.