Wage imports tell you what actually went wrong

Uploading a wage card or a DIR determination and getting back Unexpected token '<', "<!DOCTYPE "... is not valid JSON told you nothing. It was our plumbing leaking onto your screen. Two different failures were both coming out that way, and neither is your fault for not deciphering.

The wrong layer. The selector next to Upload PDF says whether the file is a DIR determination or a union wage card / CBA, and the two are read by different rules. Send a wage card through as a determination and the reader balks — correctly, since the documents aren't the same shape. That now comes back as a plain sentence pointing you at the selector, instead of a generic "try again" on something retrying can't fix.

A parse that outran the connection. Reading a full rate schedule takes a while, and on a long one the browser's connection can drop before the answer comes back. The upload is saved either way — it's sitting in the Imports list. Now the message says so and points you at Re-parse rather than leaving you to guess whether anything landed.

Nothing about how rates are read or promoted changed. This is the error text doing its job.