docs(review): hygiene cleanup and review preparation for 3 pending posts

src/content/posts/architecting-sea-payment-and-offline-licensing-pipelines.md

@@ -33,7 +33,7 @@ When engineering commercial distribution for client-side desktop utilities acros
 Asian markets (specifically Malaysia, Singapore, and Indonesia), standard Western payment
 architectures fall short.
 
-If you drop Stripe Elements or PayPal onto your checkout page, you immediately hit two walls:
+Dropping standard Stripe Elements or PayPal onto a regional checkout page triggers two immediate barriers:
 1. **Low Credit Card Penetration**: Across local businesses and independent operators in Malaysia, over **70% of digital transactions occur via FPX (Financial Process Exchange) direct online banking or DuitNow QR rails**, not Visa or Mastercard.
 2. **Offline Software Piracy**: Desktop executables distributed as raw binaries suffer immediate redistribution unless tied to cryptographically verified, machine-specific hardware fingerprints.
 
@@ -121,8 +121,8 @@ I implemented a dual-tier delivery architecture:
 No intermediary landing pages, no ad-supported download portals, and no third-party captcha friction:
 one purchase yields one cryptographically signed installer.
 
-<details>
-<summary>View multi-lingual checkout notification dispatch (Python excerpt)</summary>
+<details class="tech-deep-dive">
+<summary>🔍 View multi-lingual checkout notification dispatch (Python excerpt, 27 lines)</summary>
 
 ```python
 def notify_fulfillment(order_id, customer_email, bill_code, license_key, download_url):

src/content/posts/batch-generating-80-technical-covers-with-comfyui.md

@@ -37,8 +37,8 @@ and a third a photorealistic macro lens shot, the site feels like an uncurated c
 Recently, the technical learning portal I manage (`hoelee-learning`) needed 89 individual cover assets
 to replace generic SVG placeholders.
 
-If you generate 89 covers by clicking around in WebUI interfaces or Discord bots, you immediately
-confront three structural problems:
+Attempting to generate 89 covers manually via WebUI interfaces or Discord bots introduces
+three structural failure modes:
 1. **Style Drift**: Different seeds and random prompts cause lighting, camera angles, and art directions to wander uncontrollably.
 2. **Diffusion Text Hallucination**: Diffusion models notoriously struggle with text. They produce garbled alien glyphs, pseudo-English letters, and smeared gibberish across the focal plane.
 3. **Zero Negative Space for Typography**: Models naturally fill the center and upper thirds of an image with busy visual noise, leaving no clean area to render readable article titles or badges.
@@ -98,8 +98,8 @@ internal WebSocket API.
         └── (Commit Clean Asset directly into Git Repository)
 ```
 
-<details>
-<summary>View batch automation orchestrator (Python excerpt)</summary>
+<details class="tech-deep-dive">
+<summary>🔍 View batch automation orchestrator (Python excerpt, 48 lines)</summary>
 
 ```python
 import json
@@ -165,8 +165,8 @@ an automated **visual clearance audit** using Python Pillow with an explicit tol
 2. **Mean Luminance vs. Laplacian Edge Variance**: Checking only average brightness creates a dangerous blind spot: high-contrast dark wireframes or glyph hallucinations still have low mean luminance, but utterly destroy title readability. To solve this without adding heavy OpenCV dependencies, the script convolves a 3×3 Laplacian high-pass kernel directly via pure Pillow (`ImageFilter.Kernel`) and measures standard deviation across the edge map.
 3. **Dimension & Format Compression**: Output images are automatically resized to canonical Open Graph dimensions (`1200×630`), converted to 85%-quality WebP, and verified for sub-100KB file sizes.
 
-<details>
-<summary>View pure Pillow negative-space audit implementation (Python excerpt)</summary>
+<details class="tech-deep-dive">
+<summary>🔍 View pure Pillow negative-space audit implementation (Python excerpt, 33 lines)</summary>
 
 ```python
 from PIL import Image, ImageFilter, ImageStat
@@ -215,4 +215,4 @@ By turning visual asset creation into a deterministic, API-driven engineering pi
 * **100% brand consistency**: Every single article shares the identical dark-mode color temperature, technical mood, and compositional negative space.
 * **Zero manual prompting**: Once the topic metadata was defined, the entire batch executed unattended, and the resulting WebP assets were verified and committed straight to Git.
 
-Generative AI belongs in an automated build pipeline, not in a copy-paste web interface. When you constrain the model with hard contracts, consistency follows.
+Generative AI belongs in an automated build pipeline, not in a copy-paste web interface. When the model is constrained by hard contracts, consistency follows.

src/content/posts/traefik-yaegi-plugin-package-name-trap.md

@@ -60,7 +60,7 @@ Traefik does not load plugins as compiled `.so` C-shared libraries. Instead, it
 an interpreted Go runtime that parses, compiles, and evaluates raw Go source code on the fly
 inside the running Traefik daemon.
 
-When you declare a plugin in your static configuration:
+Declaring a plugin in static configuration:
 
 ```yaml
 experimental:
@@ -124,8 +124,8 @@ plugins-local/
                 └── ...
 ```
 
-<details>
-<summary>View corrected example dynamic Traefik configuration</summary>
+<details class="tech-deep-dive">
+<summary>🔍 View corrected dynamic Traefik configuration (YAML excerpt, 29 lines)</summary>
 
 ```yaml
 http:
@@ -173,6 +173,6 @@ cleanly in **0.42 seconds**:
 2026-10-23T04:48:44Z INF Plugin loaded successfully module=github.com/hoelee/traefik-botfilter
 ```
 
-If you are developing custom Traefik plugins, remember: **the Go compiler's acceptance is only half the battle.**
-Always match your package declaration to the sanitized final segment of your Go module path,
-or Yaegi will silently refuse to start your edge.
+When developing custom Traefik plugins, remember: **the Go compiler's acceptance is only half the battle.**
+Matching the package declaration to the sanitized final segment of the Go module path is mandatory,
+or Yaegi will silently refuse to start the edge proxy.

src/content/posts/zh/architecting-sea-payment-and-offline-licensing-pipelines.md

@@ -31,7 +31,7 @@ dynamicCta: true
 
 在面向东南亚区域（尤其是马来西亚、新加坡和印尼）的企业客户与独立专业人员交付桌面客户端工具时，直接套用欧美的常规 SaaS 支付架构往往会在上线第一天遭遇滑铁卢。
 
-如果你的结账页面上只放了 Stripe Elements 或 PayPal，你会立即撞上两堵现实高墙：
+如果在结账页面上直接套用常规的 Stripe Elements 或 PayPal，系统会立即撞上两堵现实高墙：
 1. **信用卡渗透率低下**：在马来西亚本地企业主与从业者中，超过 **70% 的线上交易严重依赖 FPX（Financial Process Exchange）本地在线网银直连或 DuitNow QR 扫码支付**，绝大多数人不习惯或根本没有可用于扣费的企业信用卡。
 2. **离线桌面软件的盗版风险**：如果是纯离线运行的高性能工具（例如批量视频转码器），二进制包一旦交付，如果缺乏基于物理硬件的授权签名机制，极易在团队内部被无限制复制扩散。
 
@@ -109,8 +109,8 @@ public function callback(): ResponseInterface
 
 拒绝多层跳转诱导页，杜绝垃圾广告与冗长人机验证：**一次支付成功，一键拿到经过数字签名的专属安装包**。
 
-<details>
-<summary>点击查看多渠道履约通知调度逻辑（Python 关键片段）</summary>
+<details class="tech-deep-dive">
+<summary>🔍 查看多渠道履约通知调度逻辑（Python 关键片段，27 行）</summary>
 
 ```python
 def notify_fulfillment(order_id, customer_email, bill_code, license_key, download_url):

src/content/posts/zh/batch-generating-80-technical-covers-with-comfyui.md

@@ -90,8 +90,8 @@ ComfyUI 的底层设计天然由节点图（Node Graph）驱动，其工作流
         └── (直接提交合入 Git 仓库对应目录)
 ```
 
-<details>
-<summary>点击查看批处理编排核心脚本（Python 关键片段）</summary>
+<details class="tech-deep-dive">
+<summary>🔍 查看批处理编排核心脚本（Python 关键片段，47 行）</summary>
 
 ```python
 import json
@@ -155,8 +155,8 @@ def generate_cover(slug, topic_metaphor):
 2. **平均亮度与拉普拉斯边缘方差双重门禁**：单纯检查平均亮度存在严重盲区——暗色背景上的高对比度青色线框或乱码文字同样具备极低的平均亮度，却会彻底摧毁大标题的可读性。为了避免引入 OpenCV 等重型依赖，审计脚本直接利用纯 Pillow 内置的 3×3 拉普拉斯卷积核（`ImageFilter.Kernel`）提取高频边缘图，并计算标准差（`stddev`）进行拦截。
 3. **规范化转码**：统一缩放至 Open Graph 标准的 `1200×630` 规格，输出为 85% 质量等级的现代 WebP 格式，严格确保单张体积控制在 100KB 以内。
 
-<details>
-<summary>点击查看纯 Pillow 留白净度审计算法实现（Python 关键片段）</summary>
+<details class="tech-deep-dive">
+<summary>🔍 查看纯 Pillow 留白净度审计算法实现（Python 关键片段，33 行）</summary>
 
 ```python
 from PIL import Image, ImageFilter, ImageStat

src/content/posts/zh/traefik-yaegi-plugin-package-name-trap.md

@@ -114,8 +114,8 @@ plugins-local/
                 └── ...
 ```
 
-<details>
-<summary>点击查看修正后的动态 Traefik 中间件配置示例</summary>
+<details class="tech-deep-dive">
+<summary>🔍 查看修正后的动态 Traefik 中间件配置示例（YAML 摘录，29 行）</summary>
 
 ```yaml
 http: