Signal End To End

• Signal changes rarely stop at extraction; CLI schema, router-owned metadata headers, or bindings often need updates too.
• New matched-signal families often need more than one UI touchpoint: matched_signals JSON, x-vsr-matched-* headers, chatRequestSupport, HeaderDisplay, HeaderReveal, topology backend conversion, and topology frontend parser or constants.
• New signal semantics need explicit E2E ownership, not just unit-level classifier coverage.
• If the header or topology contract originates from signal evaluation, keep it in this primary instead of inventing a header-only flow.

Must Read

• docs/agent/change-surfaces.md
• docs/agent/module-boundaries.md
• docs/agent/playbooks/go-router.md

Standard Commands

• make agent-report ENV=cpu CHANGED_FILES="..."
• make agent-ci-gate CHANGED_FILES="..."
• make agent-feature-gate ENV=cpu CHANGED_FILES="..."

Acceptance

• Router config, signal extraction, and Python CLI schema stay aligned for the signal contract
• Any router-owned signal metadata updates the relevant classify or eval payloads, emitted headers, and dependent reveal or topology consumers together
• Relevant E2E coverage is added or updated when behavior changes