fix(mcp): disclose blocked writers in project overviews #492
No reviewers
Labels
No labels
code-review
correctness
dos
performance
security
severity/high
severity/low
severity/medium
tech-debt
Kind/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
h-dv/code-index!492
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/overview-writer-contention"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
When another process holds the index database write lock, the daemon already reports
writer_blocked, but the MCPproject_overviewtool andcode-index://project/overviewresource drop it. Preserve the existing report on both surfaces so agents can distinguish write-lock contention from indexing work. Keep it absent when the daemon does not report blockage; do not invent a lock-holder identity.The real-daemon MCP regression holds
BEGIN IMMEDIATEacross a watched edit, verifies the episode identity and elapsed time on both overview surfaces and the existing stats/freshness surfaces, then releases the lock and verifies the edit lands and every blockage field clears. It fails before the fix and passes after it. The same omission was independently reproduced on installed v0.41.36 with the official signed Rust package.Validation: 68 targeted tests passed (disclosure contracts, derivation/surface registries, review honesty); MCP binary/test clippy with warnings denied, formatting and diff checks passed. No new CI lane, dependency, runtime state or timeout change.
Fixes #304.