@stage5/lumine 0.2.70 → 0.2.71
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +8 -4
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -159,10 +159,14 @@ grants. A creator or app owner can remove one with
|
|
|
159
159
|
`lumine sdk call live.deleteReplay '{"replayId":"..."}' --allow-write`.
|
|
160
160
|
|
|
161
161
|
`Twinkle.rewards` is callable too, on the same server-verified endpoints the
|
|
162
|
-
published app uses — the CLI holds no award logic.
|
|
163
|
-
|
|
164
|
-
|
|
165
|
-
|
|
162
|
+
published app uses — the CLI holds no award logic. The server decides who may
|
|
163
|
+
take part exactly as it does for the app in a browser: any signed-in account
|
|
164
|
+
that can open a public app with an approved reward policy, the owner included,
|
|
165
|
+
within the policy's attempt, daily and budget limits. `lumine sdk call
|
|
166
|
+
rewards.getStatus '{}' --build <id>` is read-only and works without
|
|
167
|
+
`--allow-write` (the endpoint accepts only the `rewards:claim` scope, which is
|
|
168
|
+
minted for it as a deliberate exception to the read-only rule, but only the
|
|
169
|
+
status operation is sent).
|
|
166
170
|
`rewards.start '{"ruleId":"..."}'` and
|
|
167
171
|
`rewards.claim '{"challengeId":"...","answers":[1,2]}'` mutate real XP/Coins
|
|
168
172
|
state and require `--allow-write`. Every rewards call first reads the
|