---
name: project-version-change-priority-high
description: "version-change owl message uses priority=high (HIGHEST PRIORITY banner) because it only fires on Stop hook — agent turn already ending, banner can't interrupt"
metadata: 
  node_type: memory
  type: project
  originSessionId: 913dd2ae-1860-4575-829c-2458854f7a6d
---

Version-change owl message (`<spt-version-changelog>`) routes through `priority="high"` + `[OWL SYSTEM - HIGHEST PRIORITY] STOP your current task` banner. `is_informational` at `src/common/hook_output.rs:319` only matches `[WORKING_PERCH_NOTICE]` — not version-change.

**Why:** Stop hook is the only emission point. Agent turn is ending anyway when banner arrives — "STOP your current task" is structurally a no-op for the receiving agent. The earlier n4b "defect 2" concern (banner misleading Claude into treating changelog AUQ as urgent inter-agent comm) was REVERTED on 2026-05-20 as N/A — the AUQ-misleading rationale is irrelevant when there is no current task to stop.

**How to apply:** If anyone proposes re-adding `<spt-version-changelog>` to `is_informational` in `src/common/hook_output.rs` to suppress the urgent banner, push back. The banner is harmless here. If new emission sites for version-change are added OUTSIDE Stop hook (e.g., PreToolUse, SessionStart), revisit — those would interrupt live work and the n4b concern reactivates. See `.planning/quick/260517-n4b-version-change-uat-defect-cleanup/260517-n4b-SUMMARY.md` (defect 2 marked N/A) for history.