Skip to content

Rework confluence-librarian around native HTML edits - #2172

Open
gunzip wants to merge 4 commits into
mainfrom
chores/confluence-librarian-eval-harness-v2
Open

Rework confluence-librarian around native HTML edits#2172
gunzip wants to merge 4 commits into
mainfrom
chores/confluence-librarian-eval-harness-v2

Conversation

@gunzip

@gunzip gunzip commented Sep 9, 2026

Copy link
Copy Markdown
Contributor

What

Reworks the confluence-librarian skill 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:

  • SKILL.md — restructured around two explicit paths, Create (publish a prepared document once, as a single native-HTML create) and Edit (change an existing page in place on its unpublished draft). Adds the Native edit protocol (work from a known-good baseline, send only granular data-local-id edits, keep native-only constructs such as toc, expand/<details>, panels, and macros intact) and the Baseline contract (snapshotToken + version, context/file persistence, staleness recovery).
  • README.md — documents the Create/Edit paths and describes the native-edit-in-place and small-update-large-file eval 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 the update-target.md fixture 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-id anchors). 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

Depends on #2164

@gunzip
gunzip requested a review from a team as a code owner September 9, 2026 09:58
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
gunzip force-pushed the chores/confluence-librarian-eval-harness-v2 branch from 233b87b to 5aba104 Compare September 9, 2026 15:35
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