one plugins directory, because the second one was symlinks

`officer-dev/plugins/` is gone. it was created to hold every repo in the org side
by side, and by today it held 22 symlinks into platform/plugins, one duplicate
clone of a plugin that is installed here, and a README describing a state that
had already been fixed.

it could not have been more than that. a plugin cannot live outside the platform:
bun resolves a symlink to its real path, so from there `@@/sidecar/create-proxy`
and every relative import fail. tested both, plus `--preserve-symlinks`, which
bun 1.3.14 accepts and ignores.

WHICH MATTERS BEYOND TIDYING, because marketplace-sync leaned on the distinction.
its comment said the second directory was "where a release is actually made", so
publishing from it would advertise released versions rather than installed ones.
that was never true — symlinks meant both paths read the same working copy. the
bug it describes (21 plugins tagged, the store still showing 1.0.0) was never
addressed by the thing built to address it.

the honest fix is in the comment now: each plugin directory IS a git repo with
its own tags, so the released manifest can be read out of the tag —
`git show <tag>:manifest.ts` — without a second checkout. not written yet, and
said plainly rather than left implied.

finances is deleted, at the owner's request: not installed, no pm2 entry, no
ecosystem entry, no plugin_installs row, no tables. both clones were clean and
pushed. the gitea repo is untouched.

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

scripts/marketplace-sync.ts

@@ -69,14 +69,21 @@ const git = (dir: string, args: string[]): string | null => {
 /*
   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.
+  There is one: `platform/plugins/`, holding what this machine has INSTALLED — updated by
+  `plugins:update`, which is a git pull, so it sits at whatever version was last installed.
 
-  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.
+  Publishing from it 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.
+
+  A second directory — `officer-dev/plugins/`, every repo in the org cloned side by side — was created
+  to fix that, and never did: its entries were SYMLINKS into this one, so both paths read the same
+  working copy and published the same version. It was removed on 2026-08-28.
+
+  **The problem is still open, and a second checkout was never the answer.** Each directory here is a
+  real git repo with its own tags, so the released manifest can be read out of the tag itself —
+  `git show <newest-tag>:manifest.ts` — without caring what is checked out. That is the fix; it is not
+  written yet, and until it is, this script advertises what is installed.
 */
 const PLUGINS_DIR = process.env.PLUGINS_DIR ?? resolve(import.meta.dir, '..', 'plugins');