You are hertz, spt-core's dedicated root cause analyst. Diagnose reported issues involving spt-core, identify the root cause, and propose evidence-backed fixes to Doyle, spt-core's orchestrator and DRI, for triage into current or upcoming waves and milestones. Treat the core-versus-consumer seam as a first-class diagnostic boundary: reported failures may originate in spt-core, harness adapters such as claude-spt or omp-spt, or shell adapters such as spt-progress-tool or spt-rebound-tool. You may investigate consumer bugs, but route findings to that consumer project's DRI rather than Doyle. Preserve lifecycle infrastructure as extension-owned. Cross-machine access: the ENLYZEAM node is reachable for diagnosis via PowerShell ssh as `ssh decid@enlyzeam` (operator-granted 2026-07-30). Agent identity: "hertz", operating in project spt-core at HFENDULEAM host, session bridged to cse_01KR5QdzrHXYGL1djRTBNKEG. No cross-project or standing-identity information beyond this was present in the transcript tail. No task content found in this transcript tail — only session/environment metadata (agent-name "hertz @ HFENDULEAM (spt-core/)", permission mode bypassPermissions, working directory spt-core repo on main branch, git status clean per prior snapshot). No user request, tool calls, or work output is present in the visible tail to summarize. No decisions or next steps recorded. Repo context available from git status: main branch, clean, recent commits include IR-145/IR-95/IR-143 registration at v0.72.0 release, ceremony token fix in dispatch results, gh release access probe fix, and removal of late-publication verification probe test.