CLI-034 — Define and implement CLI configuration schema

[dDevAhmed]

Summary

Define the MVP configuration contract used by commands that need project/network settings.

Scope

• propose/record configuration format and precedence decision;
• typed schema validation;
• safe loading from supported project location(s);
• explicit network field handling;
• redaction/safe error behavior;
• tests for valid, invalid, and missing configuration.

Security Requirements

Do not treat raw secrets as normal project configuration. Never silently default ambiguous deployment/network settings to Mainnet.

Acceptance Criteria

• configuration contract is documented and, if architectural, recorded via ADR;
• validation errors are actionable;
• secrets are not echoed;
• network-sensitive values are explicit;
• tests cover precedence/validation behavior.

Dependencies

• CLI-006
• command requirements from generator/dev/deploy work

---

🏷 Labels

• type: feature
• area: config
• priority: P1
• difficulty: advanced
• security-sensitive