Can Serena users falsify a no-write repo-memory proof?

[nike-17]

Disclosure: I maintain Sverklo.

Serena is probably the sharpest comparison point for what I am trying to make falsifiable: before a coding agent edits, can a local tool show useful repo relationships instead of just sounding plausible?

I am not asking for stars or adoption. I am looking for one correction from people who already understand semantic coding-agent tooling.

From a repo root:

npm exec --yes --package=sverklo@latest -- sverklo prove --no-write --guided --markdown

Useful feedback would be one of:

• the proof picked the wrong central files
• the selected symbol is noisy or unimportant
• callers are technically references but not meaningful impact
• Serena already covers this better
• grep/ripgrep is plainly the better tool
• setup friction around Node/model cache/output

Public proof thread for receipts/corrections: sverklo/sverklo#79

Tracker for the proof sprint: sverklo/sverklo#85