fix(env): add app config summary to env info [DEVEX-715]

[qcai-godaddy]

Summary

• Enrich env info for the active environment with always-present configFile (expected godaddy.toml / godaddy.<env>.toml path) and configSummary (object when the manifest validates, otherwise null)
• Leave env get / env list shapes unchanged; unknown --env hard-fail and old GODADDY_* overrides already fixed
• Skip TS display (color/label) and optional env info [environment]: display is unused noise, and a positional inspect switch duplicates/confuses global --env while env * already reports persisted active (~/.gdenv)

Test plan

• cargo build / cargo fmt --check/ cargo clippy -- -D warnings / cargo test
• gddy env info --output json returns env, apiUrl, graphqlUrl, configFile, configSummary
• gddy env info ote is rejected (no positional)
• With a valid godaddy.toml in cwd, configSummary is populated; without it, configFile is still set and configSummary is null

[Copilot]

Pull request overview

This PR updates the env info command to support inspecting a specific environment without changing persisted state, and enriches the JSON output with local app manifest (godaddy*.toml) context for tooling.

Changes:

• Extend EnvInfo output to include configFile and configSummary derived from the local manifest when present/valid.
• Add an environment selector argument to gddy env info (defaulting to the active environment).
• Add tests covering the new env info output fields and argument behavior, plus unit tests for manifest summarization.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.

Suppressed comments (1)

rust/src/env/mod.rs:40

• The doc comment for config_context says godaddy[.env].toml, which reads like it refers to a .env file rather than the intended optional .<env> suffix. This could mislead readers about which manifest file is being summarized.

/// Path to the env's `godaddy[.env].toml` (absolute when possible), plus an
/// optional summary when the file exists and validates. Missing/invalid
/// configs yield `configSummary: null`.

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.

Suppressed comments (2)

rust/src/env/mod.rs:481

• config_summary_for_path is documented/used to treat missing and invalid manifests as a soft failure (configSummary: null), but the unit tests only cover the missing-file case. Adding a test that exercises the invalid/parse-failure path would lock in the behavior.

    #[test]
    fn config_summary_for_path_returns_none_when_missing() {
        let dir = tempfile::tempdir().expect("tempdir");
        let path = dir.path().join("godaddy.toml");
        assert!(super::config_summary_for_path(&path).is_none());
    }

rust/src/env/mod.rs:35

• The PR description says both configFile and configSummary should be null when the local manifest is missing/invalid, but EnvInfo defines configFile as a required string and the implementation always returns a path even when the summary is null. Please align the description and implementation (either make configFile nullable/conditional, or update the description/help text to reflect that configFile is always populated with the expected manifest path).

This issue also appears on line 476 of the same file.

    "env": "string";
    "apiUrl": "string";
    "graphqlUrl": "string";
    "configFile": "string";
    "configSummary": "object|null";

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.