Follow-up to #3929 (GitHub tracker fix by @sealocal). The same bug
existed in jira, gitlab, ado, and notion trackers: their getConfig()
methods read every key from the Dolt store, but secret keys (API
tokens, PATs) should never be in the database because it gets pushed
to remotes, triggering secret-scanning blocks.
Changes:
- Add jira.api_token, gitlab.token, ado.pat to the yaml-only key
list so they are stored in config.yaml (not the Dolt database),
consistent with github.token and linear.api_key.
- Add IsYamlOnlyKey guard to getConfig() in all four trackers,
mirroring the pattern in linear/tracker.go and the merged GitHub
tracker fix.
- Add regression tests (nil-store bypass + yaml-read) for jira,
gitlab, and ado; defensive yaml-only path test for notion.
- Update existing tests that put secret keys in mock stores to use
t.Setenv instead, matching the new yaml-only behavior.
Co-Authored-By: sealocal <4951910+sealocal@users.noreply.github.com>