fix(api): getRecommendationDetail 404s on hidden recs (closes #214)

[cristim]

Summary

• getRecommendationDetail previously called ListRecommendations which runs applyAccountOverrides, so a rec hidden by an account-service override silently 404d on deep-link (issue fix(api): getRecommendationDetail 404s on hidden recs instead of returning a 'filtered-out' marker #214). A deep-linked URL now returns the rec payload with a hidden_by marker instead.
• Suppressed recs (actively dismissed) still 404 — that case is intentional and a banner there would be noise.
• New Scheduler.GetRecommendationByID fetches by ID, applies suppressions, and checks override reasons without dropping the rec. overrideHiddenReasons names each failing dimension (enabled=false, engine, region, resource_type).
• RecommendationDetailResponse gains hidden_by []string (omitempty); TS RecommendationDetail interface gains optional hidden_by?: string[].

Test plan

• go test github.com/LeanerCloud/CUDly/internal/scheduler/... passes (3 new cases: visible / hidden-by-override / absent)
• go test github.com/LeanerCloud/CUDly/internal/api/... passes (new hidden_by case + updated detail tests using GetRecommendationByID mock with AssertExpectations)
• go build ./... clean
• Deep-link to a rec under enabled=false override: 200 with hidden_by: ["enabled=false"]
• Deep-link to a fully-suppressed rec: 404
• Deep-link to a genuinely absent rec: 404

[cristim]

@coderabbitai review

[coderabbitai]

Warning

Review limit reached

@cristim, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 22 minutes and 31 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 7ab7dda1-d10c-4dda-a8c7-8b874b2d30dc

📥 Commits

Reviewing files that changed from the base of the PR and between 4956d66 and 90073b6.

📒 Files selected for processing (12)

• frontend/src/api/recommendations.ts
• internal/api/handler_per_account_perms_test.go
• internal/api/handler_recommendations.go
• internal/api/handler_recommendations_test.go
• internal/api/mocks_test.go
• internal/api/types.go
• internal/config/store_postgres_recommendations.go
• internal/config/types.go
• internal/scheduler/scheduler.go
• internal/scheduler/scheduler_overrides_test.go
• internal/server/interfaces.go
• internal/testutil/mocks.go

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/214-wave12

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[cristim]

@coderabbitai full review

[coderabbitai]

✅ Actions performed

Full review triggered.

[cristim]

@coderabbitai review

[coderabbitai]

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.