Probably? hence why this is in Clever rather than best practices

It doesn't, it turns 9s into 10s and replaces the match with the new number

Could I know their names?

A couple of days ago, two of your solutions of blue kata were invalidated by a mod, that is why your rank slightly dropped. These are old solutions, from July 2020. All your recent solutions are valid and you still have points for them.
In total you have a few (4 or 6 or so, would have to count exactly and it's not easy) solutions invalidated by a mod, most probably because they were recognized as copies from other solutions or somewhere from internet.

I had 2909 points & %73.5, couple of days ago I noticed that they were reduced to 2878 & %70.5, previous solved kata weren't counted.

Here it said Blue code challenge completed == 24, Although I got about at least 26 complete valid solutions, Also it says 145 yellow katas were completed although I have 147.
https://www.codewars.com/users/ShehabMuhammad/site-events

And you can you check the katas here, https://www.codewars.com/users/ShehabMuhammad/completed

Not only the last 4 kyu kata wasn't counted 32 points were deducted from my already existing points. Why this happened?

BTW, here's how that test looks like: (I don't think it's much of a spoiler)

var a = add(1)(2);
var b = add(3)(4);

Then it checks that a == 3 and b == 7. I hope that helps.

Although the first example was not included in the instructions, But should a == 3, after a = add(1)(2) and a(1) ?

No, it should be 4 then. (not a itself, but the result of calling a(1) afterwards)

Yes, The "it must store values" is the only test that it doesn't pass.

I think this might be because, if a = add(1)(2). then if called a(1), and tried to check 'a' value again without calling it, it'll be 4.

But if I called a(9) for example, It'll be 12 (3 + 9 == 12), It'd preserve the original value.

Although the first example was not included in the instructions, But should a == 3, after a = add(1)(2) and a(1) ?

I think that's everything. Have you tried submitting your code?

I mean, it literally shows you an example after that text. It just means you can store an intermediate result in a variable, and then call it again.

If you implement it correctly, there's no real difference.

It wasn't completely clear what the order of the arrays should be for case multiple solutions, so I just did what was easiest. It's probably based on order of first element though.

Yes, I didn't think I was going to solve it, But I came up with an idea and didn't believe myself when it passed all tests.