Changelog

Scribe can now use AI to help write and review documents: - **Bring-your-own API keys** for OpenAI, Anthropic (Claude), and DeepSeek. Per-user keys live in **Settings → AI providers**, and admins can set a company-wide fallback key that members can opt into. - **Generate with AI** tab on the New Document page — describe what you want and stream a Markdown draft into a preview, then accept it as the initial content. - **Ask AI** in the editor (toolbar button or ⌘/Ctrl-K). With no selection it inserts at the cursor; with a selection it rewrites or extends it. Streams tokens into a live preview with Accept / Discard / Regenerate. - **AI review** for the document author and assigned reviewers — runs an AI pass and posts inline review comments (anchored to the lines they refer to) plus a top-level summary, all badged "AI" so they're easy to triage alongside human comments. - **Per-user daily token budget** (default 200k tokens/day, configurable via `AI_DAILY_TOKEN_BUDGET`) tracked in the new `AIUsage` table. Returns 429 when the budget is exhausted. Security notes: API keys are encrypted at rest with AES-256-GCM, never returned to the browser, and only ever sent to the provider you chose. Document content sent to the LLM is fenced as untrusted data to mitigate prompt-injection by document authors targeting reviewers. Prompts and completions are not logged — only token counts, model, latency and error class. `ENCRYPTION_KEY` is now required at boot in production.

A new **My Reviews** entry in the dashboard sidebar opens a page showing every document that's been assigned to you for sign-off, with the document title, author, and current status. Tabs let you switch between **Pending**, **Accepted**, and **Closed** reviews so you can quickly see what still needs your attention versus what you've already acted on.

ArchDoc now supports a fourth document type, **PRD** (Product Requirements Document), aimed at technical product managers. Creating a new document exposes the PRD option with a starter template covering problem statement, target users, requirements, success metrics, scope, and open questions. PRDs are filterable from the documents list alongside ADRs, RFCs, and Design Docs. A new **Linked Documents** panel on the right sidebar of every document page lets you cross-reference related documents (for example, attaching the Design Docs and RFCs that come out of a PRD). Links appear on both the source and target document, are clickable, and can be removed with one click.

The changelog at /changelog used to be auto-generated from git history, which surfaced noisy and duplicated developer commit messages. Each release now contains hand-written, user-focused notes grouped by Added / Changed / Fixed / Removed / Deprecated / Security.

After installing or updating the ArchDoc GitHub App, the callback now redirects back to the configured site URL (`NEXTAUTH_URL`) instead of the container's bind address, so users land on `/dashboard/integrations` on the public domain as expected.

Navigating from the in-app docs back to the dashboard could leave the sidebar in a collapsed/mobile state with the sidebar toggle button unresponsive. The **Documentation** sidebar link now triggers a hard navigation, so the dashboard always re-mounts in a clean state when you return.