Project update: 14 November 2026. GitHub pull request #7: merged into GitHub source, not necessarily deployed. Commonveil has not been independently security audited.
A follow-up patch corrected a JavaScript initialisation error introduced by the experimental protocol integration.
Why this matters
Shipping new capabilities can expose ordinary application reliability problems. Here, references to a function were evaluated before JavaScript had initialised that function, causing a blank page during the sign-in experience. The fix moved those references into the correct order. The failure was about rendering and not evidence that encrypted messages had been decrypted or lost.
Detailed change record
The public engineering notes below describe what was implemented or proposed and the evidence recorded with the change. Historical instructions in the notes describe the pull request at the time it was raised.
Urgent: the live site shows a blank page to everyone signed in
0.23.0 (#6) broke the app. After "Checking your keys" it throws Cannot access 'loadProfiles' before initialization and shows a blank page. This fixes it.
Cause: in src/lib/secure/ChatContext.jsx, two lines I added with the experimental protocol layer use loadProfiles about 100 lines above where it is declared. That throws as soon as the component renders.
Effect: the app can't be used. No messages, keys or accounts are affected, because it stops before showing or sending anything.
Fix: the two lines now come after the declaration.
So it can't happen again: npm run check:order now runs in npm run verify, and so in CI. It runs the TypeScript compiler over src/ and fails on anything used before it is declared. On the 0.23.0 code it reports this exact bug. On the fix it reports nothing.
Tested
- Reproduced in headless Chromium against a local self-hosted site: sign up, finish set-up, blank page with the error above.
- Fixed: the same walk-through now loads the app with no errors. The new Settings section renders and "Turn on for this device" works, showing the protocol handle.
- Checks:
npm run verifypasses: lint, the new order check, type checks, 237 tests and the build.
Why this wasn't caught
The tests run the app's logic against the real backend handlers, but nothing rendered the app itself, and I did not open 0.23.0 in a browser before it was merged. docs/SECURITY_REVIEW.md records the incident. An automated sign-in browser test in CI is still missing.
Decisions and principles behind the work
Comutability is building towards privacy, user control and genuinely self-hostable software. That does not mean every proposal is already deployed. Cryptography and security improvements need qualified human review and meaningful tests before any strong safety promises are made.
What comes next
Retain regression coverage for the sign-in path and verify deployment rather than relying on a successful source-code merge alone.
