Remove project title from README

[lyonzin]

Removed the project title 'knowledge-rag' from the README.

Summary

Closes #

Type of change

• feat — new feature
• fix — bug fix
• docs — documentation only
• refactor — no behavior change
• perf — performance improvement
• test — adding or improving tests
• chore — tooling, deps, CI
• BREAKING CHANGE (explain in Migration section below)

What changed

Why

---

7 Pillars Quality Gate

Mark each item. CI enforces these via the quality-gate.yml workflow.

1. Security

• No new secrets, tokens, or credentials in the diff (gitleaks will block)
• No new use of eval, exec, subprocess shell=True, pickle.loads on untrusted input, or arbitrary deserialization
• New dependencies (if any) reviewed for known CVEs and license compatibility
• Path traversal, command injection, and SSRF surfaces explicitly considered for any new I/O code

2. Stability

• All existing tests still pass on Linux + Windows × Python 3.11/3.12
• New behavior covered by tests; tests are deterministic (no time.sleep / network / OS-scheduler dependencies)
• Coverage does not regress (codecov gate)
• No tests were skipped, deleted, or marked xfail to make the PR pass

3. Memory leak

• Long-lived objects (orchestrator, watcher, cache) are bounded
• New caches have eviction policy (LRU, TTL, or explicit size limit)
• No new global state that grows unbounded with usage
• If you added a new module that loads heavy resources, consider lazy initialization

4. Versatility

• Works on Linux, Windows, macOS (paths, line endings, locale considered)
• Works on Python 3.11, 3.12, 3.13 (no Python-version-specific syntax without fallback)
• No hardcoded paths, locales, or encodings (use pathlib.Path, encoding="utf-8" explicit)
• If you touched a parser, all 20 supported formats still parse correctly

5. Scalability

• No O(n²) or worse algorithms on user-controlled inputs
• Benchmark impact considered (run pytest bench/ locally if you touched search/index/embed)
• If perf regression > 10% in any metric, justification provided below
• Concurrency safety: no new shared mutable state without lock or documented thread confinement

Performance impact (required if you touched mcp_server/server.py, mcp_server/ingestion.py, or bench/):

metric          before    after    delta
search p95      ___ ms    ___ ms   ___%
index docs/sec  ___       ___      ___%
RSS @ 1k docs   ___ MB    ___ MB   ___%

6. Versioning

• If this is user-facing change: bumped version in pyproject.toml, mcp_server/__init__.py, and npm/package.json atomically
• If this is a breaking change: bumped MAJOR, added migration notes in CHANGELOG, marked BREAKING CHANGE: in commit footer
• CHANGELOG updated with entry under ## Unreleased in README.md
• Public API surface (mcp_server/server.py MCP tool decorators) unchanged, OR breaking changes documented

7. Quality

• ruff check passes
• ruff format --check passes
• Type hints on new public functions (mypy --strict clean for new files)
• Docstrings on new public functions (used by interrogate)
• Cyclomatic complexity reasonable (radon cc --max=C)
• No dead code (vulture would not flag new code)
• PR is reasonably sized (< 500 lines of diff preferred; bigger PRs split or justify)

---

Migration / Breaking changes

N/A

Test plan

• pytest tests/ -v passed locally
• pre-commit run --all-files clean
• Manual smoke test:

Documentation

• Updated README.md (if user-facing)
• Updated docs/ (if applicable)
• Added entry to ## Unreleased in README CHANGELOG section

Reviewer checklist

• Reviewed line-by-line
• Verified the 7 pillars CI status checks are green
• Verified no obvious adversarial implications
• Approved performance impact

---

By submitting this PR I confirm I read CONTRIBUTING.md and agree to the Code of Conduct.

Greptile Summary

Removes the redundant visible project-title heading from the README while retaining the banner, metadata, badges, and descriptive content.

• Deletes the # knowledge-rag heading below the project banner.

Confidence Score: 5/5

The PR appears safe to merge because it only removes a redundant README heading.

The documentation remains coherent, and the change does not affect code, configuration, links, or runtime behavior.

Important Files Changed

Filename	Overview
README.md	Removes a single redundant H1 heading without affecting documentation links, metadata, or runtime behavior.

_{Reviews (1): Last reviewed commit: "Remove project title from README" | Re-trigger Greptile}

Summary by CodeRabbit

• Documentation
  • Removed the redundant top-level project heading from the README for a cleaner presentation beneath the banner image.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 3f7fa64c-5c48-4334-bdac-f8027fdb5415

📥 Commits

Reviewing files that changed from the base of the PR and between c6213aa and d6730e5.

📒 Files selected for processing (1)

• README.md

💤 Files with no reviewable changes (1)

• README.md

Included review availability: Your plan provides up to 2 included reviews per hour; 1 remains after this review.

---

📝 Walkthrough

Walkthrough

The README no longer contains the top-level knowledge-rag heading before the centered badge block.

Changes

README cleanup

Layer / File(s)	Summary
Remove the top-level README heading README.md	Removed the # knowledge-rag heading before the centered badge block.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk: ⚪ Minimal · up to d6730

This change only removes a redundant project-title heading from the README and does not affect runtime behavior, links, or configuration; no actionable merge-blocking risk remains.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes the README change to remove the project title.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches 💡 1

🛠️ Fix failing CI checks 💡

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch lyonzin-patch-1

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}