Upstream Mike PR #299 review

[github-actions]

Automated-Upstream-Mike-Sync: true
Upstream-Risk: high

PR open-legal-products#299 is promising but crosses protected architecture and security boundaries; no patch is appropriate.

Mike PR open-legal-products#299

• Outcome: needs-decision
• Capability: ROSS Word add-in assistant workspace with persistent chat, document context, workflows, and tracked-edit interactions
• Series: word-addin-chat-299
• Dependencies: Mike PR [Feature 14] feat: Word add-in — chat, tracked-changes rewrites, workflows and projects in Word open-legal-products/mike#221 foundational Word add-in, Mike PR fix(word-addin): WKWebView completion scroll jump + streaming performance (stacked on #299) open-legal-products/mike#311 scroll and streaming follow-up, Mike PR fix(word-addin): review fixes for #299 — WebKit e2e gate, streaming perf, and correctness edges open-legal-products/mike#320 review-hardening follow-up
• Prerequisites: Product approval for a ROSS Word add-in, Complete upstream patch evidence, Authentication, privacy, and tenant/data-boundary threat review, Schema, migration, API, dependency, deployment, and Office-host compatibility review, Focused Word/WebKit end-to-end harness covering streaming, persistence, tracked edits, and failure recovery
• Reason: ROSS has reusable web assistant, chat streaming, workflow, and tracked-change seams but no Word add-in surface. The metadata-only change couples a new Office client to authentication, persistent schemas, APIs, dependencies, deployment, and document-data boundaries, requiring explicit architecture and security decisions.

Architecture brief

Build a ROSS-native Office task pane that reuses presentation concepts from frontend assistant components while integrating through reviewed adapters to backend chat/project-chat streaming and docx tracked-change services. Keep Office identity, authentication, persistence, and tenant enforcement behind dedicated ROSS-owned boundaries rather than importing upstream architecture.

Implementation plan

• Define the Word add-in product scope, supported Office hosts, and document-data boundary.
• Specify authenticated add-in APIs using current ROSS access and tenant controls.
• Design chat persistence and migrations with RLS/data-lifecycle review.
• Create adapters for current assistant streaming, workflows, document context, and tracked-change seams.
• Establish Word/WebKit integration tests for authentication, streaming, history isolation, tracked edits, retries, and cleanup.
• Review dependencies, manifest permissions, deployment topology, privacy implications, and the complete upstream patch before implementation.

Required human action

This is a draft state-only architecture record. Review the brief and implementation plan before any code is attempted.