Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In @.github/workflows/ci.yaml:
- Around line 799-803: The worker readiness checks in the CI workflow use curl
in the wait steps without failing on non-2xx HTTP responses, so a 503 from
/healthz can still pass. Update the curl commands in the wait-for-ready steps to
include --fail alongside the existing retry options, and apply the same change
to both readiness blocks so the tests only proceed once the workers are actually
healthy.

In `@e2e/creditsdisabled/settlement_mode_test.go`:
- Around line 69-94: The negative settlement-mode checks in the credits-disabled
tests only assert HTTP 400, so they can pass for the wrong validation path.
Update the relevant assertions in the custom subscription test in
settlement_mode_test.go (and the other credits-disabled cases it matches) to
verify the response body/error detail contains "credits are not enabled on this
deployment of OpenMeter" using the existing CreateSubscriptionWithResponse flow,
so the guard in CreateSubscription is explicitly covered.

In `@e2e/creditsdisabled/setup_test.go`:
- Around line 46-57: The helper is assuming the 201 response body always decodes
into resp.JSON201 and its UsageAttribution field, which can panic if the payload
is empty or malformed. In the setup helper that calls
client.UpsertUsageAttributionWithResponse, add require.NotNil checks for
resp.JSON201 and resp.JSON201.UsageAttribution before accessing SubjectKeys, and
keep the existing status/assertion flow so failures stay readable.

In `@e2e/ledger_accounts_test.go`:
- Around line 32-38: The current assertion in the ledger_accounts_test.go flow
only verifies that business accounts exist after customer creation, but it does
not prove they were provisioned by that create path. Update the test around
getBusinessAccountIDs and the customer-create call to either use an isolated
namespace or capture a before/after snapshot of ledger.BusinessAccountTypes so
the test asserts a real delta for the new customer provisioning path. Keep the
existing account-type checks, but make them validate the accounts were created
by this specific test scenario rather than preexisting state.

In `@e2e/Makefile`:
- Around line 59-63: The wait-local target uses curl health checks that can
succeed on 4xx/5xx, so the suite may continue before services are actually
ready. Update both readiness probe commands in the wait-local rule to use curl’s
failure-on-HTTP-error behavior so non-2xx responses keep retrying. Keep the
change localized to the wait-local target and preserve the existing
retry/timeouts.

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@e2e/Makefile`:
- Around line 31-47: The teardown in the test-local-credits-disabled and
test-local-base targets only runs after successful commands, so failures in
wait-local or the test targets leave the compose stack running. Update these
Makefile targets to use a single shell flow with an EXIT trap or equivalent
always-run cleanup so env-local-down is executed even when setup or tests fail.

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In `@e2e/billinginvoices_v3_test.go`:
- Around line 201-203: Replace the `lo.Find` scan in the invoice test with the
standard library helper `slices.IndexFunc`, and apply the same change to the
matching search pattern elsewhere in this test. Update the surrounding logic in
`billinginvoices_v3_test.go` so it uses the returned index to access the item
instead of relying on `foundStandard`, keeping `lo` only for the pointer helpers
used in this test.