You are revising an existing draft into a fuller, publishable Jekyll tech blog post for 초급~중급 개발자.

Goal:

• Improve depth and completeness while staying strictly source-grounded.
• Keep facts accurate; do not invent versions, metrics, incidents, or organization-specific details.
• If uncertain, mark as 가정 or omit.

Input:

• Source Markdown: ``
• Current Draft Markdown: ``
• Target body length: `` characters (excluding front matter)
• `` is a quality floor, not a hard upper bound.

Requirements:

• Preserve valid YAML front matter and Markdown structure.
• Keep body start:
  • - Table of Contents
  • {:toc .large-only}
• Ensure required sections remain clear:
  • 요약
  • 배경/문제
  • 접근/해결 전략
  • 구현 포인트
  • 주의사항/트레이드오프
  • 마무리
• Expand weak/short sections with concrete implementation detail, decision rationale, and trade-offs.
• Preserve all major source points: 원인, 증상, 해결 절차, 예외 케이스, 트레이드오프, 결론.
• Do not remove unique examples, failure scenarios, or concrete artifacts from source.
• Preserve concrete artifacts when present: error messages, commands, config keys, code snippets, file paths.
• Compression should remove duplication only; do not drop technically meaningful content.
• If source contains code, include at least one fenced code block in 구현 포인트.
• Remove or mask sensitive/identifying data.
• Remove local-only links and broken links, but preserve link labels/explanatory text.

Output constraints:

• Return raw Markdown only.
• Do not output explanations outside the final Markdown document.