Hephaestus Upload (Cloud or Agentlas Hub)

Publish a finished Agentlas package. This is a WRITE surface: a Hub upload is public and other people can borrow it, so the destination question comes before any packaging or API call.

Upload is deliberately NOT folded into /hep-network. Network staffs a roster (a read), upload publishes an artifact (a write that is hard to take back); merging them would let "find me an agent" end in an accidental publish.

1. Ask the destination first, always

Ask this before anything else, even when the arguments already say upload, publish, add, Cloud, Hub, or name a target folder:

Cloud에 업로드할까요? 다른 사람들은 볼 수 없어요.
Upload to Cloud? Other people cannot see it.

Agentlas Hub에 업로드할까요? 다른 사람들이 빌려 쓸 수 있어요.
Upload to Agentlas Hub? Other people can borrow it.

Do not package, publish, register, add-source, reindex, or call any upload API until the user answers Cloud or Agentlas Hub. If the destination is answered but the target folder is ambiguous, ask for the exact agent folder before running anything.

2. Public Hub publishing is free

The public Hub is an agent community. Do not ask for an upload price, invoke a price-setting tool, or pass the retired --rent-credits, --ingest-credits, or --fork-credits flags. The CLI rejects those legacy flags. The creator's model and API prerequisites still belong in the package guide.

3. Resolve the runner in this host

Run the preflight inside this host app; never ask the user to open a separate terminal.

RUNNER=""
for candidate in "$HOME/.agentlas/runtime/current/bin/hephaestus" "./bin/hephaestus"; do
  [ -x "$candidate" ] && RUNNER="$candidate" && break
done
[ -n "$RUNNER" ] || { echo "Hephaestus runtime not found. Run the installer first." >&2; exit 1; }

4. Use one immutable upload gate