a) it is devkit board, which means it is intended for developing; for that you need to have access to logs from UART and at the same time access to USB peripheral (assuming you want to work with USB); of cource it is possible to use USB for logging purpose, but it would not let you to use peripheral...

Then the additional chip can fail... I am a little bit stuck... Then i will follow this way of thinking and i will ask, do you have fail safe in case of transistor fail, or selenoid, bad soldering, or just a wires? Everything may pass quality tests, but after some time fail. In other hand esp32 is ...

Admins, please mark it as spam and remove due to links in post ^UP

There is typo in so, the header file is:

This is only theory, but: - esp_sleep_get_ext1_wakeup_status is reading latched register, - that latched register stores values for all pins being high during wakeup and being setup as wakeup pins, - since it is big button with some bigger debounce it is possible that button during reading and latch...

You can open feature request on github to add this as parameter in menuconfig.

Very nice project, but maybe in next version you may think about esp32 S3, which is BLE 5 and shipped with native USB OTG.
Still few months before it will be available on market, but you can experiment with S2 and its USB code.

Some oflags does not exist in esp32 for fopen, dont remember which one, and few functions like posix_fallocate does not exist.