mirror of
https://github.com/stablyai/orca.git
synced 2026-09-28 00:02:41 +00:00
Neil
e8cbcacbb9
The suites in this branch drive both builds' real Store over a real orca-data.json. This is the same comparison one layer out: two packages built by electron-builder from this stack and from the v1.4.199 tag, each booted headless on an isolated user-data-dir, so the rollback also crosses packaging, the data-path init ordering, and the cohort migrations that only run at real startup. Three answers, all with a same-version control on a byte-identical copy: the old build reads the new state without throwing or losing a row, writes back a shape the new build still accepts (0 keys removed, 0 added on the return leg), and deletes nothing it does not understand. The controls are the point. A restart of EITHER build empties workspaceSession.unifiedTabs and tabGroups for the worktree; read as a downgrade diff alone that is terminal tab-group loss which is not there. An injected ssh:* partition that failed schema validation was discarded identically by both builds, producing exactly the silently-dropped-SSH-rows symptom this effort was hunting -- from a malformed fixture, not from the rollback. Also records what a userData rollback cannot reach: the old-client empty-publish skew and relay protocol-version negotiation are both wire surfaces needing two paired runtimes.