[Shorton88]

SOAR actions can return mixed outcomes even when their run status is successful. Receipts now keep each result's status, summary, and data together, preserve expanded details when results reorder, and show mixed outcomes alongside SOAR's reported status.

Changes

• Read additional action-result pages within a five-request budget, counting failures beyond the five-item detail preview. Mark incomplete coverage explicitly rather than implying all results succeeded.
• Use the same labeled SOAR run-status totals in submissions and receipts; individual result outcomes remain separate.
• Increase the regex limit from 512 to 2,048 characters in the builder and backend, with a multiline editor, character count, and unchanged evaluation timeout.
• Bump package metadata to 0.5.10, validate lockfile versions during packaging, and document search head cluster version troubleshooting.

Validation

• npm test: 46 JavaScript and 207 Python tests pass.
• npm run package: builds the 0.5.10 Splunk bundle successfully.
• Browser checks in light and dark themes using isolated, simulated SOAR responses: mixed outcomes, incomplete 125/126-result coverage, consistent list/receipt totals, and an 880-character IPv6 pattern that saves and accepts/rejects appropriate preview inputs. No browser console errors.
• Live Splunk/SOAR integration and Splunk AppInspect have not been run for this change.