Document shortcuts and the draft composer

[jesseditson]

Documents the shortcut drafts feature landing in the editor (archival-editor#468).

archival_editor.toml gains a top-level [[shortcuts]] array naming the lists worth one tap from anywhere in the editor. Configuring one puts a button in the bottom right corner of every editor screen that opens a full-screen composer for a new entry, with a publish button that writes and deploys it in one step.

Three sections on the Archival Editor Configuration page:

• Shortcuts — the name / path keys, that shortcuts is reserved at the top level, and how path addresses a list: an object type, the filename when that type holds many objects, then child lists with the index of the entry descended through between them. Also what makes a shortcut resolve to nothing, and that correcting the path brings it and its drafts back.
• Drafts — the badge and menu, save / cancel / publish, paging between drafts, that a draft lives on the device and is never a pending change to the site. Plus what publishing derives the commit message and the new filename from, and that publishing a draft publishes whatever else was unsynced.
• Changing a schema under an open draft — a field the type no longer declares, or one whose type changed incompatibly, is dropped on open; everything still valid is kept.

The existing views content moves out of the page description into an Object views section, so each topic gets its own sidebar entry and the page matches the description-plus-sections shape every other doc with sections uses. Its wording is unchanged.

Verified with archival build: the three sections render with anchors, the sidebar picks them up, and the new content reaches dist/docs/llms.txt.

🤖 Generated with Claude Code