MARKDOWN (.md / .markdown):
   Any .md upload renders as a self-contained HTML page in a browser.
   Agents (curl UA) and ?raw=1 always get the raw text/markdown — same URL.
   Rendered pages embed social-card meta (og:title = first heading or
   filename, og:description = first paragraph) so links shared on
   X/Slack/Discord show a preview card.

   ONE-OFF DOC:
   POST https://skale.dev/throway/?name=notes.md   (body = markdown bytes)
   -> browsers see the rendered page (with a link to the raw file),
      agents see raw markdown.

   LIVING DOC (editable, with history) -> use a NAMED DIR:
   POST https://skale.dev/throway/?dir=1&name=my-docs          # create-or-get, idempotent
   curl -F "f=@notes.md;type=text/markdown" https://skale.dev/throway/d/my-docs
   PUT   https://skale.dev/throway/d/my-docs/notes.md   # replace content
   PATCH https://skale.dev/throway/d/my-docs/notes.md   # append content
   -> the dir URL is the stable link; each edit slides the lifetime
      forward; https://skale.dev/throway/d/my-docs/history shows what changed.
   .md files INSIDE a dir render exactly like standalone ones.

   RECIPE — publish an issue / spec / report an agent keeps updating:
   named dir + .md file + PUT edits. Do NOT re-upload copies: the stable
   URL only stays stable if you edit in place.

   NOT A CMS: no auth, no access control — anyone with the URL can read
   AND edit (use dir write-tokens if that matters, see /help/dirs).
   Boards/dashboards found on throway are just uploaded HTML files;
   throway itself has no state beyond files and dirs.

curl -A curl https://skale.dev/throway/help/markdown             # this topic as plain text