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,72 @@
# 2026-03-28 Q-004 Coverage Remediation Pass 9
## Scope
- Continue strict `Q-004` closure work after Pass 8.
- Fully close the remaining `LoginPage` frontend page cluster before moving to the next task.
- Re-verify closure through targeted tests plus full frontend validation.
## Changes
### Frontend
- Expanded login-page behavior coverage in:
- `frontend/admin/src/pages/auth/LoginPage/LoginPage.test.tsx`
- Newly covered behavior includes:
- fallback to default auth capabilities when capability loading fails
- password login success and failure
- safe redirect usage from router state and sanitized fallback from unsafe redirect queries
- email-code send success and validation-error swallow path
- email-code login success and failure
- sms-code send success and failure
- sms-code login success and failure
- OAuth provider rendering, disabled-provider filtering, startup success, and startup failure
### 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/auth/LoginPage/LoginPage.test.tsx
npm.cmd run lint
npm.cmd run build
npm.cmd run test:coverage
```
## Results
### Frontend coverage
- Overall:
- statements `78.38%`
- branches `64.77%`
- functions `76.92%`
- lines `79.19%`
- Target areas:
- `src/pages/auth/LoginPage/LoginPage.tsx`: statements `92.56%`, branches `84.09%`, functions `86.2%`, lines `95.61%`
- `src/pages/auth/RegisterPage/RegisterPage.tsx`: statements `77.63%`, branches `60.65%`
- `src/pages/admin/ProfileSecurityPage/ProfileSecurityPage.tsx`: statements `70.17%`, branches `48.97%`
- `src/lib/http/client.ts`: statements `52.17%`, branches `43.26%`
- `src/lib/http/csrf.ts`: statements `25.71%`, branches `19.23%`
## Validation Notes
- Frontend full coverage now completes with `41` passing test files and `155` passing tests.
- 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.
- One attempt to run `npm.cmd run lint` and `npm.cmd run build` concurrently produced a transient Windows/Vite `index.html` emit-path failure.
- The required standalone `npm.cmd run build` rerun passed immediately afterward.
- This pass does not have enough evidence to classify that transient as a deterministic project defect.
## Real Conclusion
- `LoginPage` is no longer an open `Q-004` gap.
- `Q-004` still cannot be honestly declared closed.
- The remaining highest-value frontend gaps are now more concentrated in:
- `RegisterPage`
- deeper remaining `ProfileSecurityPage` branches
- `lib/http`