GuardLatice public network operator challenge bundle

Public anchor: https://ddbs.guardlatice.com/
Challenge page: https://ddbs.guardlatice.com/network/operator-challenge
Packet builder page: https://ddbs.guardlatice.com/network/operator-packet-builder
Challenge API: https://ddbs.guardlatice.com/api/public/network/operator-challenge
Packet builder API: https://ddbs.guardlatice.com/api/public/network/operator-packet/build
Review package API: https://ddbs.guardlatice.com/api/public/network/operator-packet/review-package
Canonicalize API: https://ddbs.guardlatice.com/api/public/external-evidence/canonicalize
Preflight API: https://ddbs.guardlatice.com/api/public/external-evidence/handoff-preflight

Purpose:
- Bind an external operator evidence packet to the current public network observability snapshot.
- Give a non-local operator an offline packet template, builder request, canonical signing request and preflight request.
- Keep claim admission fail-closed until official external-evidence gates review a completed packet.

Use:
1. Inspect challenge-payload.json and MANIFEST.json.
2. Fill builder-request.json or packet-template.json with truthful independent operator identity, endpoint, expiry and public key fields.
3. POST builder-request.json to /api/public/network/operator-packet/build to receive a packet plus signing_message_hex.
4. Sign signing_message_hex with ML-DSA outside GuardLatice control, then add signature fields to the packet.
5. POST review-package-request.json, after replacing the packet object with the completed signed packet, to /api/public/network/operator-packet/review-package.
6. POST preflight-request.json, after replacing the packet object with the completed signed packet, to /api/public/external-evidence/handoff-preflight.
7. Submit only a preflight-ready completed packet to the official drop zone listed by the API.

Helper:
1. Copy operator-profile.example.json to operator-profile.json and replace every REPLACE_WITH_* value with truthful external operator values.
2. Run: python3 operator-fill-review-package.py --profile operator-profile.json --out-dir operator-review-output
3. Sign operator-review-output/signing-message.hex outside GuardLatice control, add signature fields to operator-profile.json, then rerun the helper.
4. Use operator-review-output/review-package.json only when summary.json reports candidate_ready_for_official_drop_zone=true.

Boundary:
This bundle is not external evidence by itself. It imports no packet, admits no sovereign claim, and proves no decentralization until non-local operator evidence is accepted by official gates.
