Is your feature request related to a problem? Please describe.
There's currently no configuration surface for Web of Trust (WoT) in the settings schema. Without it, we can't build any WoT-based features in a way that's toggleable or configurable by relay operators.
Describe the solution you'd like
- Add a WotSettings interface to src/@types/settings.ts defining the shape of WoT configuration (enabled flag, depth, trust anchors, etc.).
- Add a wot: block to resources/default-settings.yaml with sensible defaults and disabled by default.
- Add unit tests in test/unit/utils/settings.spec.ts to verify defaults merge correctly with user-provided overrides.
Describe alternatives you've considered
- Hardcoding WoT values and adding config later — rejected because it creates tech debt and makes the follow-up logic PRs messier.
- Using environment variables instead of the settings file — rejected for consistency with how every other feature is configured.
Additional context
This is a config-only PR with no runtime logic. It lays the groundwork for subsequent PRs that will implement WoT graph construction, scoring, and event filtering.
Is your feature request related to a problem? Please describe.
There's currently no configuration surface for Web of Trust (WoT) in the settings schema. Without it, we can't build any WoT-based features in a way that's toggleable or configurable by relay operators.
Describe the solution you'd like
Describe alternatives you've considered
Additional context
This is a config-only PR with no runtime logic. It lays the groundwork for subsequent PRs that will implement WoT graph construction, scoring, and event filtering.