chore: remove references to plugin sdk ARCHITECTURE.md

packages/plugin-sdk/src/backend.ts

@@ -96,9 +96,8 @@ export interface PluginFiles {
  * Scoped by name: every table carries the p_<id>_ prefix, and `refs` exposes
  * users, ssh_data, roles and user_roles read-only so a plugin can join against
  * them without being able to write them. In-process code could reach around
- * all of this - see "What this protects, and what it does not" in
- * ARCHITECTURE.md. The capability, the prefix, lint and review are the
- * contract, not a sandbox.
+ * all of this. The capability, the prefix, lint and review are the contract,
+ * not a sandbox.
  */
 export interface PluginDatabase {
   /** Registers a definition and returns its queryable table object. */

packages/plugin-sdk/src/manifest.ts

@@ -420,8 +420,7 @@ export interface PluginManifest {
    * never bundles them: they stay a real dependency in the plugin's own
    * package.json and are resolved from node_modules at runtime instead,
    * because esbuild bundling a native addon breaks the relative path it uses
-   * to locate its compiled binary. See ARCHITECTURE.md under "native
-   * dependencies".
+   * to locate its compiled binary.
    */
   nativeDependencies?: string[];
   /** How a linked desktop treats this plugin. Defaults to "mirror". */

packages/plugin-sdk/src/vitest-preset.ts

@@ -6,8 +6,7 @@
  *   import { pluginVitestConfig } from "@termix/plugin-sdk/vitest-preset";
  *   export default pluginVitestConfig(import.meta.url);
  *
- * Two projects, matching the layout in ARCHITECTURE.md: tests/backend runs in
- * node, tests/frontend in jsdom.
+ * Two projects: tests/backend runs in node, tests/frontend in jsdom.
  */
 
 import fs from "node:fs";