Two things - one you can check in about ten seconds, and one you probably want to fix in the question itself.

Check the raw author email, not the attribution. Append .patch to the commit URL:

https://github.com/Ale-Newport/Keyframes/commit/25c9badaeb306e7921d1b184e79372978421a91a.patch

The From: line is the address that was actually baked into the commit by your local git config. This matters because the avatar/attribution you see on the commit page and the contribution graph are not the same check - seeing your account linked on the commit is not proof that the author email matches a verified address. Things that show up here surprisingly often:

• a generic machine address such as [email protected]. Those can never be added to a GitHub account, so those commits can never count, no matter what you verify.
• a near-miss alias or a different case from the address you added.
• an author/committer split - the graph follows the author, so a rebase or a squash done by someone else can leave you as committer only.

Your example repo isn't public. From an unauthenticated request:

$ curl -s https://api.github.com/repos/Ale-Newport/Keyframes
{"message": "Not Found", "status": "404"}

So Ale-Newport/Keyframes is renamed, deleted, or private right now. Nobody reading this can verify your example against it, which is worth correcting if you want useful replies. It also matters for the diagnosis: if that repo is in fact private, its commits only ever render on your own view of the graph with "Private contributions" enabled, and never for logged-out visitors - so it is worth confirming whether you are looking at your graph while signed in, or in a logged-out/incognito window.

For completeness, the documented conditions are all of: the author email is on your account, the commit is on the default or gh-pages branch, and the repo is not a fork. The fork rule is the one that catches people - commits in a fork never count until they are merged into the parent.

On the rebuild: the docs confirm what you assumed, that adding the address rebuilds the graph automatically and that it can take up to 24 hours. There is no user-facing way to force it. Since you are past that window, the documented next step is exactly the .patch check above, and then Support with that output attached - see Troubleshooting missing contributions.

That framing is probably also how you get past the auto-close. "My contribution graph is missing commits" reads as a self-service question and gets routed accordingly. "Commit <sha> has author email <x> in its .patch, <x> is a verified address on my account, the commit is on the default branch of a non-fork repo, and it has not appeared after N days" is a concrete data inconsistency rather than a how-to, and it is the kind of report that the graph-rebuild team can act on.