docs: Add Scheduler Device setup guide

[Copilot]

Adds a new reference page for configuring a HyperBEAM node as an AO scheduler, and links it from the existing Running a HyperBEAM Node guide.

New: docs/run/reference/setting-up-a-scheduler-device.md

• Explains that ~location@1.0 and ~scheduler@1.0 are included in the default device list — no extra config needed
• Provides the canonical curl invocation (must run on node host):

  curl -sS -H 'Accept: application/json' http://127.0.0.1:8734/~location@1.0/node

• Describes the expected HTTP 200 response and the resulting on-chain transaction tags (Data-Protocol, Variant, Type: Scheduler-Location, Url using https, nonce)

Updated: docs/run/running-a-hyperbeam-node.md

• Adds a Scheduler Device bullet to the Next Steps section linking to the new page at ./reference/setting-up-a-scheduler-device.md

Original prompt

Create documentation for setting up a Scheduler device and link it from the Running a HyperBEAM Node guide.

Repository/branch:

• Repo: jonny-ringo/HyperBEAM
• Base branch: docs/deploy

Context:

• Existing file to update: docs/run/running-a-hyperbeam-node.md
• Add a new doc page under: docs/run/reference/setting-up-a-scheduler-device.md

Requirements:

1. Add a new bullet in the Next Steps section of docs/run/running-a-hyperbeam-node.md linking to the new page using the correct relative link: ./reference/setting-up-a-scheduler-device.md.

   • Keep formatting consistent with existing bullets.

2. Create docs/run/reference/setting-up-a-scheduler-device.md with title casing consistent with other docs.

   • H1: # Setting Up a Scheduler Device
   • Audience: someone already running a production node.
   • Explain that if they used the default device list, both ~location@1.0 and ~scheduler@1.0 are already onboarded.
   • Provide the key step: call the location device endpoint from the same origin (run the curl command on the node host).

3. Include the canonical curl example (Ubuntu):

curl -sS -H 'Accept: application/json' http://127.0.0.1:8734/~location@1.0/node

• Explain what success looks like: HTTP 200 OK from ~location@1.0.
• Explain that this publishes a transaction announcing the scheduler location.

4. Use the NEW/CORRECT tag format example (GraphQL-style) and state that the emitted transaction should include tags similar to:

• Data-Protocol: ao
• Variant: ao.N.1
• Type: Scheduler-Location
• Url: https://push.forward.computer (use https)
• nonce:
• time-to-live:

5. Keep the doc concise and focused, and include a short verification section suggesting to look for the transaction via Arweave GQL (no need to provide full query unless trivial) and/or node logs.

Notes:

• The repository URL for the existing doc is: https://github.com/jonny-ringo/HyperBEAM/blob/docs/deploy/docs/run/running-a-hyperbeam-node.md

This pull request was created from Copilot chat.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.