[ZacharyZcR]

Fixes Termix-SSH/Plugin-Sync#8. That server was upgraded 2.5.1 → 2.9.2 → 26.11.0 on SQLite and logs no such column: "sync_id" on every sync pass.

2.8 added these columns on start (release-2.8.0-tag, src/backend/database/db/index.ts):

addColumnIfNotExists("vault_profiles", "sync_id", "TEXT");
addColumnIfNotExists("dashboard_service_links", "sync_id", "TEXT");
addColumnIfNotExists("dashboard_service_links", "updated_at", "TEXT");
addColumnIfNotExists("homepage_items", "sync_id", "TEXT");

2.9 handed those tables to plugins and dropped that code. The plugins' adoption migrations use CREATE TABLE IF NOT EXISTS followed by a rename, so an existing 2.5 table keeps its columns. A database that skipped 2.8 therefore never gets them. Homepage and Vault define syncId on the adopted tables, so every sync read of those rows fails and that kind of data is skipped. Snippets had the same gap and already has a repair in core. Homepage and Vault did not.

This runs the existing repair over these tables too, under their legacy and adopted (p_…) names. It adds the missing columns, fills a sync_id for every row and creates the unique index, the same way it does for snippets. The columns come from comparing the plugins' current table definitions with 2.5.1's schema: homepage_items and vault_profiles only miss sync_id, dashboard_service_links also misses updated_at, and homepage_layouts misses nothing. Vault's provider column comes from its own migration. Since the repair now covers more than snippets, the file and function are renamed (legacy-plugin-columns.ts, repairLegacyPluginColumns).

Validation: a new test builds the three tables with their 2.5.1 columns under the adopted names, as on the reporter's server, and checks the columns and filled sync ids after repair. It fails with the previous table list. Full suite: 4638 passed, 1 skipped. tsc -b, eslint, prettier and the test location check pass.

[termix-triage-bot]

AI review | Needs changes

Adds missing sync and timestamp columns to legacy homepage and vault tables during SQLite upgrades to resolve sync failures for databases that skipped version 2.8. The change is safe, follows repository rules, and includes appropriate tests.

• major Core PRs should target the current dev-* branch, not main. If no dev-* branch exists yet, ignore this.

_{Reviewed 0d2b562. AI can be wrong, a maintainer still decides. Comment /termix review to run it again.}