The architecture docs publish the internal network map to GitHub Pages

Nobody has claimed this yet.

`deploy-architecture.yml` publishes `chakra-docker/architecture/*.html` and `ARCHITECTURE.md` to GitHub Pages. Those contain both internal server IPs, the SSH key path (`/home/root1/.ssh/website-key`), the s3fs credential-file location, and the full internal port map.

Not a credential leak, but it hands an attacker the entire target map for free — and the documents are genuinely good, which is why they are worth protecting rather than degrading.

**Fix:** make the Pages site private, or redact IPs and filesystem paths from the published copy while keeping them in the repo.

---

**Evidence**

```
chakra-docker/.github/workflows/deploy-architecture.yml; architecture/*.html
```

- Verified against: `origin/master 44ca47e (2026-07-25)`
- Verdict: **CONFIRMED**

Start with chakra-docker/.github/workflows/deploy-architecture.yml and inspect how architecture/*.html and ARCHITECTURE.md are selected for GitHub Pages. Review the published copies for the listed IPs, filesystem paths, credentials location, and port map. Done means the Pages output is private or those sensitive details are redacted while repository copies remain intact.

Written by the indexing model from the issue text.