You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Fix Chambers Total ACM double-count
- Avoid summing chamber ACM across overlapping governor memberships
- Update dto parser unit test to ensure no double-count
* Align chamber quorum UI with server threshold
- Remove misleading '+ 1' chamber quorum label from proposal chamber page
- UI now reflects pure percentage quorum participation
* fix(web): phase-76 stabilization for proposal stages, chamber UX consistency, and live-state reliability
- align proposal/chamber surfaces with corrected server stage semantics
- add/normalize passed-stage handling for non-formation proposals
- remove formation-stage UI expectations where proposal type does not use formation
- sync chamber vote tiles and labels with server-calculated quorum/passing outcomes
- improve proposal/chamber detail consistency under auto-advancing vote transitions
- preserve chamber submission UX for cross-chamber submission policy (submission open, voting scoped)
- stabilize formation/chamber page behavior for milestone-driven vote returns and finalization paths
- align feed/chamber/proposal rendering with updated DTO behavior from server
- ensure address/status presentation remains consistent with governor/tier fixes now emitted by API
- synchronize local and VM web runtime files to eliminate drift on production-visible surfaces
* prettier fixes
return"General chamber proposals require voting rights in any chamber.";
27
-
}
28
-
if(chamberId){
29
-
return`Only chamber members can submit to ${formatProposalType(chamberId)}.`;
30
-
}
24
+
typeofdetails.chamberId==="string"
25
+
? details.chamberId
26
+
: "this chamber";
27
+
return`Submission to ${formatProposalType(chamberId)} was blocked by outdated chamber-membership gating. Any eligible human node can submit to any chamber; refresh and retry.`;
0 commit comments