docs: post-PR #41 nits — fallow snapshot refresh + drop shipped golden-queries from roadmap

[SutuSebastian]

Summary

Two small follow-ups surfaced when checking the doc set against the codebase post-PR #41:

1. docs/research/fallow.md — date stamp 2026-05-01 → 2026-05-02; added a one-liner under "Adjacent — also shipped post-refresh" naming PR refactor: lift cli/* engine helpers into application/* (close all layer-reversal imports) #41 (cli/* → application/* engine lift). Worth tracking there because it's the architectural prereq that unblocks the HTTP transport (serve is the next backlog item up).
2. docs/roadmap.md — golden queries are operational (scripts/query-golden.ts runs in bun run check + CI on every PR; canonical doc = docs/golden-queries.md). Per docs-governance Rule 2 (shipped items leave the forward-looking section), removed from "Next".

Behavior change

None — docs only.

Test plan

• bun run check passed locally.
• CI green.

[changeset-bot]

⚠️ No Changeset found

Latest commit: d942e29

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]

Warning

Rate limit exceeded

@SutuSebastian has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 5 minutes and 57 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: e8013cc3-95a4-4464-9ed8-2ca22b50c564

📥 Commits

Reviewing files that changed from the base of the PR and between 0134944 and d942e29.

📒 Files selected for processing (2)

• docs/research/fallow.md
• docs/roadmap.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/post-pr41-nits

---

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

• X
• Mastodon
• Reddit
• LinkedIn

_{Review rate limit: 0/1 reviews remaining, refill in 5 minutes and 57 seconds.}

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