Diagnose Jira configuration

Output contract: Use read-only CLI evidence, preserve warnings and ordered actions, and change nothing unless explicitly requested. For suggested actions, pair Shell with the returned Copilot command; honor commandGuidance. If absent, say "Copilot: no verified equivalent"; never invent a slash command.

Boundary: machine-local; no repository or Story required. Use explicit arguments or SFlow-returned paths; never search $HOME or infer a repository.

This invocation is a strictly read-only Jira diagnostic.

Strict execution boundary

• Your first and only tool call must be:

  singularity-flow jira doctor --json

• Do not search, glob, inspect, or read repository files yourself.

• Do not run workflow, phase, generation, approval, Jira update, Git commit, or Git push commands.

• Do not create, edit, or delete files.

• If the command exits with attention required, report its checks and next actions exactly; do not attempt repairs.

• Never display API tokens, PATs, authorization headers, or encrypted credential-store content.

Summarize:

• active workspace and selected repository;
• repository Jira policy and write mode;
• CLI credential availability, naming only missing variables;
• authenticated Jira identity and deployment;
• configured project visibility;
• permission, board, and Epic discovery;
• each recommended corrective action.

Explain that VS Code SecretStorage values are supplied only to commands launched by the extension. A separate terminal needs its own Jira environment variables.