## 1. Integration preparation

- [x] 1.1 Confirm `origin/master` base `27c7b6d` and source commits `1cd0087`, `9d5953f`, `3f7c655`, `52071f0`, and `7a452f3`.
- [x] 1.2 Confirm that the database has no production data, no release is scheduled, and the first administrator will be inserted directly into the database before release.
- [x] 1.3 Create an isolated branch from current `master` without changing source branches or the user's dirty worktree.
- [x] 1.4 Exclude historical source-branch OpenSpec records; retain only this integration plan.

## 2. Runtime integration

- [x] 2.1 Apply `1cd0087`, `9d5953f`, `3f7c655`, and `7a452f3` in dependency order.
- [x] 2.2 Omit `52071f0` because it changes only historical documentation excluded by task 1.4.
- [x] 2.3 Confirm no code conflicts occurred with current device, phone, or WeCom changes.
- [x] 2.4 Retain the required beginner comments for new or modified backend and frontend methods/callbacks.

## 3. Verification

- [x] 3.1 Run the backend test suite.
- [x] 3.2 Run the frontend production build.
- [x] 3.3 Run the dedicated login and refresh browser tests.
- [x] 3.4 Run the complete frontend browser regression suite for device, phone, WeCom, and legacy pages.
- [x] 3.5 Review the final staged diff for accidental source documents, secrets, generated files, and omitted runtime files.

## 4. Deferred release actions

- [ ] 4.1 Verify the first inserted administrator's password hash, role, and page permissions against the backend implementation.
- [ ] 4.2 Obtain explicit approval before pushing this branch, creating an MR, merging to `master`, deploying, or running the database migration.
