Description
Thinking of patterning a .config/go-script-bash directory convention along the lines of the XDG_CONFIG_HOME spec. This way there could be a mechanism to import .config/go-script-bash/* to get the top-level config for the project (some possibly standard, but can pull in user-defined config like this, too).
This could also support a recursive mechanism to import and install plugins by following every .config/go-script-bash/plugins file in the _GO_PLUGINS_DIR tree. Only plugins defined in the top-level .config/go-script-bash/plugins file would then be available to the top-level command script, to support an npm-like node_modules plugin directory structure where by common plugins are shared, but without cluttering up the main command namespace.
More generally, there could be a mechanism to determine which commands to expose as part of the public vs. private interface, but that's for a future issue.