Question
The feat/baseone-rebrand branch (PR #52) is meant to introduce behaviour where configurations paths with a baseone in their names will be used if they are available, and otherwise it will fall back to the standard opencode configuration paths. Does this behaviour look like it should work?
Question
The
feat/baseone-rebrandbranch (PR #52) is meant to introduce behaviour where configurations paths with abaseonein their names will be used if they are available, and otherwise it will fall back to the standardopencodeconfiguration paths. Does this behaviour look like it should work?