Sessions with no project directory are never trusted and get their own settings handling

What

Claude Code can now recognise a session that has no project: no starting directory and no project path. In such a session:

• Workspace trust, the approval that lets a folder's hooks and settings run, is always refused. There is one exception, for a particular context-store case.
• The warning about ignored settings no longer tells you to run Claude Code interactively and accept the trust dialog. It says instead that a session with no working directory is never trusted.
• Project config reads, including the one that normalises allowedTools, return defaults or nothing instead of looking up an entry in the global config under a project path.
• The cached project path for config is not reused.
• The check for whether the project is tracked returns true straight away.
• Settings-source selection returns both project and local settings without doing any git-tracking work.

Why

This changes whether project-level features such as hooks and settings load when Claude Code runs outside a project. Such sessions no longer read or write a project entry stored under an arbitrary path, and are no longer pointed at a trust fix that cannot work for them.