Most of miniterms' interesting surface area landed in the API release. The polish bundle that shipped behind it isn't glamorous — but it closes the kind of paper-cut gaps that turn a working product into a tool you actually rely on.
Editing a subprocessor — region, DPA URL, anything — now re-emits the same drift event the rest of the pipeline already expected, so downstream documents flag as out-of-sync. Before today, only adds emitted; edits silently changed the underlying record without telling the rest of the pipeline. No schema change, just the missing emit.
The dashboard now surfaces a needs_review / flagged count as a fifth tile, with an amber pill on documents that need your eye. The 72-hour drift sweep includes them. Anything in attention shows up on the overview without making you click through three nested screens to find it.
Compliance tools fail quietly. Surfacing the failure on the page the user already opens is most of the work.
GDPR gives you 72 hours to acknowledge a data subject request. miniterms now runs a daily sweep that scans every workspace's open DSARs and pings the inbox before the clock expires. A per-DSAR tombstone prevents duplicate alerts. The job is idempotent and bounded — large workspaces don't get O(n) emails on a single run.
Subprocessor mutations from the dashboard now share the same emit pipeline the API uses, so events fire from the UI path identically to the API path. One emit point, both surfaces — no more 'works in curl, silent in the dashboard' bug class.