[BUG] Sessions containing /loop command are permanently hidden from /resume

If a session contains even a single /loop invocation (regardless of whether it was the session's primary purpose), that session is permanently filtered out of the /resume picker — including search.

Steps to reproduce

1. Start a normal session
2. Run /loop once (e.g. to try it out), then stop it
3. Continue working in the same session as usual
4. Exit and try to find the session via /resume — it's gone

Expected behavior

Sessions should only be hidden from /resume if they were exclusively loop sessions (no human conversation after the loop ended), or not hidden at all — with a visual indicator instead.

Actual behavior

The session is permanently excluded from /resume and from search. The only workaround is claude -r <session-id> with a manually copied UUID.

Root cause (found via binary inspection)

The filter checks r.includes("<command-name>/loop</command-name>") on the raw session file content and marks it as filtered from /resume: /loop session. One match = excluded forever, regardless of what happened in the session after.

Version

2.1.201