Discourse Bridge connects a WordPress site to an external Discourse forum, pushing posts to Discourse and pulling comment counts back. Rather than maintaining its own database tables, the bridge stores sync state in wp_postmeta keys like discourse_post_id, discourse_permalink, discourse_comments_count, and a publish flag. User-level sync state — including the Discourse user id — lives in wp_usermeta. The plugin's settings screen handles configuration but doesn't offer a flat audit of which posts synced, which failed, and which haven't been touched.

SleekView reads wp_posts filtered to the configured publish post types, joins the Discourse postmeta keys into named columns, and joins wp_users with their discourse_sso_user_id for cross-system identity. Filter to posts without a discourse_post_id for the unsynced queue, sort by discourse_comments_count to find Discourse threads worth pulling back into WP commenting, and bulk-toggle the publish-to-Discourse flag across many rows.

Inline edits go through update_post_meta and the bridge's own filters so cascade logic stays consistent. Direct postmeta writes are available behind a flag for clean-up of orphaned sync state, with conflict detection on the meta_id column.

Bridge plugins are quiet by design. Discourse Bridge does its work in the background, leaving sync flags in postmeta and usermeta that the rest of the WordPress admin doesn't surface. That works fine when the bridge is healthy and the team has nothing to investigate.

It breaks down the moment something goes wrong: a publishing batch failed mid-way, comment counts stopped updating, an SSO user got out of sync. Suddenly the team needs to audit which posts have discourse_post_id set, which ones don't, which ones got stale because the WP post updated after Discourse last pulled. None of those are views the default admin offers because the data lives in long-format meta.

SleekView's job is to pivot that meta into a real audit workspace where unsynced posts, failed pushes, and stale sync state surface as named filters. Same data, same WP meta APIs on writes, dramatically less SQL spelunking when the bridge needs attention.