SwarmSpan developer handoff brief

Start with this read-only check after configuring your coding client's SwarmSpan
MCP connection and the receiving device's agent bridge. Both devices must be
paired, awake, and reachable. The receiving agent needs its own tools and sign-in.

Goal: Ask an available agent on my selected paired computer to report its OS
and installed development SDK versions and return a small text report.

Before assigning work:
- Discover peers and ask me to select one if the target is ambiguous.
- Inspect that peer's advertised agent capabilities. Use an actually available
  provider and execution mode; never assume it matches this computer.
- Limit the task to read-only OS and SDK inventory. Do not install software,
  sign in to services, change settings, edit a repository, or reveal credentials.
- If this would use a paid model route, confirm it is within my authorized spend.

Expected output: developer-inventory.txt in the peer's Agent Handoff folder,
containing OS/version, SDK versions found, and any checks that could not run.

Success criteria:
- Report the work ID and actual terminal status. Accepted or launched is not done.
- Retrieve the returned artifact through SwarmSpan and open it.
- Verify that it contains the requested information and name any missing checks.
- If the task blocks, report the concrete permission, tool, or sign-in requirement.

For later jobs, replace the goal with one small reproducible task and specify:
the allowed checkout and revision; files that may change; exact test/build
command; success criteria; expected logs/artifacts; rollback; and any approvals.
Keep Git, signing, publishing, payments, and account changes explicitly scoped.