Lexicon Garden

pet.trezy.getResetStatus

The caller's most recent account reset, if they have ever started one. Answers the question the client asks on every load: is a reset running, did the last one finish, and did it finish cleanly. A QUERY rather than a procedure because it is read-only and polled while a reset runs. It takes no parameters at all — it reports on `caller_did` and nothing else, so there is no way to watch somebody else's reset. Anonymous callers get a refusal rather than a 401: a Lua script cannot set its own HTTP status, and this is a status read rather than an action, so a 200 carrying `not-authenticated` is the honest shape.

Repository @trezy.pet did:plc:ollch4g7tes2reb5eceiwuol namespace authority
Details · query
Kindquery
Authoritytrezy.pet
Indexed
Compare Edit in builder → Fork →

Query

query · GET

Output

application/json

complete

boolean

Whether the finished job cleared every ledger row. ⚠ ONLY MEANINGFUL WHEN `status` IS `completed`, and FALSE THERE MEANS THE ACCOUNT IS PARTIALLY RESET — the client must not send that player to onboarding, because a surviving row will refuse the first pet they pick.

error

string

Present instead of a status.

  • knownValues: not-authenticated | unavailable

failure

string

The job's error, when it failed. Verbatim from the worker and not written for a player — show it as diagnostics to copy, not as the explanation.

jobId

string

The reset being reported on.

message

string

progress

ref

The last snapshot the job wrote. Absent before it writes its first.

Reference

status

string

The job's state. `pending` and `running` both mean a reset is IN FLIGHT and the game should not be played over it — the ledger is being deleted underneath. `paused` and `cancelled` mean an operator stopped it, which leaves the documented partial state: the ledger is gone and some records may remain.

  • knownValues: pending | running | completed | failed | paused | cancelled

survivingTables

array

Ledger tables that could not be cleared. What to quote when reporting a failed reset.

itemsstring

#progress

object

The job's own snapshot, passed through as it was written. Every field is optional because the job writes different shapes at different phases, and a client that assumed otherwise would break the moment a phase was added.

Properties

attempted

integer

Records tried so far, whether or not they went.

clearedRows

integer

deleted

integer

Records actually deleted.

phase

string

Which part of the reset is happening.

  • knownValues: starting | listed | ledger | records | done

recordsTotal

integer

Records found to delete.

tablesDone

integer

tablesTotal

integer

Similar lexicons

semantic match

Lexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.

  • pet.trezy.resetAccount

    procedure

    Queue the erasure of everything the game knows about the caller. THE MOST DESTRUCTIVE CALL IN THE GAME AND IT CANNOT BE UNDONE — pets, money, the starter grant, the high-water mark and every record in the caller's repo. It ENQUEUES rather than doing the work, and returns a job id to watch with pet.trezy.getResetStatus. That is not for the progress bar's sake: the erasure makes one PDS round trip PER RECORD, activity records accrue one per interaction, and XRPC scripts have an instruction limit