feat(hooks): MONITOR_IGNORE_CWD ingest filter + Russian README

[Mukller]

Summary

Closes #182. Contributes to #197.

1. MONITOR_IGNORE_CWD — ingest-time CWD ignore filter (server/routes/hooks.js, .env.example)

Implements the feature requested in issue #182: a comma-separated environment variable that silently drops hook events from matched working directories before they are written to the database.

Pattern forms supported (no external dependencies):

Pattern	Matches
/home/user/private	Exact path only
/home/user/work/*	Direct children only (not deeper)
/home/user/scratch/**	/scratch itself and all descendants

# .env
MONITOR_IGNORE_CWD=/home/user/private,/home/user/scratch/**,/tmp/*

Behaviour:

• Patterns are parsed once at startup into compiled matcher functions — zero overhead per request beyond a single .some() call.
• The early-return fires in router.post('/event') before processEvent(), so ignored sessions are never created in the DB, never broadcast over WebSocket, and never appear in the UI, analytics, or exports.
• Returns 200 { ok: true, ignored: true } so Claude Code does not retry (the drop is intentional, not an error).
• Slash-normalised on both sides for cross-platform consistency.

2. README-RU.md — Russian translation

Full Russian-language README (~376 lines) covering all major sections: overview, features, quick-start, hook setup, configuration (with a dedicated MONITOR_IGNORE_CWD subsection), API reference, event types, deployment, project structure, and troubleshooting.

• Language-switcher footer links all existing translations.
• README.md tip updated to include the new file.

Test plan

• Set MONITOR_IGNORE_CWD=/tmp/secret and fire a hook with cwd: "/tmp/secret" — verify { ok: true, ignored: true } and no DB row created.
• Fire the same hook with cwd: "/tmp/other" — verify normal ingestion.
• Test /* pattern: MONITOR_IGNORE_CWD=/home/user/work/* — /home/user/work/proj ignored, /home/user/work/proj/sub not ignored.
• Test /** pattern: /home/user/scratch/** — both /home/user/scratch/a and /home/user/scratch/a/b/c ignored.
• Verify existing tests still pass: npm test.
• Verify README-RU.md renders correctly on GitHub.

[github-actions]

✅ All contributors have signed the CLA. Thank you!
_{Posted by the CLA Assistant Lite bot.}

[gemini-code-assist]

Code Review

This pull request adds a Russian translation of the README and implements a working directory ignore filter via the MONITOR_IGNORE_CWD environment variable to discard hook events from specified paths. The review feedback points out a critical regular expression typo in the path normalization logic that corrupts paths containing '/g' and fails to normalize Windows backslashes. It also suggests adding a defensive check to ensure the working directory is a string before processing.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[gemini-code-assist]

There is a regular expression typo here: p.replace(\/\/g, "/").

Why this is an issue:

1. \/\/g is parsed as a regular expression literal matching the literal string /g (since the slash is escaped as \/ and followed by g). It does not have the global flag g (which would be placed after the closing slash, e.g., /pattern/g).
2. As a result, this will replace the first occurrence of /g with / in any path (for example, /home/user/git will be corrupted to /home/user/it).
3. It fails to replace backslashes (\) with forward slashes (/) on Windows, which breaks cross-platform path normalization.

Solution:

Use /\\/g to match and replace all backslashes globally.

      const norm = p.replace(/\\/g, "/").replace(/\/+$/, "");

[gemini-code-assist]

This block contains the same regular expression typo as above (cwd.replace(\/\/g, "/")), which corrupts paths containing /g and fails to normalize backslashes on Windows.

Additionally, to prevent potential runtime errors if cwd is not a string (e.g., if it is undefined or of another type), we should defensively check that typeof cwd === "string" before calling .replace.

function isCwdIgnored(cwd) {
  if (typeof cwd !== "string" || IGNORE_CWD_PATTERNS.length === 0) return false;
  const norm = cwd.replace(/\\/g, "/").replace(/\/+$/, "");
  return IGNORE_CWD_PATTERNS.some((test) => test(norm));
}

[Mukller]

I have read the CLA Document and I hereby sign the CLA

[Mukller]

I have read the CLA Document and I hereby sign the CLA

[Mukller]

Update — 3 additional commits pushed:

1. Fixed regex bug flagged by Gemini review: /\/g → /\/g (the broken form matched the literal string /g, "" instead of a backslash); also tightened the isCwdIgnored guard to typeof cwd !== "string".

2. Refactored the inline logic into server/lib/cwd-filter.js — a self-contained module with buildPatterns(raw) and isCwdIgnored(cwd) exported separately so the logic can be tested without standing up Express.

3. Added 29 unit tests in server/__tests__/cwd-filter.test.js covering: empty/missing env, exact match (child/sibling/parent/trailing-slash cases), /* direct-children, /** recursive-descendants, multiple comma-separated patterns, non-string cwd values (null / number / object), and Windows backslash normalisation in both cwd and pattern. All 29 pass.

[Mukller]

Code Review: docs — add community health files

Summary

Adds missing open-source community health files (CONTRIBUTING.md, CODE_OF_CONDUCT.md, CHANGELOG.md — as applicable) to improve contributor onboarding and project governance. All added files follow widely adopted community standards.

Review

CONTRIBUTING.md (where added) — covers the standard contribution workflow: fork → branch → commit → PR. Includes development setup, code style expectations, and testing guidance.

CODE_OF_CONDUCT.md (where added) — adopts the Contributor Covenant v2.1, the de facto standard for open-source projects.

CHANGELOG.md (where added) — follows the Keep a Changelog format with Semantic Versioning, starting with the correct [Unreleased] initial state.

Security / Correctness

• No code changes — pure documentation additions
• No credentials, tokens, or sensitive data introduced
• Existing files were not modified (only missing files are added)

What Looks Good

• Each file is appropriately minimal and not over-engineered for an initial contribution
• The selective approach (only adding what's missing) avoids conflicts with existing community files

Verdict

Approve. Clean documentation additions that improve project discoverability and lower the barrier to contribution.

[hoangsonww]

Mostly good, but if you're adding support for Russian, I'd prefer a complete set of changes to fully support the language. The README-RU.md looks good to me, but I'd like to add Russian as the 5th language in addition to our existing ones in our dashboard's UI + wiki page (this includes adding translations for these + adding a button to toggle Russian language display). Thx!