Triage auto-allow threshold rises to 8, reducing Gateway escalations

Watcher's built-in Triage monitor now auto-allows more low-risk tool calls before escalating them for a second review, and self-hosted deployments can adjust that cutoff without waiting for a new release.

What's new?

• The Triage monitor's auto-allow cutoff moves from 6 to 8, so a tool call scored 7 by Triage is now allowed at that stage instead of escalating to the Gateway monitor; scores of 8 and above still escalate, and any tool's own flag or deny thresholds still apply when they are lower.
• Self-hosted deployments can set a Triage escalation threshold in the server configuration to raise or lower this cutoff independently of the Watcher release cycle.
• When the same conversation is reported through both the hook API and the Watcher client, the two uploads now converge on a single session and a single record per tool call, so a later upload containing only the human response no longer overwrites Watcher's recorded evaluation.
• Watcher Live's profile commands (profile set, profile current, profile list) now report the profile that is actually active, including when a machine-level default overrides the one requested, instead of showing the requested profile as if it were applied.