Fix npm bugs, add thread reply processing

[lionuncle]

Summary

• Fix ModuleNotFoundError on npm installs — from rpr import __version__ fails when run via the Node shim; added _get_version() fallback that parses the sibling __init__.py
• Fix re-review loop — rpr was feeding its own prior reviews back as context, causing infinite commenting instead of approving. Now tags outgoing reviews with <!-- rpr --> and filters them out on subsequent runs
• Add thread reply processing — when re-running, rpr checks its own review threads for human replies. If someone says "fixed", it fetches the current code and verifies with Claude before replying/resolving. If someone provides a technical explanation, it acknowledges and resolves the thread
• Bump version to 0.1.4 across __init__.py, pyproject.toml, and package.json

How thread processing works

1. GraphQL fetches all unresolved review threads, filters to rpr's own (by marker)
2. Identifies threads with human replies (excludes rpr's own replies)
3. Fetches current file content at HEAD for each thread's location
4. Single batched Claude call verifies all pending threads
5. Replies in-thread and resolves confirmed threads via GraphQL

Test plan

• npm install -g @dedev-llc/rpr && rpr <PR> — no more ModuleNotFoundError
• Run rpr twice on the same PR — second run should not re-comment on its own feedback
• Reply "fixed" to an rpr thread, push a fix, re-run — thread should be verified and resolved
• Reply with a technical explanation to an rpr thread, re-run — thread should be resolved
• rpr <PR> --dry-run — thread processing should be skipped

🤖 Generated with Claude Code