API shared HTTP success predicate

Trap: telemetry using status >= 400 looks consistent with ordinary HTTP failure handling, but API output treats every status outside 200–299 as an error, so 199 and 3xx responses lose api_error attributes. Fix: use the exported shared HTTP-success predicate in both output and telemetry, and keep boundary regression tests for 199, 200, 299, and 300.