fix(cli): add defaultValue overloads and typed key unions to typegen output

[olamide226]

Summary

• get() in the REP interface now emits both overload signatures (defaultValue: string → string, defaultValue?: undefined → string | undefined), matching the SDK's actual implementation
• Standalone exported get() gains the same two overloads with the typed public key union (was incorrectly key: string)
• Standalone exported getSecure() now uses the typed sensitive key union instead of key: string

Why

The SDK declares get() with two overloads (§5.2) so callers get a narrowed string return type when they pass a default value. The typegen was silently dropping both overloads, meaning consumers lost the type narrowing and got no autocomplete on key names for the standalone exports.

Test plan

• Run rep typegen against a manifest with public + sensitive vars and verify the generated .d.ts includes both get() overloads with the typed key union
• Confirm rep.get('KEY', 'fallback') resolves to string (not string | undefined) in a consuming project
• Confirm rep.get('KEY') still resolves to string | undefined
• Confirm passing an unknown key to get() or getSecure() is a TypeScript error

[Copilot]

Pull request overview

Updates the CLI’s TypeScript typegen output so generated declarations better match the SDK’s get() overload behavior and provide typed key unions for standalone exports.

Changes:

• Emit both get() overload signatures in the generated REP interface so defaultValue narrows the return type to string.
• Generate standalone exported get() overloads using the typed public key union (instead of key: string).
• Generate standalone exported getSecure() using the typed sensitive key union (instead of key: string).

---

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