Private-span fix — 15 November 2026
[[private: …]] spans never reach any model and never appear in the handoff or export. The shared router replaces each span with [private note withheld] before any device-only, hybrid, cloud, local-rules or rehearsal processing; unclosed spans are withheld to the end. Original and masked offsets are retained, and actions quoting private spans or placeholders are dropped. Retained model quotes must be verbatim substrings of the submitted masked text. The UI and Markdown export header report the number of spans withheld. Automatic email/phone masking applies to the cloud packet; emails and phones remain visible in device-only and local-rules results.
The owner's on-device observation below predates this fix. This release's regression checks use fake device/cloud ports, local rules and loopback rehearsal ports. The original privacy-fix task did not itself perform post-fix live inference; the later human Edge cloud observation is recorded below. No post-fix Nano success is recorded.
Live Firebase verification — 14 November 2026
- Project: dedicated Firebase project with the Gemini Developer API backend; Firebase AI Logic App Check enforcement ON (basic protection, replay protection off).
- App Check: the local development debug provider, with a debug token registered by the owner in the Firebase console. It lives only in the untracked
.env.development.local. - Before registration: a fresh Chrome profile was rejected with
401 Firebase App Check token is invalid, which shows enforcement is active. After registration, App Check passed. - Model:
gemini-3.5-flash-lite(listed as stable on the Firebase AI Logic models page) returned a real cloud response. - UI flow (fresh headless Chrome profile,
npm run dev:live): Firebase mode → fictional sample → cloud consent on the redacted preview → Create handoff. Result badge Gemini · cloud; attempted route "Firebase cloud route attempted with the redacted preview"; 3 source-linked action cards; about 2 s. - Production safety:
npm run build/build:livenow end withscripts/check-dist.mjs. It fails if a bundle contains a debug-token assignment, the dev marker, the debug-token variable name or the local token value. A real-config production build passes; a deliberately wrong (development-mode) bundle fails. - Production build: configured with the reCAPTCHA Enterprise site key (domain-restricted to the hosted web.app domain); the release configuration check and the dist check pass.
- Hosted (15 November 2026): deployed with Firebase Hosting to https://hushbrief-hybridai.web.app. A fresh headless Chrome profile ran Firebase mode → fictional sample → cloud consent → Create handoff on the hosted site: App Check attested with reCAPTCHA Enterprise (no debug token exists in the production bundle), and the result badge read Gemini · cloud with 3 source-linked action cards.
-
On-device (15 November 2026): on the owner's desktop Chrome with Gemini Nano available, Prepare Nano → Create handoff with cloud off returned Gemini Nano · on device ("Device-only route attempted. Cloud was excluded.") with 5 source-quoted actions. This run exposed that private spans reached the on-device prompt; fixed in this release (see above).
-
After the private-span fix (15 November 2026, redeployed): a human run in desktop Edge (no built-in model) on the hosted app gave Gemini · cloud. Automated headless/CDP-driven browsers were rejected by reCAPTCHA Enterprise attestation (403 "App attestation failed") and fell back to local rules, which is the intended bot protection. Automated live cloud probes are no longer run against the hosted app.
Local checks
npm test: 42 single-process tests, all passing (the existing 26 cases, with private-route expectations updated, plus 16 regressions for private masking, offsets, routes, validation, notices, Markdown and credential-free dist checking).npm run build: strict TypeScript check, default Vite production build with no private environment files, then the dist check.npm run check:dist: build-output-only check; no private configuration read. Rejects debug-token assignments, markers, environment-variable names and UUID-shaped literals.npm run check:browser: regression checks now include visible singular/plural withholding notices, closed/unclosed spans, contact preservation in device rehearsal, and the downloaded Markdown header. Attempted in this task with a fresh temporary profile, but the restricted Windows token blocked Chrome launch withspawn EPERMbefore any UI check ran. Browser verification remains pending outside this sandbox.
Finish validation — 17 November 2026
The earlier EPERM result above is preserved as historical evidence. A new isolated local run completed successfully this time.
- 42/42 existing single-process tests passed; strict TypeScript passed.
- Sanitized default production build passed into a separate local build directory; private configuration loading was disabled and the existing live
dist/was preserved. Build-output safety check passed. - A local browser validation script passed 19 checks in a newly created, unsigned-in Chrome 157 profile, then deleted that temporary profile. Only a loopback static server and loopback fake backend were exposed. Non-loopback page requests were blocked; no external app requests or page exceptions were observed.
- Checks covered preview masking, no-consent local extraction, exact consented loopback packet, exported withholding notice, consent reset, error recovery, simulated device privacy, closed/unclosed spans, plain-text rendering, clear/empty input, delayed-response rejection, actual service-worker offline reload and 320/390/640 px layouts.
- No Nano probe, model download, protected hosted-route automation or live Firebase request was performed. Post-fix Nano and actual permitted hybrid fallback remain owner acceptance steps.
- Evidence (validation report, logs and browser report) is kept with the local validation records; the commands above reproduce it.
- Anonymous read-only comparison of seven named public files found matching text after normalizing line endings (README, core, Firebase adapter, UI entry point, core tests, verification record and MIT licence), before tonight's documentation edits. The public page displays MIT.