opencode.service diagnostic cgroup contamination

Trap: treating changes in memory.events, PSI, reclaim, or swap during diagnosis as pure OpenCode workload evidence looks right because the assessment is read-only. Fix: check /proc/self/cgroup first; diagnostics launched inside opencode.service share its memory accounting and can trigger reclaim, so use snapshots as bounded evidence and never infer an uncontaminated event rate.