[thystra]

Summary

• render the configured operator_name value for {{OPERATOR_NAME}} website content tokens
• HTML-escape the operator name before inserting it into generated pages
• reject generated pages that retain unresolved uppercase template tokens
• add regression coverage for the default About and Privacy pages
• add regression coverage for unknown tokens in operator content overrides

Background

The relay2 status-footer deployment performed a prospective static-site build before making runtime or frontend changes. That build correctly detected unresolved {{OPERATOR_NAME}} tokens in the generated About and Privacy pages.

The website configuration already required operator_name, but the builder did not include OPERATOR_NAME in its replacement map.

Validation

• Python compilation
• complete contrib/web unit-test suite
• real generated-site build
• no unresolved uppercase tokens in generated output
• About and Privacy pages render the configured operator name

Validated base

• complete contrib/web unit-test suite
• real generated-site build
• commit:

2eea622bde5d7f1627ca62867b3870f38a08f86c

Validated and applied tree:

e2929e04e4f3f262232893048f0c91fe0d9b2bab

Validated patch SHA-256:

9142588dbd32161fe78a2cfabeb666d10d49e22a8957bccd5151e3940595d09d

The change was prospectively validated before being applied to the feature branch.