Update how long to beat extension

[ridemountainpig]

Description

Fix: update to new API endpoint.

Screencast

Checklist

• I read the extension guidelines
• I read the documentation about publishing
• I ran npm run build and tested this distribution build in Raycast
• I checked that files in the assets folder are used by the extension itself
• I checked that assets used in the README are located outside the metadata folder if they were not generated with our metadata tool

[raycastbot]

Thank you for your contribution! 🎉

🔔 @Cronos87 @whitespacecode @7splay @pernielsentikaer you might want to have a look.

You can use this guide to learn how to check out the Pull Request locally in order to test it.

📋 Quick checkout commands

BRANCH="how-long-to-beat"
FORK_URL="https://github.com/ridemountainpig/extensions.git"
EXTENSION_NAME="how-long-to-beat"
REPO_NAME="extensions"

git clone -n --depth=1 --filter=tree:0 -b $BRANCH $FORK_URL
cd $REPO_NAME
git sparse-checkout set --no-cone "extensions/$EXTENSION_NAME"
git checkout
cd "extensions/$EXTENSION_NAME"
npm install && npm run dev

We're currently experiencing a high volume of incoming requests. As a result, the initial review may take up to 10-15 business days.

[greptile-apps]

Greptile Summary

This PR updates the HowLongToBeat extension to use the new upstream API endpoints, replacing /api/find/ and /api/find/init with /api/bleed/ and /api/bleed/init respectively. The change is minimal and straightforward, with a changelog entry and a one-line constants update.

Confidence Score: 5/5

Safe to merge — the only finding is a P2 style issue with the changelog date format.

All findings are P2 or lower. The core change (API endpoint update) is a clean two-constant swap with no logic concerns.

No files require special attention.

Important Files Changed

Filename	Overview
extensions/how-long-to-beat/CHANGELOG.md	Adds new [Fixes] entry for the API endpoint update; uses a hardcoded date instead of the required {PR_MERGE_DATE} placeholder.
extensions/how-long-to-beat/src/constants.ts	Updates two API search endpoint constants from /api/find/ to /api/bleed/ to match the new upstream HLTB API.

Prompt To Fix All With AI

Fix the following 1 code review issue. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 1
extensions/how-long-to-beat/CHANGELOG.md:3
The new changelog entry uses a hardcoded date instead of the `{PR_MERGE_DATE}` placeholder. New entries should use the placeholder so the date is automatically populated when the PR is merged.

```suggestion
## [Fixes] - {PR_MERGE_DATE}
```

_{Reviews (2): Last reviewed commit: "Update CHANGELOG.md" | Re-trigger Greptile}

[0xdhrv]

Looks good to me, approved ✅

[github-actions]

Published to the Raycast Store:
https://raycast.com/Cronos87/howlongtobeat

[raycastbot]

🎉 🎉 🎉

We've rewarded your Raycast account with some credits. You will soon be able to exchange them for some swag.

[win7guru]

Thank you