Goal
Update Accounting to consume github.com/flarexio/stoa v1.0.2, and update config.example.yaml to document the new OpenAI-compatible LLM configuration added by that Stoa release.
Background
flarexio/stoa v1.0.2 includes PR flarexio/stoa#45:
- Adds
BaseURL to llm/openai.Config.
- Keeps
APIKey and BaseURL environment fallback behavior.
- Explicit config values should take precedence over environment defaults.
Accounting currently depends on:
github.com/flarexio/stoa v1.0.1
Accounting's config.example.yaml currently documents only:
and says OPENAI_API_KEY must be set in the environment. It should be updated to show the new settings supported by the Stoa OpenAI adapter.
Scope
Allowed changes:
- Update
go.mod / go.sum to use github.com/flarexio/stoa v1.0.2.
- Wire Accounting's LLM config into the updated Stoa OpenAI adapter fields if Accounting has an app-level config struct for
llm settings.
- Update
config.example.yaml to document the new OpenAI-compatible provider configuration.
- Update README or CLI help text if it currently says the API key can only come from
OPENAI_API_KEY.
- Add or update tests for config parsing / adapter construction behavior if applicable.
Out of scope:
- Reintroducing config into Stoa itself.
- Changing unrelated accounting domain behavior.
- Replacing the OpenAI adapter abstraction.
- Logging, printing, or committing real API keys.
Requirements
- Bump Stoa dependency to
v1.0.2.
- Extend Accounting's config shape, if needed, so the
llm section can carry:
model
api_key / apiKey
base_url / baseURL
- Ensure explicit config values are passed into the OpenAI adapter and take precedence over environment defaults.
- Preserve existing environment-variable-only behavior for users who do not put credentials or base URL in config.
- Update
config.example.yaml with safe placeholder values, for example:
llm:
model: gpt-5.4-mini
# api_key may be omitted to use OPENAI_API_KEY from the environment.
api_key: ${OPENAI_API_KEY}
# base_url may be omitted for default OpenAI; set for OpenAI-compatible providers.
base_url: https://api.openai.com/v1
Use the actual field names supported by Accounting's config parser. Do not include a real API key.
Acceptance Criteria
Verification
Run:
If config-specific tests exist, run those too and mention them in the PR.
Expected Output
When complete, the worker should:
- Create a branch.
- Commit changes.
- Push the branch.
- Open exactly one PR linked to this issue for review.
- Do not merge the PR.
- Comment with the PR URL, summary, tests run, and any remaining risks.
Goal
Update Accounting to consume
github.com/flarexio/stoav1.0.2, and updateconfig.example.yamlto document the new OpenAI-compatible LLM configuration added by that Stoa release.Background
flarexio/stoav1.0.2includes PR flarexio/stoa#45:BaseURLtollm/openai.Config.APIKeyandBaseURLenvironment fallback behavior.Accounting currently depends on:
Accounting's
config.example.yamlcurrently documents only:and says
OPENAI_API_KEYmust be set in the environment. It should be updated to show the new settings supported by the Stoa OpenAI adapter.Scope
Allowed changes:
go.mod/go.sumto usegithub.com/flarexio/stoa v1.0.2.llmsettings.config.example.yamlto document the new OpenAI-compatible provider configuration.OPENAI_API_KEY.Out of scope:
Requirements
v1.0.2.llmsection can carry:modelapi_key/apiKeybase_url/baseURLconfig.example.yamlwith safe placeholder values, for example:Use the actual field names supported by Accounting's config parser. Do not include a real API key.
Acceptance Criteria
go.modreferencesgithub.com/flarexio/stoa v1.0.2.config.example.yamldocuments model, API key, and base URL settings for the LLM provider.OPENAI_API_KEYstill work.go test ./...passes.Verification
Run:
go test ./...If config-specific tests exist, run those too and mention them in the PR.
Expected Output
When complete, the worker should: