Rework confluence-librarian around native HTML edits - #2172
Open
gunzip wants to merge 4 commits into
Open
Conversation
gunzip
added a commit
that referenced
this pull request
Sep 9, 2026
…update-target fixture Port the eval-harness updates from the v2 branch (PR #2172) without the accompanying README/SKILL rework: - rework eval scenarios around native HTML draft edits (no Markdown round trips, single known-good baseline, no publish) - add fixtures/update-target.md; remove the now-unused fixtures/design-review.md
Base automatically changed from
chores/confluence-librarian-eval-harness
to
main
September 9, 2026 15:31
Restructure the skill around two explicit paths, Create (single native-HTML create) and Edit (granular edits on an unpublished draft), adding the Native edit protocol and the Baseline contract. Update the README to document the paths and the eval cases now shipped by #2164. This branch is rebased onto main: the eval-harness scenarios and fixtures (evals.json, update-target.md, harbor overlay) landed via #2164, so this PR carries only the skill and reference-doc rework.
gunzip
force-pushed
the
chores/confluence-librarian-eval-harness-v2
branch
from
September 9, 2026 15:35
233b87b to
5aba104
Compare
…e and confluence-librarian-3-small-update-large-file
…content fetching process
…fy working copy handling
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.
What
Reworks the
confluence-librarianskill itself, stacked on top of #2164 (the benchmark-harness PR), so the skill and its evals agree on how Confluence pages should be edited in place rather than round-tripped through Markdown:data-local-idedits, keep native-only constructs such astoc, expand/<details>, panels, and macros intact) and the Baseline contract (snapshotToken+ version, context/file persistence, staleness recovery).native-edit-in-placeandsmall-update-large-fileeval cases that Add benchmark harness to confluence-librarian SKILL #2164 ships (draft edits through Confluence's native HTML/granular edits, never a Markdown round trip, read-only seed pages).The matching eval scenarios (
native-edit-in-place,small-update-large-file) and theupdate-target.mdfixture were ported into #2164, so the skill/reference docs and the eval harness stay aligned while each PR stays reviewable on its own.Why
An existing Confluence page holds constructs with no Markdown form (
toc, collapsible expands, info panels, images, smart links, inline comments,data-local-idanchors). Converting a page to Markdown and back silently destroys them, so an edit must run on the page's own native HTML, staged on the unpublished draft. This change encodes that protocol in the skill.Notes
evals.jsonscenarios and fixtures); Add benchmark harness to confluence-librarian SKILL #2164 was updated with them so this PR only carries the skill and reference-doc changes.plugins/are not part of the Nx release projects.Depends on #2164