IS_DEMO skips the trust dialog without granting trust, so the status line and hooks silently never run

What happens

When I open Claude Code in a new folder whose parent folder is already trusted, it doesn't ask me to trust the folder. It seems to treat the folder as trusted through the parent. But the folder's own entry in ~/.claude.json is created with hasTrustDialogAccepted: false, and the status line never appears in that folder. It shows up fine in sibling folders whose own entry is true.

Since the trust question is skipped, nothing ever sets that value to true. The only way out is editing ~/.claude.json by hand.

Steps to reproduce

1. Trust a parent folder, e.g. ~/Development/Projects (hasTrustDialogAccepted: true).
2. Set up a command status line in ~/.claude/settings.json.
3. Clone a new repo to ~/Development/Projects/new-repo and run claude there.
4. No trust question appears, and ~/.claude.json now has "~/Development/Projects/new-repo": { "hasTrustDialogAccepted": false, ... }.
5. The status line doesn't render. The status line command works when run by hand in that folder with the same JSON input.
6. Set the project's hasTrustDialogAccepted to true and restart. The status line appears.

Expected

Trust should be checked the same way everywhere. Either:

• the status line (and anything else that needs trust) also counts the trusted parent folder, like the trust question does, or
• the trust question is shown for the new folder so the user can accept it.

Environment

• Claude Code 2.1.282, macOS (Darwin 27.0.0)
• Status line: {"type": "command", "command": "/path/to/statusline-binary"}
• 6 of my ~256 projects are in this state. All of them were created after the parent folder was trusted.

Related

• #96928: worktree of a trusted repo stuck on "workspace isn't trusted", trust dialog never shown
• #90220: hasTrustDialogAccepted: false alongside working hooks, no reliable trust signal