edgeos-applications

# OpenClaw Popup Application (v1)

Run the EdgeOS application flow with a strict, reliable sequence:

1. Authenticate user via OTP once per session.
2. Persist and reuse JWT for all subsequent calls in that session.
3. Resolve target popup.
4. Collect required application fields.
5. Submit application.
6. Check status on demand.
7. After acceptance, guide product selection and payment.

Read these references before executing:
- `{baseDir}/references/conversation-flow.md`
- `{baseDir}/references/flow.md`
- `{baseDir}/references/api-contract.md` (API source of truth)

Before collecting fields, read workspace `USER.md` and use it as prefill context when values are relevant and trustworthy for the current user.

## Runtime configuration

This v1 skill is intentionally pinned to PROD backend values (no user setup required).
Values are defined once in:
- `{baseDir}/scripts/env.sh`

Do not ask users to configure runtime values in v1.
Use the values from `scripts/env.sh` consistently for auth and API calls.

## Script-first rule

Prefer scripts in `{baseDir}/scripts` over ad-hoc curl construction:
- `auth_request_otp.sh`
- `auth_login.sh` (persists JWT in local state file)
- `submit_application.sh`
- `check_application_status.sh` (supports `--application-id` or `--citizen-id` + `--popup-city-id`)
- `payment_preview.sh`
- `payment_create.sh`
- `payment_status.sh`

Only fall back to raw curl if a script cannot handle the case.

## Data collection policy (strict minimal questions)

Use this exact sequence:
1. Determine required + optional application fields.
2. Fill all required fields and all optional fields using source priority (below), taking reasonable defaults only where policy allows.
3. Ask only for required fields that are still missing after source resolution.
4. Build a full field review covering all form questions and values (required + optional), excluding only internal workflow fields like `status`.
5. For every unresolved field, ask the user and label it as requ...