For a boostrapped add-on that gets automatically installed (perhaps by distribution or upgrade(?)), its startup gets called with APP_STARTUP. That's arguably correct, except now bootstrapped add-ons can't rely on ADDON_INSTALL for startup reason, which is what they normally get if the user manually installs the add-on. Workaround: Track ADDON_INSTALL from install() and check it from startup().
Is this something that can be fixed Dave?
Not only can we fix it, but we already have