Introducing handling of empty config files

[GreyTeddy]

What do you want to change?

I would like to introduce proper handling of empty config files, given error.FileIsEmpty thrown.

Commit on personal fork: e581440

Why do you want to make this change?

I saw the following warning/error when running zig build run and thought that introducing handling of empty config files should be introduced and considered.

warning: error reading optional config file, not loading err=error.FileIsEmpty path=/Users/dennisduka/Library/Application Support/com.mitchellh.ghostty/config.ghostty

---

• I don't currently have a confident opinion on how empty configs should be fully handled (apart from :loaded false and I am happy for it to be discussed with/without me.
• AI Disclosure: used free version of Opencode with DeepSeek V4 Flash Free as a second pair of eyes before commiting.
  • Note: I did not approve initial suggestions and did somewhat argue with it.

I acknowledge that:

• I have read the Contributing Guide and understand the contribution process.
• I have read and agree to follow the AI Usage Policy.
• I wrote this vouch request myself, in my own voice, without AI generating it.