wiki: add Public Statements & Disclosures area + Statement 001 (v0.5.56/57/58) New transparency space, structurally separate from release notes so a future security disclosure has a home that does not read as marketing. Public-Statements: index of dated statements, plus STANDING DISCLOSURES restated in one canonical place so their status is never inferred from silence — the coordination subsystem is CONTAINED NOT CLOSED, and we explicitly do not assert that no unauthorised access occurred, because our logs could not be correlated at the time. That is a limitation of our logging, not a finding of safety, and it is stated that way deliberately. Statement-001: combined technical record for the three releases. Reports the two defects live testing found AFTER v0.5.56 shipped, including the security-surface sibling we found ourselves that no reporter raised, and the live Cerebras catalogue defect our own currency check caught. Documents the 16-test parent differential for v0.5.57 and the all-stage fault injection for v0.5.58 — the case our internal review had NOT tested. Closes with the unplanned real provider failure that occurred during the v0.5.58 post-deploy smoke and was handled exactly as designed; it is the strongest evidence in the statement precisely because we did not plan it. Also names what is still open: model diversity (two of three seats were running the same model, which weakens the premise the design rests on), the counsel track, and no legal certification. Sidebar gains a Transparency section. Footer version corrected from v0.5.12 to v0.5.58 — it was 46 releases stale. Every factual claim verified before publishing: live /health reports 0.5.58 and 13/8/5, and all three release tags resolve to the exact commits cited. Forbidden-claim sweep clean. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01E2WLyXrgH8dSXqKJiXW5Cu