olcli 0.15.3

olcli 0.15.3

Fixed

• mv and rename_entity move entities between folders. olcli rename (alias mv) and the MCP tool rename_entity used to rename only, so olcli mv sub/x.txt chapters/x.txt failed with HTTP 400 even though mv is documented as a move. The destination now decides what happens:

  • intro.tex renames in place; the entity keeps its folder, as before
  • chapters/intro.tex moves the entity into chapters/ and renames it; missing folders are created
  • chapters/ moves it and keeps the name
  • / or a leading / targets the project root

  Documents, files and folders can all be moved. A destination that already exists, a missing source, or a folder moved into itself or one of its subfolders is refused with exit status 1 before anything is written. rename_entity accepts the same paths in new_name, and its confirmation shows From, To and any folders it creates.

  Thanks to @Wang-Chuming for reporting that the mv example could not move a file (#61).

Changed

• The MCP registry entry (io.github.aloth/olcli) is now published by the release workflow after npm publish.

Documentation

• SKILL.md, README.md and docs/MCP.md describe rename/mv as rename and move. The 0.15.2 docs claimed a rename moves an entity to the project root; it keeps its folder. docs/ARCHITECTURE.md lists the move endpoint.

Full changelog: v0.15.2...v0.15.3