Changes to Engage

Changelog

Read recent changes to Engage, from new features to fixes and improvements. The source repository holds the full development history.

17 November 2026

2 commits
  1. Ops & CIquorum
    Stop leaking per-case replica-set databases (#132)

    * test(quorum): drop each replica-set database and document test hygiene * chore(changelog): record the test database hygiene fix

    34c8d17 ↗
  2. Ops & CIplatform
    [Consolidated] Two-tier quorum and Discord attention-debt digest (#127)

    * feat(discord): add attention-debt ranking and safe weekly webhook delivery (#125) * chore(discord): configure safe opt-in digest settings (#125) * chore(discord): configure safe opt-in digest settings (#125) * chore(discord): configure safe opt-in digest settings (#125) * feat(discord): expose guarded weekly scheduler and admin test API (#125) * feat(discord): expose guarded weekly scheduler and admin test API (#125) * feat(discord): add digest preview and test-send to engagement admin (#125) * feat(discord): wire admin preview and safe test-send controls (#125) * fix(discord): rank inaugural proposals by attention, not legacy creation date (#125) * fix(discord): determine Melbourne digest week independent of locale formatting (#125) * test(discord): cover attention-debt fairness, launch cohort and isolated webhook delivery (#125) * fix(discord): escape titles safely and type delivery ledger (#125) * docs(discord): document launch cohort, algorithm and test-server rollout (#125) * docs(discord): register digest channel and scheduled endpoint (#125) * style(discord): format read-only message preview (#125) * fix(discord): link directly to eligible open ballots and discussions (#125) * refactor(discord): isolate safe webhook URL validation (#125) * feat(discord): persist encrypted, audited webhook and schedule settings in Engage (#125) * feat(discord): read in-app settings and enforce editable weekly schedule (#125) * fix(discord): preserve immutable settings record key during updates (#125) * feat(discord): add admin-only encrypted integration settings API (#125) * feat(discord): add in-app webhook, role and schedule configuration UI (#125) * feat(discord): integrate Discord configuration into Platform settings (#125) * fix(discord): report saved config and enforce settings authority (#125) * chore(discord): move integration configuration out of environment variables (#125) * chore(discord): move integration configuration out of environment variables (#125) * refactor(discord): centralise setup and testing in Platform settings (#125) * refactor(discord): remove superseded engagement dashboard controls (#125) * fix(discord): actually remove saved secrets from MongoDB on clear (#125) * test(discord): exercise isolated sending through stored encrypted config (#125) * test(discord): cover encrypted in-app settings, removal, isolation and schedule (#125) * docs(discord): document in-app encrypted settings and configurable schedule (#125) * docs(discord): align scheduled jobs and settings architecture (#125) * feat(ballots): add two-tier constitutional-style quorum Evaluate platform quorum (30 eligible registered members) and ballot quorum (max(ceil(sqrt(N)), min(30, ceil(N/2)))) once at closure, inside the closure transaction. Persist one immutable ballot_quorum_records snapshot with the electorate, thresholds, participation, tally and verdict. Certification refuses a missing, unreadable or mismatched snapshot and cannot override a quorum failure into approval or rejection. Ballots closed before the rule keep the approval-only basis. Record genuine signed-in use as a daily activity signal for the 90-day active electorate. Refs #122 * feat(proposals): explain quorum to members and officers Show the current eligible registered membership, active electorate, estimated requirement, participation and the closure caveat on every ballot page. After closure, show the recorded calculation and whether each test was met. Give administrators the same calculation and any closure anomaly on the proposal workspace and inline outcome control. Inconclusive ballots are presented as neither adopted nor rejected, and a quorum failure can only be recorded as inconclusive. Refs #122 * test(discord): type string-keyed MongoDB settings fixture (#125) * docs(discord): document in-app settings endpoint (#125) * fix(discord): support Node strip-only TypeScript test runtime (#125) * docs(governance): record the two-tier quorum decision and basis Record D37–D39 and the rule 36 adaptation: platform quorum, ballot formula, the 90-day active member definition, closure immutability, inconclusive failure and the no-override rule. Note that rule 30(4)(e) AGM obligations continue and that rule 98 confirmation is still needed before the first post-adoption closure is treated as binding. Update the public explanation, legal Terms wording, lifecycle, data model, capability and known-gap records, and add the quorum procedure page. Refs #122 * test(ballots): cover quorum boundaries and closure evidence Cover the published formula and its transitions, platform boundaries, approval and quorum separation, abstentions, vote changes, duplicate participation, zero active members, legacy pre-rule closures, open ballots at rollout, membership changes after closure, participation mismatch, missing snapshots and concurrent closure with a membership update. Move existing certification mechanics fixtures to pre-rule closures so they keep testing the approval rule. Refs #122 * fix(discord): use accessible confirmation for removing saved webhooks (#125) * fix(proposals): clarify zero active electorate in quorum displays Show 'No active electorate yet' rather than a zero participant target, and show recorded participation without a misleading 'of 0'. This keeps the formula exact while making the small-electorate state understandable. Refs #122 * test(discord): allow same-week catch-up when the scheduled slot was missed (#125) * docs(discord): clarify same-week scheduling catch-up behaviour (#125) * chore(changelog): record the two-tier quorum work Refs #122 * fix(ballots): close the activity window at the ballot deadline Cap every activity source at the closure timestamp and anchor the snapshot to the official deadline rather than a late scheduler run. Post-deadline browsing must not enlarge the active electorate. Refs #122 * chore(changelog): record the quorum activity-window fix Refs #122 * docs(governance): state the zero-active quorum edge case Refs #122 * chore(changelog): record the quorum edge-case note Refs #122 * test(ballots): keep projection certification case pre-quorum Refs #122 * chore(changelog): record the projection test fix Refs #122 * chore(changelog): refresh for the consolidated branch Refs #122, #125 * test(discord): assert webhook fields are absent, not substrings Resolve CodeQL's incomplete URL substring sanitization alerts in the secret-redaction test without weakening the assertion. Refs #125 * chore(changelog): record the Discord test hardening Refs #125

    5eb4e20 ↗

15 November 2026

4 commits
  1. Ops & CIplatform
    Rewrite Engage copy around political participation (#97) (#98)

    * fix(copy): clarify participation and public discussion (#97) * docs(copy): record delivered batch and resumable PR (#97) * fix(copy): invite participation across homepage queues and highlights (#97) * fix(copy): explain participation and current decision process (#97) * docs(copy): record guide delivery and preserve changelog history (#97) * fix(copy): make proposal discovery and submission clearer (#97) * docs(copy): checkpoint proposal form delivery (#97) * fix(copy): clarify ballot status, amendments and proposal history (#97) * docs(copy): checkpoint ballot review and validation (#97) * fix(copy): distinguish policy adoption records and community input (#97) * docs(copy): checkpoint policy and community review (#97) * fix(copy): explain sign-in and optional member participation (#97) * test(copy): align membership label assertion and checkpoint progress (#97) * fix(copy): explain member setup, branch following and notifications (#97) * docs(copy): checkpoint member setup and preferences (#97) * fix(copy): make participation emails and unsubscribe wording clearer (#97) * docs(copy): checkpoint participation email review (#97) * fix(copy): clarify officer tasks and member decision authority (#97) * docs(copy): checkpoint governance administration review (#97) * fix(copy): clarify administration settings and public visibility direction (#97) * docs(copy): checkpoint remaining administration review (#97) * fix(copy): reconcile final notices, errors and terminology (#97) * docs(copy): finalise editorial coverage and resumable handover (#97)

    b9286f4 ↗
  2. Ops & CIplatform
    Branch policy registry import, branch-scoped URLs and post-ratification policy changes (#90)

    * feat(policies): import adopted branch policy with explicit provenance (#89) A branch may already hold policy adopted outside Engage. The import treats that as a provenance operation, not a proposal flow: - reads a branch policy feed and validates every record before writing; - requires an explicit authority basis and fails closed without one; - writes a published, adopted registry record plus an immutable policy_revision holding the exact source document and content hash; - records the source, authority basis, timestamps and provenance lineage; - reports created, unchanged, changed, conflicting, invalid and missing records without overwriting anything; - never republishes a record that was withdrawn, superseded or repealed. Dry-run and re-run are safe: only 'create' entries write, every write is keyed, and a changed source is a review item for the change lifecycle rather than a silent rewrite. * feat(policies): branch-scoped registry and changes to adopted policy (#89, #37) The registry is now navigable by authority and topic, and adopted policy can change through a proposal instead of being frozen at publication. Registry: - policy addresses become /policies/<branch>/<slug>/; internal IDs stay stable and legacy /policies/<id>/ addresses redirect to the canonical path; - the registry collates by adopting branch, then by the branch's own topics, so 41 Victorian policies are browsable rather than one flat list; - each branch has its own registry page with adoption basis, source and current/past tabs; a search and branch filter remain available; - rows show title, two-line summary, topic, branch and adoption origin; - imported records show their authority, import date and source. Post-ratification lifecycle: - a proposal may declare targetPolicyId and amend/replace/repeal; the target is fixed at creation against the exact published revision; - the policy page shows the proposed changes separately and never implies a draft has changed adopted policy; - ratification of a repeal records the deciding proposal; an amendment or replacement supersedes the predecessor only when the successor is published, so the public registry never shows a gap; - imported and Engage-ratified lineage read together in the same history. * chore(changelog): refresh public changelog for policy registry work * fix(policies): clear search and branch filters together in the registry * chore(changelog): include registry filter fix in the snapshot * chore(changelog): refresh snapshot at merge head * fix(policies): use the ballot-scoped result filter in policy detail

    10146b9 ↗
  3. Ops & CIgovernance
    Cover governance writes on a MongoDB replica set (#91)

    * test(governance): cover governance writes on a MongoDB replica set Add replica-set cases for the deletion guard, stage-transition audit events, formal-decision idempotency and conditional-write concurrency. The in-memory database cannot prove transactions, unique indexes or race behaviour, so each case is skipped without VOTING_TEST_MONGODB_URI and drops its own database. Covers known gap 17 (docs/status/known-gaps.md) and RFC 0001 cross-slice risk 4. * test(governance): adapt replica-set coverage to closed-ballot certification #28 requires a closed ballot before a result can be recorded, and checks the recorded result against the votes bound to the ballot and revision. Close the fixtures as the scheduler does and record the zero-vote certifications as explicit overrides, so the atomicity, idempotency and concurrency cases keep testing what they claim. Adds a real-MongoDB case proving an open ballot cannot be certified, that the refusal writes no result, and that certification succeeds after closure with the computed tally stored.

    dd57aa3 ↗
  4. Ops & CIplatform
    RFC 0001: Sprint 1 integration, Phase 1 lifecycle, rendering performance and Turnstile (#51)

    * docs(rfc): propose platform evolution and integrity programme * fix(governance): enforce ballot deadlines, rebinding, atomic decisions, and deletion guards (#26, #50) * fix(membership): guard CRM-sourced memberships, exempt national row from conflict, and record manual provenance (#32) * fix(rbac): consolidate permission enforcement, ballot binding gate, and ratification authority checks (#27, #31) * fix(proposals): clear provenance without a conflicting stage update Staff editing a proposal through the admin form always submits provenance: null for the default 'clear provenance' option. saveProposal placed provenance in both $set and $unset, which MongoDB rejects with a path conflict, so every staff edit failed against a real database. Make the clear and set branches mutually exclusive and cover the case against the real MongoDB voting suite. * fix(ballots): keep the deadline banner hydration-stable The ballot deadline rendered a server date and a post-mount relative time in the same text nodes. React 19 reported a text hydration mismatch on every ballot with a deadline, forcing an unnecessary client re-render. Mark the two intentionally time-dependent nodes as hydration-stable and make the date helper's timezone explicit so server and client markup match before the viewer-local deadline replaces it. * test(rbac): reconcile Sprint 1 authority expectations after integration The governance branch made ballots.bind and a future closing date mandatory when entering Decide, and refuses deletion of matters with governance history. The RBAC branch assumed neither. Align the fixtures with real session permissions, supply a ballot deadline, and delete a draft with no history. Ignore branch grants for permissions the catalogue reserves to National scope, allow branch-scoped comment moderation, and prove that a branch proposals.delete grant does not confer destructive authority. * docs(rfc): integrate Sprint 1 and record maintainer decisions Add the canonical governance decision register, the RFC 0001 programme tracker and the Sprint 1 integration report. Update the documentation index and replace the open-question list with the decisions now supplied, while keeping genuinely unresolved questions explicit. Add a browser verification script for the deadline, voting and vote-change journeys and record its evidence. * chore(changelog): refresh snapshot for the Sprint 1 integration * docs(rfc): track active workstreams and new implementation issues Record the Phase 1, rendering-performance and Turnstile workstreams, link the new issues for performance (#52), the command layer (#53), the decision record and responsibility queue (#54), and ballot-results migration safety (#55). Clarify that #36 is deferred rather than blocked inside this programme. * docs(rfc): correct membership workstream status The CRM branch did not add the unique branch-membership index or the duplicate-resolving migration required by #32, so I3 remains partial. * feat(lifecycle): second proposals and schedule advancement and ballot closure Implements the approved lifecycle schedule from the decision register (D3-D7, RFC 0001 Phase 1, refs #26 and #30). - A verified member who is not the author may second a proposal while it is in Propose. The act records `secondedBy`, `secondedAt` and `deliberationEndsAt` (30 days) and writes `proposal.seconded`. It does not change the stage or grant ballot authority. - `src/lib/lifecycle-schedule.ts` is the single source of truth for the 30-day deliberation period, 30-day ballot period and 60-day ceiling. - A system actor (`system:lifecycle-scheduler`) advances due deliberations to Decide, binding the latest immutable revision and setting `ballotClosesAt = secondedAt + 60 days`. It requires no `ballots.bind`; the human early-advancement gate is unchanged. - Advancement fails closed on unresolved amendments (`rejected`, `withdrawn`, `applied`, `not-endorsed` and `inconclusive` are the only non-blocking statuses), on votes bound to other wording, on a missing seconding anchor, and on a ceiling already in the past. - Ballots close automatically at their deadline: `ballot.closed` is recorded once, the stage and result are untouched, and voting is refused after the boundary (D12 is not implemented). - Conditional filters, deterministic event IDs and transactional writes make both operations idempotent and safe under concurrent runs. - An officer opening a ballot without a date now receives the 30-day default; explicit dates remain authoritative. - Adds a read-only report for legacy ballots without deadlines and matters in Deliberate without a deliberation clock. * feat(ops): add governance scheduler and deadline migration report commands - `npm run governance:scheduler` runs the lifecycle scheduler as a dry run by default and writes only with `--apply`. It prints a JSON report with advanced, skipped, closed, blockers and errors, and exits non-zero on errors. - `npm run governance:migration-report` prints the read-only legacy report. - Both require MONGODB_URI and fail loudly without it; neither adds a daemon nor requires production credentials. * docs(lifecycle): document seconding, scheduled transitions and closure Records the implemented behaviour and the assumptions visible for review: - one seconder who is not the author; seconding records the clock but does not change the stage or gate Propose -> Deliberate; - automatic proposal advancement at the deliberation deadline by a system actor, without `ballots.bind`; - the conservative blocking-amendment set, reason codes and failure behaviour; - automatic closure at the ballot deadline without a stage change or result; - the 30-day default for officer-opened ballots; - new proposal fields (`secondedBy`, `secondedAt`, `deliberationEndsAt`, `ballotClosedAt`), deterministic event IDs and scheduler transaction rules; - the read-only migration report and its manual recovery options. * chore(changelog): refresh snapshot for the Phase 1 lifecycle work * docs(lifecycle): state that returning to Propose keeps the seconding clock * chore(changelog): include the lifecycle documentation commits * feat(security): verify Turnstile tokens for unauthenticated actions Add server-side Cloudflare Turnstile verification (D32) and a shared MongoDB fixed-window limiter for the abuse-prone unauthenticated routes. - protect Sense Box submission, magic-link sign-in/first registration, and email sign-up if it is enabled later - fail closed with 503 and an operational error when production requires Turnstile but the secret or site key is missing - report missing, invalid, expired, replayed and malformed tokens with plain-language errors; never log or return the secret or token - store only a keyed hash of the client address, with a TTL index, so limits are shared across instances - leave authenticated voting, deliberation and admin writes untouched - tests cover configuration states, verification outcomes, route refusal and acceptance, real-MongoDB concurrency and the voting exemption * feat(security): show the Turnstile widget on protected forms Render Cloudflare Turnstile on the Sense Box and magic-link sign-in forms using Horizon primitives. The widget renders nothing when no site key is configured, reports load and expiry failures inline with a retry action, and asks for a fresh token after a rejected submission because tokens are single-use. * docs(security): document Turnstile enforcement and rate limits Record the protected actions, configuration contract, fail-closed states, failure messages, privacy boundary, rate-limit defaults and remaining gaps (CSP and headers stay with #38). Add the new keys to the environment example. * chore(changelog): refresh snapshot for Turnstile abuse protection * docs(security): name the rate-limit collection plainly * perf(tooling): add rendering performance harness and DB command metrics Adds an opt-in MongoDB command monitor (disabled unless ENGAGE_DB_COMMAND_MONITOR=1 and APP_MODE is not production), a development-only diagnostics route, and a repeatable Playwright/Mongo measurement harness with baseline and comparison modes. No production behaviour changes. * perf(proposals): batch independent detail reads and defer ballot hydration Runs supersede, eligibility, related-branch and evidence reads with the rest of the proposal-detail batch instead of in sequence. The ballot hydrates on idle rather than blocking load; the stance selector does the same. * perf(auth): resolve a session once per request render Layouts and pages each asked for the same session. Cache the in-flight resolution against the Request object so one browser request performs one session lookup while role revocation remains request-scoped. Adds a regression test for reuse. * perf(lists): project list reads and reuse member vote queries Stops list queries returning detailHtml and, where no search depends on it, long rationale text. Home and the proposals list reuse one member-vote read for outstanding ballots; the member page loads shared activity inputs once instead of twice. Member-page islands in inactive views hydrate only when visible. Adds visibility and vote-reuse regression tests. * perf(admin): consolidate register reads and defer participation panel The proposals register now reads the proposal collection once and batches amendment and revision lookups instead of issuing one query per row. The overview's recent-participation panel moves to a server island with a stable fallback, so its session-dependent reads no longer block the dashboard. Admin timelines hydrate when visible; migrations hydrate on idle. * perf(client): defer notification hydration off the critical path The header notification bell and notification preferences hydrate when the browser is idle. The bell is secondary to page content but still loads its unread count; no API or preference behaviour changes. * docs(status): record the rendering performance audit and measurements Classifies initial, deferred and interaction-only data per audited page; records baseline and after medians, queries removed or deferred, bundle findings, limitations and the highest-value remaining work. Adds a pnpm/npm perf:render entry point. * chore(changelog): refresh snapshot for the rendering performance slice * fix(admin): render saved values in select controls Astro renders React component slot children as raw HTML, so React never sees the options inside NativeSelect and cannot apply defaultValue. Every select rendered its first option, which meant editing a proposal could silently reset its stage, clearing provenance, changing a member's status to pending, or applying the wrong filter or sort. Mark the stored option as selected at each affected call site. The admin proposal editor and register, member administration, Sense Box review, engagement period, policy filters and public proposal filters are covered. * feat(proposals): make seconding the act that opens deliberation D3 requires a seconder before Deliberate and D4 anchors the clock to seconding. The initial Phase 1 implementation recorded the seconding but left Propose -> Deliberate to an officer, which could stall a proposal indefinitely and run the clock in the wrong stage. Seconding now performs the transition and records both the seconding and the stage transition. Officer and API transitions into Deliberate are refused without a recorded seconder. A member-facing control appears on the proposal page for eligible, non-author members, with inline feedback and no raw controls. Update the unrelated stage-transition fixtures to record a seconder explicitly. Extend the browser verification to cover seconding, the 30-day default when no ballot date is given, a rejected past date, and the editor showing the proposal's real stage. * docs(lifecycle): record Phase 1 delivery and the remaining decisions Mark seconding, scheduled advancement and automatic closure as implemented, update the known-gap register, and add O9/O10 for the administrative direct-creation path and renewed seconding after material rewrites. * chore(changelog): refresh after the rendering performance merge * docs(rfc): record Phase 1, rendering performance and Turnstile integration Update I2, I6, I10, I12 and the workstream table with measured evidence and the remaining gaps. Mark the performance and Turnstile documents as merged into the integration branch. * docs(rfc): mark integrated workstreams and the next Phase 2 slices * docs(rfc): add the Phase 2 orchestrator handover brief Record the handover state, governance invariants, traps found during delivery, the recommended Phase 2 sequence, parallelisation rules, verification commands, open decisions and the first ten actions for the next orchestrator. * fix(security,proposals): address PR #51 review findings * chore(deploy): pass Turnstile and rate-limit env vars to app container * fix(governance,security,ui): address CodeRabbit review findings on PR #51 * test(rate-limit): align future window assertions in real MongoDB test

    3b36947 ↗

13 November 2026

9 commits
  1. Ops & CIplatform
    Governance transparency, extensibility hardening, notifications, PWA & Web Push (#23)

    * docs(governance): specify historical access, reporting privacy, and AI briefing design * feat(governance): add evidence-backed contribution outcomes and historical safety checks * fix(reporting): enforce branch admin scope and add PDF confidentiality disclosures * chore(changelog): record governance transparency sprint * docs(rbac): document RBAC audit, permission matrix, and configurable roles spec * fix(security): enforce archived proposal review permission on GET /api/amendments * feat(rbac): add configurable scoped roles, permission evaluation, and admin UI * chore(changelog): record RBAC audit and configurable roles * fix(governance): exclude governance resolutions from policy ratification and publication workflows * docs(governance): document safe policy registry reconciliation for misclassified resolutions * chore(changelog): record governance resolution classification fix * feat(ballots): add 14 Jan 2027 open ballot expiry migration and prominent deadline display * feat(governance): add extensible matter registry and type-aware lifecycle validation * feat(governance): decouple ballot/decision records and add provenance relationship validation * fix(security): enforce scoped RBAC permissions across admin API endpoints * feat(architecture): add integration seams, authorised read models, resilience helpers, and indexes * chore(changelog): record extensibility sprint and ballot expiry migration * feat(email): add responsive Horizon email templates for all lifecycle notifications * feat(email): add explicit approval-gated batch re-engagement workflow * feat(pwa): add installable Engage manifest, Horizon icons, and safe service worker * fix(pwa): generate app icons from Horizon SVG logo * feat(notifications): add self-hosted VAPID Web Push, in-app inbox, and unified preferences * feat(member): add unified NotificationCenter UI for inbox, email, and push * test(notifications): add notification/PWA tests, preview script, and docs * chore(changelog): update changelog snapshot * fix(deploy): stop repeated Coolify deployments after health failures * chore(changelog): record Coolify deployment fix

    baae42d ↗
  2. Ops & CIplatform
    Feat/usability governance sprint (#22)

    * feat(admin): redesign navigation, overview, ballots and reporting IA * feat(admin): overhaul proposal workspace with progressive disclosure and feedback * feat(reports): add on-demand proposal PDF report generation * test(admin): add proposal PDF tests, CSV scope fix and changelog * docs(agents): enforce shadcn primitive usage * refactor(ui): migrate custom controls to shadcn primitives * chore(changelog): record shadcn primitive migration

    b271a70 ↗
  3. Ops & CIchangelog
    Record GitHub protection defaults (#19)
    b8af56b ↗
  4. Ops & CIrepo
    Add CODEOWNERS for default review routing (#18)

    Every path defaults to @finneh4249 so pull requests are routed to a single accountable reviewer. Ownership is advisory only: the main ruleset keeps a one-approval requirement for all contributors.

    041c469 ↗
  5. Ops & CIchangelog
    Record Sense Box destination picker
    430bec4 ↗
  6. Ops & CIchangelog
    Record branch identity repair
    63e0a28 ↗
  7. Ops & CIchangelog
    Record self-service branch membership
    123606c ↗
  8. Ops & CIchangelog
    Record Sense Box availability fix
    e22aa5e ↗
  9. Ops & CIchangelog
    Record Sense Box release
    f2b384d ↗

9 November 2026

9 commits
  1. Ops & CIproposals
    Capture approved desktop and mobile journeys
    9ef66f5 ↗
  2. Ops & CIchangelog
    Include voting status safeguard
    99a9ea0 ↗
  3. Ops & CIchangelog
    Record proposal participation redesign
    a17770f ↗
  4. Ops & CIchangelog
    Record proposal experience changes
    dede16c ↗
  5. Ops & CIagents.md
    Enhance AGENTS.md with more bounded structure for Coding agents working on the repository
    50a7710 ↗
  6. Ops & CIchangelog
    Record audited platform settings
    d619b8f ↗
  7. Ops & CIchangelog
    Record durable migrations and branch seed
    b808f0b ↗
  8. Ops & CIchangelog
    Record branch participation and verification
    b980369 ↗
  9. Ops & CIchangelog
    Record the member engagement admin repair
    ba482d0 ↗