[hellofrequencylab]

My Quest is available to every authenticated member in the current access contract, but the root /crew page setting still requires the retired community crew role. That stale setting redirects ordinary members to the feed.

This PR prepares a narrowly scoped operator repair and an OPEN manual-verification ledger row. It does not execute SQL or change production access by merging. The script requires exactly one root Space and exactly one published root /crew row whose visibility and updated_at match the reviewed snapshot. It locks that row, changes only its visibility to native NULL (any authenticated member) and its timestamp, and verifies all other target columns remain unchanged. Missing, stale, ambiguous, already-cleared, wrong-status or wrong-visibility states refuse and roll back.

No generic route gate, authentication, RLS, grant, role, migration or unrelated Space setting changes. The existing layout still protects other host-only/draft routes and signed-out access. This is an operator script, not a migration, and it has no automatic invocation.

Validation:

• Normal merge from main 93c68083049621c341498a67f68135113bba3697, with only the two reviewed files in the PR diff; no current open PR file or row overlap.
• Exact SQL SHA256 258956ee13d656f2b67959fc9a4c3c15690dc3e6a1740d0ced9d2127e1e43cec is unchanged from the reviewed candidate.
• Eleven actual-script cases pass in disposable PGlite 0.4.0 / PostgreSQL 17.5-compatible fixtures: valid one-row repair with unrelated tenant/host/draft rows preserved; missing/stale/wrong/already-cleared/ambiguous cases and unexpected target-column trigger changes refuse or roll back. This is not hosted Supabase, live-session or browser equivalence.
• Static backlog, one-list and diff guards pass. No protected tests, probes, baselines or thresholds change.

Release sequence: the serialized root driver must verify exact-head CI and the real deployment, merge the exact script onto main, then perform a fresh read-only schema/root/row compare-and-set preflight and separately cleared single execution. Verify row/postconditions and actual authenticated member/guest behavior afterward. NAV-QUEST-VISIBILITY remains OPEN until that proof exists. Never rerun against a changed or already-cleared row.

Coordination: #4306 (comment). No auto-merge; root owns release and production verification.

[vercel]

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

Project	Deployment	Actions	Updated
frequency-web	Ready	Preview	Nov 4, 2026 9:40pm UTC