v1.14.1

Fixed

• Bumped @simpleworkjs/bao-conf to 1.0.1 so standalone/no-OpenBao boots don't crash. bao-conf 1.0.0's init() threw when VAULT_TOKEN was unset, which — combined with bin/www's .catch(() => process.exit(1)) — made the jump host exit at boot in any deployment without an OpenBao sidecar. 1.0.1 makes init() fail-soft on a missing token (warn + continue from CONF_SECRETS). The theta-env stack is unaffected (it always sets a scoped VAULT_TOKEN).