Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@editors/vscode/README.md`:
- Around line 28-33: The README currently documents a symlink using the path
"$(pwd)/vera/editors/vscode" which only works when run from the parent of the
repo; update the docs to show two correct workflows: keep the existing
clone+symlink example for running from the parent, and add the alternative
symlink command using "$(pwd)/editors/vscode" for users who are already in the
repository root (reference the exact strings "$(pwd)/vera/editors/vscode" and
"$(pwd)/editors/vscode" in the README entry to make the distinction explicit).
- Line 68: The scope table documents the pipe operator incorrectly as `\|>`;
update the table row that uses the symbol `\|>` to instead use the actual
operator `|>` so the mapping to `keyword.operator.pipe.vera` is accurate (search
for the table entry containing `\|>` and replace it with `|>` in
editors/vscode/README.md).

In `@editors/vscode/syntaxes/vera.tmLanguage.json`:
- Around line 120-131: The current regex match
"\\b([A-Z][A-Za-z0-9_]*)(\\.)([a-z_][a-z_0-9]*)\\b" (which assigns the
"entity.name.function.effect-op.vera" capture) is too broad; narrow it so only
effect-qualified calls are matched. Replace this single generic rule with a
two-step approach: (1) add a rule to explicitly capture effect
declarations/names (store them in a repository or tag them as
"entity.name.type.effect.vera"), and (2) change the effect-op matcher to only
match when the qualifier is one of those effect names (or, as a simple
narrowing, require the qualifier to follow an explicit effect naming convention
such as ending with "Effect" or be matched via a lookbehind/backreference),
keeping the same capture names ("1" = effect type, "2" =
punctuation.accessor.vera, "3" = entity.name.function.effect-op.vera). Ensure
you remove or replace the broad "\\b([A-Z]...)(\\.)([a-z_]...)" rule so regular
qualified names are no longer highlighted as effect operations.