regression: Near-silent failure to start when convict file is bad

[ariane-emory]

Description

When the configuration file is bad - for example, if it contains unknown keys, or unknown key commands in its keybindings - opencode, when run using bun dev, simply fails to start with no error other than error: script "dev" exited with code 1 instead of reporting a specific error as it used to. This error was introduced yesterday in commit adae0d185.

Sample bad opencode.json file:

{
  "$schema": "https://opencode.ai/config.json",
  "bad_setting": "i am a bad configuration file",
}

Plugins

None

OpenCode version

1.1.8

Steps to reproduce

1. Use the configuration file above.
2. Try to start opencode using bun dev.
3. Observe that open code silently fails to start.

Screenshot and/or share link

No response

Operating System

MacOS Sequoia latest

Terminal

iTerm2

[github-actions]

This issue might be a duplicate of existing issues. Please check:

• ConfigInvalidError on Windows due to unrecognized keys in opencode.json #7483: ConfigInvalidError on Windows due to unrecognized keys in opencode.json - similar issue with bad configuration not being properly reported
• [FEATURE]: Missing key commands ought not be fatal errors. #6397: [FEATURE]: Missing key commands ought not be fatal errors - directly addresses the keybinding validation problem mentioned in this issue
• Plugin syntax errors are handled poorly #4850: Plugin syntax errors are handled poorly - related error handling and reporting improvements

Feel free to ignore if none of these address your specific case.

[github-actions]

For keybind-related issues, please also check our pinned keybinds documentation: #4997

[ariane-emory]

Resolved via #7522.