Every DIR area gets its own determination

A DIR determination is one PDF covering several areas. Area 1 is the Bay Area counties, Area 2 is Monterey and Santa Cruz, and so on down the list — and each area pays a different rate for the same trade. The import had nowhere to put an area, so it kept everything in one determination and quietly renamed the rows to keep them apart: journeyman, journeyman_area2, journeyman_area3.

That broke the wage floor without saying so. The floor check matches a worker's hours to a rate by classification, and a timecard says journeyman — so only whichever area happened to win that plain name was ever used. Every other area's rate sat in the table doing nothing while its crews were checked against the wrong area's floor.

If you have imported a determination covering multiple areas, its floor is wrong. The determinations list now says so on the affected rows, in red, with what to do: re-import it. Nothing was changed underneath you — these are compliance records, and correcting one is your call, not something to happen silently overnight.

What changed for new imports:

• Each area saves as its own determination, with only its own counties and its own rates. Matching a job to a floor already works by county, and an area is a list of counties, so the right rate now finds the right job on its own.
• Craft variants stay separate. A carpenter determination lists Carpenter, Millwright, and the hardwood floorlayer group — all at journey level, all at different rates. They used to arrive as three identical journeyman rows, which meant two of the three were dropped on save. Each keeps its own line now.
• The review screen shows DIR's own label — "Carpenter (Area 1)", "Millwright (Area 3)" — next to each row, so you can check what was read against the page it came from. Previously every row just said journeyman and there was no way to tell them apart.
• The rate grid stopped cutting off. The last columns were running off the edge of the card; the table scrolls properly now.
• The importer warns before you save if two rows would collide, if an area ended up inside a classification name, or if one county turns up in two areas.