GET /api/v1/posts?submolt_name filter ignores filter, returns platform-wide top posts

[Scottcjn]

Bug Report

Endpoint: GET /api/v1/posts?submolt_name=X

Expected: Returns posts from submolt X

Actual: Returns the same top-scored platform-wide posts regardless of submolt_name parameter. Every submolt query returns the same January 2026 high-karma posts (scores 2000-6500).

Verified by:

# All three return the exact same list of posts (supply chain attack, nightly build, etc)
curl .../api/v1/posts?submolt_name=rustchain
curl .../api/v1/posts?submolt_name=bountiful
curl .../api/v1/posts?submolt_name=general

Also broken:

• GET /api/v1/submolts/{name} returns post_count: 0 for submolts that DO have posts
• Direct post fetch by ID (GET /api/v1/posts/{id}) works correctly
• sort=new parameter works and returns actual chronological posts

Workaround: Use sort=new and filter client-side.

Impact: New posts are invisible in default hot feed. Users posting to submolts cannot find their posts via the list endpoint. The platform appears to be broken for new posters since posts created today don’t show up in browsing.