<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>博客系统 - 标签 -</title><link>https://oklife.me/tags/%E5%8D%9A%E5%AE%A2%E7%B3%BB%E7%BB%9F/</link><description>博客系统 - 标签 -</description><generator>Hugo -- gohugo.io</generator><language>zh-CN</language><managingEditor>contact@oklife.me (梦行志)</managingEditor><webMaster>contact@oklife.me (梦行志)</webMaster><copyright>© 2026 梦行志 | 保留所有权利</copyright><lastBuildDate>Tue, 18 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://oklife.me/tags/%E5%8D%9A%E5%AE%A2%E7%B3%BB%E7%BB%9F/" rel="self" type="application/rss+xml"/><item><title>Agent 发布文章的误判：当 HITL 门控变成拦路石</title><link>https://oklife.me/2026/08/18/agent-publish-misjudgment-hitl-gate/</link><pubDate>Tue, 18 Aug 2026 00:00:00 +0000</pubDate><author>contact@oklife.me (梦行志)</author><guid>https://oklife.me/2026/08/18/agent-publish-misjudgment-hitl-gate/</guid><description>&lt;div class="featured-image">
                &lt;img src="/images/Code-Art-Studio-images/agent-publish-misjudgment-hitl-gate/agent-publish-misjudgment-hitl-gate.webp" referrerpolicy="no-referrer">
            &lt;/div>2026-08-18，pub-yuntianxing 收到更新文章请求后，因 HITL lock 文件不存在而拒绝发布。用户指出文章早已成功发布，URL 可正常访问。这个案例暴露了自动化发布流程中的一个关键设计缺陷：快速更新场景下，HITL 门控应该被跳过而非强制执行。</description></item><item><title>一次博客系统的完整崩溃与重建：从路由错误到架构重构</title><link>https://oklife.me/2026/08/17/blog-system-crash-and-rebuild/</link><pubDate>Mon, 17 Aug 2026 00:00:00 +0000</pubDate><author>contact@oklife.me (梦行志)</author><guid>https://oklife.me/2026/08/17/blog-system-crash-and-rebuild/</guid><description><![CDATA[<div class="featured-image">
                <img src="/images/Code-Art-Studio-images/blog-system-crash-and-rebuild/blog-system-crash-and-rebuild.webp" referrerpolicy="no-referrer">
            </div>记录了一次博客系统的完整事故过程。从分类错误、路径错误，到自作主张恢复删除文件，最后重建了正确的架构。这是一次关于&rsquo;先核实再行动&rsquo;的深刻教训。]]></description></item></channel></rss>