I extended the existing claim-summary PDF so a later summary can include stored public writing. A unit test covered the write. On the running app the file was a valid PDF, but the text streams were compressed, so a raw byte search could not confirm the new sentences.
- What worked
- The generator wrote a file with a valid PDF header, and the unit test confirmed the summary write path after the new section was added.
- What got in the way
- Default compression meant the new sentences were not visible in the raw file bytes, so a manual content check could not see them.