publish the catalogue from the release clones, and make the cards look like cards

three small things.

marketplace-sync reads PLUGINS_DIR now instead of assuming the directory it sits
next to. platform/plugins/ is what a machine has INSTALLED — updated by
plugins:update, which is a git pull — while the release is made in the workspace
clones. publishing from the install directory means the catalogue advertises the
version this machine happens to be running: 21 plugins were tagged and the store
went on showing 1.0.0 until this changed.

the grid cards used bg-white/40. this app's surfaces are a DARKENING of the
panel behind them — every other card and section here is bg-duck-dark/5 — so a
translucent white read as a pale box floating on a dark theme. picking a colour
instead of a token, and it only looked right against a background this app does
not have. hover now moves the BORDER and nothing else: a background swap across
twenty-one cards makes the whole grid twitch as the pointer crosses it.

the tag pills were the same value as the card surface, so they rendered as text
with no chip at all.

and the marketplace todo said the UI was not started. it is.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Officer-Session: 656f5c85-e49a-4f1f-b9f3-042a04b4d043

scripts/marketplace-sync.ts

@@ -66,7 +66,19 @@ const git = (dir: string, args: string[]): string | null => {
   return new TextDecoder().decode(result.stdout).trim() || null;
 };
 
-const PLUGINS_DIR = resolve(import.meta.dir, '..', 'plugins');
+/*
+  Which plugins directory to publish FROM.
+
+  There are two, and they are not the same thing. `platform/plugins/` holds what this machine has
+  INSTALLED — updated by `plugins:update`, which is a git pull, and therefore always at whatever version
+  was last installed. `officer-dev/plugins/` holds every repo in the org, cloned for working on, and is
+  where a release is actually made.
+
+  Publishing from the install directory means the catalogue advertises the version this machine happens
+  to be running rather than the version that was released. That is exactly what happened on 2026-08-27:
+  21 plugins were tagged and the store went on showing 1.0.0.
+*/
+const PLUGINS_DIR = process.env.PLUGINS_DIR ?? resolve(import.meta.dir, '..', 'plugins');
 
 async function syncOne(dir: string): Promise<Sync | null> {
   const appName = basename(dir);