disclosure-bureau/web
Luiz Gustavo e45f1c04d0 fix(seo): use body H1 as case-file <title> and OG title
generateMetadata still derived the page <title>/OG title from the generic
auto frontmatter topic ("Dow Uap D44 …"). Search engines, link cards, and
AI crawlers show that string, so it must be the human magazine headline the
narrator wrote as the body H1. Mirror the page component's H1 extraction.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-25 04:09:15 -03:00
..
app fix(seo): use body H1 as case-file <title> and OG title 2026-05-25 04:09:15 -03:00
components W6.1: batch-narrate all 122 documents + magazine titles from body H1 2026-05-25 03:54:35 -03:00
lib W6: 2 new narrated iconic case files (Kenneth Arnold, Mantell) 2026-05-25 02:19:30 -03:00
.dockerignore baseline: Disclosure Bureau pipeline + Next.js UI + Supabase stack 2026-05-17 22:44:36 -03:00
.env.local.example baseline: Disclosure Bureau pipeline + Next.js UI + Supabase stack 2026-05-17 22:44:36 -03:00
Dockerfile baseline: Disclosure Bureau pipeline + Next.js UI + Supabase stack 2026-05-17 22:44:36 -03:00
instrumentation.ts W0+W1+W1.2: security hardening, observability, autocomplete, glitchtip, forgejo CI 2026-05-23 18:18:42 -03:00
middleware.ts W0+W1+W1.2: security hardening, observability, autocomplete, glitchtip, forgejo CI 2026-05-23 18:18:42 -03:00
next-env.d.ts baseline: Disclosure Bureau pipeline + Next.js UI + Supabase stack 2026-05-17 22:44:36 -03:00
next.config.ts baseline: Disclosure Bureau pipeline + Next.js UI + Supabase stack 2026-05-17 22:44:36 -03:00
package-lock.json W5.4 (Phase 3B): sitemap + robots + Article schema + magazine reading view 2026-05-24 16:09:50 -03:00
package.json W5.4 (Phase 3B): sitemap + robots + Article schema + magazine reading view 2026-05-24 16:09:50 -03:00
postcss.config.mjs baseline: Disclosure Bureau pipeline + Next.js UI + Supabase stack 2026-05-17 22:44:36 -03:00
README.md baseline: Disclosure Bureau pipeline + Next.js UI + Supabase stack 2026-05-17 22:44:36 -03:00
sentry.client.config.ts W0+W1+W1.2: security hardening, observability, autocomplete, glitchtip, forgejo CI 2026-05-23 18:18:42 -03:00
sentry.server.config.ts W0+W1+W1.2: security hardening, observability, autocomplete, glitchtip, forgejo CI 2026-05-23 18:18:42 -03:00
tailwind.config.ts W5.4 (Phase 3B): sitemap + robots + Article schema + magazine reading view 2026-05-24 16:09:50 -03:00
tsconfig.json baseline: Disclosure Bureau pipeline + Next.js UI + Supabase stack 2026-05-17 22:44:36 -03:00

web — Disclosure Bureau Next.js app

Next.js 15 + React 19 + Tailwind + Supabase + assistant-ui.

Quick start (local dev)

# 1. Install deps
npm install

# 2. (Optional) Start local Supabase
#    Requires Docker. Skip if pointing at remote Supabase.
npx supabase init        # first time only — creates supabase/ folder
npx supabase start       # spins up Postgres/GoTrue/Storage on :54321

# 3. Configure env
cp .env.local.example .env.local
# Edit .env.local — paste local Supabase keys (printed by `supabase start`)

# 4. Apply migrations
psql postgresql://postgres:postgres@localhost:54322/postgres \
  -f ../infra/supabase/migrations/0001_chat_schema.sql

# 5. Start dev
npm run dev
# http://localhost:3030

Without Supabase

The app degrades gracefully if Supabase env vars are unset:

  • Wiki browsing works (read-only from filesystem)
  • Auth bar shows "auth: disabled (dev)"
  • Chat bubble shows "Auth not configured"

Useful for quick UI work without spinning up Docker.

Production (Coolify on VPS)

See ../infra/coolify/. Stack:

  • Coolify orchestrates everything
  • Supabase self-hosted: db.disclosure.top, studio.disclosure.top
  • Next.js: disclosure.top
  • Meilisearch (shared): search.disclosure.top
  • Imgproxy (shared): img.disclosure.top
  • Caddy: TLS + reverse proxy (built into Coolify)

Architecture

app/
├── page.tsx                          # home — 116 docs grouped by collection
├── auth/
│   ├── signin/page.tsx               # magic-link form
│   ├── callback/route.ts             # exchanges code for session
│   └── signout/route.ts
├── d/[docId]/
│   ├── page.tsx                      # doc detail
│   └── [page]/page.tsx               # page reader (OCR + entity highlights + crops + sidebar PNG)
├── api/
│   ├── me/route.ts                   # GET current profile
│   ├── sessions/route.ts             # GET list, POST new
│   ├── sessions/[id]/route.ts        # GET detail, PATCH, DELETE
│   ├── sessions/[id]/messages/route.ts  # POST send → assistant reply
│   ├── documents/, pages/, entities/, tables/  # read-only data
│   └── static/[...path]/route.ts     # sandboxed file serve
components/
├── chat-bubble.tsx                   # floating Sherlock — auth-aware, session list
├── entity-modal.tsx                  # opens on entity click
├── reader-content.tsx                # OCR + highlights + crops
└── auth-bar.tsx                      # sign in / out + budget tracker
lib/
├── wiki.ts                           # markdown reader (gray-matter)
├── entity-index.ts                   # match loader + text segmentation
└── supabase/{server,client}.ts       # SSR helpers
middleware.ts                         # session refresh on every request

Tech notes

  • No RAG: chat agent reads markdown directly. Wiki-link traversal substitutes for vector search.
  • RLS-first: Supabase Row Level Security enforces "user sees only own sessions" at the DB layer.
  • Magic-link auth: no passwords. GoTrue handles email delivery.
  • Anti-abuse: per-user budget cap (default $5) + daily message quota (default 100) enforced via check_budget RPC before each Claude call.

Cost

Each chat turn costs ~$0.005-0.05 depending on context size (mostly Haiku $1/M input, $5/M output).