Sloba 2026-05-06T16:55Z chat: "lets flip the switch i want the repo public".
Pre-launch security audit signed off:
- G2-P0-1 (/Users/slobodan/ paths) cleared end-to-end
- G2-P0-2 (10.8.0.x WG mesh IPs) cleared end-to-end
- G2-P0-3 (Slobodans-MacBook-Air mDNS) cleared end-to-end
- G2-P0-4 (MyBoard / TruthGraph names) cleared end-to-end
All four verified clean on the live https://benchmarks.weeyuga.com/
deploy at SHA 0ba4451 by Miljan's pen-test re-grep on
/index.html, /catalog.html, /benchmarks/09d8fbde.html (0 hits per
pattern per page). Full live security probe earlier the same day
also cleared: path traversal blocked, methods 405-locked, autoindex
OFF, hidden files (.git/.DS_Store/.env/.htaccess) all 404,
_template.html 404 via vhost SPA-fallback fix, all 6 security
headers + HSTS holding.
Updated:
- README banner: "PRIVATE STAGING — pre-launch audit pending" →
"PUBLIC — anonymous-readable since 2026-05-06"
- Status table: "Pre-launch security audit | scheduled" →
"cleared 2026-05-06 (G2 P0-1/2/3/4 all verified clean on live
benchmarks.weeyuga.com at SHA 0ba4451)"
- Status table: "Visibility flipped to public | pending audit
sign-off" → "2026-05-06 ✓"
This commit lands the README copy update inside the repo. The
Gitea-side visibility flip (Settings → Visibility → Make Public)
is a UI click Sloba does himself; no Gitea API token available
locally to drive it from this session.