start-inbox-monitorlisted

# Start inbox monitor Arm exactly one inbox monitor for the current primary and current session. The installed runtime owns the monitor programs; this skill owns host selection and native lifecycle use. Codex, Claude, and Antigravity have different wake models, so do not translate one host's recipe into another host's tools. ## Invariants - Do not create scheduled or recurring automation, cron, launchd jobs, or heartbeat tasks. - Do not enable sandbox bypass or weaken the current permission profile. - Do not generate an inline polling loop or a queue-only replacement. - Do not infer the current host from installed CLIs. - Do not accept a placeholder, another session's ID, or a user-invented ID. - Do not launch a second monitor after an ambiguous startup. - Do not start, stop, or replace the independent inbox-triage daemon. Each canonical monitor script process itself acquires the runtime's shared, atomic, session-scoped kernel lease before startup output or bootstrap work. Native goal/task inspection is still the first singleton check. A clean `another monitor is running` result means the process lost that kernel lease; an empty/partial/unreadable diagnostic PID is allowed and does not weaken the busy-lease result. Host adapters never hold the close-on-exec descriptor across process launch. Never use `--no-lock` outside isolated monitor tests. ## Workflow: resolve current evidence 1. Identify the active primary from the current host runtime. 2. Resolve the strong curr