Thesis workspace verification Audit date: 2026-10-27 Reading-view update, 2026-10-28 The workspace now opens rendered documents by default and retains explicit source editing. Its Markdown/Quarto subset includes tables, native MathML equations, and bounded sanitized Mermaid diagrams. LaTeX opens the compiled main.tex PDF as canvas pages with previous/next controls. References use the official pinned APA 6 CSL style through citeproc-js, both in the reading view and in generated main.bbl for the natbib starter. Full APA 6 in-text multi-author rules remain to be checked during chapter review. Quarto code cells and remote images do not execute in the reader. The new readers use scripts-only opaque-origin frames without authentication, network connections, navigation, forms, downloads, or persistent storage. Source, BibTeX, and PDF bytes cross only an in-memory postMessage boundary with exact frame/source/origin/request checks. PDFs render one bounded page at a time. The compiler bootstrap preserves prepared main.bbl between passes by skipping the original automatic BibTeX run; its pinned vendor bytes are unchanged. 42 served browser checks passed in Chromium and Firefox, including actual PDF pages/navigation, APA 6 compilation, source preservation, rendering of a long plan, hostile source URLs, opaque-origin isolation, load failure, and account cleanup. Eight of these check the reused message-rendering engine. An exact lockfile npm audit found zero advisory matches in the new preview dependency tree (48 entries including optional platform variants). This excludes existing site SDKs and the old TeX interpreter. Claude returned APPROVE with no blockers in two independent review rounds; the exact reviewer model was not exposed. New exact runtime versions are Citation.js core/BibTeX 0.9.0, citeproc-js 2.4.63, and PDF.js 6.4.299. Shared versions remain markdown-it 15.0.2, KaTeX 0.19.0, Mermaid 12.1.0 and DOMPurify 3.4.16. The build uses esbuild 0.28.2. Static source, licenses, CSL, and asset hashes are in ../thesis-preview-assets/public/NOTICE.txt and checksums.json. Vendor-only dormant XHR/DOM capabilities are documented in the repository baseline and remain behind the opaque frame CSP. Unknown future vulnerabilities and operating-system resource isolation are not established. Scope The generic Quarto editor shell, thesis.js, thesis-compiler.js, the compiler worker and static runtime assets, and the owner-restricted thesisWorkspace Firebase callable. The rendered artifact is /tools/thesis.html. Shared browser authentication was reused, not migrated. Private project files are stored in Firebase and are not included in the published editor assets. Boundaries checked The server resolves an enabled account grant to a private workspace and checks server-managed membership on every request. It also checks the provider, active session, production origin, and consumed App Check token. Record validation, file/project byte limits, owner/address/global quotas, revision comparisons, five prior saves, and deletion tombstones run on the server. Browser users cannot read or write the private database branch directly. Both verified owner sign-in identities map to the same existing project. The live bindings and runtime App Check verifier role were checked. New users need explicit operator enrollment and receive separate generic projects. Only the owner's two identities are enabled. Accounts are not globally merged. The browser displays source and compiler logs as text. Imports have schema and byte limits. Sign-out clears text and revisions, terminates compilation, revokes download URLs, and invalidates late asynchronous responses. Compilation uses a temporary worker with exact self-hosted asset paths, bounded fetch, fixed binary synchronous reads, a two-minute watchdog, and bounded PDF/log results. Unknown TeX filenames never become network requests. Report-only CSP is not an enforced boundary and has no reporting endpoint. Corrections and review Claude reviewed the generic code in three rounds and returned APPROVE with no blocking findings in the third round. The actual reviewer model identifier was not exposed. Private thesis text and personal research motivation were excluded. Corrections include cold-instance save proposals, binary request-mode/size checks, clear session errors, a request envelope that accepts dense LaTeX, deletion cleanup, and bounded download URLs. A subsequent missing-compiler fallback was checked with browser regressions. Model review does not replace the deterministic checks below. The focused access redesign received a further APPROVE in one independent Claude review round, with no blocking findings. The production migration verified unchanged source, history, revision and timestamps. Persisted schema 2 adds owner and membership metadata, while source exports retain schema 1. Revocation atomically disables a grant and removes membership, which is checked inside the save transaction. Enrollment and revocation commands are documented for the trusted operator; no public signup or access-management endpoint is provided. Validation completed 127 backend tests passed, including parser-advisory regressions, owner/session checks, quotas, malformed/oversized text, revision conflicts, deletion, bounded history, and a maximum-size project with JSON-escaped LaTeX characters. Three actual database emulator tests passed, covering all direct-browser denials and real Admin SDK cold saves, conflicts, tombstones, shared identity revisions, future-user isolation, and access revocation. 22 served-page browser checks passed in Chromium and Firefox. They include real multi-file PDF output, the full initial chapter structure, literal hostile source, conflicts, restore, late responses, cancellation, watchdog timeout, sign-out during compilation, URL cleanup, missing compiler assets, and unknown TeX file probes. Browser sign-in was mocked with synthetic content in these tests. Real owner-browser login against production remains to be exercised. Targeted Quarto rendering, JavaScript syntax checks, scoped dangerous-API scans, private-plan sentinel checks, and source/render parity passed. The generic Quarto helper inherits its existing baseline. The new vendor exception records seven XMLHttpRequest constructions with worker-only synchronous reads; no eval, Function constructor, HTML sink, importScripts, or WebSocket appeared in the vendor scan. The exception has a 2026-10-27 review date and a 2026-11-17 reassessment deadline, or earlier on any relevant change. Versions and limitations Quarto 1.10.18. Existing Firebase browser compat SDK 10.12.0, Admin 13.10.0, Functions 7.3.2, and deployed Node.js 22. Local backend checks ran with Node 25.9.0. Playwright 1.62.1 and rules-unit-testing 5.0.2. Emulator 4.11.2 used a checksum-verified temporary Temurin JRE 21.0.13, not a system Java installation. Compatible transitive patches pin body-parser 2.4.0 and qs 6.17.0. The subsequent exact-lockfile npm audit has no high/critical findings and eight moderate findings in the existing optional Google dependency chain, stemming from uuid buffer APIs. The new workspace does not use those APIs. Broader SDK migration remains separate maintenance work. The old WebAssembly interpreter is outside npm audit coverage. Its pinned bytes and worker limits do not establish absence of unknown vulnerabilities. See NOTICE.txt and checksums.json for provenance, original licenses, upstream source, and the missing reproducible-build attestation. PDF compilation targets main.tex with a fixed package set and a 2020 LaTeX format. Full Quarto rendering, Biber, binary figures, and the final university submission template are not included in this initial workspace. Project export is a portable JSON backup; individual text files can be downloaded separately. Stored source is not end-to-end encrypted. Administrators and the storage provider can administer it. Live deletion removes the project and its saved revisions; provider backups have a separate retention policy. Primary references reviewed on 2026-10-27 https://firebase.google.com/docs/database/admin/save-data https://firebase.google.com/docs/app-check/cloud-functions https://docs.cloud.google.com/iam/docs/roles-permissions/firebaseappcheck https://developer.mozilla.org/en-US/docs/Web/API/Worker https://developer.mozilla.org/en-US/docs/Web/API/Worker/terminate https://developer.mozilla.org/en-US/docs/Web/API/URL/createObjectURL_static https://developer.mozilla.org/en-US/docs/Web/API/URL/revokeObjectURL_static https://quarto.org/docs/output-formats/pdf-basics.html https://github.com/expressjs/body-parser/security/advisories/GHSA-27r3-jxmh-p828 https://github.com/ljharb/qs/security/advisories/GHSA-6pq8-jhm2-2vcw https://github.com/uuidjs/uuid/security/advisories/GHSA-w5hq-g745-h8pq