Not a working solution yet - LED is still on, I ran request system configuration rescue save from the CLI, show chassis alarms and show system alarms are all clear.
When I run "request support information member 2" I get
root@ccf4200stack> show chassis alarms no-forwarding
error: the alarm-control subsystem is not running
root@ccf4200stack> show chassis hardware detail no-forwarding
error: the chassis-control subsystem is not running
However, when I run "request support information member 1" I see
root@ccf4200stack> show chassis alarms no-forwarding
error: Aborted! This command can only be used on the master routing engine.
[etc]
So, request system reboot member 2 - And the LED goes off. Yay.
So, the VC member just came up in a slighty cockeyed manner.
I don't consider it a hassle to reboot a new VC after it's been installed and "commit synced" with the master. Considering my experience with "stacks" from other vendors, this is trivial. Thanks for all the replies.