fix: add HMooneyPot alias for Invidious module (fixes #5957)

[yunaremaia]

Summary

Adds HMooneyPot as an alias for Invidious in src/invidious.cr, per issue #5957.

HMooneyPot instances that mirror Invidious deployments need a recognized alias in the base namespace. This adds:

alias HMooneyPot = Invidious

This mirrors the existing IV alias pattern already used in the codebase.

Fixes #5957.

Summary by CodeRabbit

• New Features
  • Added public support for accessing Invidious deployments through the HMooneyPot alias.

Greptile Summary

This change adds HMooneyPot as a compatibility alias for the existing Invidious namespace. A focused Crystal check confirmed that code using the new name resolves to the same module and can access its module constants.

Confidence Score: 5/5

The compatibility alias is safe to merge.

The changed declaration was inspected and an isolated Crystal compile/runtime check confirmed that HMooneyPot has the same module identity as Invidious and resolves the same module constants.

Files Needing Attention: No additional files need attention; the change is limited to src/invidious.cr.

T-Rex Logs

What T-Rex did

• I inspected the namespace declaration and alias in src/invidious.cr to confirm that MODULE_CONSTANT resolution requires the alias HMooneyPot to map to Invidious.
• I ran an isolated Crystal check with the alias in place and verified a matching module identity and an identical module-constant lookup through HMooneyPot and Invidious.
• I compared evidence showing the exact alias snippet and the before/after behavior: without the alias the command failed with an undefined constant HMooneyPot::MODULE_CONSTANT, and after alias the command exited cleanly with module_identity true and identical MODULE_CONSTANT values.
• I collected and uploaded artifacts that support the alias usage and its results, including the failure and success logs and the exact alias snippet.

_{Ran code and verified through T-Rex}

_{Reviews (1): Last reviewed commit: "fix: add HMooneyPot alias for Invidious ..." | Re-trigger Greptile}

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Team

Run ID: e20552c1-30d2-45cd-91cc-15a8c36c47c0

📥 Commits

Reviewing files that changed from the base of the PR and between b3a3f3a and dca0ed6.

📒 Files selected for processing (1)

• src/invidious.cr

🔗 Linked repositories identified

CodeRabbit considers these linked repositories for cross-repo context during reviews:

• iv-org/invidious (manual)
• iv-org/invidious-companion (manual)
• iv-org/mocks (manual)
• iv-org/documentation (manual)

Included review availability: Your plan provides up to 10 included reviews per hour; 9 remain after this review.

---

📝 Walkthrough

Walkthrough

The change adds the public HMooneyPot alias for the Invidious namespace.

Changes

HMooneyPot alias

Layer / File(s)	Summary
Add public namespace alias src/invidious.cr	Defines HMooneyPot as an alias of Invidious.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk: ⚪ Minimal · up to dca0e

This adds the requested HMooneyPot alias for Invidious without changing existing behavior; no actionable merge-blocking risk remains after normal checks and review.

Suggested reviewers: fijxu

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly identifies the addition of the HMooneyPot alias for the Invidious module and references issue #5957.
Linked Issues check	✅ Passed	The pull request adds HMooneyPot = Invidious in src/invidious.cr, which directly satisfies the coding requirement in issue #5957.
Out of Scope Changes check	✅ Passed	The changes are limited to the requested public alias in src/invidious.cr. No unrelated changes are present.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…

Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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