proxy/.scratch/tui-redesign/issues/09-protocol-probe-field-action.md

09 — Attach Protocol Probe to the Profile field

What to build: Make Protocol Probe an explicit, user-initiated URL-field action whose progress and result remain attached to the input that produced them.

Blocked by: 08 — Deliver the mature Profile editor.

Status: ready-for-agent

• The applicable URL field visibly offers Protocol Probe and documents its keyboard shortcut.
• Probe never runs when the form opens, when focus changes, or when a Profile is saved.
• Progress, endpoint-safe status, and detected capabilities render with the initiating field rather than as unrelated global status.
• HTTP-only detection populates the established HTTP representation.
• SOCKS5-only detection preserves the established socks5h semantics.
• Dual HTTP/SOCKS5 detection creates the established compatible Advanced Profile values.
• Editing the relevant URL, changing mode, saving, or cancelling invalidates an in-flight result.
• Repeated invocation while the same probe is active does not start duplicate work.
• Userinfo and credentials never appear in dial evidence, status, errors, or rendered frames.
• Failure and unrecognized-protocol results leave user input editable and do not prevent saving a manually chosen value.
• Complete-Model tests cover all capabilities, failure, explicit invocation, no hidden network work, duplicate suppression, resize, and every stale-result path.