leave_organization confirm names neither the organisation nor what is lost: confirmText has no declared record scope for interpolation, and a host cannot override the platform bundle #24021

Activity

1. objectstack-fleet

   added

   enhancementNew feature or requestNew feature or request

   priority:p3

   area:i18nThe customer's own language, across UI, metadata and notificationsThe customer's own language, across UI, metadata and notifications

   needs-triage

   on Oct 16, 2026
2. objectstack-fleet commented on Oct 16, 2026

   

   objectstack-fleetBot

   on Oct 16, 2026

   ContributorAuthor

   More actions

   Triage: pm:on-hold on decision #24034 · a framework widening, held for the maintainer to name · triage seat · session_01AavokzJ5DndAwitDXvKy4U · 2026-10-16T19:58Z

   Triage seat (objectstack-wide, seat post #6015). ⛔ Not a claim, ⛔ not a dispatch.

   • This card is one of four widenings cloud#2910 asks of the framework (platform-objects: sys_organization declares no invite action, so an organisation record page cannot offer 邀请成员 in its header (page:header ids resolve only against the object's own actions) #24016, spec: ActionSchema declares disabled but no authored reason, so a header action cannot say why it is unavailable (e.g. "You are the only owner; transfer ownership first") #24018, leave_organization: no predicate root carries "the caller is this organisation's only owner", so the platform action cannot be disabled for the last owner before the click (better-auth refuses it only after the confirm) #24020, leave_organization confirm names neither the organisation nor what is lost: confirmText has no declared record scope for interpolation, and a host cannot override the platform bundle #24021). Under this seat's standing rule, a feature widening is held for the maintainer to name. They are put to the maintainer together as [Decision] cloud#2910 (the organisation page): which of four framework widenings to build — an invite action on sys_organization, an action disabled-reason key, an "only owner" predicate root, a record-scoped leave confirm? #24034, with options and workload.
   • Restart-when: the maintainer's ruling on [Decision] cloud#2910 (the organisation page): which of four framework widenings to build — an invite action on sys_organization, an action disabled-reason key, an "only owner" predicate root, a record-scoped leave confirm? #24034 names this card. The lane and grade are set then; the filer's priority:* stays until the ruling.
3. objectstack-fleet

   added

   pm:on-holdDecision made, deliberately deferred — no dispatch, no nag; restart condition in the hold commentDecision made, deliberately deferred — no dispatch, no nag; restart condition in the hold comment

   and removed

   needs-triage

   on Oct 16, 2026
4. objectstack-fleet commented on Oct 17, 2026

   

   objectstack-fleetBot

   on Oct 17, 2026

   ContributorAuthor

   More actions

   Closed not_planned · by ruling B′ on #24034 (record 6228318638, batch #358 item 3, the maintainer's 「24034 同意」) · director seat (summon #43 continuation 3, session_01QJC7i981TSs9L1CGJK59Ax) · 2026-10-17T02:14Z

   The copy half (what is lost: the organisation's environments and members) rides #24016's PR, in both bundles. The record-scope key for confirmText (naming the organisation) is not added before GA; re-file when a second consumer needs it.
5. objectstack-fleet

   removed

   pm:on-holdDecision made, deliberately deferred — no dispatch, no nag; restart condition in the hold commentDecision made, deliberately deferred — no dispatch, no nag; restart condition in the hold comment

   on Oct 17, 2026
6. objectstack-fleet

   closed this as not plannedon Oct 17, 2026