fix: bundled plugins path for source runs and backend cleanup

src/backend/tests/database/db/audit-log-user-id-nullable.test.ts

@@ -10,8 +10,8 @@ import { afterEach, beforeEach, describe, expect, it, vi } from "vitest";
  *
  * The Drizzle schema said so, the repository was written against it, but the
  * runtime bootstrap still created `user_id TEXT NOT NULL`. A second, corrected
- * `CREATE TABLE IF NOT EXISTS` further down was a no-op — the table already
- * existed — so every fresh install got the old constraint and every user
+ * `CREATE TABLE IF NOT EXISTS` further down was a no-op, the table already
+ * existed, so every fresh install got the old constraint and every user
  * deletion (including the OIDC account-link cleanup) failed once the account
  * had logged in at least once.
  */

src/backend/tests/database/db/bootstrap-covers-all-tables.test.ts

@@ -7,7 +7,7 @@ import { afterEach, beforeEach, describe, expect, it, vi } from "vitest";
 /**
  * `migrateSchema()` carried a `SELECT id FROM <table> LIMIT 1` probe for a
  * number of tables that the primary bootstrap already creates. The probe never
- * threw, so the `CREATE TABLE IF NOT EXISTS` in its catch never ran — and one
+ * threw, so the `CREATE TABLE IF NOT EXISTS` in its catch never ran, and one
  * of those unreachable copies had drifted away from the real definition
  * (`sessions` had lost `ON DELETE CASCADE`).
  *
@@ -61,7 +61,7 @@ describe("bootstrap creates the tables the removed probes covered", () => {
   });
 
   it("creates them on a database old enough to predate them", async () => {
-    // A database with users and hosts but none of the tables above — the
+    // A database with users and hosts but none of the tables above, the
     // upgrade path the deleted probes appeared to be protecting.
     const seed = new Database(":memory:");
     seed.exec(`

src/backend/tests/database/db/multi-dialect.test.ts

@@ -59,7 +59,7 @@ describe("needsExplicitPersist", () => {
 
 /**
  * schema.pg.ts and schema.mysql.ts are generated from schema.ts. These check the
- * generated output is usable rather than merely syntactically valid — the
+ * generated output is usable rather than merely syntactically valid, the
  * repository layer's correctness rests on all three behaving the same way.
  */
 describe("generated schemas", () => {
@@ -133,7 +133,7 @@ describe("generated schemas", () => {
    * SQLite builds its indexes at runtime from PERFORMANCE_INDEXES; Postgres and
    * MySQL only ever get what the migrations declare, which comes from schema.ts.
    * Anything listed in one and missing from the other is an index the engines
-   * chosen for scale silently do without — which is how 31 of them went missing.
+   * chosen for scale silently do without, which is how 31 of them went missing.
    */
   it("declares every performance index in schema.ts", () => {
     // Both are the leading column of an existing composite unique index, which

src/backend/tests/database/db/share-ssh-auth-backfill.test.ts

@@ -7,7 +7,7 @@ import { afterEach, beforeEach, describe, expect, it, vi } from "vitest";
 /**
  * Sharing a host used to hand the owner's SSH authentication to the recipient
  * unconditionally. 2.6.1 put that behind `ssh_data.share_ssh_auth`, added as
- * `NOT NULL DEFAULT 0` — so every host shared before the upgrade silently
+ * `NOT NULL DEFAULT 0`, so every host shared before the upgrade silently
  * stopped supplying credentials, and recipients hit "No valid authentication
  * method provided" on hosts that had worked the day before.
  *

src/backend/tests/database/db/ssh-credentials-username-rebuild.test.ts

@@ -7,7 +7,7 @@ import { afterEach, beforeEach, describe, expect, it, vi } from "vitest";
 /**
  * `ssh_credentials.username` became nullable when key-only credentials landed,
  * and databases created before that are rebuilt on startup to drop the
- * constraint — SQLite cannot ALTER a column.
+ * constraint, SQLite cannot ALTER a column.
  *
  * The rebuild restated the table's columns as a literal, then copied rows with
  * `INSERT INTO temp SELECT <every live column>`. The table has gained columns