The protocol explorer for the Stellar network.

The explorer's entire application shell crashed on the home page — TypeError: Cannot read properties of undefined (reading 'toUpperCase'), surfaced as "Stellar Index hit an unexpected error" on every route.

An apply path for the r1 ansible config. deploy-binary.yml swaps binaries only, so the config-apply gate in deploy.yml was a forcing function with nowhere to force *to*: the full render needs the ansible vault, which lives in Actions secrets and nowhere a person can reach from a laptop. Config therefore lagged binaries and features shipped dead — exactly what that gate exists to prevent (the 2026-08-25 declared-peg and rules.d incidents). The same credentials that already prove drift every Monday can now correct it: ansible-drift.yml takes an apply input that drops --check.

The actions SHA-pinning lint matched `uses:` as a substring, so ordinary prose in a workflow tripped it: an error message reading "Usual causes: sshd not listening…" was parsed as a tag-pinned third-party action named sshd and hard-failed the PR that introduced it. The match is now anchored to a YAML key boundary (line start, whitespace, or list dash). Verified in both directions — a genuinely tag-pinned action is still caught, and prose containing "causes:" no longer fails. The capture index moved with the added group, which would otherwise have made the lint report the wrong token.