feat(FR-3877): move the system announcement to the domain app config

[ironAiken2]

Resolves #9526 (FR-3877)

Summary

Top of the FR-1203 app-config stack (#9361 → #8860 → #9362 → this). The system announcement moves from the manager's legacy announcement endpoint (/manager/announcement, one markdown string in etcd, first line lifted out as the title) to the domain app config:

// domainConfig (DOMAIN scope, merged into `myAppConfigs(['domainConfig'])`)
{
  "announcement": {
    "enabled": true,
    "title": "Maintenance tonight",          // plain text, shown in every banner state
    "body": "Details in **markdown** …",     // optional, revealed on expand
    "updatedAt": "2026-09-08T05:12:00.000Z"  // keys per-session dismissal
  }
}

Hooks (react/src/hooks/useAppConfig.tsx)

• useUpdateDomainAppConfig() — the missing DOMAIN-scope setter next to useUpdatePublicDomainAppConfig / useUpdateMyUserAppConfig. (subKey, nextValue): takes the domain uuid from the client (useCurrentDomain().id, stored at login — see below), re-reads the raw DOMAIN-scope domainConfig fragment, replaces one sub-key (undefined removes it) through scopedUpsertAppConfigFragments, then refetches the merged myAppConfigs(['domainConfig']) view so every useDomainAppConfig reader updates — no window.location.reload(), no per-save domainV2 round-trip.
• Reads go through the existing useDomainAppConfig<T>(subKey) (first consumer).

Banner / editor

• AnnouncementBanner reads useDomainAppConfig<DomainAnnouncement>('announcement'). Title in every state; the body renders behind the expand toggle; a title past the 120-code-point cutoff collapses like before. Dismissal is keyed by updatedAt, so a re-published announcement resurfaces the banner.
• AnnouncementEditModal gains a Title field (a BAIFormItem inside Form, required + whitespace, so its error renders like every other form field and an untouched empty title stays error-free; Publish / Save as Draft run validateFields() first) and a Publish split button whose menu offers Save as Draft (enabled: false, which the legacy endpoint could not persist — it stored by presence only); a saved draft is marked by a Draft token in the modal title. Delete stands alone on the left and removes the sub-key. body is trimmed on save. The content suspends on the Relay read behind a skeleton-bodied modal fallback, so the Maintenance page opens it without a page-level Suspense.
• Deleted: announcementSummary.ts (first-line extraction, markdown-to-prose) and useSuspenseGetAnnouncement.tsx (TanStack). helper/announcement.ts keeps the title cutoff and the visibility / collapsibility predicates, with tests. service.get_announcement / update_announcement stay in backend.ai-client (library API) but have no caller in the app.
• i18n: summary.AnnouncementTitle, summary.AnnouncementTitleRequired (all 21 locales); summary.AnnouncementMessageRequired removed (no consumer).

Login reads myUserV2 (react/src/helper/loginSessionAuth.ts)

connectViaGQL used to chain keypair → user → group.list and only ever stored the domain name, so the DOMAIN-scope setter above had to resolve the uuid on every save. It now reads myUserV2 once — id, basicInfo, organization { domainName role }, domain { entityId basicInfo { name } }, projects(filter: { isActive: true }) — and stores the uuid as _config.domainId (new useCurrentDomain() hook returning { name, id }; LoginConfigState.domain_id). The read is a module-level Relay graphql tag used through fetchQuery(RelayEnvironment, …): RelayEnvironment's fetch resolves globalThis.backendaiclient at request time, which connectViaGQL installs first, so the response type is the generated loginSessionAuthMyUserQuery rather than a hand-written one.

• UserV2.projects caps an unpaginated read at the manager's default page size (10), so the login walks the pages with limit: 100 / offset, bounded by the connection's count (a single pagination mode; no cursor to stall on).
• V2 ids are Relay global ids; toLocalId decodes them for user_uuid and groupIds.
• Dropped what nothing read: the stored resource_policy and need_password_change, and the fetched-but-unstored username / is_active. groupIds now holds only the user's projects (the legacy map held every group in the domain); its sole reader, current_group_id(), only ever looks up the user's current project.
• useAppConfigDomainIdQuery is gone with its __generated__ artifact.

myUserV2 is 26.2.0+, below the 26.9.0 this PR already requires, so no gate.

No version fallback

myAppConfigs / scopedUpsertAppConfigFragments need manager 26.9.0+. This ships in the LTS that guarantees it (decision: FR-3877 discussion), so there is no legacy-endpoint fallback — on an older manager the banner query fails inside ErrorBoundaryWithNullFallback and the Maintenance page's Edit modal errors on load.

Verification

• bash scripts/verify.sh → all checks pass at commit time (Lint, Format, TypeScript ×2, Vite warmup, StyleX, Astryx theme build, Astryx integration, z-index, Agent mappings, Terminology). The Relay check flagged only the two new __generated__ artifacts as uncommitted before this commit; they are committed.

• vitest run src/helper/announcement.test.ts — 8 tests.

• vitest run src/helper/loginSessionAuth.test.ts — 11 tests on a createMockEnvironment() stand-in for RelayEnvironment (single read, offset walk bounded by count, role → is_admin/is_superadmin mapping, domain fallback, remembered project, unauthenticated logout, endpoint history); STokenLoginBoundary.test.tsx and useWebUIConfig.test.ts still pass.

• pnpm relay — useAppConfigDomainRawQuery, loginSessionAuthMyUserQuery generated; useAppConfigDomainIdQuery removed.

• Not yet verified against a live manager (the 10.82.0.x test network was unreachable from the authoring box). Assumptions to confirm on the first run: domainConfig is allow-listed at DOMAIN scope for the read (myAppConfigs); myUserV2.domain.entityId is the uuid AppConfigScopeRef.scopeId expects; and ProjectV2.id / UserV2.id come back as Relay global ids (base64("ProjectV2:<uuid>")), which is what the manager source declares (NodeID on PydanticNodeMixin). A dev server for this branch is up for that: https://fr-3877.localhost:1355.

• Review round (7d5d2c7ff): bash scripts/verify.sh → === ALL PASS ===; vitest run src/helper/loginSessionAuth.test.ts src/helper/announcement.test.ts → 2 files / 19 tests passed.

• Stack rebased onto main (f8d974dd3) and the title moved to the form engine (826d213b5): bash scripts/verify.sh → === ALL PASS ===.

Reviewer checklist

• 1. As superadmin, Maintenance → Edit Announcement: set a title and a markdown body, Publish. The banner appears at the top with the title and an expand toggle that reveals the body.
• 2. Dismiss the banner, then re-publish with any change → the banner comes back (dismissal is keyed by updatedAt).
• 3. Save as Draft (Publish menu) → banner gone, the modal reopens with a Draft token and the saved title/body.
• 4. Delete → banner gone, the modal opens empty with Delete disabled.
• 5. Sign in as a non-admin user of the same domain → the banner shows without the Edit button.
• 6. Sign in as a user who belongs to more than 10 active projects → the project selector lists all of them, and the remembered project survives a reload (login now pages myUserV2.projects).

🤖 Generated with Claude Code

https://claude.ai/code/session_01B13bqRK3V12jiCvia8fm2w

[github-actions]

Coverage Report for react-coverage (./react)

Status	Category	Percentage	Covered / Total
🔵	Lines	17.94%	6642 / 37006
🔵	Statements	15.18%	8198 / 53982
🔵	Functions	16.02%	1068 / 6664
🔵	Branches	10.98%	5614 / 51102

File Coverage

File	Stmts	Branches	Functions	Lines	Uncovered Lines
Changed Files
react/src/components/AnnouncementBanner.tsx	1.58%	0%	0%	2.77%	36-68
react/src/components/AnnouncementEditModal.tsx	66.44%	65.74%	18.51%	71.76%	77, 85, 86, 87, 91, 97, 98, 133-154, 159-168, 177-183, 204-247, 357-381, 387-404, 423, 426, 430, 431, 432, 437, 438, 441, 442, 445, 446, 449, 450, 453, 454, 458, 460, 467, 468, 471, 475, 476, 479, 483, 484, 488, 490, 493, 494, 497, 501, 502, 505, 509, 510, 513, 515, 527, 535, 536
react/src/helper/announcement.ts	100%	100%	100%	100%
react/src/helper/loginConfig.ts	38.77%	5.55%	25%	39.31%	25-46, 193-615, 624
react/src/helper/loginSessionAuth.ts	32.25%	28.78%	28.57%	33.05%	65-89, 204-398
react/src/hooks/index.tsx	65.74%	54.65%	52.72%	64.11%	65-68, 168, 169, 174-186, 197-198, 206-218, 225-235, 398-399, 404, 509-512, 527-530, 538-566, 574, 584-599, 616, 642-656, 664-693, 696-725
react/src/hooks/useAppConfig.ts	16.25%	20%	0%	21.66%	125-131, 140-142, 153-162, 170-179, 189-196, 237-244, 280-177

Generated in workflow #933 for commit 3654fa6 by the Vitest Coverage Report Action

[agatha197]

1. The title validation error has a block unlike form item. Let's remove the background. 2. Instead of enabled button, let's add a draft publish (replace better representation ;)) to the left of the publish button with primary outlined button. And leave delete button to the left only.

