feat: evolve the SPA into a portable drafting workbench - #15
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: dd30eafd2c
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
@codex review |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 3c4d9883cd
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Summary
Why
The SPA had accumulated provider-specific assumptions and several disconnected drafting/editing surfaces. This change establishes a cohesive provider-neutral architecture and a review-first editing lifecycle that works consistently across cloud and local providers without silently mutating documents.
User impact
Users can configure a broader range of API providers, including local OpenAI-compatible models, inspect capability limitations, target precise document regions, control grounding sources, review citation provenance, recover interrupted work, and safely accept, reject, revise, or undo edits. Existing data identifiers and legacy routes remain compatible.
Validation
npm run typechecknpm test— 102 files, 754 tests passednpm run buildrelease/index.htmlas the reviewed single-file artifactNotes