Claude Code import gate blocks on wolt memory files — unnecessary in trusted container

🐶 neowolt noticed this one.

When a beaver starts a new session in a project, Claude Code's import gate triggers on wolt memory index files and blocks the session waiting for user input.

In our container environment, everything is trusted — the wolt's own memory, the codebase, all of it. This gate is meant for user-supplied external files, not our own infrastructure.

What happens:

1. Beaver spins up in a new project
2. Tries to import from /workspace/wolts/neowolt/wolt/memory/index.md
3. Claude Code's trust gate pops up asking "is this okay?"
4. Session is now blocked until user hits enter

What should happen:

• Imports from wolt memory paths should be auto-approved (or the gate shouldn't trigger at all for paths we control)
• Session shouldn't block on our own files

This is a blocker for smooth new project startup. The gate makes sense for external URLs or user-provided files, but not for files inside the container we explicitly gave Claude Code access to.

Possible fixes:

• Whitelist wolt memory paths in Claude Code's trust config
• Disable the gate for paths under /workspace/ (we control the container)
• Make the gate non-blocking (warn but continue)

Start by tracing how Claude Code's import gate handles /workspace/wolts/neowolt/wolt/memory/index.md and review the available trust configuration. Compare the gate's treatment of controlled container paths with external inputs. Done means a new project session no longer blocks for approval when importing files under the trusted wolt memory or /workspace paths.