Skip to content

feat(agent-runtime): keep search index fresh across file writes and workspace changes#444

Merged
yuniel-acosta merged 1 commit into
mainfrom
feature/358-keep-the-search-index-fresh-across-file-writes-and-local-workspace-changes
Apr 5, 2026
Merged

feat(agent-runtime): keep search index fresh across file writes and workspace changes#444
yuniel-acosta merged 1 commit into
mainfrom
feature/358-keep-the-search-index-fresh-across-file-writes-and-local-workspace-changes

Conversation

@yacosta738
Copy link
Copy Markdown
Contributor

  • Add post-write index sync (sync_written_path) after successful file_write
  • Add content_sha256 as trust boundary in plan_candidates() for freshness
  • Add regression tests for stale index detection (changed/deleted/renamed paths)
  • Add hash guard test for same-size/same-mtime rewrite detection
  • Add integration test proving own writes are searchable without manual rebuild
  • Update workspace-index spec with REQ-WIDX-011 (freshness guard) and REQ-WIDX-012 (v1 docs)
  • Archive SDD change 2026-04-05-search-index-freshness

Closes #358

…orkspace changes

- Add post-write index sync (sync_written_path) after successful file_write
- Add content_sha256 as trust boundary in plan_candidates() for freshness
- Add regression tests for stale index detection (changed/deleted/renamed paths)
- Add hash guard test for same-size/same-mtime rewrite detection
- Add integration test proving own writes are searchable without manual rebuild
- Update workspace-index spec with REQ-WIDX-011 (freshness guard) and REQ-WIDX-012 (v1 docs)
- Archive SDD change 2026-04-05-search-index-freshness

Closes #358
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Apr 5, 2026

Warning

Rate limit exceeded

@yacosta738 has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 21 minutes and 15 seconds before requesting another review.

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 21 minutes and 15 seconds.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: e84364b6-6131-4b45-8eb1-de98e31e6291

📥 Commits

Reviewing files that changed from the base of the PR and between 79080e4 and b2bfffc.

📒 Files selected for processing (15)
  • clients/agent-runtime/src/search/discovery.rs
  • clients/agent-runtime/src/search/index.rs
  • clients/agent-runtime/src/search/mod.rs
  • clients/agent-runtime/src/search/sqlite.rs
  • clients/agent-runtime/src/search/tests.rs
  • clients/agent-runtime/src/tools/code_search.rs
  • clients/agent-runtime/src/tools/file_write.rs
  • openspec/changes/archive/2026-04-05-search-index-freshness/design.md
  • openspec/changes/archive/2026-04-05-search-index-freshness/exploration.md
  • openspec/changes/archive/2026-04-05-search-index-freshness/proposal.md
  • openspec/changes/archive/2026-04-05-search-index-freshness/specs/workspace-index/spec.md
  • openspec/changes/archive/2026-04-05-search-index-freshness/state.yaml
  • openspec/changes/archive/2026-04-05-search-index-freshness/tasks.md
  • openspec/changes/archive/2026-04-05-search-index-freshness/verify-report.md
  • openspec/specs/workspace-index/spec.md
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feature/358-keep-the-search-index-fresh-across-file-writes-and-local-workspace-changes

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

Comment @coderabbitai help to get the list of available commands and usage tips.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Apr 5, 2026

✅ Contributor Report

User: @yacosta738
Status: Passed (12/13 metrics passed)

Metric Description Value Threshold Status
PR Merge Rate PRs merged vs closed 89% >= 30%
Repo Quality Repos with ≥100 stars 0 >= 0
Positive Reactions Positive reactions received 10 >= 1
Negative Reactions Negative reactions received 0 <= 5
Account Age GitHub account age 3082 days >= 30 days
Activity Consistency Regular activity over time 108% >= 0%
Issue Engagement Issues with community engagement 0 >= 0
Code Reviews Code reviews given to others 515 >= 0
Merger Diversity Unique maintainers who merged PRs 2 >= 0
Repo History Merge Rate Merge rate in this repo 90% >= 0%
Repo History Min PRs Previous PRs in this repo 201 >= 0
Profile Completeness Profile richness (bio, followers) 90 >= 0
Suspicious Patterns Spam-like activity detection 1 N/A

Contributor Report evaluates based on public GitHub activity. Analysis period: 2025-04-05 to 2026-04-05

@yuniel-acosta yuniel-acosta merged commit 82fa489 into main Apr 5, 2026
12 checks passed
@yuniel-acosta yuniel-acosta deleted the feature/358-keep-the-search-index-fresh-across-file-writes-and-local-workspace-changes branch April 5, 2026 18:45
@yacosta738 yacosta738 mentioned this pull request Apr 5, 2026
@sonarqubecloud
Copy link
Copy Markdown

sonarqubecloud Bot commented Apr 5, 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.

Keep the search index fresh across file writes and local workspace changes

2 participants