Naver drafts

Naver Blog drafts (임시저장 글) and edits to published posts. There are three different jobs here; find out which one the person means before calling anything:

The person wants	Tool	What happens
A draft in Naver's draft box published exactly as it is there	`publish_naver_draft`	The extension opens that draft in Naver's editor and presses publish, so edits made by hand in Naver are kept
Uplika's own copy of a draft it saved with `options.naver_blog.draftOnly` published instead	`update_post`	Uplika's text goes out as a new post with its own URL, and the old draft leaves the box
A post that is already published changed	`update_post`	The post is rewritten in place, at the same URL

Before anything

Call bridge_status. The Uplika extension in the person's Chrome reads the draft box, reads posts written in Naver's editor and writes the posts. If state is not online, relay userMessage word for word. With a terminal on the same computer, show the wake command for their system and run it only if they say yes; without one, ask them to open Chrome. Listing drafts and reading a post need it online, so wait until the person says Chrome is open.
If any call answers workspace_required, show the workspaces it lists, ask which one, and pass workspaceId from then on.

naver-drafts

Naver drafts

Before anything

Publish a draft as it is