**RESOLVED 2026-07-12 (w6 follow-ups).** Root cause: the two tests omitted Context in graphql.Params; graphql-go v0.8.1 Do does not default a nil Context, so the resolver dereferenced nil. Fixed by setting Context: background() (the package convention). internal/apps is fully green.

# Red internal/apps tests: TestGraphQLSet/DisableAutoscalingMutation — from w6/m6 triage

Two tests in `lego/backend/internal/apps/autoscaling_test.go` fail at HEAD (and on
clean `main`, so they are **pre-existing**, not from w6/m6):

- `TestGraphQLSetAutoscalingMutation` (autoscaling_test.go:260)
- `TestGraphQLDisableAutoscalingMutation` (autoscaling_test.go:282)

Symptom: `res.Errors` carries a `runtime error: invalid memory address or nil
pointer dereference` — graphql-go surfaces a resolver panic. The `setAutoscaling`/
`disableAutoscaling` GraphQL resolvers (or the `SetAutoscaling`/`DisableAutoscaling`
service methods they call) dereference a nil pointer.

Why filed, not fixed here: w6/m6 is a security milestone; autoscaling is an
unrelated feature and the fix needs tracing the `SetAutoscaling` path
(`apps/service.go`) + its resolver to find the nil. Surfaced by the w6/m6 review
because `internal/apps` going into a commit red means git bisect / CI attribute
the red to that commit. Fix before the next `/ship` that touches `internal/apps`,
or skip these two tests with a tracked issue reference until owned.

Reproduce: `cd lego/backend && go test ./internal/apps/ -run 'TestGraphQLSetAutoscalingMutation|TestGraphQLDisableAutoscalingMutation' -v`

Source: w6/m6 triage review (finding 2), 2026-07-12.
