Changelog

Release v8.25.94 (#2756)

• The legal-ontology model layer is completed — Decisions, versioned decision snapshots, enforcement actions, their targets, neutral process-state and authority-reference objects, all as feature-flagged typed data on a matter (no legal interpretation, no new tables), giving the future counsel content layer a structured home.

Release v8.25.69 (#2737)

• Redesign executive Decision Records with distinct lifecycle and outcome, authorized badge ownership, structured cost and governance records, computed CAD 5,000 approval escalation, due-date alerts, and deterministic newest-first presentation.

Release v8.25.44 (#2289, #3171)

• When no read-only GitHub token is set, the Command Center now shows one "Connect GitHub" notice instead of three separate empty panels, so the dashboard stays compact until the integration is connected.

Release v8.25.39 (#2289, #3171)

• The Command Center's overdue-deadline panel now groups by matter — a matter with many overdue items collapses to one expandable summary (count, oldest date, worst days-overdue) instead of flooding the list, and nothing is hidden.

Release v8.25.34 (#3181)

• Wire the brand-registry validator into CI (new Brand Registry workflow runs validate.py on brand-registry/** changes — enforcing schema, fail-closed integrity, sanctions review-expiry, SEO noindex, and generated-doc freshness in one pass), and add the provenance & domain-governance rollout plan sequencing per-market provenance and per-apex domain governance across the Launch Gates.

Release v8.25.33 (#3176)

• Land the JAIDC global jurisdiction/brand registry (v0.7.1 records model) as a tracked, validated, UNWIRED library under brand-registry/ — canonical brand-registry.json (419 records), JSON Schema, Python validator + Markdown generator, a fail-closed identity-first resolver with behavioral tests, plus the routing-policy, legal-applicability, decision-log, and market-activation docs. Nothing is wired into request routing; it sits beside lib/editions.ts until a deliberate reconciliation.

Release v8.25.32 (#2289, #3171)

• Command Center count labels now state their scope (platform total, calendar month) so the same metric no longer looks contradictory across panels, and revenue collapses to a single figure with a note when every period is equal.

Release v8.25.27 (#3073, #3084, #3107, #3141)

• Bailiff paid-order fee now matches the founder-set huissier-qc platform fee everywhere (was silently drifting to a stale $7); closed a second, unguarded huissier-testimonial path in provider onboarding; added a dark provider-category/jurisdiction catalog bridge; added a private-bucket, scan-gated document upload to the bailiff order form.

Release v8.25.22 (#2289, #3169)

• Command Center overdue-deadline rows now show clean titles — markdown fragments and mid-word filename slices are stripped, fixing garbled labels and their duplicate rows.

Release v8.25.17 (#3029, #3030, #3155, #3156)

• Generalized the consent/do-not-contact/removal apparatus to every scraped provider type (not just commissioners), added the counsel_salience demand-telemetry recompute + acquisition-gap report, and closed two recurring CI failure classes (invalid changeset class, unreviewed Dependabot major bumps).

Release v8.24.92 (#2594, #2602, #2997, #2998)

• Security hardening — expert profiles now expose only a public view at the database boundary (no internal columns to direct clients), expert intake gains durable idempotency + rate limits + a notification cooldown, CSP enforces object-src/base-uri/frame-ancestors and drops unsafe-eval, and profiles.role gets a defense-in-depth RLS check.

Release v8.24.87 (#3025, #3026, #3027, #3028)

• Provider Category Registry v0.6 goes live on the marketplace — the Barreau crosswalk classifier, seven provider-profile facets, a registry-driven category browser, and fail-closed UPL/Class-B promotion gating (Class B stays searchable, never promoted, until counsel sign-off).

Release v8.24.62 (#3161)

• The document-service Stripe line item and receipt now (1) show a human-readable provider label per locale — "Bailiff (Québec)", "Process server", "Notary", "International service" — instead of the raw slug (huissier-qc / process-server), and (2) brand to the active edition instead of hardcoding "Juge.ca" on every edition. Also gives the English-first Canada edition its own domain-style brand "Judge911.ca" (it defaulted to bare "Judge911"), matching qc "Juge.ca" and us "Judge911.com". The platform-fee-vs-professional-fee separation and amounts are unchanged.

Release v8.24.60 (#3146)

• Restore production deploys — the evidence-storage protocol gate now skips gracefully when its Supabase service-role key is absent (as it correctly is in the leak-guarded .env.local) instead of hard-failing every Fly deploy.

Release v8.24.55 (#3079)

• Corrected the document-service catalog to real flat transaction fees ($10 mandates, $14 international) — the fictitious $99–$249 placeholders would otherwise charge live at activation.
• Separate the live $10/$14 platform transaction fee from professional estimates and disclose the provider's separate charges before payment and in Stripe.

Release v8.24.45 (#2912)

• Make the version hand-bump guard non-fatal on the "behind-main" case. A branch that never touched lib/version.ts or package.json but fell behind main's release version was hard-failed, forcing a rebase + full-CI rerun on every downstream chore(release) — an unwinnable treadmill on a fast-moving main. It's now a warning; the guard still fails closed on real hand-bumps. Squash-merging a stale branch cannot corrupt the version (its diff contains no version change; auto-version-bump assigns the next release).

Release v8.24.44 (#3069)

• Preserve the paid service-of-process funnel while adding an edition-aware, durably recorded no-payment request option.

Release v8.24.39 (#2907)

• Revert the automated tailwindcss 3.4.13 → 4.3.3 dependency bump. Tailwind v4 is a breaking major release that needs `@tailwindcss/postcss` and a CSS-first config migration; merged as-is it broke the production build (`tailwindcss` used directly as a PostCSS plugin), reddening main and blocking every PR and Fly deploys. Restore the known-good v3 until a deliberate v4 migration.

Release v8.24.37 (#3136)

• A paid bailiff order now completes end-to-end — after the $7 platform fee is charged, the buyer lands on a bailiff-specific confirmation page (order reference, fee paid, party to be served, service deadline and next steps), receives a confirmation email, and the order is durably queued for huissier dispatch with a guaranteed internal alert so it is never missed. The order form also collects an optional service deadline and requester address.

Release v8.24.32 (#2750)

• Unblock main CI so every open PR can rebase onto a green base — reclass an unreleasable pending changeset (viewer-ai-actions used an invalid class `enhancement`, now `aiAutomationFeature`) and harden the evidence-storage protocol guard test so it checks real deploy-workflow step order instead of matching a `flyctl deploy` mention inside a header comment.
• The file viewer gains an ✨ AI actions menu — a one-click deterministic summary and a "extract facts & parties" action that sends dates, events and party names into the existing human review queue as suggestions, never auto-applied.

Release v8.24.22 (#2577)

• Emergency kill-switch for three Conflict Model™ surfaces (looping intake, Objective step, demand-letter doctrine) that reached production unratified. They now render/run only when CONFLICT_MODEL_ENABLED is explicitly set — off by default — so the dispute-intake wizard skips those steps and the AI draft route refuses demand-letter drafts until the surfaces are ratified. The code is preserved (flag, not revert) so the review audit trail is intact.

Release v8.24.17 (#2871)

• "Loi 25 access-export triage COMPLETE (#2871): all 33 matter-scoped baseline tables classified into the subject-data export registry. The clear-cut 23 (batch 1) plus the 9 held third-party-PII tables now EXPORT WITH REDACTION per the founder disposition (exec seq 111) — sensitive/third-party/credential/financial/privileged columns redacted by column exclusion (free-text that could embed third-party identifiers conservatively excluded); `storage` excluded as the object-store index (files disclosed via documents/evidence_items metadata). Per-table redaction recorded in IMPLEMENTATION_2871.md (disposition log). Backlog now empty; unredacted originals retained under restricted access."
• Evidence storage now reserves and meters bytes against the matter owner across browser, server, automation, and generated-document uploads.

Release v8.23.87 (#2861)

• The research editorial queue now shows each submission's Loi 25 consent, no-privileged-data and CC BY 4.0 attestations, lets editors read the full text and citations, record review notes, and requires a written reason before declining.

Release v8.23.77 (#3068)

• Fly production deploys now reject incomplete or symlink-dependent standalone runtimes before rollout, pin the intended fleet count, wake exact-image spare capacity, and require every Machine to pass health checks.

Release v8.23.52 (#128, #3055)

• Add the (inert-until-KMS) matter-content envelope plumbing — a per-matter KEK manager and a seal/open helper that will encrypt matters.data under matter_keks once a root CMK is provisioned.

Release v8.23.47 (#128, #3056)

• Add an off-by-default production guard that refuses to persist operator-decryptable (plain:/LocalKeyProvider) envelope writes once ENFORCE_PROD_ENVELOPE_KMS is armed after a KMS key is provisioned.

Release v8.23.42 (#3090)

• Marketplace categories now select one of ten canonical, fail-closed workflow-family policies backed by the shared assignment lifecycle.

Release v8.23.37 (#3127)

• Fixed the judge911-ca deploy mirror, which was silently no-op'ing on every run — flyctl's status JSON needed a fallback field to resolve the image to promote, so judge911.ca is now actually kept in sync with juge.ca again.

Release v8.23.32 (#3124)

• judge911.ca now auto-deploys with juge.ca — the Fly pipeline mirrors juge-ca's just-shipped image to judge911-ca after every deploy, non-fatally, closing the drift gap between the two sites.

Release v8.23.7 (#2752)

• Correct an unreleasable pending changeset (evidence-search-depth used an invalid class `enhancement`) so the required changeset-validity CI gate passes and the entry can be consumed at release time.
• Evidence search now reaches inside documents — it matches extracted text, party names, and detected dates (not just filename/folder/ID) and shows an in-text snippet of the match under each hit, with the search index built off the render path so typing stays fast.