Skip to content

KS78: Sync docs — ROADMAP v0.7.5, CHANGELOG, MCP tool count#23

Closed
Liorrr wants to merge 3 commits intomasterfrom
chore/ks78-sync-docs
Closed

KS78: Sync docs — ROADMAP v0.7.5, CHANGELOG, MCP tool count#23
Liorrr wants to merge 3 commits intomasterfrom
chore/ks78-sync-docs

Conversation

@Liorrr
Copy link
Copy Markdown
Contributor

@Liorrr Liorrr commented Apr 10, 2026

Summary

  • Updated docs/ROADMAP.md from stale v0.5.0 to current v0.7.5 state
  • Added CHANGELOG.md v0.7.5 section covering KS67-KS77 work
  • Fixed MCP tool count across docs (was 9 in some places, now correctly 12)

Files changed

  • docs/ROADMAP.md — Full rewrite to v0.7.5 state
  • CHANGELOG.md — Added v0.7.5 section
  • CONTRIBUTING.md — MCP tool count 9→12
  • docs/ARCHITECTURE.md — Updated MCP tool list

Test plan

  • No code changes — docs only
  • Verify tool count matches actual MCP server (12 tools)

🤖 Generated with Claude Code

Liorrr and others added 2 commits April 10, 2026 05:20
- Rewrite ROADMAP.md from stale v0.5.0 to current v0.7.0 state
- Add CHANGELOG [0.7.5] section covering KS67-KS77 changes
- Fix MCP tool count: 9 -> 12 in CONTRIBUTING.md, CHANGELOG.md, ARCHITECTURE.md
- Update SECURITY.md supported version: 0.5.x -> 0.7.x
- List all 12 MCP tools where tool names are enumerated

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
- Remove merged supersession-demotion changes (hebbian_boosts type change,
  demotion→superseded_count rename, multiplicative demotion) that belong
  on a separate branch
- Keep only the recency tie-breaker epsilon (step 7c7) and google_result
  test fix from PR #13

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@greptile-apps
Copy link
Copy Markdown

greptile-apps Bot commented Apr 10, 2026

Greptile Summary

This is a docs-only sync PR (no code changes) that brings ROADMAP.md, CHANGELOG.md, CONTRIBUTING.md, SECURITY.md, and ARCHITECTURE.md up to date with the v0.7.5 release covering KS67–KS77.

Key updates:

  • CHANGELOG.md: new v0.7.5 section documenting schema-driven extraction, entity unification, configurable embedding, universal prompt, temporal boost, and importance scoring
  • docs/ROADMAP.md: full rewrite replacing the stale v0.5.0 prose with concise v0.7.5 state — however, the "Current State" section header reads v0.7.0 while all content describes v0.7.5 features (12 tools, KS73–KS77 additions)
  • CONTRIBUTING.md + docs/ARCHITECTURE.md: MCP tool count corrected from 9 → 12, with the full tool list consistent across all files
  • SECURITY.md: supported-version table bumped from 0.5.x to 0.7.x

Confidence Score: 4/5

Safe to merge after fixing the v0.7.0 → v0.7.5 label in docs/ROADMAP.md.

No code changes; all factual updates (tool count, version table) are consistent across files. The single concrete defect — the ROADMAP "Current State" header still saying v0.7.0 while the body describes v0.7.5 content — is a one-line fix but would leave the primary purpose of the PR (syncing to v0.7.5) visibly incomplete.

docs/ROADMAP.md — "Current State" section header should read v0.7.5, not v0.7.0.

Important Files Changed

Filename Overview
docs/ROADMAP.md Full rewrite to v0.7.5 state, but the "Current State" section header still says v0.7.0 — content and heading are mismatched.
CHANGELOG.md Added v0.7.5 section with accurate feature list; minor style inconsistency (-- vs —) in version heading.
CONTRIBUTING.md MCP tool count correctly updated from 9 to 12 in the crate table.
SECURITY.md Supported version correctly bumped from 0.5.x to 0.7.x to match the current release.
docs/ARCHITECTURE.md MCP tool description updated to list all 12 tools accurately; count and tool names are consistent with CHANGELOG and CONTRIBUTING.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[PR KS78: Docs Sync] --> B[CHANGELOG.md]
    A --> C[docs/ROADMAP.md]
    A --> D[CONTRIBUTING.md]
    A --> E[SECURITY.md]
    A --> F[docs/ARCHITECTURE.md]

    B --> B1["Add v0.7.5 section\n(KS67–KS77 changes)"]
    C --> C1["Rewrite from v0.5.0 → v0.7.5\n⚠️ header still says v0.7.0"]
    D --> D1["MCP tool count: 9 → 12"]
    E --> E1["Supported version: 0.5.x → 0.7.x"]
    F --> F1["MCP tool list: 7 tools → 12 tools\nAll tool names listed explicitly"]

    style C1 fill:#f9a,stroke:#f00
Loading

Reviews (1): Last reviewed commit: "KS78: Sync docs -- ROADMAP v0.7.5, CHANG..." | Re-trigger Greptile

Comment thread docs/ROADMAP.md Outdated
---

## Current State v0.5.0
## Current State -- v0.7.0
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Section header version mismatch (v0.7.0 vs v0.7.5)

Line 8 reads:

## Current State -- v0.7.0

But the content under this section describes v0.7.5 features: 12 MCP tools (added in v0.7.5), entity unification (KS73, v0.7.5), importance scoring (KS76, v0.7.5), configurable embedding (KS75, v0.7.5). The PR description also explicitly says the goal is to sync to "current v0.7.5 state". The heading version should match:

Suggested change
## Current State -- v0.7.0
## Current State -- v0.7.5

- docs/ROADMAP.md: "Current State" header said v0.7.0 but content
  describes v0.7.5 features (12 MCP tools, entity unification, etc.)
- CHANGELOG.md: v0.7.5 entry used "--" instead of em dash "—",
  inconsistent with all other version headings in the file

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Copy link
Copy Markdown

@greptile-apps greptile-apps Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Liorrr has reached the 50-review limit for trial accounts. To continue receiving code reviews, upgrade your plan.

@Liorrr
Copy link
Copy Markdown
Contributor Author

Liorrr commented Apr 10, 2026

Closing: branch contaminated with code changes from other worktrees. Recreating as clean PR.

@Liorrr Liorrr closed this Apr 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant