refactor(cli): cover config push tests with effect lint (CLI-2486)

[7ttp]

TL;DR

brings the supabase config push tests under the effect lint, which completes the config family

whats introduced?

effect lint applied to the config push tests:

• the per subcommand allow list entries collapse into one config/** entry
• integration tests write fixtures through FileSystem, seed linked project state through setup, and set env through withEnvVar
• both test setups provide the CLI config provider like production, with a new case for an env(VAR) secret read from the root .env
• v1 mock failures are real transport errors
• cause assertions use Cause.pretty, and field checks read the typed error directly
• e2e tests run through the effect native harness, the live test through the cliEffect fixture with its proofs polled on a Schedule

ref:

• closes: CLI-2486

[github-actions]

🤖 AI Review

Both independent reviews were available. The reported inconsistency in the live test is confirmed as a nit; the test still captures and reports the failure. No additional verified findings emerged from the changed code. This was a static review.

Findings

Severity	Location	Category	Sources	Claim
⚪ NIT	apps/cli/src/commands/config/push/push.live.test.ts:137	consistency	claude	The target and cleanup generators call requireLiveSuccess directly, so a failed check becomes an Effect defect, while diffMaxRows converts the same check into a typed LiveConfigPushError.

Stats

Claude findings: 1 · Codex findings: 0 · Confirmed: 1 · Refuted: 0 · Uncertain: 0

---

Models: claude-opus-5-5 + gpt-6-sol · Trigger: auto · Workflow run

This review runs once per PR. A maintainer can request another with a /ai-review comment.

[avallete]

Tests only. push.e2e / push.integration / push.live are re-excluded from effect lint after the push/** ignore is lifted for the runtime files. Assertions moved to Cause.pretty / error fields and still check the same messages. No runtime behavior change.