gameslab.henhen1227.com

checkpoint_work

Group everything you have done since your last checkpoint into one finished phase, with a title and a sentence on what it accomplished. **Call this two to four times over a substantial request** — after the board and pieces are in place, after the rules are, after it validates — and once more with done: true at the end. The person watching sees your phases instead of forty rows, with every call still under them; this is the only summary of your work the page will ever show, because it does not write one for you. The result also carries what *they* did while the step was active, which is how you find out about an edit of theirs without asking. Closing a run marks the work ready to **try**, and `try_it_out` is what the page offers them the moment it lands. When closing a validation phase, preserve its strongest numerical evidence in the summary. Prefer: "40 simulations finished; every rule fired and no game stalled." Avoid: "Validation completed."

Input schema

{
  "type": "object",
  "properties": {
    "title": {
      "type": "string",
      "description": "What this phase was, in three or four words. \"The board and the pieces\"."
    },
    "summary": {
      "type": "string",
      "description": "What it accomplished, in **one short sentence** a person reads. Not a list of tool names. It is shown on a single line under the finished step in Agent Control, so keep it under about 100 characters."
    },
    "done": {
      "type": "boolean",
      "description": "True when this closes the whole request, not just a phase of it."
    },
    "stepId": {
      "type": "string",
      "description": "Required with an active project: the stable id of its current step."
    }
  },
  "required": [
    "title",
    "summary"
  ],
  "additionalProperties": false
}