[agatha197]

Requesting changes for the two login-path issues below (loginSessionAuth.ts:119 and :124) — both are unverified assumptions sitting on the app's only entry path, and both are cheap to guard. The remaining comments are minor cleanups.

Everything else checks out: logic and Relay patterns follow the sibling hooks, i18n is in sync across all 21 locales, regenerated Relay artifacts show no drift, and the projects connection uses a single pagination mode (first+after).

[ironAiken2]

Addressed the review-body feedback from @agatha197 in 7d5d2c7ff:

1. The title validation message now uses TextInput's detached status placement, so it reads like the form items (no bordered block), and it appears only after the title has been edited.
2. The Enabled checkbox is gone. Publish is a split button (same shape as the session launcher's Launch) whose menu offers Save as Draft — same document, enabled: false — and Delete stands alone on the left. A saved draft is marked with a Draft token in the modal title.

[ironAiken2]

Dev server on box sungchul: http://fr-3877-pr9527-move-system-announcement.sungchul.10-82-0-159.sslip.io

[agatha197]

Could you change “quote” into something easier to understand? At the moment, the color is so faint that it is hard to distinguish.

Collapsed version - centered

Expanded version - move to the top

Please change it so that it always come to the center.

[ironAiken2]

Addressed the review from @agatha197 in ccdfd431f:

1. Quote legibility — a blockquote inside the announcement body now draws its rule in the band's info colour and its text in the primary text colour (.webui-announcement-body .astryx-blockquote, applied to both the banner and the editor preview), so it no longer sinks into the info tint.
2. Centering — Banner only centres its icon and actions while it has no description, which is why they jumped to the top once expanded; the banner header now keeps align-items: center in both states.

Measured on the dev server: icon and Edit sit at the header's vertical centre collapsed and expanded (offset ≤ 0.01px); the quote rule is rgb(2, 141, 242) with primary text.

Collapsed	Expanded

[agatha197]

Dev server on box sujin: http://fr-3877-pr9527-move-system-announcement.sujin.10-82-0-159.sslip.io