Skip to content

fix(markdown): secure browser document bindings - #2969

Draft
George Ng (GeorgeNgMsft) wants to merge 2 commits into
georgengmsft-markdown-durable-updatesfrom
georgengmsft-markdown-browser-server
Draft

fix(markdown): secure browser document bindings#2969
George Ng (GeorgeNgMsft) wants to merge 2 commits into
georgengmsft-markdown-durable-updatesfrom
georgengmsft-markdown-browser-server

Conversation

@GeorgeNgMsft

Copy link
Copy Markdown
Contributor

Summary

Layer 4 of the replacement stack for #2940.

  • validate browser and IPC writes against the active binding token, workspace identity, and content revision
  • preserve nested relative paths and isolate same-basename documents with binding-scoped collaboration rooms
  • bootstrap browser bindings, correlate live Markdown reads, publish committed snapshots, and evict rotated idle rooms
  • keep the Markdown HTTP/WebSocket service on IPv4 loopback and advertise its bound loopback port
  • preserve layer 3's headless durable, exactly-once persistence path

Validation

  • pnpm run build markdown
  • pnpm test in packages/agents/markdown (54 tests)
  • focused viewService, urlPath, and markdownUpdatePersistence specs
  • Prettier check
  • lint, complexity, circular dependency, and debt ratchets against origin/georgengmsft-markdown-durable-updates
  • git diff --check

Stack

Base: georgengmsft-markdown-durable-updates (#2968)

The final browser-client serializer/autosave, revision adoption/reconciliation UI, toolbar, and browserPersistence.spec.ts changes remain deferred to layer 5. No src/view/site/** or aiclient changes are included.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant