[no-mistakes#312] test(bitbucket): add host.go state-mapping tests

[github-actions]

Decision needed - no-mistakes#312

PR review by @e-jung · merge-ready

test(bitbucket): add host.go state-mapping tests

Situation

• Compliance: pass
• Tests: green
• Notes: compliance=pass tests=green

Recommended action

Merge - compliance and tests are green.

Your decision

Tick one box for a quick call, or reply with a slash-command (/merge, /close, /decline <reason>, /hold, /comment <text>):

• Merge it
• Close / decline
• Investigate - deep code-grounded review (leaves this card open)
• Hold - I'll handle this manually

_{Only the repository owner can drive this decision - everyone else's edits and comments are ignored.}

[github-actions]

MERGE

I read internal/bitbucket/host.go and host_test.go in full and traced every test assertion against the actual production code. All six helpers are pure functions with no side effects; the tests are correct.

• normalizePRState (host.go:177-188): Tests accurately cover the strings.ToUpper(strings.TrimSpace(raw)) switch for all five recognized tokens, plus the raw-passthrough default. The tricky whitespace-only case " " → TrimSpace→"" → default → scm.PRState(" ") is correctly expected as " " in the test.

• statusName / statusBucket (host.go:213-234): 9 and 18 subtests respectively; every branch of both functions is exercised, including whitespace-only fallback to key, and the IN_PROGRESS/INPROGRESS split for pending.

• normalizePipelineUUID (host.go:236-243): The tests correctly document strings.Trim's cutset semantics — stripping all leading/trailing { and } characters, not just one pair. The "a{b}c" → "a{b}c" interior-brace preservation case matches the implementation exactly.

• pipelineUUIDFromStatusURL (host.go:245-262): Fragment is checked before path because []string{parsed.Fragment, parsed.Path} iterates in that order. The %xx malformed-URL test is correct: Go's url.Parse returns an error on invalid percent-encoding, so the function returns "".

• failedPipelineUUIDs (host.go:264-292): 15 subtests cover nil/empty/whitespace failingNames returning nil early, key-fallback via statusName, LatestStatuses dedup ordering (first entry wins), UUID normalization, and map-key dedup. The slices.Sort comparison pattern is correct for a map[string]struct{} return type.

No production code is touched, conventions match the existing client_test.go / client_env_test.go files in the same package, and the diff is entirely additive.

[github-actions]

Merged no-mistakes#312 (squash).