xarmian 80ec51c18c fix(BUG-3185): an item export's file name whose stem is a Windows device gets a "_" prefix, on the server and in the CLI (#1495) ...

`pad item export` saves to "<slug>.pad.md", so an item slugged nul, con,
aux, prn, com1-9 or lpt1-9 named a Windows device, and the CLI on Windows
wrote the artifact nowhere.

- attachments.WindowsDeviceName is exported (a rename, no behaviour
  change): the one device rule from BUG-2822 (#1493), where the stem ends
  at the first "." or ":". Its doc says not to write a second one.
- artifactExportFilename prefixes "_" to a device name, so the
  Content-Disposition both clients save under is safe.
- The CLI applies the same rule to the path it will write
  (defaultExportPath): it is the process writing the file, an older server
  still suggests the device name, and the "<ref>.pad.md" fallback never
  passed through the server.

Population (every Content-Disposition and client default name): the
bundle export ("<slug>-export.tar.gz", whose stem is never bare), the account
export (a fixed name) and the edit temp/recovery files (the "pad-edit-"
prefix) are safe; attachments are #1493. Import has no mirror: nothing it
creates is named from content.

Claude-Session: https://claude.ai/code/session_01Vf8uZmYdsrQqJtbAmjUFSX

2026-09-24 03:44:11 -04:00

..

loadtest-collab

fix(loadtest): codex catch-up review fixes (TASK-1270) (#470)

2026-05-09 16:41:07 -04:00

pad

fix(BUG-3185): an item export's file name whose stem is a Windows device gets a "_" prefix, on the server and in the CLI (#1495)

2026-09-24 03:44:11 -04:00