fix(mcms): improve error messages when proposal ctx is not correctly provided [OPT-325] #661
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.




This pull request introduces improved error handling and validation for the proposal analysis context and EVM registry initialization across the MCMSv2 CLI and EVM analyzer. These changes help prevent misconfiguration and provide clearer guidance to developers when required dependencies are missing.
Validation and error messaging improvements:
buildMCMSv2AnalyzeProposalCmdto ensureproposalCtxProvideris not nil, returning a descriptive error if missing.newCfgv2to verify that the proposal context returned by the provider is not nil, with a clear error message for initialization issues.EVM registry initialization guidance:
AnalyzeEVMTransactionto instruct developers to provide an EVM registry via theProposalContextProviderwith theWithEVMABIMappings()option if it is missing.