post(case-studies): link the published whitepaper from both locales

doc.hoelee.com/whitepaper-504-read-amplification-swr.html now exists, so the
closing line stops being a promise and becomes a link.

src/content/posts/read-amplification-504-gateway-timeout-swr-cache.md

@@ -257,4 +257,4 @@ Four honest caveats, because a benchmark without them is marketing:
 
 The harness generates its own corpus and prints strictly valid JSON, so `python swr_bench.py` reproduces the whole table on any machine within roughly ±30% hardware variance. Every figure in this post is a number some script produced during the run it describes — including the four that made the original version of this post look better than it was, before they were deleted and the experiment was redone.
 
-*The full whitepaper — including the multi-worker state-sharing options, the complete harness, and the three raw result sets — is published separately under the technical reports section.*
+*The full whitepaper — including the multi-worker state-sharing options, the complete harness, and the three raw result sets — is published separately: [Moving a 504 out of the system (technical whitepaper v1.2)](https://doc.hoelee.com/whitepaper-504-read-amplification-swr.html).*

src/content/posts/zh/read-amplification-504-gateway-timeout-swr-cache.md

@@ -257,4 +257,4 @@ def _scan(content_dir, locale):
 
 基准脚本自带语料生成、stdout 为严格合法 JSON，因此在任何机器上执行 `python swr_bench.py` 都能在约 ±30% 硬件差异内复算整张表。本文每个数字都是某次运行里某个脚本产出的——包括那四个让这篇文章的初版看起来比实际更好的数字，它们在实验重做之后被删掉了。
 
-*完整白皮书——含多 worker 状态共享的各档方案、完整实验脚本与三份原始读数——另行发布于技术报告栏目。*
+*完整白皮书——含多 worker 状态共享的各档方案、完整实验脚本与三份原始读数——已单独发布：[《把一个 504 从系统里移出去》（技术白皮书 v1.2）](https://doc.hoelee.com/whitepaper-504-read-amplification-swr.html)。*