Add a remote operations UI for synced WikiBricks memory

[philtief]

Use case

WikiBricks can sync immutable local page versions to Lakebase and run remote maintenance, but people do not have a browser for the remote archive, maintenance results, or publication state. Discover Pages expose a governed subset to business users and Genie Ontology; they do not replace an operations view of the full WikiBricks replica.

Add an optional remote UI for inspecting curated pages, synchronization state, maintenance proposals, conflicts, and Discover Page publication status.

Proposed API

Deploy a Databricks App alongside the optional remote maintenance resources:

databricks bundle deploy -t personal \
  --var="enable_remote_ui=true" \
  --var="lakebase_project=wikibricks"

The app reads curated pages and archive state from Lakebase. When Discover publication is enabled, it also reads candidate and publication state from the Unity Catalog Delta staging table proposed in #4.

The first release should provide:

• search and rendered page views with metadata, sources, history, links, and backlinks;
• replica and user isolation enforced through Databricks authentication;
• the last committed local sync time, with stale remote state clearly marked;
• remote maintenance proposals, review state, and conflicts; and
• Discover candidate, draft, publication, and error status from the staging table.

The app may share backend and deployment code with the stateless Genie Code MCP endpoint proposed in #3, while keeping /ui and /mcp as separate surfaces.

Acceptance criteria

• The feature is optional and disabled by default.
• The app reads page content and synchronization state from Lakebase without changing the local-first authority model.
• Databricks authentication prevents access across users and replica IDs.
• Every page view reports the source replica and last committed sync watermark.
• Search and navigation exclude raw sessions by default.
• The UI shows maintenance proposals and conflicts without applying them in the first release.
• If Publish curated WikiBricks pages through remote maintenance #4 is enabled, the UI reads Discover candidate and publication state from its Unity Catalog staging table.
• If Publish curated WikiBricks pages through remote maintenance #4 is disabled, the rest of the UI works without the staging table.
• The app does not call undocumented Databricks endpoints.
• Remote resources can remain stopped or scale to zero when unused.
• Tests cover authorization boundaries, stale replicas, missing optional resources, and failed maintenance or publication states.
• Documentation covers deployment, permissions, cost controls, and teardown.

Editing, conflict resolution, and publication actions can follow after WikiBricks defines their authorization and version checks.

Alternatives considered

Exporting the archive to Markdown creates another synchronized copy and does not expose maintenance or publication state. Discover Pages are suitable for approved business concepts, but they omit raw operational context and review queues. A local-only browser cannot show what has reached Lakebase or the Lakehouse staging layer.

Additional context

• Add a deployable MCP endpoint for Genie Code #3 proposes the remote MCP endpoint for Genie Code.
• Publish curated WikiBricks pages through remote maintenance #4 proposes the remote maintenance path from Lakebase through Unity Catalog staging to Discover Page drafts.
• Databricks Apps
• Databricks Discover Pages