A test proves the Resilience page's rows: each protection in docs/THREATS.md appears once with its standing from the last full gate, and an unknown standing is said, not hidden #7526

Intent: the owner's one look at what protects the forge is honest. readResilience (src/checks/resilience.ts) feeds the Resilience page and the terminal, and no test imports it directly.

Done:

• [ ] A new test/checks-resilience.test.ts gives readResilience a temp data directory. With no gate yet, every protection named in docs/THREATS.md is listed once with an unknown standing, never dropped. After a recorded full gate with one protection green and one red, those two read so and the rest stay unknown. Every protection in the document appears, in its order.
• [ ] If any of these fail, fix src/checks/resilience.ts, and the pull says what was wrong.

Files: a new test, and src/checks/resilience.ts only if the test finds a fault.