feat: first login flow

[shortlight5980]

1. 增加了进入首页的弹窗编排器，弹窗按顺序弹出
2. 当加入团队时必须设置成员名
3. 通知接收 -> 联系方式，并修改弹窗样式
4. 当处于同步模式时，后台禁止新增用户

[github-actions]

Coverage Report

Status	Category	Percentage	Covered / Total
🔵	Lines	41.5%	4393 / 10583
🔵	Statements	41.36%	4653 / 11250
🔵	Functions	34.9%	871 / 2495
🔵	Branches	34.9%	2249 / 6444

File Coverage

No changed files found.

Generated in workflow #3357 for commit 93a7f51 by the Vitest Coverage Report Action

[github-actions]

✅ Admin Preview Image Ready!

ghcr.io/labring/fastgpt-pr:admin_93a7f51cbdeb7f64bfd9009861d673fa00f1586e

🕒 Time: 2026-09-14 16:36:30 (UTC+8)

[github-actions]

✅ Build and publish successful - Preview fastgpt Image:

ghcr.io/labring/fastgpt-pr:fastgpt_93a7f51cbdeb7f64bfd9009861d673fa00f1586e

🕒 Time: 2026-09-14 16:36:01 (UTC+8)

[FinleyGe]

[P1] Preserve the legacy invitation acceptance API

This change removes POST /proApi/support/user/team/invitationLink/accept and replaces it with acceptWithMemberName (see packages/global/openapi/support/user/team/invitationLink/index.ts:17 and the Pro submodule change). Existing clients and SDKs that still send the legacy { linkId } request will receive a 404 after upgrading. The new OpenAPI test at packages/global/test/openapi/support/user/api.test.ts:89 also explicitly asserts that the legacy route is absent.

Please keep the old route and contract as a compatibility adapter while retaining the new endpoint. The adapter should preserve the legacy request/empty-response behavior and username-based member name semantics, without applying the new interactive 20-character member-name validation.

[shortlight5980]

[P1] Preserve the legacy invitation acceptance API

This change removes POST /proApi/support/user/team/invitationLink/accept and replaces it with acceptWithMemberName (see packages/global/openapi/support/user/team/invitationLink/index.ts:17 and the Pro submodule change). Existing clients and SDKs that still send the legacy { linkId } request will receive a 404 after upgrading. The new OpenAPI test at packages/global/test/openapi/support/user/api.test.ts:89 also explicitly asserts that the legacy route is absent.

Please keep the old route and contract as a compatibility adapter while retaining the new endpoint. The adapter should preserve the legacy request/empty-response behavior and username-based member name semantics, without applying the new interactive 20-character member-name validation.

无需解决

[FinleyGe]

[P1] Make the team capacity check atomic

checkTeamMemberLimit(invitation.teamId, 1) at pro/admin/src/service/support/user/team/invitationLink/controller.ts:44 runs before mongoSessionRun, while the findOneAndUpdate that creates or activates the member runs inside the transaction. Two concurrent accepts for different invitations can both observe the same free slot and then both insert, exceeding maxTeamMember. Please reserve capacity atomically or serialize invitation acceptance per team, and re-check under the same concurrency control.

[FinleyGe]

[P2] Avoid the post-commit invitation lookup for audit data

After acceptInvitationWithMemberName succeeds and its transaction commits, the handler performs a second MongoInvitationLink.findOne at pro/admin/src/pages/api/support/user/team/invitationLink/acceptWithMemberName.ts:33 solely to read description. A transient read failure then returns 500 even though the member was already added, causing clients to retry a successful join and producing misleading failure behavior. Please return the audit description from the controller result, or capture it before commit, so the successful mutation does not depend on an extra post-commit database read.

[shortlight5980]

[P1] Make the team capacity check atomic

checkTeamMemberLimit(invitation.teamId, 1) at pro/admin/src/service/support/user/team/invitationLink/controller.ts:44 runs before mongoSessionRun, while the findOneAndUpdate that creates or activates the member runs inside the transaction. Two concurrent accepts for different invitations can both observe the same free slot and then both insert, exceeding maxTeamMember. Please reserve capacity atomically or serialize invitation acceptance per team, and re-check under the same concurrency control.

resolved

[shortlight5980]

[P2] Avoid the post-commit invitation lookup for audit data

After acceptInvitationWithMemberName succeeds and its transaction commits, the handler performs a second MongoInvitationLink.findOne at pro/admin/src/pages/api/support/user/team/invitationLink/acceptWithMemberName.ts:33 solely to read description. A transient read failure then returns 500 even though the member was already added, causing clients to retry a successful join and producing misleading failure behavior. Please return the audit description from the controller result, or capture it before commit, so the successful mutation does not depend on an extra post-commit database read.

resolved

[FinleyGe]

Avaliable for testing.

[c121914yu]

当处于同步模式时，后台禁止新增用户：这个是不是有问题，应该是能增加，但是同步时候不影响这些手动的用户？