MCP CLI: surface resolved configuration and its source (env vs profile vs default)

[glorydavid03023]

There is no single command to see which configuration the gittensory-mcp CLI is actually using and where each value came from. status reports health/version, doctor runs checks, and whoami shows session identity, but none answer "what config is in effect and which source supplied it?" — the common question when an API URL or profile is not picked up as expected.

Proposal: a gittensory-mcp config command that prints the resolved effective configuration with provenance (environment / profile / config / default) for the API URL, active profile, config-file location, cache dir, and token source. Provenance labels only — no token values or local absolute paths. --json for tooling.

Implemented in #335.

[JSONbored]

2026-07-01 audit: appears implemented (owner note cited #335) but the config-source surfacing was not verifiable in packages/gittensory-mcp/src during the audit — verify the config command output, then close.

[JSONbored]

Closing as completed — gittensory-mcp config already surfaces resolved configuration + its source (env/profile/config/default) via configCommand (bin/gittensory-mcp.js:2504), with --json support and no token/path leakage, and is test-covered (test/unit/mcp-cli-basics.test.ts:214-271). Verified directly against the current code.