Position parameter for REST API

What is the challenge?

• The API has no way to set a page or folder's position within the table of contents tree. parent_id controls nesting, but not order among siblings. Reordering only works by manually dragging in the UI.

What is the impact?

• Teams automating knowledge setup can't fully script their structure. Anything needing a specific order requires manual cleanup after every API-driven creation.

Describe your idea.

• Add a position parameter to the update a note endpoint