feat(blocks): add block visibility gating (preview blocks + AppConfig reveals)

[TheodoreSpeaks]

Summary

• preview: true on a BlockConfig hides the block from every discovery surface (toolbar, cmd+K, mentions, tool picker, mothership VFS/metadata/tools, Access Control, docs/catalog) in every environment until revealed — fail-closed, including SSR
• reveal paths: hosted block-visibility AppConfig document (per-block {enabled, orgIds, userIds, adminEnabled} rules — admins/org allowlists get a (Preview) name suffix, enabled: true = GA) or PREVIEW_BLOCKS env for self-host/dev; enabled: false on a shipped block = discovery kill switch
• execution is never gated: getBlock stays pure, gated blocks stay in getAllBlocks() as clones (clone-not-remove), placed instances keep running
• new blocks/visibility/ context (client resolver + per-request server ALS, independent of the custom-block overlay), registry projection with a zero-cost fast path when no preview blocks exist
• shared AppConfig rule parsing extracted to appconfig-rules.ts (feature-flags refactored onto it)
• mothership: VFS static files + exposed integration tools stay ungated process-global caches, filtered per-viewer at stamp/consumer time; tool-schema LRU keyed by visibility signature; visibility memoized per (user, workspace)
• generate-docs/check-block-registry skip preview blocks (no public docs/catalog/meta until GA); Access Control hides them from the list while keeping stored allowlists viewer-independent
• /gate-block skill documents the lifecycle; infra profile landed in simstudioai/infra#262

Type of Change

• New feature

Testing

966 tests across touched suites (new coverage: rule parsing, visibility evaluation, registry projection, hydrate no-op, route, preview-not-exempt), tsc, lint, check:api-validation:strict, react-query + client-boundary audits, check-block-registry — all green. Route-count baseline 919→920 (new contract-bound route).

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
docs	Ready	Preview, Comment	Jul 10, 2026 2:35am

[cursor]

PR Summary

Medium Risk
Touches many discovery surfaces and copilot/VFS paths with per-viewer projection; execution is intentionally left ungated, but mis-wiring visibility into run paths or allowlist logic could hide blocks incorrectly or leak preview metadata in client bundles.

Overview
Adds block visibility gating so unreleased blocks can ship in code but stay off discovery surfaces until revealed, with optional kill-switches for shipped types—without blocking execution of blocks already on a workflow.

preview: true on BlockConfig hides a block everywhere (toolbar, search, mentions, copilot, access control UI, docs) until rules say otherwise. Reveal paths are the hosted block-visibility AppConfig profile (per-type enabled / org / user / adminEnabled rules) and PREVIEW_BLOCKS env for self-host/dev. Non-GA reveals get a " (Preview)" name suffix on discovery; getBlock stays unprojected for execution.

New blocks/visibility/ layer (client hydrate + server AsyncLocalStorage), GET /api/blocks/visibility, and BlockVisibilityLoader in the workspace layout drive the overlay. getAllBlocks / getCanonicalBlocksByCategory project visibility (clone-not-remove for hidden types). Shared appconfig-rules refactors feature-flags onto the same rule parser.

Copilot/VFS/integration tools keep ungated process-global caches and filter per viewer at stamp/consume time; discovery server tools run inside withBlockVisibility. Toolbar, matcher, and search caches invalidate on overlay version bumps. Docs/registry checks skip preview blocks; access control separates full allowlist universe from UI-visible blocks.

^{Reviewed by Cursor Bugbot for commit a5da72e. Bugbot is set up for automated code reviews on this repo. Configure here.}

[greptile-apps]

Greptile Summary

This PR adds block visibility gating for preview and AppConfig-controlled blocks. The main changes are:

• Adds client and server visibility context for registry projection.
• Hides preview and disabled blocks from discovery surfaces while keeping execution ungated.
• Adds a workspace API route and client loader for viewer-specific visibility state.
• Updates copilot, VFS, toolbar, mentions, access-control, docs, and catalog paths to use the gated view.
• Adds shared AppConfig rule parsing and tests for visibility behavior.

Confidence Score: 5/5

This looks safe to merge.

• No blocking issues found in the changed code.

Important Files Changed

Filename	Overview
apps/sim/blocks/visibility/client.ts	Adds client-side visibility hydration and preserves disabled entries during workspace switches.
apps/sim/app/workspace/[workspaceId]/providers/block-visibility-loader.tsx	Loads workspace-specific block visibility and resets reveal state while new data is loading.
apps/sim/blocks/registry.ts	Projects registry results through visibility state while keeping direct block lookup unchanged.
apps/sim/app/api/blocks/visibility/route.ts	Adds an authenticated workspace-scoped endpoint for block visibility state.
apps/sim/lib/copilot/tools/server/router.ts	Scopes selected copilot discovery tools under server-side block visibility.

_{Reviews (4): Last reviewed commit: "fix(blocks): carry kill-switch entries a..." | Re-trigger Greptile}

[TheodoreSpeaks]

@greptile review

[TheodoreSpeaks]

@greptile review

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 4fec85f. Configure here.}

[TheodoreSpeaks]

@greptile review