Several commands documented in README/skill are missing from installed binary (version "dev")

[4ier]

Several commands documented in README/skill are missing from installed binary (version "dev")

Summary

The README / skill docs for v0.7.0 describe a number of commands that my freshly-installed binary does not have. Either:

• the docs are ahead of the latest released binary, or
• go install github.com/4ier/notion-cli@latest is pulling a different branch than the release,
• or the release tag doesn't exist as a public artifact.

Either way, this creates a confusing UX: agents/users read docs, call the documented command, get "unknown command" errors.

Environment

$ notion --version
notion version dev

$ go install github.com/4ier/notion-cli@latest        # (how I installed)

Binary: ~/.local/bin/notion, 10 MB, 2026-05-08 build.

Commands documented but missing

Per the skill docs (claims current = v0.7.0):

Documented command	Result on my build
notion page markdown <id>	unknown command "markdown" for "notion page"
notion page markdown <id> --out page.md	(same)
notion page set-markdown <id> --file new.md	unknown command "set-markdown"
notion page set-markdown <id> --append --text ...	(same)
notion page property <id> <prop-id>	unknown command "property"
notion page archive <id> / notion page trash <id>	only notion page delete exists
notion comment update <id> --text ...	unknown command "update"
notion comment delete <id1> <id2>	unknown command "delete"
notion file get <upload-id>	unknown command "get"

My notion page --help shows:

Available Commands:
  create, delete, edit, link, list, move, open, props, restore, set, unlink, view

— no markdown, set-markdown, property, archive, trash.

Expected

One of:

1. If the docs describe features on a release, make the release installable via go install @latest / Homebrew / npm — the README already advertises these install methods.
2. If @latest intentionally tracks main which has these features, the binary should report a semver (e.g. v0.7.0) rather than the literal string dev so users can tell.
3. If some commands are still in-flight, call them out in the README as "coming in v0.8" and remove them from the SKILL.md distributed to agents.

Why this matters for agent workflows

The skill file at ~/.pi/agent/skills/notion-cli/SKILL.md is what coding agents read to decide what to call. When it advertises page markdown / page set-markdown as the preferred way to do a whole-page dump or replace, agents will try those first, fail, and have to fall back to raw API + custom parsers. This is exactly what I just did — wrote a ~200-line Python uploader because page set-markdown didn't exist and block append --file mangles tables (see issue #1).

Suggested concrete fix

• Tag and publish v0.7.0 (or whatever is current) so go install @vX.Y.Z and the Homebrew/npm artifacts all match.
• Have notion --version print the actual git tag / short sha instead of dev for untagged builds (via -ldflags -X main.version=...).
• Gate SKILL.md features by "available since vX.Y.Z" so agents can check.
• Consider publishing a release JSON at /version.json so agents can probe feature support at runtime.

Related

• Companion issue: block append --file markdown parser drops tables and crashes on ts/sh code aliases.