Put yourself in the manufacturer's shoes. You have spent a lot of $$ in R & D, and if it doesn't get into the code who is going to buy it, especially if it does have problems.
First mention of AFCI in the NEC was in 1999 edition, with a date of effectiveness of Jan 1, 2002. Why did that happen? They weren't ready with product yet but made sure they persuaded the code making panel they would be by that date, because they wanted to start selling instead of sitting on there R & D for three more years when the next code comes out. Even though next code was 2002, there would be many places that don't adopt it right away, so the date in 1999 gets sales up for anyone using 1999 once 2002 comes around.
Then we later find out the first units don't do everything they say they will do, and they come up with the CAFCI, and if I recall put similar date in code to get time to get them to the market but yet assures they don't have to wait three more years to get it into code.
Will they someday have a legitimate product that people trust? maybe, but nothing like using the consumer as a major part of your testing lab and crying it is all about saving lives as justification and continuing to profit by forcing what many consider a poor product into the code.