From 911b79b6a2fb5f37ce02916fbfa8bd0b7fb95df9 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Andr=C3=A9=20Padez?= Date: Wed, 12 Aug 2026 22:07:19 +0000 Subject: [PATCH] drop a comment describing a machine that no longer exists MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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) --- src/servers/app-store/paths.ts | 4 ---- 1 file changed, 4 deletions(-) diff --git a/src/servers/app-store/paths.ts b/src/servers/app-store/paths.ts index 0e70d2f5..25da7da4 100644 --- a/src/servers/app-store/paths.ts +++ b/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` ── //