No the government did not get involved. Intel would be nuts to let it go that far, and they aren't nuts. In the end Intel offered to replace the processor for anyone that wanted to. The problem was their first proposal at the big revelatory announcement. They wanted to replace it only for those who could demonstate it was genuinely needed, like in mathematical research. But if I paid the same amount as some mathematician at a university, why can't I get mine replaced too? People forget that the first Pentiums cost over a thousand bucks, and the price did not come down all that fast. They were still getting over $200 bucks for Pentium 1 MMX when PIIs were superceding them.
I doubt if an on-screen CAD display uses the level of precision that would be needed to see the error. I don't think the engineering of bridges use that level of precision either. Accounting for one part in 10,000 is doing very well in real life.
Since it was a floating point error, you probably would never see it in monetary calculations, because they wouldn't use floating point.
Since the error was in the lower bits, and only in some cases, the odds of one calculation being in error were billions to one. However, even back then a computer could do tens or hundreds of millions of calculations in one second. If you crunch for a month or a year, the error odds are not exclusionary. The difficulty is you don't know. Some people did not like the way Intel hammered excessively on how insignificant it was.
It seems to me compilers to this day have an option that works around that bug.
Pretty good account of the bug
"As I recall, there was also an even older error with the old Pentium Pros....This problem was fixed quickly but not before the French lost an Arianne rocket to the fault -"
This was a story intended to illustrate what an error like this could do, but Intel was not involved.
An account of this error
From article: "When talking about the bug Collins gives an interesting analogy about a launch failure of the Ariane 5 rocket, which happened because a floating point to integer conversion overflowed and the overflow was not handled right."