Change `return` to `$result` for method return values in refinements

@rajshivu is already working on this.

Since Feb 9, 2026.

• #145 by @rajshivu — open

`return` is a statement, and it's strange to have it as a variable to represent the return value.
Therefore, we could change it for `result`. But since result can be an actual variable that represents something other than the return value we, we can try using `$result`.

This would mean a small change in the grammar, probably, and a change in replacing the return value.
Ps: the _ should still work in any case

Example Before:
```java
@Refinement("return > 0")
int test2 (){
return 10;
}
```
Example After:
```java
@Refinement("$result > 0")
int test2 (){
return 10;
}
```

Start by locating the refinement grammar and the code that replaces or checks return values; the issue mentions both but names no files or tests. Compare the existing `return` and `_` handling with the proposed `$result` syntax, and consider the open pull request before starting. Done means the new syntax works without breaking existing behavior.

Written by the indexing model from the issue text.