Skip to content

Add Word add-in: track-changes triage (extensions/pritt24) - #17

Open
pritt24 wants to merge 1 commit into
superdocsapp:mainfrom
pritt24:word-track-changes-triage
Open

Add Word add-in: track-changes triage (extensions/pritt24)#17
pritt24 wants to merge 1 commit into
superdocsapp:mainfrom
pritt24:word-track-changes-triage

Conversation

@pritt24

@pritt24 pritt24 commented Aug 9, 2026

Copy link
Copy Markdown

Groups tracked changes by reviewer, classifies each as substantive/stylistic/typo via SuperDocs' chat API, and lets a reviewer act by plain-English instruction with a preview before anything is applied. Reviewer comments can be answered (AI-drafted reply, editable) and resolved from the same pane.

Document mutation (accept/reject/reply/resolve) happens entirely through Word's native Office.js API, never through SuperDocs' document pipeline -- see the README's Architecture section for why, given the assigned card's own honesty note about multi-reviewer attribution. SuperDocs' /v1/chat is used for classification and instruction interpretation, verified against the live API with a real key. Also documents a real API bug found while testing: sync /v1/chat's approval_mode pending_changes aren't approvable via the documented endpoint, only async job IDs work.

No build step: plain HTML/CSS/JS, React 18 UMD + htm, openssl-based local HTTPS dev server (serve.py) so sideloading doesn't need Node.

Groups tracked changes by reviewer, classifies each as
substantive/stylistic/typo via SuperDocs' chat API, and lets a
reviewer act by plain-English instruction with a preview before
anything is applied. Reviewer comments can be answered (AI-drafted
reply, editable) and resolved from the same pane.

Document mutation (accept/reject/reply/resolve) happens entirely
through Word's native Office.js API, never through SuperDocs'
document pipeline -- see the README's Architecture section for why,
given the assigned card's own honesty note about multi-reviewer
attribution. SuperDocs' /v1/chat is used for classification and
instruction interpretation, verified against the live API with a
real key. Also documents a real API bug found while testing: sync
/v1/chat's approval_mode pending_changes aren't approvable via the
documented endpoint, only async job IDs work.

No build step: plain HTML/CSS/JS, React 18 UMD + htm, openssl-based
local HTTPS dev server (serve.py) so sideloading doesn't need Node.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.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