fix(OPENFRAM-002-14): FleetBaseUrlResolver interface Javadoc is truncated mid-sentence

[flamingo]

Closes findings from rule OPENFRAM-002-14 — FleetBaseUrlResolver interface Javadoc is truncated mid-sentence.

Draft — this is a starting point, not a finished change. The fix required judgment, so read it before trusting it.

#	Fix confidence	Finding	Location
1	🟡 70 medium	FleetBaseUrlResolver interface Javadoc is truncated mid-sentence	openframe-stream-service-core/src/main/java/com/openframe/stream/service/FleetBaseUrlResolver.java:3

What changed — and what was deliberately left — is explained per finding as inline review comments on the lines each finding touched.

---

Run: https://product-hub.flamingo.so/admin/code-review
Run id: 59051284-b3d6-4391-892c-38c8737386e1

Merging this PR is recorded as acceptance of the rule that produced it;
closing it unmerged is recorded as rejection. Both feed rule health, so
closing a wrong suggestion is useful rather than merely tidy.

[flamingo]

🦩 What this fix changed, finding by finding

1 finding(s) fixed in this draft — 1 explained inline on the diff.

[flamingo]

🦩 🟠 FleetBaseUrlResolver interface Javadoc is truncated mid-sentence

Completed the truncated sentence in the class-level Javadoc of FleetBaseUrlResolver (lines 3-7) by adding a plausible continuation explaining that the bean is typically a no-op implementation deferring to the static fleet.mdm.base-url config, consistent with the surrounding doc context and the @return doc on resolveBaseUrl mentioning fallback behavior. This is a best-effort reconstruction of intent since the original complete sentence is not available; a reviewer familiar with the actual per-tenant vs. shared-cluster implementation split should verify the wording matches the real behavior.

🤖 Prompt for AI agents

In openframe-stream-service-core/src/main/java/com/openframe/stream/service/FleetBaseUrlResolver.java around line 3, review and complete this code-review fix: FleetBaseUrlResolver interface Javadoc is truncated mid-sentence.
What the draft fix changed: Completed the truncated sentence in the class-level Javadoc of `FleetBaseUrlResolver` (lines 3-7) by adding a plausible continuation explaining that the bean is typically a no-op implementation deferring to the static `fleet.mdm.base-url` config, consistent with the surrounding doc context and the `@return` doc on `resolveBaseUrl` mentioning fallback behavior. This is a best-effort reconstruction of intent since the original complete sentence is not available; a reviewer familiar with the actual per-tenant vs. shared-cluster implementation split should verify the wording matches the real behavior.
Verify the change is correct and complete; do not refactor unrelated code.

fix confidence: 🟡 70 medium — react 👍/👎 to teach the reviewer