Approval Watermark Missing on Executed Template Contracts

What This Skill Debugs

This runbook covers the specific mismatch where approval / ready-to-sign watermarking behaves differently by workflow:

• TPP / upload-sign / editable flows keep the watermark after execution
• Template / template-editable flows show the watermark at signing time, but the executed platform copy loses it

This is not usually a random rendering issue. The important split is in how the executed PDF is produced:

• Editable / TPP path signs the already-generated PRE_SIGN_PDF, so the watermark survives into the final copy
• Template path historically regenerated the executed PDF from scratch and, before the Mar 2026 fix, did not re-apply the watermark before generating the executed copy

Confirmed fix pattern from incident #incident-20260311-medium-doceree-inconsistent-watermark-behavior-between-templat / Jira SPD-42223:

• move watermark application into get_pre_sign_pdf_for_template_contract()
• let save_executed_pdf_for_template_contract() consume that already-watermarked PDF
• regression-test Native signing, DocuSign, HelloSign, and Aadhaar/native-sign variants before prod rollout