Looks like a bug. I can confirm that the threshold is not set differently on Code Golf. Thanks for the report, and sorry for the delayed empowerment.

I'm happy waiting longer to be able to edit - it's not something I need often so I won't be making too much work for edit reviewers. Just wanted to raise the bug so it isn't forgotten.

I recalced your abilities manually, so you should now have the ability to edit posts directly, but this does indicate an issue where the recalc script doesn't run or doesn't work correctly, so we'll have to look into it.

Thank you - that worked and I have the ability now.

Possibly related bug (probably too rare and unimportant to make a new Meta post, unlike you'd like me to):

Now that I have the Edit Posts ability, viewing my own suggested edit that was made before I had the ability shows the message "You can't approve or reject suggested edits because you haven't yet earned the Edit Posts ability".

I'm not sure if this is because the suggested edit predates my gaining the ability, or if this is because it's my own suggested edit. I would guess that neither of these reasons is a good reason to prevent someone approving a suggested edit, so maybe there's a bug somewhere.

This is mostly out of interest, as it's just one edit and it's not important.

It looks like it's because it's your suggestion. I just checked the code, and two conditions must apply: (you have the edit ability or it's your post), and it's not your own suggested edit. I guess it would make sense to drop that last part? If you have the ability now, you'd be able to make that edit directly, so it makes sense that you can approve your own edit. On the other hand, an astute user could game the system to rack up a bunch of free approved edits, which could feed into another ability someday. On the third hand... is that rare case something to guard against?

For now, I agree that the restriction on approving your own suggested edits is redundant. As you say, I could simply make the edit directly rather than via a suggestion now that I have the ability, so the restriction is an inconvenience rather than a real protection.

If at some point we introduce a third layer beyond "not able to edit" and "able to edit", then that would probably involve carefully rethinking everything anyway, so this restriction could be added back in then.

Just checked and I was wrong about the restriction being just an inconvenience. Since the Edit button below a post is replaced with "Review suggested edit", there is no way for me to edit that post until the suggested edit is approved.

I'd expect this to be a rare problem, as on most communities where someone has had enough suggested edits approved to get the ability, there will probably be enough reviewers around to approve such left over suggested edits. Mentioning just as an extra small argument in favour of removing the restriction.

The bug with blocking your previous suggested edits is now fixed. The main issue of why the ability wasn't recalculated remains.

Thank you! I've now been able to approve my old suggested edit.

Thanks for confirming the fix in prod. (We tested on the dev server where noisy edits don't get in anyone's way, but I didn't have a convenient test case here.)