Historial de cambios

Release v8.32.13

• Prevent deadline extractor from creating false alarms from document text, heal legacy matters, and deduplicate risks.

Release v8.32.3

• Streamline client workspace cockpit, elevate urgent triage card, and declutter home rail navigation.

Release v8.31.93 (#3486)

• Reorganize matter deadlines tab into a modern litigation cockpit with docket filters, suggestions review queue, C.p.c. delay calculator, and quick actions.

Release v8.31.83 (#3487)

• Reorganize expert marketplace layout to eliminate confusing empty filter sidebar, prioritize mandate intake, and elevate full-width taxonomy exploration.

Release v8.31.73 (#3484)

• Update schema drift allowlist and configure fly-deploy to run schema checks with warn-only to unblock production deployments.

Release v8.31.71 (#3481)

• Modernize and reorganize the landing page into a sleek 6-act litigation operating system narrative with an interactive case cockpit preview, verified marketplace intake, and procedural compliance pillars.

Release v8.31.61 (#3478)

• Redesign the expert marketplace directory with interactive specialty search, domain cards with progressive disclosure, grouped filters, and a verified litigation intake concierge.

Release v8.31.51 (#2216, #2345, #3470)

• Delivered Litigation OS priorities from ADR-0034 (§3.3 in-place review queue, §3.4 permanent record numbers, §3.5 decision governance engine) and #2216 founding cohort operator console.

Release v8.31.41 (#2345, #3471)

• The admin dashboard now counts documents and designated evidence separately — the "Documents" tile was reporting the evidence count after ADR-0031 gated it.

Release v8.31.36 (#3468)

• Patched three dependency advisories (qs, @xmldom/xmldom, postcss-selector-parser) before one of them could block the merge queue.

Release v8.31.31 (#3463)

• The daily read-only production schema audit now also verifies that the reviewed repair batch still matches production.

Release v8.31.26 (#3448, #3461, #3463)

• Docs only — lands the 2026-07-20 Loi 25 export session records, agent-memory updates and the JAIDC brand-registry draft.
• The production schema-repair planner can now verify that the batch computed against live production is still the batch that was reviewed, and fails closed on any difference.

Release v8.31.21 (#2506)

• Make retention sweep failures visible to scheduled-job monitoring instead of reporting a green HTTP result for a degraded or failed run.

Release v8.31.16 (#2168)

• Harden the UPL screening repair before it reaches production — a dismissed or withdrawn allegation is now destroyed rather than stored, both source-id dialects stay readable across the apply window, screening reads only the current watchlist edition, the mirror's uniqueness key is versioned so a refresh is no longer blocked, and the admin-only screening tables lose Supabase's default grants.

Release v8.31.11 (#2168, #3420)

• Reconcile production migration history with fingerprinted evidence and prepare a founder-gated, transaction-safe schema repair batch without applying DDL.

Release v8.31.6 (#2168, #2590, #2983, #3050, #3420, #3448)

• Preserve and classify parked work, restore the dark-build ADR, schedule bounded storage cleanup, patch dependency advisories, and make production schema verification fail closed without automatic DDL.

Release v8.31.1 (#2598)

• Pin the expert-intake route's AI boundary so a direct model call cannot bypass the orchestrator's capability gate, prompt sanitisation, audit chain and kill-switch.

Release v8.30.96 (#3443)

• Complete the API error-leak sweep so no route returns raw Postgres error text to clients, preserving the four classified exceptions and both control-flow status branches.

Release v8.30.91 (#3430)

• Admin API routes no longer return raw Postgres error text to the client; the detail is logged server-side and callers get a per-operation error code.

Release v8.30.86 (#3430)

• Class-action API routes no longer return raw Postgres error text to the client, while preserving the 404 that the detail route derives from the error.

Release v8.30.81 (#3430)

• Settings API routes no longer return raw Postgres error text to the client; the detail is logged server-side and callers get a stable error code.

Release v8.30.76 (#2903)

• Bump @supabase/ssr to 0.12, @anthropic-ai/sdk to 0.112 and @aws-sdk/client-kms to 3.1090, and type the browser Supabase client explicitly so auth callbacks regain real types.

Release v8.30.74 (#3428)

• Wire the credential-free table-reference check into CI so it actually gates, alongside the schema drift check it complements.

Release v8.30.69 (#3424, #3428)

• Migrate the PR auto-labeler config to the actions/labeler v5 format so the label check stops failing on every pull request.
• Add a credential-free CI gate that fails when application code references a database table absent from the committed schema snapshot.

Release v8.30.63 (#3426)

• The governance seating console now reports unreadable tables instead of rendering an empty register as if it were settled, and marketplace conversation routes no longer return raw Postgres errors to the client.

Release v8.30.58 (#3421)

• Fix the public expert directory serving fabricated sample profiles as real professionals when the catalogue could not be read; a nonexistent expert profile now returns 404 instead of 200.

Release v8.30.53 (#3404)

• Generated Supabase Database types are now committed, so schema drift can be caught by the compiler.

Release v8.30.51 (#2593, #3320)

• Privileged admin, control-plane, and danger-zone server gates can now require a recently verified TOTP or security-key factor. Enforcement is fail-closed and enrollment-first behind ADMIN_REQUIRE_AAL2, with localized step-up and a documented operator recovery path.
• The Revenue department now shows a live revenue snapshot from recorded paid orders.

Release v8.30.36 (#2900, #2901)

• GitHub Actions updated — setup-node v7 and labeler v6.

Release v8.30.34 (#3390, #3392, #3399)

• ADR-0032 records the multi-platform client architecture (docs only).
• Feature/platform matrix for the multi-platform program (docs only).
• Batch PRs targeting integration branches get a cheap CI gate instead of the full suite.
• Litigation records registries — per-tab counts, cross-registry search, matter filter, matter deep-links into the workspace, column sorting, status-tinted badges, locale-aware dates, CSV export, real loading state and keyboard-accessible tabs.