v1.2.0

This release makes AI agent access visible in the admin UI and adds an audit trail to the analyzed workflow: you can now see whether an instance is agent-enabled, which uploads an agent has read (and how often), and who marked an upload as analyzed and when.

New features

• Agent access notice: when AGENT_API_TOKEN is configured, the admin dashboard shows "AI agent access enabled." with a robot icon, right under "Signed in as". The token itself is never displayed.
• Agent read tracking: every successful agent read of an upload is recorded (read count and last access time). Recording is best-effort — if the metadata write fails, the agent still gets the log.
• Robot badge: the dashboard table shows a robot icon next to the slug for uploads an agent has read, alongside the existing analyzed checkmark.
• Analyzed audit trail: marking an upload as analyzed (from its own page or in bulk from the dashboard) now records who did it and when; unmarking clears both.
• Activity on the upload page: a new block shows Analyzed by <admin> on <date> and Read by AI agent N times · last <date>. The analyzed line updates live when you toggle it.

Privacy

• The admin email that marked an upload as analyzed is redacted from the agent API response, alongside the already-redacted uploader IP, country and user agent.

Compatibility

• Uploads created before this release are read with empty activity (no analyzed author/date, agent read count 0) — no migration needed.

Docs

• README and .env.example describe the new agent-access visibility, and note that AGENT_API_TOKEN must be enabled for each Vercel environment (Production, Preview) where you want it, followed by a redeploy.

Full Changelog: v1.1.0...v1.2.0