james/vmall
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(openspec): propose 8 tigshop migration changes (P0-P7) + migration plan

Browse Source
This commit is contained in:
Chengdong Zhang
2026-09-23 13:30:36 +08:00
parent 0d0e10b97b
commit 9a749e2551
47 changed files with 1607 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
openspec/changes/add-membership-messaging/specs/frontend-admin/spec.md
+20
View File
@@ -0,0 +1,20 @@
## ADDED Requirements
### Requirement: Member level management
Platform admins SHALL manage member levels from a dedicated admin console page through the shared API contract: levels listed in growth-threshold order, and create, edit, and delete actions over name, icon, growth threshold, and benefits with both locales editable. Deleting a level in use SHALL surface the API rejection instead of silently succeeding, and member-level management SHALL be reachable from the authenticated console navigation beside existing platform operations.
#### Scenario: manage a member level
- **WHEN** a platform admin creates a level with bilingual name and benefits, an icon, and a growth threshold
- **THEN** it appears in threshold order and is available for automatic leveling
#### Scenario: edit a growth threshold
- **WHEN** a platform admin changes a level's growth threshold to a unique value
- **THEN** the level persists with the new threshold and the bilingual content unchanged
#### Scenario: deleting a level in use fails visibly
- **WHEN** a platform admin deletes a level that customers hold
- **THEN** the console surfaces the rejection and the level and its members remain unchanged
#### Scenario: level management appears in admin navigation
- **WHEN** an authenticated platform admin opens the admin console
- **THEN** member-level management is reachable from the console nav