Structured error codes for action-thrown failures under ipfs_id execution

[technohippi3]

Lit support question — structured errors for ipfs_id action failures

Status: prepared, non-blocking; no staging or production dependency.

When an action is submitted as raw code, an action-thrown error has been observed with the
message and stack represented in the response. When the same registered, published action is
executed by ipfs_id, expected policy rejections return HTTP 500 but no stable action error code
or action message is available through the bounded JSON fields observed by the caller.

Questions:

1. Does ipfs_id execution expose a documented, stable structured error code for an exception
   thrown by user action code?
2. If so, which response field is contractual and safe to use for programmatic classification?
3. Is returning a bounded structured result from the action, rather than throwing for expected
   policy rejection, the recommended integration pattern?

Sanitized observed shape:

• raw-code control: HTTP 500 with an action-originated uncaught-error representation;
• ipfs_id execution: HTTP 500; bounded JSON inspection yields no registered-action message;
• no nonce was reserved and no transaction was produced;
• no raw provider body, credential, request payload, or stack trace is included here.

Relevant immutable artifact identity:

• CID: QmR9EqhLEK7jE1wp44wLanmeJwK3Wr3kPtsfD4pjAmogm7
• SHA-256: 59b65894559e6feb454586f5aae6342f35f2100018a72889f8fcc55d9dd20155