docs(agents): plan the layout accuracy programme - #219
Open
eliahilse wants to merge 1 commit into
Open
Conversation
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Contributor
|
All contributors have signed the CLA — thank you! ✍️ ✅ Posted by the CLA bot. |
Greptile SummaryThis documentation-only PR adds a measurement-first programme for improving Word layout fidelity.
Confidence Score: 5/5The PR appears safe to merge because it changes documentation only and no concrete inaccurate or harmful guidance was identified. The plan accurately frames the missing benchmark harness, current layout behavior, proposed measurement phases, and adjacent CRDT caching work without changing runtime behavior.
|
| Filename | Overview |
|---|---|
| openspec/accuracy-plan.md | Adds a coherent accuracy roadmap whose material current-state claims align with repository implementations and documentation; no actionable defect was found. |
Reviews (1): Last reviewed commit: "docs(agents): plan the layout accuracy p..." | Re-trigger Greptile
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.
TL;DR:
Summary:
openspec/accuracy-plan.md, sequencing the Word-fidelity work as measurement first: committed corpus + scorer, a manual AppleScript capture path for goldens, then reproducing the page-count figure, then ranking the residual error before fixing anythingexact(0.80 baseline ratio, font-independent) andatLeast(slack above the baseline) are already implemented and Word-measured inooxml-text, and metric quantization is correctly opt-in — so those are not open workTest plan: