Two more links in the same chain, both of which fail SILENTLY — the pod serves
the base weights under the adapter's name and nothing errors.

* `seed_model_env` computed the content id behind `os.path.isfile(local)`, which
  is False for a directory, so the adapter never reached the pod's config. The
  per-request push sends the BYTES but its rewritten entry is discarded by the
  caller, so the seed is the only thing that tells a pod an adapter exists.

* a named shared pool seeded only the entry of whichever model created it;
  `seed_entries` was populated for CAPABILITY pools alone. Sharing a pool exists
  so one pod answers for several names on one copy of the weights — a base and
  its adapters — which cannot work when only one name is known. Siblings now
  travel with `path` resolved to what the pod can FETCH, because these entries
  are described by `runpod.hf_repo` and carry no path of their own, and a seed
  without one is dropped.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01PxYHWbCAjjjD7A1rhFKtaW