refactor(db): rename profiles entity to authors

[bbornino]

Closes #210

What changed

Standardizes on "author" instead of "profiles" across the schema, relations, routes, and worker job payloads. The two names were being used interchangeably for the same entity — this makes author the single name everywhere.

• DB schema (packages/db/src/schema/profiles.ts → authors.ts): profiles table → authors, profile_achievements table → author_achievements, profile_slug column → author_slug on both author_achievements and author_roles.
• Relations (packages/db/src/relations.ts): all r.profiles/r.profileAchievements references renamed to match.
• Routes: merged GET /content/profiles (list) and GET /content/authors/:slug (single) into one file, apps/api/src/routes/content/authors.ts, exposing both under /content/authors. profiles.ts is deleted; createApp.ts updated to register a single authorsRoutes.
• Worker: sync-author, sync-post, sync-collection, and grant-author-achievements processors updated for the renamed tables/columns.
• Job payload: GrantAuthorAchievementsInput.profileSlug → authorSlug (see Deploy note below).
• Test fixtures: packages/test-fixtures/src/db-mock.ts updated to mock authors/authorAchievements.
• Tests updated to match; profiles.test.ts merged into authors.test.ts alongside the list-route tests.

Migration

profiles and profile_achievements are live production tables, so this was not a drop-and-recreate. The generated migration (packages/db/drizzle/20260902153554_hot_leech/migration.sql) is four ALTER TABLE statements only, confirmed via drizzle-kit's interactive rename prompts (not a diff-and-guess):

ALTER TABLE "profile_achievements" RENAME TO "author_achievements";
ALTER TABLE "profiles" RENAME TO "authors";
ALTER TABLE "author_achievements" RENAME COLUMN "profile_slug" TO "author_slug";
ALTER TABLE "author_roles" RENAME COLUMN "profile_slug" TO "author_slug";

No data is dropped or recreated.

Explicitly out of scope

profileImage (DB column), profileImageUrl (API response field), and the author-image S3 key prefix (profiles/${authorId}.jpeg) are intentionally left unchanged. These describe the image itself, not the profiles-vs-authors entity naming this issue is about — renaming them would touch the public API response shape (client-facing, needs a coordinated frontend change) and raise an S3 key migration question that #210 doesn't cover. Flagging for a separate issue if the team wants that follow-up.

Deploy note: in-flight job payload change

The GRANT_AUTHOR_ACHIEVEMENTS job payload shape changed from { profileSlug } to { authorSlug }. Any jobs already sitting in the Redis queue at deploy time were enqueued with the old profileSlug key and won't have authorSlug populated — they'll fail (or silently no-op, depending on how the field is read) until the queue is drained past the deploy boundary. Worth either draining the GRANT_AUTHOR_ACHIEVEMENTS queue before deploying, or manually re-running any jobs still pending afterward.

Testing

- pnpm test:unit — clean
- pnpm run build:all (matches CI's unit-tests workflow build step) — clean
- pnpm prettier (check mode) — clean

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Team

Run ID: 8976e68e-a06e-4c9e-854b-77efe211f1c3

---

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

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