feat(symbols): add visibility column derived from JSDoc tags (B.7)

[SutuSebastian]

Summary

Implements B.7 from docs/research/fallow.md § Tier B: promote JSDoc visibility tags from a LIKE '%@beta%' regex inside the visibility-tags recipe to a real symbols.visibility TEXT column.

SCHEMA_VERSION 3 → 4. .codemap.db rebuilds automatically on next index via the existing createSchema() mismatch-detection path — no manual intervention.

What's new

Surface	Change
Schema	New symbols.visibility TEXT column. Partial index idx_symbols_visibility(visibility, file_path, name, line_start) WHERE visibility IS NOT NULL covers WHERE visibility = ? queries.
Parser	New exported helper extractVisibility(doc): string | null. Anchored on line-start (after the JSDoc * prefix), so backticked references inside prose ("matches @public, @private") intentionally don't match — those are descriptions, not declarations. First match in document order wins when multiple line-leading tags are present.
Recipe	visibility-tags SQL switches to WHERE visibility IS NOT NULL and returns the visibility value as a column so agents can filter / group without re-parsing the doc_comment.
Tests	Parser unit tests cover null/empty doc, each canonical tag, in-prose false negatives, ordering, look-alike rejection (@betaTwo, @publicly), and per-method override on classes. DB test inserts three symbols with mixed visibility and asserts the partial-index round-trip. Golden visibility-tags.json regenerated with the new column.

Why a minor changeset

Per .agents/lessons.md "changesets bump policy (pre-v1)" — schema bumps that force a .codemap.db rebuild are minor, even in 0.x. Same precedent as 0.2.0.

What's not in this PR

• --group-by visibility shortcut — no special-casing; agents already get it via SQL GROUP BY visibility or --group-by directory against the visibility-tags recipe rows.
• Visibility on exports (vs symbols) — re-exports inherit the source symbol's tag; no separate column needed today.
• @deprecated promotion — orthogonal to visibility (a deprecation is a lifecycle signal, not a visibility level). Stays on the doc_comment LIKE '%@deprecated%' path until a separate PR justifies its own column.

Test plan

• bun run check passes locally (build, format:check, lint:ci, test, typecheck, test:golden — all 19 golden scenarios green).
• Smoke tests against this clone:
  • bun src/index.ts --full succeeds and reports the schema-version-mismatch rebuild path.
  • bun src/index.ts query --json -r visibility-tags returns rows with visibility: "internal" (and similar) instead of just doc_comment regex matches.
  • bun src/index.ts query --json "SELECT visibility, COUNT(*) FROM symbols WHERE visibility IS NOT NULL GROUP BY visibility" works (uses the new partial index).
  • The earlier false positive (extractVisibility's own docstring matching @public because of backticked references) is gone.
• Minor changeset added per pre-v1 "schema bump = minor" rule.
• CI green.

[changeset-bot]

🦋 Changeset detected

Latest commit: cfbc9c8

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@stainless-code/codemap	Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another 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 23 minutes and 16 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: b7bdbe1d-7114-4144-b669-e119e5589fe3

📥 Commits

Reviewing files that changed from the base of the PR and between c32f052 and cfbc9c8.

📒 Files selected for processing (9)

• .changeset/symbols-visibility-column.md
• docs/architecture.md
• docs/glossary.md
• fixtures/golden/minimal/visibility-tags.json
• src/cli/query-recipes.ts
• src/db.test.ts
• src/db.ts
• src/parser.test.ts
• src/parser.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/symbols-visibility-column

---

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 23 minutes and 16 seconds.}

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