What Changed

• Updated error message in fortress-benchmarks.yml to include a title attribute and more detailed failure information indicating panic, fatal, or timeout scenarios with reference to job summary
• Modified input and timing data parsing in fortress-completion-finalize.yml to use base64 encoding/decoding and heredoc syntax for safely handling multiline values
• Normalized environment variable keys by replacing hyphens with underscores (e.g., env-json becomes env_json) for GitHub Actions expression compatibility
• Changed from simple key=value parsing to a multi-line heredoc approach with EOF delimiters (EOF_INPUT_<key> and EOF_TIMING_<key>) for both input and timing data
• Added continue-on-error configuration to artifact download step in the completion finalize workflow

Why It Was Necessary

• The enhanced error message provides clearer diagnostics when benchmarks fail, making it easier to identify the failure type and locate details in the job summary
• Base64 encoding and heredoc syntax prevent parsing failures when environment variable values contain newlines or special characters (particularly important for complex JSON data like env-json)
• Normalizing hyphens to underscores in variable names ensures compatibility with GitHub Actions expression syntax, which doesn't support hyphens in variable references

Testing Performed

• Verify that benchmark failures now display the enhanced error message with title and detailed context
• Test parsing of multiline input values (especially JSON data) to ensure they are correctly stored in environment variables
• Confirm that normalized variable names (with underscores) are accessible in subsequent workflow steps using GitHub Actions expressions
• Validate that artifact download continues appropriately based on the continue-on-error configuration

Impact / Risk

• Low risk - Changes primarily improve error reporting and fix data parsing edge cases without altering core workflow logic
• No breaking changes - The variable normalization is internal to the workflow and maintains backward compatibility
• Improved reliability - Better handling of multiline values reduces potential parsing failures in complex workflow scenarios