DRIFT v0.8.0

Codex session record

• Carried 019f6a78-6fa2-7121-9059-85ac8ceb9904 from reviewed-evidence release
  hardening and v0.7.0 hosted verification through this v0.8.0 source
  release.

Added

• Gave the three fixture Insights typed claims arrays backed by frozen,
  checked-in synthetic source files. Every span, offset, source URL, and
  source-content SHA-256 now follows the same invariant as a live claim; a
  regression test rejects mismatched source text, hashes, URLs, offsets, or raw
  item IDs. The Inspect claim evidence panel now renders in no-key fixture
  mode without implying that example text is an upstream release note. The suite
  passes 150 tests at 100% backend coverage.
• Ask DRIFT grounded-chat box in the frontend (frontend/app/AskDrift.tsx):
  a single client component that posts a question to /chat and renders the
  grounded answer, its source citations, the model/audit label, and the grounded
  insight IDs, with explicit loading, no-match (HTTP 404), and error states. It
  works in both fixture and live mode. The input now matches the /chat
  contract (3–2,000 characters), reports server errors accurately, and announces
  state changes accessibly. The /chat contract was verified against the
  fixture backend and the production frontend build passes.
• Embedded the reviewed-briefing and claim-evidence screenshots in the README as
  live-state visual evidence (assets/screenshots/03-briefing.png and
  04-briefing-claim-evidence.png), alongside the branded Swagger and
  architecture assets.
• Presentation architecture diagram — a hand-authored, presentation-grade
  visual (assets/architecture/arch-{dark,light}.svg, generated by
  build_arch.py + build_arch_raster.mjs) that dramatizes the six typed
  stages as a first-look trust boundary: untrusted feeds → quarantined
  machine drafts → the human review gate → trusted, published briefing. The
  README and docs/ARCHITECTURE.md now lead with it, with the Mermaid pipeline
  kept as the maintainable system-of-record in a collapsible section.

Changed

• Restructured the README top for first impression: The Problem → What DRIFT
  Does → Try DRIFT in 60 Seconds, leading with the hosted demo links and a
  one-command docker compose up judge path. Reframed the closing Disclaimer
  as a positive Trust Model (untrusted input → frozen source span → separate
  verifier pass → human review gate) and kept the Codex/GPT-5.6 usage section
  prominent.
• Made the Quick Start cross-platform: promoted docker compose up as the
  one-command local path and added bash/curl equivalents beside every PowerShell
  command (setup, endpoint calls, and the live capture command).
• Corrected the P1 tracker to name the implemented grounded-chat component
  honestly. It uses /chat, whose retrieve-first backend already performs the
  evidence lookup; the separate /search endpoint remains available in the API
  rather than duplicating live retrieval and provider work in the browser.
• Renamed the tracked UI screenshots to clean kebab-case filenames
  (01-landing, 02-api-docs, 03-briefing, 04-briefing-claim-evidence) so
  they embed reliably in Markdown.
• Rebuilt the Mermaid architecture diagram (arch-pipeline.mmd) into three
  colour-coded trust zones (untrusted · quarantine · trusted) with the human
  review gate as the crossing point, and regenerated all four light/dark
  renders. The auto-laid Mermaid is kept acyclic — the "engineer also reviews"
  loop-closing edge appears only in the hand-laid presentation diagram — so the
  zones read left
  to right.
• Renamed the Mermaid architecture assets for clarity: architecture-diagram*
  → arch-pipeline* (source, renders, and theme configs), pairing them with the
  new hand-authored arch-* presentation diagram, and updated every reference
  across the README, docs/ARCHITECTURE.md, CONTRIBUTING.md, and the asset
  guides.
• Elevated the canonical DRIFT brand banners to share the presentation diagram's
  visual system — trust-zone palette, node styling, gold human-review gate,
  dot-grid field, and a subtle GPU compute-lattice backdrop (circuit traces,
  vias, and a PCB edge-connector) behind the evidence-path card — via a new
  assets/brand/build_banner.py generator (with a build_banner_raster.mjs
  PNG export). The API-served SVG filenames
  (drift-banner-{dark,light}.svg) are unchanged, so backend/main.py and the
  Docker image keep serving them.
• Refreshed the README Project Structure tree to match the current backend,
  frontend, assets, scripts, migrations, and tooling layout.
• Locked one DRIFT signature gradient (teal #2dd4bf → indigo #818cf8
  dark / #0d9488 → #4f46e5 light) across the banner wordmark and the
  presentation-diagram eyebrow, with the semantic node/trust colours kept for the
  diagrams. The endpoints are the diagram's own source-teal → agent-indigo
  hues; the locked palette is documented in assets/brand/README.md.
• Added a Powered by GPT-5.6 tiers · Luna · Terra · Sol credit to the brand
  banner, and a GPU compute-lattice backdrop behind the evidence-path card.

Repository operations

• Enabled branch protection on main (2026-07-17): the five CI quality-gate
  checks (Ruff lint, Mypy type check, Tests and coverage, Frontend build, and
  Documentation hygiene) are required, with strict up-to-date merges; admins
  retain a bypass for pre-deadline hotfixes. Tag-only release checks are
  intentionally excluded.
• Confirmed the Codecov pytest upload on the dashboard (2026-07-17): the
  tokenless OIDC upload is queued and processed, and the repository and
  flag=pytest coverage badges both resolve to 100%.