Skip to content

docs(research): add PR #39 to fallow.md + mark closed items in competitive-scan#40

Merged
SutuSebastian merged 1 commit intomainfrom
docs/refresh-post-pr39
May 2, 2026
Merged

docs(research): add PR #39 to fallow.md + mark closed items in competitive-scan#40
SutuSebastian merged 1 commit intomainfrom
docs/refresh-post-pr39

Conversation

@SutuSebastian
Copy link
Copy Markdown
Contributor

Two stale spots fixed:

  1. fallow.md Adjacent block: added PR feat(show + snippet): targeted-read CLI verbs + MCP tools #39 (targeted-read CLI: show + snippet + security hygiene fixes).
  2. competitive-scan-2026-04.md § 4 / § 5: marked PR feat(recipes): recipes-as-content registry — bundled .md + project-local .codemap/recipes/ #37 (recipes-as-content) and PR feat(show + snippet): targeted-read CLI verbs + MCP tools #39 (targeted-read) as ✅ shipped. Both were sitting as 'still backlog' even though their roadmap entries were already removed.

Pure docs honesty. No code change.

…d items in competitive-scan §4-§5

Two stale spots fixed:

1. fallow.md 'Adjacent — also shipped post-refresh' block: added PR #39 (targeted-read CLI: show + snippet + security hygiene fixes).

2. competitive-scan-2026-04.md § 4 'What moved to the roadmap': marked Recipes-as-content registry (PR #37) and Targeted-read CLI (PR #39) as ✅ shipped. Both were sitting as 'still backlog' even though their roadmap entries were removed at ship time. Updated § 5 'Open questions': 'Should recipes own their description?' is settled (PR #37 file-pair shape).

No code change; pure docs honesty.
@changeset-bot
Copy link
Copy Markdown

changeset-bot Bot commented May 2, 2026

⚠️ No Changeset found

Latest commit: 29d0e0d

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 2, 2026

Warning

Rate limit exceeded

@SutuSebastian has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 40 minutes and 50 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: defaults

Review profile: CHILL

Plan: Pro

Run ID: b99da38c-a31b-42a2-9306-1ab8413e00c5

📥 Commits

Reviewing files that changed from the base of the PR and between 7460b46 and 29d0e0d.

📒 Files selected for processing (2)
  • docs/research/competitive-scan-2026-04.md
  • docs/research/fallow.md
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch docs/refresh-post-pr39

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 40 minutes and 50 seconds.

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

@SutuSebastian SutuSebastian merged commit 8e99e92 into main May 2, 2026
10 checks passed
@SutuSebastian SutuSebastian deleted the docs/refresh-post-pr39 branch May 2, 2026 14:59
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