fix!: distinguish view function RPC errors

[r-near]

Closes #270

Summary

• add RpcError::MethodNotFound for missing contract methods
• surface view-method panics as the existing RpcError::ContractPanic
• keep non-panic VM failures under RpcError::ContractExecution
• preserve block_height and block_hash on applicable view RPC errors
• expose RpcError::block_height() and RpcError::block_hash() accessors
• parse both current info.vm_error and legacy info.error RPC payloads
• use lowercase error messages and format methods as contract::method
• remove the unused RpcError::FunctionCall variant and RpcError::function_call constructor
• tighten the integration assertions for unknown accounts, accounts without code, missing methods, and contract panics

Why

NEP-641 falls back to NEP-413 only when w_resolve_auth is unavailable. A missing method (or no contract code) therefore needs to be distinguishable from a method that exists but panics; treating both as one generic execution error makes a safe fallback decision impossible.

The RPC also returns the block hash and height for these failures. Preserving that context lets resolvers associate failure and fallback decisions with the exact queried state.

The removed FunctionCall API had no client construction path and overlapped with the typed errors above. Transaction function-call failures remain available as types::FunctionCallError in transaction outcomes.

Compatibility

This is a breaking pre-1.0 API change and should ship in 0.15.0. AccountNotFound and ContractNotDeployed are now struct variants, while the view-call error variants include optional block_height and block_hash fields. The fields remain optional so legacy or string-only RPC errors can retain their typed classification without fabricated block context.

Downstream code that manually constructed or matched these variants must migrate to the new fields. Unknown or newly introduced VM error shapes continue to fall back to RpcError::ContractExecution.

Validation

• cargo fmt --all -- --check
• cargo test --workspace
• cargo clippy --workspace --all-targets --all-features -- -D warnings
• cargo clippy -p near-kit --all-targets --no-default-features --features sandbox -- -D warnings
• cargo check -p near-kit --all-targets --no-default-features
• cargo test -p near-kit --no-default-features --doc
• cargo +1.88 check --workspace --all-targets
• browser WASM and WASI feature checks
• cargo package -p near-kit --allow-dirty

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[greptile-apps]

Greptile Summary

This PR refines view-function RPC error classification and preserves queried block context.

• Adds typed errors for missing methods and view-method panics.
• Keeps other VM failures under ContractExecution.
• Parses current and legacy structured error payloads.
• Adds block-height and block-hash accessors to applicable errors.
• Removes the unused function-call RPC error API and updates integration assertions.

Confidence Score: 5/5

The PR appears safe to merge.

No blocking failure remains.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[View-function RPC response] --> B{Structured RPC error?}
    B -->|No| C[Deserialize ViewFunctionResult]
    B -->|Yes| D[Read block height and hash]
    D --> E[Parse info.vm_error or legacy info.error]
    E --> F{FunctionCallError kind}
    F -->|CodeDoesNotExist| G[ContractNotDeployed]
    F -->|MethodNotFound| H[MethodNotFound]
    F -->|Guest panic| I[ContractPanic]
    F -->|Other VM failure| J[ContractExecution]

Loading

_{Reviews (4): Last reviewed commit: "test: pin panic-prefix stripping and err..." | Re-trigger Greptile}