Skip to content

docs(readme): refresh with 2026-04-15 → 2026-05-02 hardening sprint#267

Merged
EtanHey merged 1 commit intomainfrom
docs/readme-2026-05-02-refresh
May 3, 2026
Merged

docs(readme): refresh with 2026-04-15 → 2026-05-02 hardening sprint#267
EtanHey merged 1 commit intomainfrom
docs/readme-2026-05-02-refresh

Conversation

@EtanHey
Copy link
Copy Markdown
Owner

@EtanHey EtanHey commented May 2, 2026

@orcClaude — overnight maintenance README refresh. Please review when you boot.

Summary

Verified facts (each line maps to a PR I read via gh pr view)

Out of scope

Test plan

  • orcClaude reviews phrasing + accuracy
  • No PR merge until reviewed (per overnight maintenance guardrail)

🤖 Generated with Claude Code


Note

Low Risk
Low risk documentation-only change; no code paths or runtime behavior are modified.

Overview
Updates README.md to expand the BrainBar section with build-provenance details (canonical checkout/clean tree enforcement and Info.plist build stamping).

Adds a new Recent Hardening (2026-04-15 → 2026-05-02) section summarizing merged reliability/security/test-gate work with links to the relevant PRs, plus an in-flight note for PR #251.

Reviewed by Cursor Bugbot for commit f197916. Bugbot is set up for automated code reviews on this repo. Configure here.

Note

Update README to document hardening sprint changes from 2026-04-15 to 2026-05-02

Refreshes README.md with a new 'Recent Hardening' section summarizing merged work across search recall, BrainBar reliability, deployment infrastructure, test gates, and security annotations for Swift MCPRouter tools. Also updates the BrainBar description to note that the build script rejects non-canonical or dirty checkouts and stamps Info.plist with GitCommit, GitDescribe, and BuildTimeUTC. Includes an 'In flight' subsection covering ongoing work such as a resizable dashboard panel, trigram FTS5, and KG atlas improvements.

Macroscope summarized f197916.

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.

Your free trial has ended. If you'd like to continue receiving code reviews, you can add a payment method here.

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 2, 2026

Warning

Rate limit exceeded

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

To keep reviews running without waiting, you can enable usage-based add-on for your organization. This allows additional reviews beyond the hourly cap. Account admins can enable it under billing.

⌛ 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: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: c457e6cc-1a8e-47b2-aaa0-85fa312a1f6a

📥 Commits

Reviewing files that changed from the base of the PR and between 06e1e4a and f197916.

📒 Files selected for processing (1)
  • README.md
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch docs/readme-2026-05-02-refresh

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
Review rate limit: 0/1 reviews remaining, refill in 59 minutes and 9 seconds.

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

@EtanHey EtanHey marked this pull request as draft May 2, 2026 14:59
@EtanHey
Copy link
Copy Markdown
Owner Author

EtanHey commented May 2, 2026

Held as draft per orcClaude (s:9). The maintenance pass content has /never-fabricate-clean receipts and can be salvaged, but the right hands for finalizing this README are the brainlayer repo workers themselves — pending one of them taking it over after the reliability sprint cascade (Phases 2-5 / PR #251 merge → Phase 4 rebases) settles. Ref: docs.local/plans/2026-05-02-brainlayer-reliability-hardening/README.md § Phase 6 + status log.

@EtanHey EtanHey force-pushed the docs/readme-2026-05-02-refresh branch from d25fe57 to f4392c9 Compare May 2, 2026 22:56
@EtanHey EtanHey marked this pull request as ready for review May 3, 2026 00:42
- Recent Hardening section traces each claim to a merged PR
- BrainBar build-script guards (#264, #265) called out at the install step
- Phase B preventive infra block (orchestrator#58, #60) connects deploy registry
  to the BrainBar build-stamp + canonical-build refuse layer
- In-flight PR #251 entry documents NSPanel revival + trigram FTS5 startup-safety
  guard (10K-chunk threshold) + preserved /tmp/brainbar.sock pub/sub plane

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@EtanHey EtanHey force-pushed the docs/readme-2026-05-02-refresh branch from f4392c9 to f197916 Compare May 3, 2026 00:42
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.

Your free trial has ended. If you'd like to continue receiving code reviews, you can add a payment method here.

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.

Your free trial has ended. If you'd like to continue receiving code reviews, you can add a payment method here.

@EtanHey EtanHey merged commit a7c30c7 into main May 3, 2026
6 checks passed
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