[thystra]

Summary

Add an explicit operator-facing policy for deciding whether broadly
addressable activities enter public relay fan-out.

Configuration

PUBLIC_ADDRESS_DISTRIBUTION_POLICY accepts:

• explicit_public_only

  • Public must appear in the primary to audience.
  • Public appearing only in cc is acknowledged and publisher-accounted,
    but is not distributed through public relay fan-out.

• public_and_unlisted

  • Public may appear in either to or cc.
  • Preserves the pre-3.0 routing behavior.

Fresh example configurations explicitly select explicit_public_only.

An omitted value falls back to public_and_unlisted for compatibility with
existing installations. Unknown values are fatal during configuration loading.

Explicitly relay-addressed relationship traffic remains independent of this
public-address policy.

Operator visibility

The effective policy is included in the startup configuration banner.

Validation

Prospective validation passed before applying the exact patch:

• focused configuration and policy tests
• focused API routing and publisher-accounting tests
• full serialized test suite
• full serialized race suite
• go vet
• full build
• exact prospective/applied patch comparison
• exact prospective/applied Git tree comparison
• post-application focused confirmation

Validated tree:

bf28ee74f646e5c18fa90f0f401a664636480c62

Validated patch SHA-256:

4eebb2d719aadbf1eae4b85d7d50597cb214e5c0e4a6b4a555cf7eba3d864e55