The paused event is described in apexchainx_calculator/src/lib.rs and event_schema.rs as having a (true,) payload, while the on-chain PauseInfo struct contains reason, paused_at, and paused_by. The discrepancy makes it unclear whether the reason string is part of the emitted event payload (good for forensics) or only available via get_pause_info(). Align the documentation in both files — explicitly state whether the paused payload is (true,) only (the contract-level signal that mutating operations are now rejected), or whether the full PauseInfo struct is serialised into the event payload alongside (true,). Update event_schema.rs to match the truth and add a test asserting that the event payload matches the doc-comment claim.
The
pausedevent is described inapexchainx_calculator/src/lib.rsandevent_schema.rsas having a(true,)payload, while the on-chainPauseInfostruct containsreason,paused_at, andpaused_by. The discrepancy makes it unclear whether the reason string is part of the emitted event payload (good for forensics) or only available viaget_pause_info(). Align the documentation in both files — explicitly state whether thepausedpayload is(true,)only (the contract-level signal that mutating operations are now rejected), or whether the fullPauseInfostruct is serialised into the event payload alongside(true,). Updateevent_schema.rsto match the truth and add a test asserting that the event payload matches the doc-comment claim.