Rodney, I think you are correct. However, the problem is that plans/packages do get rebound for other reasons sometimes, and when that happens, there is potential for problems when select * is used in the view.
For example, a DBA might want to drop and recreate an index (which will force an automatic or explicit rebind of any plans/packages that use that index), or use rebind with explain yes to populate the explain tables, etc. So to guard against these rebinds, the program would need to be changed to add the new column, recompiled, and then do a bind replace (assuming that select * was in the view).