fix(scale): page mail and batch roles
This commit is contained in:
@@ -191,6 +191,18 @@ Status: `IN PROGRESS`. Canonical hub routing, provider-neutral reads, explicit-c
|
||||
- Preserve minimal audit metadata without sensitive body logging. Free non-AI access is verified; future AI assistance remains a Pro/privacy-gated addition, not a prerequisite for basic email.
|
||||
- Complete remaining link/unlink/dismiss/draft/send/failure/two-user browser/production provider gates. Shared application-context behavior is now covered locally. No real email may be sent during repository verification.
|
||||
|
||||
## Implemented complete inbox pagination
|
||||
|
||||
- The current Job email UI uses an additive `/api/correspondence/page` contract with bounded page
|
||||
sizes, total/page metadata and deterministic date/ID ordering. The original endpoint remains for
|
||||
compatibility rather than changing an existing client contract in place.
|
||||
- A 205-message tenant fixture proves the third page returns the final five owned messages and
|
||||
excludes another tenant. The UI exposes accessible page navigation, resets to page one when a
|
||||
filter changes and reports the complete filtered total rather than the current page count.
|
||||
- Focused backend/admin tests pass 9/9, correspondence UI 15/15, full backend 683/683, full frontend
|
||||
58 suites/239 tests and the optimized production build passes. Provider and production mailbox
|
||||
performance remain unmeasured; no provider or email was contacted.
|
||||
|
||||
## Validation limitation
|
||||
|
||||
The first focused Jest invocation exhibited the repository's open-handle delay. The passing focused and full runs used `--forceExit`; the full run took 228.709 seconds. A Next build process also failed to exit after compilation; only the exact PIDs started by those build attempts were stopped, then a clean build completed. This is recorded as tooling/runtime behavior, not hidden.
|
||||
|
||||
Reference in New Issue
Block a user