docs: project docs, scripts, deployment configs, and evidence

This commit is contained in:
2026-04-02 11:22:17 +08:00
parent 4718980ab5
commit bbeeb63dfa
396 changed files with 165018 additions and 0 deletions

View File

@@ -0,0 +1,70 @@
# 2026-03-28 Q-004 Coverage Remediation Pass 13
## Scope
- Continue strict `Q-004` closure work after Pass 12.
- Fully close the remaining deep-branch hotspot in `frontend/admin/src/pages/admin/ProfileSecurityPage/ProfileSecurityPage.tsx` before selecting the next gap.
- Re-verify closure through targeted page tests plus full frontend validation.
## Changes
### Frontend
- Extended page coverage in:
- `frontend/admin/src/pages/admin/ProfileSecurityPage/ProfileSecurityPage.behavior.test.tsx`
- Newly covered behavior includes:
- initial security-data load failure handling
- OAuth callback success and error handling
- password-update submission
- bound social-account unbind flow and post-action refresh
- no-user guard behavior for protected actions
- existing TOTP, avatar, and device behavior remained green under the rewritten page-level tests
### Backend
- No backend code changes were required in this pass.
## Verified Commands
```powershell
cd D:\project\frontend\admin
npm.cmd run test:run -- src/pages/admin/ProfileSecurityPage
npm.cmd run lint
npm.cmd run build
npm.cmd run test:coverage
```
## Results
### Frontend coverage
- Overall:
- statements `85.89%`
- branches `74.91%`
- functions `81.87%`
- lines `86.71%`
- Target areas:
- `src/pages/admin/ProfileSecurityPage/ProfileSecurityPage.tsx`: statements `90.35%`, branches `75.51%`, functions `92.45%`, lines `90.13%`
- `src/lib/http/client.ts`: statements `100%`, branches `92.30%`, functions `100%`, lines `100%`
- `src/lib/http/csrf.ts`: statements `100%`, branches `88.46%`, functions `100%`, lines `100%`
## Validation Notes
- Frontend full coverage now completes with `42` passing test files and `199` passing tests.
- The required sequential frontend validation path passed:
- `test:run -- src/pages/admin/ProfileSecurityPage`
- `lint`
- `build`
- `test:coverage`
- The successful frontend coverage run still emits one post-summary jsdom `AggregateError` network-noise line.
- It does not fail the command.
- It remains a real validation-hygiene issue and should continue to be tracked honestly.
## Real Conclusion
- `src/pages/admin/ProfileSecurityPage/ProfileSecurityPage.tsx` is no longer an open `Q-004` gap.
- `Q-004` still cannot be honestly declared closed.
- With `client.ts` and `ProfileSecurityPage` closed, the next highest-value frontend gaps shift to:
- auth recovery pages that still have `0%` coverage, especially `src/pages/auth/ForgotPasswordPage/ForgotPasswordPage.tsx`
- `src/pages/auth/ResetPasswordPage/ResetPasswordPage.tsx`
- the post-summary jsdom `AggregateError` coverage-noise hygiene issue