livlive-cli

livlive login            # opens livlive in the person's browser for one press; the token is checked with GET /api/ops and kept in ~/.config/livlive/config.json
livlive login --device   # where no browser can be opened: prints an address and a code the person types in any browser
livlive login --paste    # for CI: paste a token the person made on the backstage page /settings/tokens (shown once, starts lvl_)
livlive logout           # revokes this PC's token at livlive and removes it from the file

livlive ops                                          # name, label, what it does; --project <id> when it needs a project
livlive room.open --json '{"title":"…"}'             # a new room → data.project
livlive room.read --project <id>                     # data.versions, data.current, data.structure (the current 構成表), data.choices
livlive script.check --project <id> --file draft.json   # input.structure: the 構成表; ok when script.save would take it
livlive script.save --project <id> --file draft.json    # keep it as the next version
livlive skills.read --json '{"staff":"tsuzuri"}'      # no project; each skill's id, version, body and words

livlive skills.add --file skill.json
    # {"staff":"tsuzuri","name":"…(one line ≤ 40)","description":"when to read it (≤ 120)","body":"# …(Markdown ≤ 9600)",
    #  "words":{"title":"≤ 16","summary":"one plain sentence ≤ 60","guide":["1–3 plain lines, each ≤ 50"]}}   → data.skill { id, version }
livlive skills.edit --file skill.json   # the same fields + "id" and "version" from skills.read; a newer version is never overwritten
livlive skills.publish --json '{"id":"…","version":3,"price":0}'   # to the market's review; the first publish is made on the page

livlive room.read --project <id>                     # data.choices: cast / forms / channels ids to pick; data.recent: the work records
livlive desk.pick --project <id> --json '{"cast":["<choices.cast id>"],"channels":["youtube"]}'
livlive desk.pick --project <id> --json '{"form":"monologue"}'          # a choices.forms id, or "planned"
livlive request.write --project <id> --json '{"memo":"## 概要\n…","proposals":[]}'
    # the 要望, before script.first (it waits for it); no proposals = answered at once; a proposal waits for the person in the room
livlive request.edit --project <id> --json '{"bring":"<made.asset>"}'   # one change: take / section + words / memo / bring / drop
livlive pitch.put --project <id> --file pitch.json
    # {"title":"…","doc":"## 企画意図\n…","answers":[{"to":"概要","section":"企画意図","how":"…"}],"research":["<made.research>"]} — the 企画書, before script.first
livlive research.bring --project <id> --file research.json
    # {"title":"…","purpose":"…","claims":[{"text":"…","source":"https://…","confidence":"unverified"}]} → made.research
livlive asset.bring --project <id> --json '{"kind":"markdown","title":"メモ","text":"# …","use":"memo"}'   # → made.asset
livlive asset.bring --project <id> --json '{"kind":"markdown","title":"…","text":"# …","use":"memo","from":["<made.research>"]}'
    # written from the room's own research / 構成表 versions / 素材: name their ids in from (at most 6) — the room keeps what it was made from
livlive script.first --project <id> --file first.json
    # {"title":"…","structure":{…},"cast":["<id>"],"form":"monologue","research":["<made.research>"],"requestId":"<uuid>"}
    # → made.version (only on a room with no content)
livlive asset.shelve --project <id> --json '{"asset":"<made.asset>"}'   # later: the next version with that asset on its 参照アセット