FOIA / public-records request workflow (K-12 & government)

[markkerzner]

Use case (from a prospect): A K-12 school district (technology coordinator, Ohio) needs to respond to public-records / FOIA requests — take a set of records, search/cull to what's responsive, redact exempt content (student PII/FERPA, personnel, etc.), and produce a clean deliverable to the requester. This is the same core eDiscovery pipeline FreeEed already runs (ingest -> search -> review -> produce), with redaction as the key gap.

Workflow to support:

1. Ingest the record set (email, docs, PDFs, scans/OCR — already supported).
2. Search + tag responsive vs. non-responsive.
3. Redact exempt text/regions and burn in the redactions on the produced copy (see feat(production): burn redactions into the produced set (post-MVP) #554, feat(review): document redaction — author in FreeEedUI, burn into ESI production, overlay in Viewer FreeEedUI#69).
4. Produce a clean set (PDF/native) with a simple log of what was withheld/redacted.

Why it matters: Public-records response is a recurring, statutory obligation for every school district and government office — a well-defined, repeatable segment. FreeEed's flat-fee, on-prem, data-never-leaves model fits a school's budget and privacy posture (FERPA) far better than volume-billed eDiscovery tools.

Scope target: a first working FOIA/redaction pass on the near-term roadmap. Related: #554, shmsoft/FreeEedUI#69, #600 (per-document PDF export).