Add user details in auth status

[ramilamparo]

Sample output:

  Credentials connected via https://acme.eu1.qasphere.com
    Source: credentials.json
    Status: valid
    User: Test User <tester@example.com> (admin)
    Re-authentication required: in 89 days (resets on each use)

[claude]

Claude finished @ramilamparo's task in 2m 52s —— View job

---

Review Summary

• Gather PR context and diff
• Launch specialized review subagents
• Aggregate findings and post review
• Clean up outdated bot comments

Result: Approved with one minor DRY suggestion on the MeUser interface.

The change is clean — switching from projects.list() to /users/me for credential validation is a better semantic fit and lighter on the API. Tests are thoroughly updated. No security or performance concerns.

[claude]

Clean change — using /users/me instead of projects.list() is both a better semantic fit for credential validation and lighter on the API. Tests are well-updated to match. One minor DRY suggestion on the interface definition.

[claude]

Nit: MeUser duplicates all of User's fields, with avatar being the only addition. Consider extending instead:

export interface MeUser extends User {
	avatar: string | null
}

This avoids the maintenance burden of keeping both interfaces in sync if shared fields change.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: a5814a3d1a

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

Avoid admin-only user endpoint for auth validation

auth status now validates credentials via api.users.me(), but QA Sphere’s Users API is admin-restricted in the public docs; in environments where /users routes enforce that policy, valid non-admin credentials will be reported as invalid or expired. This is a regression from the previous projects.list() check, which worked for regular project roles, so the status command can now fail for legitimate users.

Useful? React with 👍 / 👎.