chore(main): release monolith 0.3.0

[panicboat]

🤖 I have created a release beep boop

0.3.0 (2026-07-07)

Features

• account-durability: self deactivation + 30-day grace + cron hard-delete (#766) (0133c03)
• bookmarks: proto + monolith slice (schema + repo + use_cases + handler, B1) (#701) (f5eb626)
• discovery: proto + monolith slice (3 RPC + cross-slice search/rank, D1) (#708) (d7c43d4)
• discovery: role filter for SearchUsers (全て/キャスト/ゲスト chips) (#734) (1adcf9f)
• discovery: suggested-users (おすすめユーザー) pane — Phase 1b-B PR2 (#753) (e4cf6f2)
• feed: symmetric ListFeed handler + use_case + adapter methods (#663) (3fdef23)
• feed: symmetric ListFeed proto contract + slice design spec (#660) (eebfd8a)
• footprints: F1 monolith — proto + slice + use_cases + handler (#728) (bc3b9d1)
• footprints: visit count per visitor (#754) (67b0818)
• footprints: visitor opt-out via notifications.preferences (#742) (645ab2f)
• identity: Account rename + RS256 JWT + frontend stub follow-up (#649) (00215b9)
• identity: auth hardening (single-use tokens, lockout, refresh digest, BFF cookies) (#763) (74b37e6)
• identity: auth/onboarding rebuild — login/signup/onboarding/reset + AWS SNS SMS (#761) (3f6ba37)
• karte: Cast-only Guest review + trust slice destroy (#765) (7f5b75b)
• messaging: proto + monolith slice (schema + repo + 7 unary use_cases + handler + NOTIFY publish, M1) (#711) (43485b3)
• messaging: StreamEvents server-streaming (PG LISTEN/NOTIFY subscriber, M2) (#712) (6d8f6c3)
• notifications: add MarkAllRead RPC and /notifications page button (#740) (1cb4928)
• notifications: add per-account notification preferences (settings 通知設定 tab) (#738) (aca8852)
• notifications: add target_post_id for COMMENT/REPLY deep-link (#741) (3f71081)
• notifications: cross-slice emit hooks (like/comment/reply/follow_request/follow_approved) (#694) (200f6e6)
• notifications: gate emit and drawer badge by notification preferences (#739) (b8c23c2)
• notifications: proto + monolith slice scaffold (N1) (#692) (8240d5e)
• notifications: use_cases + grpc handler (3 RPC live, N2) (#693) (a3c60a3)
• post: add ListPostsByIds use_case for cross-slice hydration (#661) (c8ea518)
• post: proto + repo + use_cases for profile content tabs (media_only + ListCommentsByAuthor + ListLikedPostsByAccount, P1) (#719) (b85de1d)
• posts: symmetric posts backend — proto/schema/PostService/LikeService (#652) (12bc787)
• post: symmetric comment author resolution via ProfileService (#655) (a29378a)
• post: symmetric comment list author resolution via ProfileService (#656) (c493592)
• profile: add ListAccountIdsByPrefecture use_case for cross-slice feed query (#662) (eae2061)
• profile: rebuild profile as full vertical slice (proto/monolith/frontend) (#651) (cda4c85)
• social: cross-slice follow-gate (ViewerCanSeePost + FilterVisiblePosts) (#679) (5567668)
• social: follower/following count display on /u/[username] (#689) (11324ba)
• social: schema migration + slice base + relations + repositories (#677) (8826a14)
• social: symmetric Follow/Block proto contract + design spec (#676) (4baac9b)
• social: use_cases + grpc handlers (14 RPC live) (#678) (69c9b7e)

Bug Fixes

• discovery: present profiles through ProfilePresenter before proto assign (#770) (1615b90)
• identity: distinguish ACCOUNT_LOCKED from invalid credentials (#768) (d30b5c8)
• karte: aggregate() must strip the relation's default ORDER BY (#769) (53fcd7c)
• messaging: dedicated PG connection for StreamEvents LISTEN loop (#813) (d493846)
• post: qualify PostPresenter in ListPostsByIds (feed crashes) (#722) (59c92bd)
• post: resolve Concerns::CursorPagination via top-level path to avoid Post::Concerns collision (#697) (5e145e8)
• social: present profiles through ProfilePresenter before proto assign (#791) (54a0e9c)
• social: present profiles through ProfilePresenter for singular fields (#801) (8d166d6)
• social: use repo transaction in BlockRepository#block (#731) (a846c12)

---

This PR was generated with Release Please. See documentation.