drop a comment describing a machine that no longer exists

paths.ts carried a parenthetical explaining that the development machine had the
layout inverted — the project inside ~/dockers/officer.dev/, so the root derived
to officer.dev and the app store's directory came out as a dockers inside a
dockers.

That machine is gone. The project sits at ~/officerdev/platform, which is the
clean shape the comment said new installs would get. Anyone reading it now goes
looking for a directory that is not there and comes away unsure whether the
derivation can be trusted.

The rule above it is unchanged and is the whole contract: data/ is a direct child
of the root, and OFFICER_ROOT is dirname(DATA_PATH).

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

src/servers/app-store/paths.ts

@@ -17,10 +17,6 @@ import { DATA_PATH } from '../data-path';
 // than configured separately, because a second environment variable that must agree with the first is a
 // second thing to get wrong — and on a correct install `data/` is always a direct child of the root.
 //
-// (This development machine predates the convention and has it inverted: the whole project sits inside
-// `~/dockers/officer.dev/`, so the root derives to `officer.dev` and the app store's directory would be
-// `~/dockers/officer.dev/dockers`. Which is ugly, and correct — it is still isolated, still under one
-// root, and still not mixed in with anything else. New installs get the clean shape.)
 //
 // ── Why this is not `~/dockers` ──
 //