File the panel's falsified doc claims and String(thrown) sites
Mirror / push (push) Successful in 3s
Test / lint (pull_request) Successful in 19s
Test / test (18) (pull_request) Successful in 30s
Test / test (20) (pull_request) Successful in 29s
Test / test (22) (pull_request) Successful in 30s
Test / test (24) (pull_request) Successful in 30s
Test / test (26) (pull_request) Successful in 30s
Mirror / push (push) Successful in 3s
Test / lint (pull_request) Successful in 19s
Test / test (18) (pull_request) Successful in 30s
Test / test (20) (pull_request) Successful in 29s
Test / test (22) (pull_request) Successful in 30s
Test / test (24) (pull_request) Successful in 30s
Test / test (26) (pull_request) Successful in 30s
This commit is contained in:
@@ -378,6 +378,15 @@ and is also what the panel ranked hardest — two methods, one answer.
|
||||
is honest that the run was 2026-09-08. Nothing runs the peers on a schedule or before a tag, so
|
||||
the claim rots silently. Goals 1 and 9.
|
||||
|
||||
- [ ] **Correct the four doc claims the 2026-09-24 panel falsified.** `send-sms.ts:317` says this
|
||||
library's own server waits for every segment before answering, where it answers each on
|
||||
arrival; AGENTS.md counts nine goals where README lists ten; README's goals point at "the hard
|
||||
rules below" and "the defect table below", both of which live in AGENTS.md.
|
||||
|
||||
- [ ] **Route the three `new Error(String(thrown))` through `errorFrom()`.** `client.ts:100` and
|
||||
`reconnect-loop.ts:84,140` convert a thrown value with `String()`, which throws for an object
|
||||
whose `toString` throws — the case `errorFrom()` exists for, and hard rule 1.
|
||||
|
||||
## Worth doing, not blocking
|
||||
|
||||
- [ ] **Decide whether `alert_notification` reaches the application as more than `incomingPduObj`.**
|
||||
|
||||
Reference in New Issue
Block a user