Changelog
Read recent changes to Engage, from new features to fixes and improvements. The source repository holds the full development history.
18 November 2026
1 commit- Define Engage as Fusion's home for participation
c0e85d1↗
17 November 2026
1 commit- Make the admin panel the home of configuration, not the deployment (#133)
* docs(config): make product ownership of configuration a standing rule Configuration belongs to the product, not the deployment. Adds AGENTS.md section 11: admin settings in MongoDB with validation, audit and defaults; environment variables reserved for secrets, the database, the public origin and deployment topology; every new variable justified in the change and in .env.example; operational thresholds, retry limits, cadences, toggles and policy timings are settings; tests inject values instead of tuning the deployment. Routes agents to the rule from the agent guide. The remaining operational environment knobs are tracked in #128. * fix(ballots): remove the tally projection deadline environment override ENGAGE_BALLOT_TALLY_DEADLINE_MS let the deployment stretch the 500 ms display-projection deadline, which is operational tuning in an environment variable. The wrapper already takes an explicit deadlineMs, so production now uses the fixed constant and callers with different needs pass a value. The projection suite no longer sets the variable. It waits a bounded time for the projection to equal the authoritative tally and, where a best-effort write was abandoned on the slow shared replica set, reconciles the row through the documented repair path before asserting. Encrypted ballots pass the explicit expected tally and decryption keys. Equality assertions are unchanged. Refs #128 * chore(changelog): record the configuration rule and projection deadline removal * chore(changelog): record the configuration policy after merging main
9e56766↗
15 November 2026
3 commits- Record the merged command layer and paginated register (#107)
d642bfc↗ - Record merged outcome validation and replica-set coverage (#92)
* docs(status): record merged outcome validation and replica-set governance coverage * chore(changelog): refresh the snapshot after the phase 1 merges
7e3d243↗ - Reconcile stale historical documentation with the canonical set (#44) (#84)
* docs(operations): correct removed endpoints, scripts and ballot closure model - Mark the page Superseded and link the canonical build/deploy guide. - Replace the removed /api/ballots check with /api/health and the removed seed-preview, backup-preview and restore-preview instructions with the behaviour that exists (startup seeding, host backup procedure). - Replace the ADR 0003 vote-admission and finalizeBallot description with the implemented deadline check, unique vote indexes and scheduler closure. - Correct the membership audit claim: no memberships.auditHistory or auditVersion exists. - Fix the missing release-gates link and stale preview/cookie statements. * docs(adr): record ballot-admission divergence in ADR 0003 Label the technology decision Current and the admission protocol Design-only, then record the verified implementation: castVote checks the deadline in application code before the transaction, uniqueness comes from the partial vote indexes, and closure writes ballotClosedAt without a tally. Notes that a vote passing the pre-check can commit after the cutoff. * docs(deploy): mark the Coolify deployment record historical Replace the 2026-11-08 cutover banner with a dated historical scope, point to the canonical deployment page, and correct the claim that no CI exists. * docs(engagement): correct the ballot deadline and label the UX record Replace the superseded 24 December 2026 deadline with the approved 30-day ballot period and the 2027-01-14 one-off expiry migration, and describe what the migration actually writes. Mark the dated UX journey record Historical so its old test counts are not read as current. * docs(governance): correct identifiable-ballot boundary and authority fields Identifiable ballots are limited to a national administrator or a holder of the national ballots.view_identifiable permission, not isAdmin alone. Record the ballots.bind and ballots.record_result gates, the current admin navigation, and mark the older governance API page Superseded. * docs(legal): reconcile the 2026-11-08 privacy review with shipped work Label the review Historical and correct the statements overtaken since: Plausible analytics, CRM membership verification, seconding and scheduled ballot closure are implemented, and the legal-acceptance enforcement and ballot privacy notice are applied. Record the delegated identifiable-ballot boundary and define the Current/Historical/Superseded/Design-only vocabulary in the index.
6fd5562↗
14 November 2026
2 commits- Require checking open issues before implementation (#48)
37aa2f0↗ - Canonical documentation set and known-gap tracking (#46)
* docs(research): add cross-industry product and UX research Compares Discord, Linear, GitHub, GitLab, Zendesk, Airtable, Notion, Discourse, Stripe, Figma, MediaWiki and Google Docs with Engage. Includes an evidence register, cross-industry synthesis, prioritised backlog, five Horizon UX concepts and an implementation sequence. * chore(changelog): record cross-industry research * fix(api): enforce minimal response DTOs, ballot privacy, and bounded pagination * feat(proposals): separate geographic scope from branch identity Add a canonical proposal scope model with stable keys (national, nsw, vic, ...) and consistent labels from the site's state configuration. Branch records remain the organisational identity; legacy records resolve to the canonical scope without being rewritten. Server validation now rejects display labels, non-string or conflicting scopes and ambiguous duplicate geography, and enforces branch administration independently of the rendered controls. * feat(proposals): use an accessible scope selector Replace the native proposal-scope dropdown with the existing ToggleGroup primitive, giving a single National option, consistently named states and territories, visible focus, keyboard navigation and responsive wrapping. Default to the member's authorised branch where one applies and submit the canonical scope key rather than a display label. * chore(changelog): refresh snapshot after proposal scope changes * fix(security): harden RBAC boundaries, CSRF origin checks, and markdown links * feat(ballots): add AES-256-GCM encrypted vote storage, blind indexing, and migration * refactor(auth): unify legacy administrative permission resolution * chore(changelog): record permission resolution consolidation * fix(security): handle rotated blind-index upserts and proxy-safe CSRF origins * feat(site): add branded 403, 404 and 500 error pages * chore(changelog): refresh snapshot after status pages * feat(auth): separate participation, voting and administration Decouple proposal destinations from branch administration. Any verified member may submit to National, any state or territory, or any recognised local branch. Submission creates no membership, voting eligibility, or administrative authority; governance authority remains restricted. Replace the destination selector's administrative filtering with a canonical list of all recognised destinations. National and the eight states/territories stay primary; local branches are revealed behind a disclosure and the member's own branch is preselected. Align Member Management with the capability model: member directory, verification, and role changes use members.view, members.verify, and roles.manage. Canonical system role names are shared, delegated branch and custom roles are visible on each member, and anti-escalation blocks delegated managers from granting or altering national administrators. Document the target authorisation model and remaining migration work. * chore(changelog): record authorisation consolidation * test(ci): update member lifecycle browser check for unified notification center * feat(site): open notifications in a header popover The notification bell now shows recent updates in place, with unread count, mark all read, and a link to full notification settings. The bell stays visible on mobile instead of living inside the collapsible menu. * chore(changelog): refresh snapshot after notification popover * fix(security): allow national RBAC grants in branch search and preserve scope on read * feat(auth): support multiple roles and a grouped scope select Allow members to hold several platform system roles at once. Member Management now uses checkboxes for Member, Moderator, and National Administrator; roles are replaced as a set, effective permissions remain a union, and removing one role does not revoke another. Session and member DTOs expose the full role list while the legacy single role remains the highest-precedence value. Replace the nine-option destination radio group with a grouped, type-ahead Select built from the design-system primitive. National and the states/territories form the primary group; local branches are grouped separately. The control stays compact, keyboard accessible, and mobile friendly without exposing nine chips. * chore(changelog): record multi-role and grouped scope select * feat(verification): verify members from Underground CRM * chore(changelog): record CRM membership verification * docs: establish canonical product, domain and architecture documentation * chore(changelog): record documentation sprint * docs(status): link known gaps to GitHub issues * chore(changelog): record known-gap tracking * chore(changelog): refresh snapshot before merge
52ffaf6↗
13 November 2026
1 commit- Cross-industry product and UX research (#25)
* docs(research): add cross-industry product and UX research Compares Discord, Linear, GitHub, GitLab, Zendesk, Airtable, Notion, Discourse, Stripe, Figma, MediaWiki and Google Docs with Engage. Includes an evidence register, cross-industry synthesis, prioritised backlog, five Horizon UX concepts and an implementation sequence. * chore(changelog): record cross-industry research * fix(api): enforce minimal response DTOs, ballot privacy, and bounded pagination * feat(proposals): separate geographic scope from branch identity Add a canonical proposal scope model with stable keys (national, nsw, vic, ...) and consistent labels from the site's state configuration. Branch records remain the organisational identity; legacy records resolve to the canonical scope without being rewritten. Server validation now rejects display labels, non-string or conflicting scopes and ambiguous duplicate geography, and enforces branch administration independently of the rendered controls. * feat(proposals): use an accessible scope selector Replace the native proposal-scope dropdown with the existing ToggleGroup primitive, giving a single National option, consistently named states and territories, visible focus, keyboard navigation and responsive wrapping. Default to the member's authorised branch where one applies and submit the canonical scope key rather than a display label. * chore(changelog): refresh snapshot after proposal scope changes * fix(security): harden RBAC boundaries, CSRF origin checks, and markdown links * feat(ballots): add AES-256-GCM encrypted vote storage, blind indexing, and migration * refactor(auth): unify legacy administrative permission resolution * chore(changelog): record permission resolution consolidation * fix(security): handle rotated blind-index upserts and proxy-safe CSRF origins * feat(site): add branded 403, 404 and 500 error pages * chore(changelog): refresh snapshot after status pages * feat(auth): separate participation, voting and administration Decouple proposal destinations from branch administration. Any verified member may submit to National, any state or territory, or any recognised local branch. Submission creates no membership, voting eligibility, or administrative authority; governance authority remains restricted. Replace the destination selector's administrative filtering with a canonical list of all recognised destinations. National and the eight states/territories stay primary; local branches are revealed behind a disclosure and the member's own branch is preselected. Align Member Management with the capability model: member directory, verification, and role changes use members.view, members.verify, and roles.manage. Canonical system role names are shared, delegated branch and custom roles are visible on each member, and anti-escalation blocks delegated managers from granting or altering national administrators. Document the target authorisation model and remaining migration work. * chore(changelog): record authorisation consolidation * test(ci): update member lifecycle browser check for unified notification center * feat(site): open notifications in a header popover The notification bell now shows recent updates in place, with unread count, mark all read, and a link to full notification settings. The bell stays visible on mobile instead of living inside the collapsible menu. * chore(changelog): refresh snapshot after notification popover * fix(security): allow national RBAC grants in branch search and preserve scope on read * feat(auth): support multiple roles and a grouped scope select Allow members to hold several platform system roles at once. Member Management now uses checkboxes for Member, Moderator, and National Administrator; roles are replaced as a set, effective permissions remain a union, and removing one role does not revoke another. Session and member DTOs expose the full role list while the legacy single role remains the highest-precedence value. Replace the nine-option destination radio group with a grouped, type-ahead Select built from the design-system primitive. National and the states/territories form the primary group; local branches are grouped separately. The control stays compact, keyboard accessible, and mobile friendly without exposing nine chips. * chore(changelog): record multi-role and grouped scope select
32edbcc↗
9 November 2026
1 commit- Record approved design reset and requirements audit
41b4682↗