Summary

• extract Markdown image references before gog docs write --replace --markdown uploads content through Drive
• upload cleaned Markdown with placeholders, then reuse the existing Docs image insertion path
• preserve remote image support, local image resolution relative to --file, default sizing, custom width/height attrs, pageless behavior, and existing output shape

Why

gog docs create --file already handles Markdown images in two passes: it strips image Markdown into placeholders before Drive import, then reads the converted Google Doc and inserts images through the Docs API with explicit sizing. That keeps large source images from being imported at their natural dimensions and gives users consistent defaults such as the 468pt max width.

gog docs write --replace --markdown was taking a different path. It sent the raw Markdown body directly to Drive update, which let Drive import image references itself. That bypassed the existing sizing logic, so large images could become oversized in the resulting Google Doc.

This change makes the write path follow the same pattern as document creation: extract images first, let Drive convert the cleaned Markdown, then reuse insertImagesIntoDocs to place remote or local images with the same default and explicit width/height handling.

Validation

• go test ./internal/cmd -run "TestDocsWrite_Markdown"
• go test ./internal/cmd -run "TestDocsWrite"
• git diff --check

Note: go test ./internal/cmd still fails locally on an unrelated auth-state-sensitive TestRequireAccount_Missing because this environment has actual@example.com configured.