sync-desktop-renderer

name	sync-desktop-renderer
description	Sync the 6529 web frontend into the 6529-core Electron renderer subtree, preserve desktop-only behavior, resolve pull-web conflicts, update duplicated desktop config, and bump the desktop version. Use when Codex is asked to bring the Electron desktop app up to date with recent or current 6529.io frontend changes.

Sync Desktop Renderer

Bring renderer/ to the current 6529-Collections/6529seize-frontend main while keeping the Electron app's local runtime model intact.

Ground Rules

• Keep root ops/ outside renderer/; future git subtree pull --prefix=renderer runs can overwrite renderer-local operational docs.
• Verify the current web SHA before claiming the desktop is current:

git ls-remote https://github.com/6529-Collections/6529seize-frontend.git refs/heads/main

• On this Windows Codex host, prefer the guarded direct command because the repo bin/6529 shim can fail on CRLF/shebang handling:

$env:SEIZE_6529_COMMAND='1'; pnpm run pull-web

• If a merge is left open, finish resolving and commit before pulling another web delta.
• Always bump root package.json for a desktop release candidate. The desktop updater release files are version keyed, and the README warns that skipping the bump can overwrite a previous release.

Conflict Policy

Take upstream web code for normal frontend features, pages, tests, services, styles, and generated renderer lockfile changes.

Preserve or reapply desktop-specific behavior in these areas:

• renderer/components/auth/Auth.tsx: Electron auth modal flow and any local sign/deep-link handling.
• renderer/components/header/share/HeaderQRScanner.tsx: desktop QR behavior, avoiding mobile-only scanner assumptions.
• renderer/components/eula/EULAConsentContext.tsx: Electron/local consent behavior.
• renderer/components/ipfs/IPFSContext.tsx: Electron bridge/local IPFS support.
• renderer/config/env.schema.ts: desktop optional IPFS env and media resolver defaults.
• renderer/config/securityHeaders.ts, renderer/lib/media/ipfs-gateways.ts, root next.config.ts: local IPFS gateway, media resolver, CSP, and image host compatibility.
• renderer/components/drops/view/item/content/media/UnsupportedMediaLink.tsx: external-browser handling and decentralized media normalization.
• renderer/styles/seize-bootstrap.scss: keep the explicit ../node_modules/bootstrap/scss/bootstrap import if bare bootstrap/scss/bootstrap fails under Turbopack/Sass on the Windows pnpm install.

Root Config Sync

The desktop root next.config.ts duplicates some renderer config because Electron builds the renderer locally. After taking web updates, check whether these concepts need to exist in both places:

• media resolver endpoint and hostname
• IPFS gateway allowlists and loopback development gateways
• Arweave gateway host additions
• CSP connect-src, media-src, and frame-src
• Next image remotePatterns
• public env passthrough for renderer runtime values

For packaged builds, next.config.ts must be able to load both:

• renderer/config/env.schema.runtime.cjs, generated by build-env-schema and included by electron-builder.
• main/config/__PUBLIC_RUNTIME.json, generated by scripts/bake-public-runtime.ts and included through main/**/*.
• main/config/__PRIVATE_RUNTIME.json, generated by scripts/bake-public-runtime.ts for main-process-only desktop secrets such as the Test backend STAGING_API_KEY. Do not copy this into renderer/public runtime config.

If either side drifts, production can either fall back to permissive env parsing or fail with a Zod missing-env error before the local Next server starts.

Validation Before Moving On

After conflict resolution:

git diff --name-only --diff-filter=U
rg -n "^(<<<<<<<|>>>>>>>)" next.config.ts package.json renderer -S
git status --short --branch

Use codex-diff-check, not raw git diff --check, for whitespace checks on this Windows worktree.