Link the container-docs post to the Synology spreadsheet API flagship (EN + ZH)

src/content/posts/reading-a-containers-own-api-docs.md

@@ -184,6 +184,8 @@ Read the vendor's own documentation when it exists — it's usually faster than
 
 Four commands — `cat` the bundled spec, `grep` the bundle for env vars, read the config blob from the registry, `exec cat /proc/net/tcp` for the port — replaced a documentation hunt with: a full OpenAPI spec, all nine env vars, the default port, the config defaults, and a Swagger UI URL. No shell in the container, no login, nothing mutated.
 
+The place this paid off hardest was Synology's spreadsheet API container — the worked example, including the four failures that made me reach for these commands in the first place, is in [The Synology Spreadsheet API Is a Container, Not an API Endpoint](/posts/synology-spreadsheet-api-is-a-container/).
+
 ---
 
 *If you're integrating a self-hosted system and the docs stop short, I do that work for small businesses in Malaysia — [WhatsApp](https://wa.me/60127972969), [email](mailto:[email protected]?subject=API%20integration), or [hoelee.com](https://hoelee.com).*

src/content/posts/zh/reading-a-containers-own-api-docs.md

@@ -207,6 +207,9 @@ docker rm -f probe
 OpenAPI 规范、全部九个 env 变量、默认端口、配置默认值，以及一个 Swagger UI
 地址。没进容器开 shell，不用登录，什么都没改动。
 
+这些命令最值的一次应用，就是 Synology 的 spreadsheet API 容器——完整案例、以及逼我动用这些命令的
+四个坑，写在[《Synology 的 Spreadsheet API 是一个容器，不是一个 API 端点》](/posts/synology-spreadsheet-api-is-a-container/)里。
+
 ---
 
 *如果你正在对接一个自托管系统，而文档又戛然而止——这正是我为马来西亚中小