mirror of
https://github.com/Xahau/xahaud.git
synced 2026-07-23 15:10:10 +00:00
9d125f4d19
`server_definitions` sourced each amendment's `enabled` straight from the
on-ledger Amendments object, so amendments force-activated via the
`[features]` config stanza (live in the Rules / tx processing, but never
voted on-ledger) were reported as not-enabled. That makes the output
misleading on any node that uses `[features]` (notably testnets).
Split per-amendment activation into its two real sources and make
`enabled` reflect what the server actually applies:
enabled = ledger_enabled || cfg_forced
ledger_enabled = recorded in the on-ledger Amendments object (canonical)
cfg_forced = forced via the [features] config stanza (node-local)
Additive JSON fields. Adds jss::ledger_enabled, jss::cfg_forced and a
ServerDefinitions test covering the config-forced case.