refactor(cli): cover db start with effect lint (CLI-2409)

[7ttp]

TL;DR

brings supabase db start under the effect lint

whats introduced?

effect lint applied to db start:

• one allow list entry for db/start
• the backup error is yielded directly
• integration tests write config.toml and .env through the layer setup returns, so test bodies stay unchanged, and set env through withEnvVar only where a test depends on it
• cause assertions use Cause.pretty, and the roles e2e decodes through Schema
• the e2e test runs through the effect native harness with its stop cleanup in Effect.ensuring

ref:

• related: CLI-2409

[github-actions]

🤖 AI Review

Both independent reviews reported no findings. The changed handler, tests, and supporting helpers reveal no concrete regression on code inspection. Tests were not run in this read-only adjudication.

Findings

No issues found.

Stats

Claude findings: 0 · Codex findings: 0 · Confirmed: 0 · 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]

Effect-lint coverage for db start looks mechanical.

The handler only switches yield* Effect.fail(new …Error) to yield* new …Error on the same tagged error. Tests are unchanged aside from Effect-style setup.