Siddharth Muneshwar — table fidelity benchmark and loss-run summary app - #130
Open
SiddharthMuneshwar26 wants to merge 6 commits into
Open
Siddharth Muneshwar — table fidelity benchmark and loss-run summary app#130SiddharthMuneshwar26 wants to merge 6 commits into
SiddharthMuneshwar26 wants to merge 6 commits into
Conversation
Added known defect section for DOCX export issue and clarified the correctness of the HTML output.
Updated README to reflect changes in test command and added details.
Updated README to reflect new app features and structure.
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
1 participant
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.
Siddharth Muneshwar
Two projects built for the SuperDocs round.
extensions/SiddharthMuneshwar26/table-fidelity-benchmark — measures whether merged cells, nested tables, spanning headers and numeric formatting survive an edit-and-export cycle, and attributes any loss to a specific stage by running every case twice: once with no edit at all, once with an edit. 20 cases run against the live API, reproduced across two independent sessions. Numeric formatting survives completely; four issues found and reported separately through the bug channel.
use-cases/SiddharthMuneshwar26/insurance-loss-run-summary — turns years of raw insurance loss-run data into one review document: claim counts, incurred totals and open claims by policy year, every figure traced to the document and row it came from. Surfaces conflicts between a reissued loss run and the original rather than silently picking one. One operation per full review; figures are parsed, never model-generated.
Both include test suites that run without an API key. AI assistance was used throughout, directed and reviewed by me.