Skip to content

feat(cloud): Phase 5.5 — Supabase sync follow-ups #173

Description

@nmrtn

Follow-up work after PR #172 (Phase 5 cloud sync) merges.

Tasks

  • --force flag on pull — bypass the content-hash check and do a clean overwrite from Supabase. Useful when a teammate has the canonical version and you want to discard local edits without running sync first.

  • pgvector semantic search — replace SQLite FTS5 with Postgres vector search when Supabase is configured. Enables cross-machine, multi-user semantic queries against the wiki without shipping the index locally.

  • JWT-scoped RLS — current RLS is allow all (permissive). Phase 5 uses the publishable anon key as the only access gate. Tighten with per-project JWT claims so the Supabase instance can safely host multiple unrelated teams without cross-tenant read/write risk. See CSO audit finding Add imperative next action to every artifact section template #3.

  • Web viewer — read-only dashboard for stakeholders who don't have the CLI. Surfaces wiki pages, opportunities, and the activity log from nanopm_wiki_log.

Context

Tracked here so Phase 5 (PR #172) can merge cleanly. None of these block the current sync layer — they extend it.

🤖 Generated with Claude Code

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions