The file sweep found the OCI registry and the PyPI index. Sweeping ops-warden's routing catalog found what files could not: gitea.coulomb.social also serves an npm registry at /api/packages/coulomb/npm/, and the catalog lane whynot-design-npm-publish (risk: high, production-exercised) vends the token that publishes @whynot/design to it. After 2026-08-31 that lane routes to a registry that does not exist, and it does not fail safe — an operator following it gets a working token for a dead endpoint and debugs the token. CI runners remain unswept; railiance-forge/tools/gitea-runner-status.sh suggests gitea-registered Actions runners exist. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| SHR-WP-0001-foundation.md | ||
| SHR-WP-0002-predecessor-and-deployment-reality.md | ||