Implement the complete mapping of all Context category error subcodes. Context errors relate to the execution environment itself — invalid protocol version, missing features, or host function calls made in the wrong context. Rare but confusing because they suggest something is wrong with the environment, not the contract logic.
Implementation Guidelines
- Create
crates/core/src/decode/mappings/context.rs
- Same structure:
ContextErrorDetail with code, name, summary, severity
- Map all known subcodes from
soroban-env-host (InvalidAction, InternalError)
Expectations
- What done looks like: Every Context subcode has a mapping. The descriptions clarify whether the issue is the contract or the environment.
Implement the complete mapping of all Context category error subcodes. Context errors relate to the execution environment itself — invalid protocol version, missing features, or host function calls made in the wrong context. Rare but confusing because they suggest something is wrong with the environment, not the contract logic.
Implementation Guidelines
crates/core/src/decode/mappings/context.rsContextErrorDetailwithcode,name,summary,severitysoroban-env-host(InvalidAction,InternalError)Expectations