`KNOT_REPO_SCAN_PATH` doesn't seem to be respected

i've been hosting a knot for the past few versions and the latest update to 1.13.0-alpha appears to have changed the directory that repos are scanned in (maybe due to new DID repo resolution?)

the Dockerfile sets env KNOT_REPO_SCAN_PATH=/home/git/repositories and yet it looks like repos are expected to be found under /home/git instead of the repositories subdir as would be expected

client side

$ git fetch origin
repo not found

fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

relevant docker logs

Accepted publickey for git from [REDACTED-IP] port 47720 ssh2: ED25519 SHA256:Z35UFvFh/+K6juKHjNWq95qtOxmhfhnglMSGDEQzME4
2026/04/27 04:41:17 INFO knot/server/internal: command components handler=Guard components="[cosmichorror.dev knot-docker]"
2026/04/27 04:41:17 DEBU knot: resolve handle DNS handle=cosmichorror.dev err=<nil> did=did:plc:zmzrlti5do46aw3y7jfdzjqs authoritative=false fallback=false duration_ms=33
2026/04/27 04:41:17 DEBU knot: resolve DID did=did:plc:zmzrlti5do46aw3y7jfdzjqs err=<nil> duration_ms=81
2026/04/27 04:41:17 ERRO knot/server/internal: repo not found on disk (legacy) handler=Guard owner=did:plc:zmzrlti5do46aw3y7jfdzjqs name=knot-docker
Received disconnect from [REDACTED-IP] port 47720:11: disconnected by user
Disconnected from user git [REDACTED-IP] port 47720

relevant compose snippet

  knot:
    container_name: knot
    image: knot-dev
    restart: unless-stopped
    volumes:
      - /opt/knot/keys:/etc/ssh/keys
      - /opt/knot/repos:/home/git/repositories
      - /opt/knot/server:/app
    ports:
      - "5555:5555"
      - "22:22"
    env_file:
      - /opt/knot/knot.env

/opt/knot/knot.env

KNOT_SERVER_HOSTNAME=knot.cosmichorror.dev
KNOT_SERVER_OWNER=did:plc:zmzrlti5do46aw3y7jfdzjqs
KNOT_SERVER_DB_PATH=/app/knotserver.db

as you can see no changes to the default KNOT_REPO_SCAN_PATH. is the knot using a hardcoded path instead?