feat: submission runbook generator — capture and reproduce institutional upload steps

[William-Hill]

Context

From AASCU Intermediary feedback session (see docs/aascu_intermediary_feedback_summary.md, pain point E):

"I have an institution that has a pretty big IR team... One of the main person retired, and that was the only person who submitted it. No one else knew how to do it. And apparently, this person did it in some way that was unique to how they wanted to do it."

"All I have to say is a lot of the knowledge tends to live with one person."

"I have one campus that, every time they submit updated data, it wants all of their data delisted and removed. Removed and then resubmitted, which I think is so weird, but that's how the person, that's their preference."

Each campus develops its own submission tribal knowledge that evaporates when the person leaves. The tool can capture and replay these steps as institutional knowledge.

Goal

After a successful upload, the tool offers to save the exact steps + field mappings + custom transformations as a named, versioned "submission runbook" that a successor can replay.

Scope

• Record every choice during an upload (file format, sheet selection, column mappings, filters, dedup rules)
• Save as a named runbook tied to the institution
• Generate human-readable PDF: "How [Institution] submits PDP data — steps 1-N"
• "Replay this runbook" button: pre-fills upload UI with previous choices
• Versioned — track changes to the runbook over time

Acceptance criteria

• User can save a successful upload as a runbook
• Saved runbooks can be replayed on a new file
• PDF export of the runbook is human-readable without our tool open
• Runbooks are versioned and per-institution

Related

• Upload validation report issue
• feat: self-service data upload for PDP, AR files, student and course data #86 (self-service upload)