✔ REQ-LIMIT-3 schema: each subject kind, limit 0 and no ceiling are accepted; bad limits, times, keys and undeclared instances refuse (12.739299ms)
✔ REQ-LIMIT-3 the writer stamps since: a new limit gets now, a changed one keeps its time, a different time is refused (233.858718ms)
✔ REQ-LIMIT-3 only tokens.* at schema depth holds token limits: agent limits named `limit` save as sent, and a token limit named `limit` is stamped and reset (274.692946ms)
✔ REQ-LIMIT-3 a reset moves since to now, is logged with its actor, and refuses a path that is not a limit (129.01269ms)
✔ REQ-LIMIT-2 schema: launch.account names a credential set; a daily quota needs a reset and an IANA zone and names the account (24.597721ms)
✔ REQ-LIMIT-2 the writer stamps a daily quota's since, keeps its reset and zone, and a reset moves since (146.514468ms)
✔ P5 per-model-key quotas are unset by default, accept digit-leading IDs and only the human changes or resets them (202.85529ms)
✔ P5 queue read uses actual bounded fixed management GET and immediately drops client and upstream values (14.363195ms)
✔ P5 bad envelope refuses safely with no retry (3.275949ms)
✔ P5 over count refuses safely with no retry (1.650709ms)
✔ P5 missing key refuses safely with no retry (1.355454ms)
✔ P5 bad counts refuses safely with no retry (2.028358ms)
✔ P5 redirect refuses safely with no retry (1.385706ms)
✔ P5 refusal refuses safely with no retry (1.027413ms)
✔ REQ-LIMIT-2 daily-quota exports interface version 2 with mayLaunch, mustStop and report (4.002643ms)
✔ REQ-LIMIT-2 the count sums every kind of the account's known records since the later of the day start and since (11.703557ms)
✔ REQ-LIMIT-2 a launch with no account (pi) is covered by no daily quota (0.285389ms)
✔ REQ-LIMIT-4 an unknown turn adds nothing and is counted apart (0.427944ms)
✔ REQ-LIMIT-2 the day turns at the reset in its zone, not in UTC, and before it the day is yesterday's (0.664291ms)
✔ REQ-LIMIT-2 the spring DST change makes the day after a 00:00 reset 23 hours long (0.359593ms)
✔ REQ-LIMIT-2 the fall DST change makes the day after a 00:00 reset 25 hours long (0.292084ms)
✔ REQ-LIMIT-2 a reset the clocks skip starts the day at the first instant after the gap (1.428363ms)
✔ REQ-LIMIT-2 a reset the clocks repeat starts one day, at the first one (0.427054ms)
✔ REQ-LIMIT-2 a launch is refused at the quota, a turn that reaches it stops, and the next day allows again (1.066274ms)
✔ REQ-LIMIT-2 counts past the safe integer range come back as digit strings (0.329306ms)
✔ REQ-LIMIT-4 bad leaves, records or times throw a code, and the check reads nothing but its arguments (2.160938ms)
✔ REQ-LIMIT-2 no daily quotas: every launch is allowed and the report is empty (0.172297ms)
✔ P5 daily quota for a model key ID matches stack key records and resets the next day (0.746089ms)
✔ REQ-LIMIT-3 token-limit exports interface version 2 with mayLaunch, mustStop and report (1.156529ms)
✔ REQ-LIMIT-3 each subject kind refuses at its limit and allows under it (1.303907ms)
✔ REQ-LIMIT-3 a limit covers only its own subject's records and launches (0.353216ms)
✔ REQ-LIMIT-4 only known records count; an unknown turn adds nothing and is counted apart (0.2777ms)
✔ REQ-LIMIT-3 a reset moves since: records before it no longer count (0.150391ms)
✔ REQ-LIMIT-3 limit 0 refuses with no records; the first limit hit in file order is named (0.1377ms)
✔ REQ-LIMIT-3 a key limit is not enforced while every record's account is null (decision 150 Q1) (0.170332ms)
✔ REQ-LIMIT-3 counts past the safe integer range come back as digit strings (0.135122ms)
✔ REQ-LIMIT-4 bad records or times throw a code, and the check reads nothing but its arguments (0.635473ms)
✔ REQ-LIMIT-3 no token limits: every launch is allowed and the report is empty (0.62587ms)
✔ REQ-LIMIT-3 token-limit ignores tokens.daily, which the daily-quota check enforces (row 126) (0.130727ms)
✔ P5 a model key ID limit counts stack records by key ID without an account (0.11813ms)
ℹ tests 40
ℹ suites 0
ℹ pass 40
ℹ fail 0
ℹ cancelled 0
ℹ skipped 0
ℹ todo 0
ℹ duration_ms 1270.553008
