What Changed

• Modified the workflow input parsing logic in .github/workflows/fortress-completion-finalize.yml to use base64 encoding and heredoc syntax instead of simple key-value assignment
• Changed from jq -r 'to_entries | .[] | "\(.key)=\(.value)"' to jq -r 'to_entries | .[] | @base64' for both ALL_INPUTS and TIMING_DATA parsing
• Replaced inline environment variable assignment (echo "INPUT_$normalized_key=$value" >> $GITHUB_ENV) with heredoc delimiters (EOF_INPUT_$normalized_key and EOF_TIMING_$normalized_key)
• Added intermediate base64 decoding steps to extract keys and values separately before writing to $GITHUB_ENV

Why It Was Necessary

• The previous implementation could not safely handle multiline values (specifically mentioned in the comment: "e.g., env-json")
• Simple key=value assignment breaks when values contain newlines or special characters
• Heredoc syntax is the GitHub Actions recommended approach for setting multiline environment variables safely

Testing Performed

• Validate that workflow inputs with multiline JSON values (like env-json) are correctly parsed and stored in environment variables
• Test that timing data continues to be properly extracted and normalized with underscores replacing hyphens
• Verify that all downstream steps can access the parsed environment variables with the INPUT_* and TIMING_* prefixes

Impact / Risk

• Low risk: This change improves robustness without changing the logical flow or output format of environment variables
• Potential issue: Base64 encoding/decoding adds minor overhead, but this is negligible for typical workflow input sizes
• Breaking change: None - the resulting environment variable names and normalization logic remain identical