{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://git.octoturge.com/Continuum/continuum-schemas/raw/branch/main/schemas/bambulab/v1/report/print/print.schema.json",
  "title": "PrintReport",
  "description": "The ongoing print-state push (root key \"print\") — NOT a direct reply to the pushall request (that goes to \"pushing\", see request/pushing/pushall.schema.json). Sending pushall makes the printer start/refresh this stream; it isn't itself request/response, which is also why this is its own category folder rather than sitting under pushing/ — a category here is 'what root key does this arrive under', not 'what triggered it'. Doesn't extend envelope.schema.json: the example seen so far doesn't show sequence_id/command on this one, and it may genuinely not carry them (an async push, not a direct reply) — revisit if a real capture proves otherwise. The real payload has many more fields than shown here (this example was truncated) — add them under `properties` the same way you'd add them to bambu_commands/print.rs.",
  "type": "object",
  "properties": {
    "ams": { "$ref": "ams.schema.json" },
    "ams_exist_bits": { "type": "string" },
    "insert_flag": { "type": "boolean" },
    "power_on_flag": { "type": "boolean" },
    "tray_exist_bits": { "type": "string" },
    "tray_is_bbl_bits": { "type": "string" },
    "xcam": { "$ref": "xcam.schema.json" },
    "xcam_status": { "type": "string" }
  }
}