result

const (
	ExitOK         = 0 // success
	ExitGeneric    = 1 // unclassified error
	ExitUsage      = 2 // bad flags/args, validated before touching Chrome
	ExitConnection = 3 // can't attach to / launch Chrome
	ExitTarget     = 4 // selector not found, nav/wait timeout, ambiguous/unknown target
	ExitCDP        = 5 // a CDP method returned an error
	ExitDaemon     = 6 // daemon not running / already running / stale lock
	ExitPermission = 7 // refused by policy (origin, verb, or upload root)
)

const (
	CodeGeneric    = "generic"
	CodeUsage      = "usage"
	CodeConnection = "connection_failed"
	CodeNotDebug   = "not_debug_enabled"
	// CodeConsentPending is Chrome holding its browser-modal "Allow remote
	// debugging?" dialog: the port is open, the WebSocket upgrade is hanging,
	// and nothing is wrong except that a human has not answered yet. It shares
	// exit 3 with the other connection failures deliberately — a new number
	// would break the documented contract — but it is a distinct code because
	// the remedy is "click the dialog", not "check your setup".
	CodeConsentPending = "consent_pending"
	CodeTargetTimeout  = "target_timeout"
	CodeTargetNotFound = "target_not_found"
	CodeAmbiguous      = "ambiguous_target"
	CodeNoTarget       = "no_current_target"
	// CodeCoordinateOOB is a coordinate outside the current viewport (RFC-0014).
	// It is deliberately NOT clamped: a wrong-sized window is the usual cause,
	// and clamping would silently turn it into a mis-click somewhere real.
	// error.details carries the point and the viewport so a caller can
	// re-screenshot instead of guessing.
	CodeCoordinateOOB = "coordinate_out_of_bounds"
	CodeCDP           = "cdp_error"
	CodeDaemon        = "daemon_error"
	// CodePermissionDenied is the policy layer's refusal (RFC-0012, RFC-0006).
	// It is deliberately distinct from a target error: an agent must be able to
	// tell "policy forbids this, do not retry, tell the user" from "element not
	// found, retry differently".
	CodePermissionDenied = "permission_denied"
	// CodeAssertFailed is an assertion verdict, not a tool failure: the command
	// ran fine and the thing it was asked to check was true (console
	// --fail-on-match found messages). It maps to ExitGeneric so `nonzero means
	// the assertion tripped` keeps working in a CI `set -e` script, while the
	// code still lets a caller tell "the page logged an error" apart from "the
	// tool broke". Shared with RFC-0003's net --fail-on-match.
	CodeAssertFailed = "assertion_failed"
)