fix(bridgeAccess): strip non-canonical permission fields before accesses.update

Plan 66 server's `accesses.update` schema is **strict** — it rejects extras
like `defaultName` and `name` in permissions[] (asymmetric vs `accesses.create`
which is lenient and `accesses.checkApp` which actually REQUIRES `defaultName`).

Phase 5 e2e on demo surfaced this:
  POST accesses.update {permissions: [{streamId, level, defaultName}]} →
  invalid-parameters-format: OBJECT_ADDITIONAL_PROPERTIES ["defaultName"]

Defensive strip in `ensureBridgeAccess` mirrors the pattern already in
`CollectorClient.acceptUpdate` line 528: keep only the canonical
`{streamId, level}` or `{feature, setting}` shape regardless of caller input.

Validated by /tmp/plan58-e2e-mismatching.mjs against demo (Plan 66, schema v1).
489/489 tests pass. Lint clean.

Author: perki

ts/appTemplates/bridgeAccess.ts

@@ -109,7 +109,14 @@ export async function ensureBridgeAccess (
     }
 
     // Update in place. Server merges clientData; we only send our new keys.
-    const updatePayload: Record<string, any> = { permissions: options.permissions };
+    // accesses.update's permissions schema is strict (rejects defaultName / name);
+    // strip to canonical {streamId,level} | {feature,setting} regardless of caller input.
+    const cleanedPermissions = options.permissions.map((p: any) => {
+      if (p.streamId) return { streamId: p.streamId, level: p.level };
+      if (p.feature) return { feature: p.feature, setting: p.setting };
+      return p;
+    });
+    const updatePayload: Record<string, any> = { permissions: cleanedPermissions };
     if (options.clientData != null) updatePayload.clientData = options.clientData;
 
     try {