Listing what is unverified beats pretending to know. Each row states where it is stuck and what would close it.
| Pending item | Stuck on | How to close |
|---|---|---|
| Verbatim bad-model-ID errors per gateway | Needs an account on each | Someone with access runs it and pastes the text |
| Exact boundary of the Windows ACL partial backend | Needs an out-of-workspace write case | Write one deliberately and record the result |
| Request body field composition from capture | Needs a TLS-decryptable path | Point the base URL at your own proxy and record field names |
| Real blast radius of plugin install scripts | Requires auditing each plugin | Read the postinstall script and record what it does |
| UI behaviour when approval is unavailable | Needs a session with no answerer | Disconnect the session, trigger an approval, watch UI and logs |
What the four statuses mean
| Status | Means | How to use it |
|---|---|---|
| Verified | Measured here, raw records exist | Follow it directly |
| Compiled | Read from sources, cited per line | Use as a lead, not as a measurement |
| To be tested | We know how, not finished | Use the method, verify the conclusion |
| Expired | True then, maybe not now | Check the date; do not copy blindly |
Why this page exists
The fastest way for a site to lose trust is to present unchecked claims as checked. Exposing the open items tells readers which parts they can rely on and which need their own run.
Maintenance: when an item closes, update the page's status first, then delete the row here. Never let the list and the pages disagree.