Would be nice: Google Docs add-on with a real markup dropdown

Documenting this so the idea is not lost. Low priority — may never be built. The cheaper mitigations are #2.

The want

When editing a staged article in Google Docs, pick the WikiMarkup construct from a dropdown and have it inserted at the cursor, correctly formatted, instead of typing {note}…{/note} by hand and remembering to highlight it.

Shape

A Google Docs add-on (Apps Script) providing a custom menu or sidebar:

• lists the SUMO constructs — {note}, {warning}, {for win,mac,linux}, {key}, {menu}, {button}, {filepath}, {pref}, [[Image:]], [[Internal Link]], templates
• inserts the chosen one at the cursor with backgroundColor #FFF2CC + Courier New, so it is a protected token by construction (see #2 for why the background colour is the thing that matters)
• ideally wraps the current selection where that makes sense, e.g. select text → {note} wraps it

Why this is awkward

• The tool creates a fresh Doc per run, so a document-bound script does not carry over. It has to be a standalone add-on installed once in the account, which means the Apps Script/add-on publishing flow rather than a file in this repo.
• It is a separate deployable artifact in a different language (Apps Script) with its own auth and lifecycle — not something npm run dev can cover.
• Contributors would each need it installed, so it helps the owner more than the team unless it is published properly.

Cheaper things that overlap

• #2 token palette — highlighted tokens in the Doc header, copy-paste to use. Most of the benefit, ~15 lines, no new deployment.
• Docs Substitutions (Tools → Preferences → Substitutions), zero code: ;;note → {note}{/note}. Personal to whoever sets it up, and inserts plain text so the highlight is still manual.
• #2 lint — catches malformed tokens on to-markup regardless of how they were typed, which a dropdown alone would not do.

Revisit only if the palette in #2 still feels clumsy in practice.

Start by reviewing issue #2 and the described Apps Script add-on publishing flow; there is no repository file or entry point identified for this separate artifact. Define the standalone Google Docs add-on scope, authentication and deployment approach, then verify that it can insert or wrap the listed SUMO constructs with the required formatting.