Skip to content

feat(doctor,hooks): loudly surface sustained vault-write failures (#243) - #250

Merged
CryptoJones merged 1 commit into
mainfrom
feat/243-vault-write-failure-alarm
Aug 14, 2026
Merged

feat(doctor,hooks): loudly surface sustained vault-write failures (#243)#250
CryptoJones merged 1 commit into
mainfrom
feat/243-vault-write-failure-alarm

Conversation

@CryptoJones

Copy link
Copy Markdown
Owner

Implements #243: one shared parser (hooks.vault_write_failure_streak, 64 KiB tail, never raises) behind both the new vault_writes doctor check (fail ≥5/24h with darwin TCC hint; write-probe with no residue; warn 1–4) and the SessionStart 'MEMORY WRITES ARE FAILING' banner. Troubleshooting doc section added. Manual FDA grant on the affected Mac remains operator work. 957 passed; ruff clean. Version 8.5.0.

Closes #243

🤖 Generated with Claude Code

Shared streak parser over hook-failures.log drives both a doctor
vault_writes check (fail at >=5 append_entry failures/24h, macOS TCC
remediation hint, direct write probe) and a SessionStart capsule banner
so the agent itself reports the outage. 64KiB tail read, never raises.

Closes #243

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Aug 14, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@CryptoJones, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 13 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 817244a7-f637-4621-b209-fbcd228802a8

📥 Commits

Reviewing files that changed from the base of the PR and between 0fb1808 and f9851ab.

⛔ Files ignored due to path filters (1)
  • uv.lock is excluded by !**/*.lock
📒 Files selected for processing (8)
  • CHANGELOG.md
  • docs/troubleshooting.md
  • pyproject.toml
  • src/omind/__init__.py
  • src/omind/hooks.py
  • src/omind/provision.py
  • tests/test_hooks.py
  • tests/test_provision.py

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.

Comment thread src/omind/provision.py
parser — the same one that drives the session-start banner — plus a direct
writability probe of the vault directory.
"""
from omind import hooks as _hooks
@CryptoJones
CryptoJones merged commit 191f49a into main Aug 14, 2026
16 checks passed
@CryptoJones
CryptoJones deleted the feat/243-vault-write-failure-alarm branch August 14, 2026 16:41
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.

feat(doctor): loudly surface sustained vault-write failures (silent memory loss)

2 participants