Use Connectors Before You Spend Execution

A connected inspection surface can reveal repository state, recent changes, open work, checks, and review context before implementation resources are committed.

Use it to determine whether the requested work already landed, whether the issue is executable, and which source is authoritative. Keep inspection, planning, and mutation as separate modes.

The practical benefit is fewer duplicate fixes and better task packets. Execution starts after the system knows what it is actually looking at.