QMAws::startTask | ECS failures - job_id: 1025611, task_definition: cupix-pano-postprocessor-product

Validation: c6afd4dc-ea88-48a7-84ae-0792b3296d3b

Plan Item	Status	Evidence
`qmAws.ts` startTask 콜백에서 `logger.error`를 `logger.warn`으로 변경	PASS	`applications/agents/packages/cupix-tesla-compute-agent/src/model/qmAws.ts`: line 198 — diff shows `-logger.error(` changed to `+logger.warn(` within the `data.failures` branch of the startTask callback

Criterion	Status	Evidence
`qmAws.ts`의 startTask 콜백에서 failures 로깅이 `logger.warn`을 사용	PASS	`applications/agents/packages/cupix-tesla-compute-agent/src/model/qmAws.ts`: line 198 in the working tree confirms `logger.warn('QMAws::startTask \| ECS failures - ...`
로그 포맷과 메시지 내용은 변경 없음 (레벨만 변경)	PASS	diff shows only the method name changed from `error` to `warn` on line 198; the format string `'QMAws::startTask \| ECS failures - job_id: %d, task_definition: %s, cluster: %s, container_instance: %s, failures: %s'` and all subsequent arguments (lines 199-203) are identical between old and new
기존 테스트 통과 (pnpm exec nx run cupix-tesla-compute-agent -t test)	CANNOT VERIFY	Cannot verify from diff — requires runtime execution of the test suite. However, since only the log level was changed (no logic, control flow, or API changes), risk of test breakage is negligible.

No blocking issues found.

The diff is minimal and surgical: exactly one token changed (error to warn) on a single line. No other code was added, removed, or modified.
The test suite criterion cannot be verified from a static diff review alone. It requires a runtime check, but the change carries virtually zero risk of test regression since it only alters a log severity level with no impact on control flow or return values.
This is a well-scoped log-level downgrade consistent with the rationale that ECS AGENT failures are transient and auto-recovered via SQS retry, reducing unnecessary alert noise.