Correct stale comments in the theme bundler, presence window, relay tests, sidecar build, and direct-interop

lib/scripts/bundle-themes.mjs

@@ -1,7 +1,7 @@
 #!/usr/bin/env node
 /**
  * Download VSCode theme extensions from OpenVSX, extract theme JSONs,
- * and write lib/src/lib/themes/bundled.json.
+ * and write lib/src/lib/themes/bundled.json and bundled-extensions.json.
  *
  * Usage: node scripts/bundle-themes.mjs
  *
@@ -33,7 +33,7 @@ const EXTENSIONS = [
 ];
 
 // Excluded: legacy/classic variants, plus HC variants (our bg-only chrome
-// renders flat in HC themes — see docs/specs/theme.md).
+// renders flat in HC themes — see DESIGN.md → "The Bg-Only Chrome Rule").
 const EXCLUDED_THEMES = new Set([
   'vscode.theme-defaults.dark',
   'vscode.theme-defaults.light',

relay/test/app.test.mjs

@@ -46,8 +46,8 @@ test('createApp refuses a setup password outside the canonical 32-byte hex shape
 });
 
 test('GET / serves the stub landing page when the Pocket app is not built', async () => {
-  // freshApp configures no `pocketDir`, so this is always the stub (slice 5
-  // serves the real Pocket build here when `pocketDir` points at one).
+  // freshApp configures no `pocketDir`, so this is always the stub (the real
+  // Pocket build is served here when `pocketDir` points at one).
   const { app } = await freshApp();
   const res = await app.request('/');
   assert.equal(res.status, 200);

relay/test/harness/malicious-relay.mjs

@@ -4,7 +4,7 @@
  *
  * It sits where `relay/src/relay.ts` sits — the real {@link RelayHub}, wrapped
  * rather than reimplemented, so what it *routes* is the shipped behavior — and
- * adds the four things a hostile operator has: it records every frame, and it
+ * adds what a hostile operator can do: it records every frame, and it
  * may drop, reorder, duplicate, modify, or invent one on either egress leg.
  *
  * `guards: false` removes the relay's own `ct` / `id` / shape checks, which are

remote-lib-common/src/security/presence-window.ts

@@ -6,7 +6,8 @@
  * Each entry names the identities its proof was verified for, so a redeem can
  * re-run the ACL conjunction against them and nothing else. In memory only,
  * and evaluated rather than reaped: an entry past its bounds reads as closed
- * and is dropped the next time anything asks about it.
+ * and is dropped the next time anything asks about it, and every `seed` also
+ * drops the entries past the hard cap.
  */
 
 import { PRESENCE_WINDOW_IDLE_MS, PRESENCE_WINDOW_MAX_MS } from './e2e-bounds.js';

scripts/direct-interop/run.mjs

@@ -88,8 +88,9 @@ const blackhole = process.argv.includes('--stun-blackhole');
 /** Whether the page is the one-time page Hosted serves; see question 5. */
 const stunPage = blackhole || process.argv.includes('--stun');
 /**
- * The policy the addon's Burrow runs under, which `directPeeringFor` reads: My
- * Relay only's unrestricted Burrow by default, as Pocket meets it.
+ * The policy the addon's Burrow runs under, which `directPeeringFor` reads:
+ * "Anywhere, through your Relay"'s unrestricted Burrow by default, as Pocket
+ * meets it.
  */
 const level = allowed ? 'local' : stunPage ? 'anywhere' : 'relay';
 const networkPolicy = { level, allowed: allowed ?? [], autoUpdate: false };

standalone/scripts/build-sidecar-proxy.mjs

@@ -55,7 +55,7 @@ const NATIVE_DIRECT = SIDECAR_RUNTIME_DEPS.flatMap((name) => [name, `${name}/*`]
 // entry and the build would go green on a `burrow.cjs` that cannot load it.
 if (!SIDECAR_RUNTIME_DEPS.includes('node-datachannel')) {
   throw new Error(
-    'sidecar: package.json no longer declares "node-datachannel" under "dependencies" — it would ' +
+    'sidecar: package.json no longer declares "node-datachannel" — it would ' +
       'be inlined into burrow.cjs, and nothing before the first direct-offer on a real machine ' +
       'would notice.',
   );