Understanding changes in accessing parsed JSON fields in Zapier

I have a Zap that I originally built back in August of 2024. This Zap consists of the following steps (at a high level): 

1. WebHook Step: Zap receives data in JSON form
2. Code Step: Javascript step parses the JSON
3. A record is looked up in the CRM using the data from step 2
4. A record is entered into a Zapier Table using data from step 2
5. A record in the CRM is updated using data from step 2

The version that is in use is from August of 2024 and has been in use since that time. It ran successfully approximately 90 days ago. Yesterday, the zap failed three times. Upon reviewing the zap with support, the steps after step 2 that rely on parsed data showed the yellow exclamation point icons indicating that there was an issue with the fields. When trying to remap the fields at the direction of support, the values from Step 2 are no longer available to me to map as individual fields. 

Is anyone able to help me understand why this would be/what changed? The code for my code step is shown below and as far as I can tell, this is the method that is recommended in numerous places on this very site. 

// Remove any "$" characters before parsing the JSON string

let cleanedRAW = inputData.RAW.replace(/\$/g, '');

let PARSED = JSON.parse(cleanedRAW);

output = [{ PARSED }];

The code is pretty basic and when tested shows that the data appears to have been parsed correctly. However, where previously I could access individual key value pairs in later steps (such as PARSED fieldA, PARSED, fieldB) I now only have access to PARSED which includes ALL key/value pairs. 

Did something change with how this is handled/supposed to be handled?