docs(research): close fallow.md — peer-tool framing off-mission post #58#61
Merged
SutuSebastian merged 1 commit intomainfrom May 4, 2026
Merged
docs(research): close fallow.md — peer-tool framing off-mission post #58#61SutuSebastian merged 1 commit intomainfrom
SutuSebastian merged 1 commit intomainfrom
Conversation
PR #58 (just merged) corrected codemap's positioning: not unique, but in a specific niche of a SQLite-backed-code-index cohort with multiple peers (srclight, Sverklo, ctxpp, KotaDB, codemogger, etc.). fallow is one of many, not a yardstick. Under the new positioning, fallow.md's framing ("adoption candidates from fallow") is off-mission. Per docs-governance closure pattern (competitive-scan-2026-04.md precedent), close the doc with a status header pointing at the new canonical home + lift open items. Closure rationale captured at the top: - Status: Closed (2026-05) header explicit - Cohort positioning summarized + cross-ref to research note for full framing - Body preserved verbatim as historical record (Status snapshot below is the authoritative "what actually landed" log) - New adoption candidates (if any) get authored against open specs + primitive sources per non-goals-reassessment-2026-05 § 4, not against fallow source tree - Outstanding open items lifted to canonical homes: - C.9 plugin layer → in-flight PR #59 plan - C.10 LSP → covered by § 2.5 of research note (thin shim resolved) - C.11 coverage → shipped - Tier D defers (suppressions, fix engine, dupes, runtime intel) → aligned with § 3 ergonomic floors Original framing preserved verbatim under "Original framing (preserved verbatim from before 2026-05 closure)" subsection so historical readers can see what the doc said in its open phase. Per docs/README.md Rule 8 closing-research lifecycle. fallow.md stays in repo (not deleted) — historical context git log alone can't reconstruct.
|
|
Warning Rate limit exceeded
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 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. ✨ Finishing Touches🧪 Generate unit tests (beta)
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. Review rate limit: 0/1 reviews remaining, refill in 26 minutes and 45 seconds.Comment |
This was referenced May 4, 2026
4 tasks
SutuSebastian
added a commit
that referenced
this pull request
May 4, 2026
…remaining surfaces (#64) Audit of remaining `[Ff]allow` references after PRs #58, #61, #62 landed found 4 surfaces still treating fallow as a positioning peer (off-mission under the cohort framing locked in by PR #58): CLEANED UP: - docs/why-codemap.md:23 — non-goal parenthetical "(those are different products — e.g. fallow, knip, jscpd)" still elevated fallow as the primary static-analysis exemplar. Mirrors the PR #62 roadmap.md fix (lockstep per docs/README.md Single source of truth — non-goals canonical home is roadmap.md; consumer-facing framing in why-codemap.md must follow). Now: "(those are different products — e.g. knip, jscpd)". - docs/glossary.md:36 (audit definition) — "Distinct from `fallow audit` (that runs code-quality verdicts...)" singled out fallow as the comparator. Generalized to "Distinct from code-quality audit tools (e.g. knip for unused exports, jscpd for duplication, framework- specific complexity linters)". Same product-class point; no peer yardstick. - .agents/rules/docs-governance.md:36 — "(fallow, future plugins)" as the canonical example of repo-wide tool adoption was stale (fallow.md closed in PR #61). Updated to "(oxlint, future plugins)" + added a closure-precedent note pointing at fallow.md's status header and non-goals-reassessment-2026-05.md for current positioning. - .agents/skills/docs-governance/SKILL.md:86,88,136 — same staleness: "fallow" as ongoing-tracker example was stale; "fallow audit" in the re-derivable test list. Updated to oxlint + generic "static-analysis tooling"; preserved the fallow.md cross-ref as the CLOSED precedent (research notes that close with status header when peer framing goes off-mission). LEFT ALONE (legitimate): - docs/why-codemap.md:110-121 (comparison table) — different-product- classes consumer framing (Codemap vs fallow vs Aider RepoMap vs LSP). Not a peer yardstick under the cohort positioning; "agents can use Codemap AND fallow AND LSP" framing is honest about distinct slots. - docs/research/fallow.md (closed historical) — body preserved per PR #61. - docs/research/competitive-scan-2026-04.md (closed historical scan). - .agents/lessons.md:16 — "Never commit absolute local user paths" lesson with PR #58 historical context referencing the fallow clone path. Historical record; preserve. - .agents/skills/audit-pr-architecture/SKILL.md (5 mentions) — recommends `bunx fallow audit` as a static-analysis TOOL during PR audits. Different-product-class tool recommendation, not positioning. Borderline; left alone for now (could be genericized later as a separate concern). Net effect: every remaining `[Ff]allow` reference in the repo is either historical (closed research, lessons) or a different-product- class acknowledgement (consumer comparison table, static-analysis tool usage). Zero peer-yardstick framing remains in the load-bearing positioning surfaces.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Closes
docs/research/fallow.mdunder the corrected positioning from PR #58.Why: PR #58 retracted the "codemap is structurally unique" claim after the cohort fact-check (
srclight,Sverklo,ctxpp,KotaDB,codemogger, etc.). fallow is now correctly framed as one of many peers, not a yardstick. The research note's framing ("adoption candidates from fallow") is off-mission post-#58.What this PR does
Status: Closed (2026-05)header at the top offallow.md.non-goals-reassessment-2026-05.md.non-goals-reassessment-2026-05.md § 2.5(resolved as thin shim).Doc-governance compliance
docs/README.mdRule 8 closing-research lifecycle — slim research notes when adopt items have shipped;competitive-scan-2026-04.mdis the precedent.git logalone can't reconstruct (per Rule 8 existence-test criterion 4).Test plan
bun run format:checkpassesOut of scope
docs/roadmap.mdnon-goals lockstep update — separate PR.