the install root is derived, not configured

Seven variables out of .env. DATA_PATH, OFFICER_ITEMS_DIR and HOME_DIR are gone
from the code entirely; PUBLIC_URL, PUBLIC_BUILD_ENV, JWT_SECRET and
VAULT_STORE_KEY are no longer written by the setup script.

data-path.ts now derives OFFICER_ROOT as dirname(process.cwd()), with data/,
capabilities/ and dockers/ as fixed names under it. The direction used to run the
other way — DATA_PATH from env, then OFFICER_ROOT = dirname(DATA_PATH) in
app-store/paths.ts — which meant three environment variables that had to agree
with each other and with the tree on disk.

Eight files re-read process.env.DATA_PATH independently, each with its own
`?? cwd()/data` fallback. They import the one value now, which is what made
removing it safe: otherwise each would have derived its own and drifted.

Three things this turned up.

The cwd pin in ecosystem.profile.cjs was broken. It set `cwd: __dirname` under a
comment asserting "__dirname is the repo root — this file sits beside
ecosystem.config.cjs", which stopped being true when these files moved into
ecosystem-files/. It walks up to the platform's package.json now, which holds
wherever the file lives. That was a live bug before this change and a load-bearing
one after it, since cwd now decides where the install is.

assertInstallLayout joins the other two boot assertions. A wrong cwd does not
error — it computes a plausible root somewhere else and writes managed homes and
agent runs into it, so the install looks empty and the data looks lost with
nothing naming the cause. It throws before serve(), first of the three, because a
wrong answer there makes the other two check the wrong files.

getOwnerHomeDir captures homedir() once at module load rather than per call.
Measured on bun 1.3.10: both os.homedir() and os.userInfo().homedir return $HOME
when set rather than reading passwd, and user-instance.ts assigns process.env.HOME
on its way to spawning an agent. A lazy read would have returned the owner's home
on the first call and a member's afterwards. data-path.ts imports only node
builtins, so it is evaluated before any of that runs.

JWT_SECRET and VAULT_STORE_KEY leaving .env means an install made by this script
does not boot — jwt.ts throws at module load without one. That is the agreed
sequencing: they move to the SQLite store (docs/secret-store.md), and writing them
here meanwhile would create a second origin for a secret the store then has to be
reconciled with. Said plainly in .env.example and in lib/env.sh rather than left
to be discovered.

Not typechecked: node_modules is empty here and installs are frozen. Every edited
file parses under `bun build --no-bundle`; the profile loads and pins the right
cwd; assertInstallLayout was exercised from both the repo and /tmp; the setup
section was run and writes five variables. Prettier was NOT run — 3.9.6 via bunx
is not the pinned resolution and reformatted unrelated unions and line wraps in
six files, so those were reverted and the edits re-applied by hand.

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

scripts/setup/officer-setup.sh

@@ -458,54 +458,22 @@ if ! skip; then
   echo ""
   info "Environment — $(env_file)"
 
-  # Read back before anything is asked. The two secrets below are kept, never
-  # reminted, and everything else becomes the default for its question.
-  ENV_JWT_SECRET="$(env_get JWT_SECRET)"
-  ENV_VAULT_STORE_KEY="$(env_get VAULT_STORE_KEY)"
+  # Read back before anything is asked; existing values become the defaults.
   ENV_PORT="$(env_get PORT)"
-  ENV_PUBLIC_URL="$(env_get PUBLIC_URL)"
   ENV_DISCORD_WEBHOOK="$(env_get DISCORD_BUG_REPORT_WEBHOOK)"
   ENV_BROWSER_RELAY_PORT="$(env_get BROWSER_RELAY_PORT)"
 
   if env_exists; then
-    echo "     exists — its values are the defaults below, and the two secrets are kept"
+    echo "     exists — its values are the defaults below"
   else
     echo "     does not exist yet"
   fi
 
-  # ── the secrets ──
-  if [[ -n "$ENV_JWT_SECRET" ]]; then
-    echo "     JWT_SECRET:      kept (regenerating it logs everybody out)"
-  else
-    ENV_JWT_SECRET="$(generate_secret)"
-    echo "     JWT_SECRET:      generated"
-  fi
-
-  if [[ -n "$ENV_VAULT_STORE_KEY" ]]; then
-    echo "     VAULT_STORE_KEY: kept"
-  else
-    ENV_VAULT_STORE_KEY="$(generate_secret)"
-    echo "     VAULT_STORE_KEY: generated"
-    echo ""
-    warn "back up VAULT_STORE_KEY somewhere safe, now."
-    echo "     It encrypts every upstream credential the platform stores, and the"
-    echo "     wallet's seed on top of your passphrase. Lose it and those are gone"
-    echo "     — the passphrase does not help, because it opens the inner envelope"
-    echo "     and this is the outer one."
-  fi
-
   # ── what is asked ──
   echo ""
   ask_required ENV_PORT "Port Officer listens on" "${ENV_PORT:-9000}"
   ENV_BROWSER_RELAY_PORT="${ENV_BROWSER_RELAY_PORT:-18792}"
 
-  echo ""
-  echo "     PUBLIC_URL is where Officer is reached from a browser. Allowed"
-  echo "     origins are derived from it, and passkeys are bound to its host —"
-  echo "     so it has to be the address you actually use, not localhost, unless"
-  echo "     localhost is genuinely it."
-  ask_required ENV_PUBLIC_URL "Public URL" "${ENV_PUBLIC_URL:-http://localhost:${ENV_PORT}}"
-
   # ── origin checking, decided by the machine rather than by a default ──
   #
   # ALLOW_ANY_ORIGIN defaults to ON inside the platform, which CLAUDE.md says is
@@ -524,13 +492,12 @@ if ! skip; then
   echo ""
   echo "     to write:"
   echo "       PORT=${ENV_PORT}   BROWSER_RELAY_PORT=${ENV_BROWSER_RELAY_PORT}"
-  echo "       PUBLIC_URL=${ENV_PUBLIC_URL}"
   echo "       ALLOW_ANY_ORIGIN=${ENV_ALLOW_ANY_ORIGIN}"
-  echo "       DATA_PATH=${OFFICER_ROOT}/data"
-  echo "       OFFICER_ITEMS_DIR=${OFFICER_ROOT}/capabilities"
-  echo "       HOME_DIR=${USER_HOME}"
   echo "       POSTGRES_URL=${POSTGRES_URL%%:*}://…"
-  echo "       JWT_SECRET, VAULT_STORE_KEY — not shown"
+  echo ""
+  echo "     the install root is not written here — the platform derives it as the"
+  echo "     parent of the repo, so data/, capabilities/ and dockers/ follow from"
+  echo "     ${OFFICER_ROOT} without anything having to agree with anything."
   echo ""
 
   if confirm "Write it?"; then