Fix: safe tooltip pipeline overwrite + menu/play/referral/pending-action hardening

[gamblecodezcom]

User description

Motivation

• Ensure the tooltip loader always overwrites the system file, validates JSON with python3, and cannot accidentally commit unrelated staged files.
• Enforce single-active-menu UX so inline callback navigation never leaves stale/stacked cards visible.
• Make Play button behavior deterministic between Browser vs Mini App and ensure Discord links always open externally.
• Harden pending-action timeout semantics, user-facing labels, and mitigate HTML injection in referral sharing.

Description

• Updated load_tooltips.sh to enable set -euo pipefail at the top, use python3 -m json.tool for validation, write tooltips via cat > "$OUT" (overwrite), and added a staged-index guard to abort if files other than .gitignore are staged; commits are scoped to .gitignore only and the script prints the same success message.
• Implemented single-active-menu helpers clearOldMenus(ctx) and replyMenu(...), added callback-query hygiene middleware to delete the source callback card before sending follow-ups, and switched menu renderers (settings, main, persistent) to use replyMenu so old menus are removed before new ones are posted.
• Added unified play helpers (getPlayMode, getPlayLink, getPlayButton, playButtonMarkup) and replaced all Play button usages so Browser mode uses a plain url external link (https://runewager.com/r/GambleCodez) and Mini App mode uses web_app metadata; ensured settings toggle persists immediately and re-renders with clearOldMenus.
• Added getDiscordLink(...) sanitation to ensure Discord URLs are raw external HTTPS links, introduced ACTION_LABELS and a robust evaluatePendingActionTimeout(...) with numeric coercion and exact-15-minute boundary semantics, and escaped referral codes in referralShareHTML(...) to prevent HTML injection.
• Updated tests: expanded test/unit.test.js and test/smoke.test.js to cover tooltip loader presence, staged-guard behavior, menu hygiene, play-button determinism, catch-all regex detection, command extraction improvements, pending-action boundary and labeling, referral HTML escaping, and TestAll summary expectations.
• Tidied environment examples by keeping BOT_PRIVACY_MODE="disabled", removing legacy BOTPRIVACYMODE alias, and documenting core env keys used by runtime checks.

Testing

• Ran unit and smoke suites via npm test --silent, which completed successfully.
• Verified load_tooltips.sh syntax with bash -n load_tooltips.sh and validated the script writes/overwrites /var/www/html/Runewager/data/tooltips.json and validates it with python3 -m json.tool.
• Ran quick repository checks used by the smoke tests (search/grep validations and updated test expectations) and confirmed updated smoke/unit tests passed locally.

---

Codex Task

---

CodeAnt-AI Description

Prevent accidental commits when running the tooltip loader script

What Changed

• The tooltip loader now aborts if any files other than .gitignore are staged, preventing unrelated files from being committed when updating tooltips
• When such staged files exist the script prints a clear message and exits with a non-zero status instead of proceeding to commit and push
• If only .gitignore is staged, the script continues to commit and push as before

Impact

✅ No accidental commits during tooltip updates
✅ Clearer failure message when other files are staged
✅ Safer tooltip deployment

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.

[codeant-ai]

CodeAnt AI is reviewing your PR.

---

Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn

[coderabbitai]

Warning

Rate limit exceeded

@gamblecodezcom has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 22 minutes and 52 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, 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 have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between f24e267 and 66b2d43.

📒 Files selected for processing (1)

• load_tooltips.sh

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch codex/perform-full-audit-and-implementation-for-runewager-bot-o35p2n

---

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 and usage tips.}

[codeant-ai]

Nitpicks 🔍

🔒 No security issues identified

⚡ Recommended areas for review set -euo interaction With set -euo pipefail enabled, a non-zero exit from the git diff command will cause the whole script to terminate unexpectedly. The current command substitution does not guard against git pathspec errors or other failures. Pathspec/Filtering The pathspec used in the staged-files check (':!.gitignore') may not behave as intended across Git versions or shells. This can yield false positives/negatives or cause the git command to fail, making the guard unreliable. UX / CI impact The script exits with failure if any non-.gitignore file is staged. This is intentional, but could break automated CI workflows if they stage files transiently; consider logging more context or offering an override mechanism for automation.

[codeant-ai]

CodeAnt AI finished reviewing your PR.