2f25dec349
A bot profile's system prompt could list the DEFAULT profile's ~80 skills and print 'Active Hermes profile: default' — while the live skills_list() correctly showed the bot's real (often empty) set. The agent plans against that index, so a false inventory makes it claim capabilities it doesn't have, waste context tokens, and lose trust. Root cause (confirmed empirically): the skills-prompt builder and the active-profile line resolve the home through get_hermes_home(), which reads a HERMES_HOME ContextVar. ContextVars do NOT propagate into threading.Thread, so an agent build running on a thread that didn't bind the profile's home falls back to the launch (default) home and builds default's index. A bare no-override thread builds default's full 7621-char block; the same thread with the fix builds empty. Fix: resolve the agent's OWN home from its dedicated _session_db.db_path (ground truth, ContextVar-independent) and pass it explicitly: - build_skills_system_prompt(skills_dir_override=...) scopes the index, the disk snapshot, and external-dir resolution to that home - the active-profile line derives the profile name from the same home Both fall back to ambient resolution when no db is present, so the CLI and default-profile paths are unchanged. Regression tests: an empty bot profile yields an empty skills block on a bare thread even with ambient HERMES_HOME bound to a skills-rich default; agent-home resolution from session_db.db_path. 3/3.