3 Commits

Include renames

Author	SHA1	Message	Date
iamdoubz	8c750c67ca	auth: two-step sign-in (TOTP) for admins, with recovery codes ... auth/totp.ts per 08 §2.4: RFC 6238 (HMAC-SHA1, 30 s, 6 digits, ±1 step) with node:crypto only, checked against the RFC's test vectors. Migration 0003: users.totp_recovery_hashes and totp_last_step. Admins turn it on from My account (the header's "Account"): scan the QR or type the key, confirm a code, get 10 recovery codes once. Login asks for the code only after the password is right (401 totp_required, no session); a wrong code is a failed login (rate limit, audit). A step signs in once (totp_last_step updated atomically) and a recovery code once (array_remove guarded by any()). Off and new codes need the password; another admin can turn it off for a lost phone, which signs that user out. Users list shows it (twoStep). Also, found by the full e2e chain on one shared database: - Linphone tokens: only the exact token issued is accepted. The last base64 character can carry ignored bits, so another spelling decoded to the same signed token. - Test scripts no longer assume a fresh system: m3-t3 picks Dan in the test box, m8-check dials whatever slot the park took (findslot = next), m10-t4 uses the admin's existing extension, m11-t1 clears the public IP on its own first (local nets are in the transports while one is set, and transports change only on a restart). e2e m11-t1-totp; the full chain M1-M11 (33 scripts) passes. Task: M11-T1	2026-10-19 15:41:53 -05:00
iamdoubz	4742ed52ea	queues: service level counts callers who weren't answered ... withinSlaPercent was "answered within sla_seconds / answered", so a queue where a caller timed out still showed 100%. It is now the usual service level: answered within sla_seconds out of every caller the queue is done with, leaving out those who hung up before sla_seconds (nobody could have answered them in time). Timed out and turned away count as missed; callers still waiting aren't counted. Written into 04; the page label says "Callers answered within N s". Real calls: m8-t1 now shows 50% (1 answered in time, 1 timed out, the early hang-up left out) and the milestone check 67% (2 of 3), and asserts it. The check moves to queue 552 (*45552) so it doesn't clash with m8-t1's 550 on a shared database. Task: M8-T1	2026-10-19 12:13:39 -05:00
iamdoubz	088372bff8	e2e: M8 milestone check ... scripts/e2e/m8-check.mjs, the scenario from 09 M8 with real calls from a DID: queue 550 with agents 340 and 341, max wait 30 s, then 342. 340 pauses with *45550 and 341 is paused by an admin, so three callers wait. 341 comes back and gets the longest waiting caller, parks them on 701 (blind transfer to 700) and 343 picks up by dialing 701; 341 takes the next caller and the last one rings 342 after 30 s. Stats: 3 offered, 2 answered, 1 timed out. Roadmap marks the M8 milestone check done; the e2e README describes m8-t4, m8-t5 and m8-check. Task: M8-check	2026-10-19 11:26:54 -05:00