[SashaMIT]

Summary

node scripts/home-clipboard-source-gate.mjs is part of just verify, and it fails on develop:

Error: capsules/chat-room/browser/chat-room.js must use the canonical Home Clipboard client and its fixed target binding

Cause: commit 32f1634d ("fix(chat): preserve conversation drafts and renew Home authority in place"). After that change, Chat builds its client options in clipboardOptions(), and it tears down and rebuilds the Home Clipboard client when Home renews its token (chat-room.js:18-24, :65-69). Chat still uses the canonical client, still has the one fixed targetId: "chat-room", and still calls homeClipboard.start(). But the gate matched the literal text createHomeClipboardClient({, which is now gone.

Evidence: the gate passes with 32f1634d^:capsules/chat-room/browser/chat-room.js (exit 0) and fails with 32f1634d:… (exit 1). git log -S 'createHomeClipboardClient({' names that commit.

Decision: the gate was wrong, the code is right. The renewed token has to reach a new client, so going back to two inline option objects would only duplicate the binding to satisfy a text match. This PR does not change Chat or any product behaviour.

Changes

1. scripts/home-clipboard-source-gate.mjs: for each migrated capsule, the gate now requires:

   • the canonical client import,
   • a createHomeClipboardClient( call,
   • exactly one targetId: in the file, equal to the fixed binding,
   • homeClipboard.start().

   This is stricter than before in one way: a second or different target is now refused even when the call uses an inline object. The old check only asked whether the binding text appeared somewhere in the file.

2. scripts/home-clipboard-source-gate.test.mjs (new): runs the real gate on a copied tree. Chat as it is now passes. These changes are refused: a different target, a second target, no start(), no canonical client, direct navigator.clipboard.

3. CI did not run this gate. .github/ has no reference to it, so the break went unnoticed. scripts/test-source-gate.sh product-ui now runs the gate and its test, so both CI source-gate and the local pre-push gate run them. just verify runs test-source-gate.sh, so its separate line is removed.

Tests

node scripts/home-clipboard-source-gate.mjs   -> {"schema":"elastos.home.clipboard-source-gate/v1","ok":true,...}
node --test scripts/home-clipboard-source-gate.test.mjs
ok 1 - Chat's renewable Home Clipboard client passes the gate
ok 2 - the gate refuses Chat with a different target
ok 3 - the gate refuses Chat with a second target
ok 4 - the gate refuses Chat with no client start
ok 5 - the gate refuses Chat with no canonical client
ok 6 - the gate refuses Chat with direct navigator.clipboard

With develop's gate, test 1 fails (not ok 1). ./scripts/test-source-gate.sh product-ui exits 0. The prepush section reports 70 OK. git diff --check, check-product-data and public-copy-entropy-check are clean.

Gaps

• The gate is a source-text check. The real Clipboard behaviour is proven by scripts/home-clipboard-headless-smoke.mjs, which this PR does not change.
• This branch does not contain the zip 9 / RUSTSEC change. Until that lands in develop or is merged here, cargo-audit fails and CI cancels the run.

---

Generated by Claude Code

[SashaMIT]

Review: A. The 6 Clipboard gate tests pass and CI now runs them. Ready for Anders once CI is green.

[SashaMIT]

CI on 4728164: source-home-linux (ubuntu-24.04) failed in the model-repair journey (run 39019721681, job 117389514977). The error was Installed Home journey failed: stage=model_interrupted_get_retry code=timeout check=restarted_home.

This failure is not caused by this PR:

• The Runtime restarted (the artifact shows 2 runtime episodes), but one of the 60 s waits after the restart, under subcheck = "restarted_home" in ci-installed-home-journey.mjs, timed out. The receipt does not record which wait.
• This PR changes only the Clipboard source gate and its test. elastos/ and capsules/ are byte-identical to ci: installed journeys name the observer failure, and the SmolLM2 proof uses a vendored license #413 at 69e2bae, and the same job passed on that head (run 39019718818).

No fix exists yet. I can't re-run the job from here (403). It needs one re-run.

---

Generated by Claude Code