Derive semantic Markdown changes - #9043
Closed
hweihwang wants to merge 1 commit into
Closed
Conversation
Parse immutable documents, normalize their semantic structure, and emit bounded stable change descriptors. Support one shared schema for both parsed documents. Assisted-by: Codex:gpt-5.6-sol Signed-off-by: Hoang Pham <hoangmaths96@gmail.com>
This was referenced Aug 14, 2026
Open
hweihwang
requested review from
max-nextcloud and
mejo-
and removed request for
max-nextcloud
August 14, 2026 16:36
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
In one sentence: the semantic model that turns two Markdown documents into a typed list of what changed.
What and why
Text cannot tell you what changed between two versions of a Markdown document. Byte diffs report edits, not meaning — nothing says a paragraph was inserted, a table row changed, or a link target moved. This PR adds the model that answers that question: two documents in, a typed list of changes out.
What's in this PR
ChangeSetDesign notes
Stack
First of six. #9044 builds on it, then #9045 and #9046. The Collectives side lands in nextcloud/collectives#2697 and #2698 after all four Text PRs.
Verification
ts:checkandlintpass; complete suite 1,768/1,768 at this tip. Zero drift against upstreammain; the sign-off rebase changed only commit metadata.AI assistance
Commits carry
Assisted-by: Codex:gpt-5.6-sol; an independent review pass was run with Claude Opus 5. This description was drafted with Hermes (deepseek-v4-pro) from my notes, then reviewed by me.Related