[{"data":1,"prerenderedAt":4585},["ShallowReactive",2],{"site-settings":3,"all-writing":103},{"site":4,"home":19,"writing":41,"services":49,"about":84},{"id":5,"title":6,"description":7,"extension":8,"footer":9,"location":13,"meta":14,"name":6,"stem":15,"theme":16,"__hash__":18},"site\u002Fsettings\u002Fsite.yml","Quilibra","这是我自己部署的小主页，用于记录想法并提供一些服务的入口。","yml",{"icp":10,"policeRecord":11,"credit":12},"皖ICP备2026023522号-1","皖公网安备34012102000966号","DESIGNED & BUILT BY GPT-5.6 IN CODEX","China · UTC+8",{},"settings\u002Fsite",{"defaultAccent":17},"#000000","jtRrbdN47gDyGs_u2ubGZhFFByRvoiraZTjokx9SF0A",{"id":20,"dock":21,"extension":8,"headline":25,"introduction":28,"kicker":29,"latestWriting":30,"meta":36,"modules":37,"stem":38,"systemsLabel":39,"__hash__":40},"homeSettings\u002Fsettings\u002Fhome.yml",{"writing":22,"services":23,"about":24},"文章","服务","关于",{"prefix":26,"emphasis":27},"你好，这里是","Equilibra","这是我自己部署的个人主页，用于记录我的一些事情并维护我的一些服务。","个人主页 \u002F 持续施工中",{"enabled":31,"title":32,"linkLabel":33,"emptyLabel":34,"limit":35},true,"最近写下","全部文章","暂无文章",3,{},{"services":31,"rgbAssembly":31},"settings\u002Fhome","SYSTEMS","mLQiZfULI1ARi0lqmzbNtwFTadrRDtSbuzkF2UyyPzU",{"id":42,"emptyLabel":43,"extension":8,"intro":44,"meta":45,"seoDescription":46,"stem":47,"__hash__":48},"writingSettings\u002Fsettings\u002Fwriting.yml","没有找到匹配的文章。","随笔、学习、交易，以及一些观察。",{},"随笔、学习、交易与观察。","settings\u002Fwriting","YEMHVxKRvAlcMP_kI5F46TdJR19p9ErI69cG5BbP_j8",{"id":50,"accessNotes":51,"accessTitle":54,"extension":8,"intro":55,"items":56,"meta":80,"seoDescription":81,"stem":82,"__hash__":83},"servicesSettings\u002Fsettings\u002Fservices.yml",[52,53],"公开入口由 VPS 上的 Nginx 提供 HTTPS 与反向代理。","家中服务通过私网连接，不直接暴露 。","访问说明","统一入口，分别运行。尚未开放的服务会在域名和登录保护完成后上线。",[57,63,69,75],{"name":58,"description":59,"href":60,"state":61,"icon":62,"showOnHome":31},"Code","浏览器里的开发环境","https:\u002F\u002Fcode.quilibra.cn","online","code",{"name":64,"description":65,"href":66,"state":67,"icon":68,"showOnHome":31},"Photos","照片备份和浏览","https:\u002F\u002Fphotos.example.com","soon","image",{"name":70,"description":71,"href":72,"state":73,"icon":74,"showOnHome":31},"NAS","文件与存储管理","https:\u002F\u002Fnas.example.com","private","hard-drive",{"name":76,"description":77,"href":78,"state":61,"icon":79,"showOnHome":31},"Status","服务可用性与故障记录","#","activity",{},"开发环境、相册、NAS 和运行状态。","settings\u002Fservices","yLhlQNGotM4SYxIDWlMMScw4erJoBdsGRFf_uffFabk",{"id":85,"contactCopy":86,"contactLabel":87,"currentFocus":88,"extension":8,"focusLabel":89,"introduction":90,"meta":91,"seoDescription":92,"stem":93,"topicsLabel":94,"writingTopics":95,"__hash__":102},"aboutSettings\u002Fsettings\u002Fabout.yml","不是，你联系我干嘛？","联系","正在上班当牛马。","正在做的事","这是我自己部署的个人主页，用于记录我的想法并维护我的一些服务。",{},"一些基本信息，以及这个网站目前用来做什么。","settings\u002Fabout","关注的主题",[96,97,98,99,100,101],"看盘看线","捣鼓电脑","折腾NAS","踢踢野球","看看科普","玩币练胆","ZVRx6CC1-GDQUGPl4C4XUfgy30ovFv6LdaXNegQjWAo",[104,581,4045,4211,4405],{"id":105,"title":106,"body":107,"category":559,"date":560,"description":561,"extension":562,"hidden":563,"meta":564,"navigation":31,"path":565,"publishedAt":566,"seo":567,"slug":568,"stem":569,"tags":570,"updated":579,"__hash__":580},"writing\u002Fwriting\u002F2026-07-29-etf-premium-discount-cost-of-carry.md","从ETF到商品期货：申赎机制、折溢价与持有成本模型",{"type":108,"value":109,"toc":537},"minimark",[110,115,119,123,140,143,146,149,209,212,215,229,240,243,257,260,264,267,274,277,301,304,307,327,330,341,344,347,351,354,357,373,376,402,408,411,416,419,423,474,477,497,500,514,517,523,526,533],[111,112,114],"h2",{"id":113},"etf与lof申赎机制决定折溢价","ETF与LOF：申赎机制决定折溢价",[116,117,118],"h3",{"id":118},"底层机制差异",[120,121,122],"p",{},"ETF和LOF虽然都是场内可交易的开放式基金，但申赎机制截然不同：",[124,125,126,134],"ul",{},[127,128,129,133],"li",{},[130,131,132],"strong",{},"ETF：实物申赎，T+0瞬时套利。"," 机构投资者用一篮子股票换取基金份额，最小申赎单位通常为50万或100万份，门槛在百万级别。每日盘前基金公司公布PCF（Portfolio Composition File）清单，列明当日申赎对应的一篮子股票明细。",[127,135,136,139],{},[130,137,138],{},"LOF：现金申赎，跨系统转托管需T+2日。"," 门槛低（1份起），普通投资者即可参与，但套利存在时滞和净值波动风险。",[120,141,142],{},"这个差异是两者折溢价收敛速度天差地别的根本原因。",[116,144,145],{"id":145},"现金替代的四种标志",[120,147,148],{},"ETF实物申赎中，并非每只成分股都能完美交收。PCF清单对每只股票标注现金替代标志：",[150,151,152,165],"table",{},[153,154,155],"thead",{},[156,157,158,162],"tr",{},[159,160,161],"th",{},"标志",[159,163,164],{},"含义",[166,167,168,179,189,199],"tbody",{},[156,169,170,176],{},[171,172,173],"td",{},[130,174,175],{},"禁止",[171,177,178],{},"必须用股票实物交收",[156,180,181,186],{},[171,182,183],{},[130,184,185],{},"允许",[171,187,188],{},"申购可现金替代，赎回必须给股票，多退少补",[156,190,191,196],{},[171,192,193],{},[130,194,195],{},"必须",[171,197,198],{},"申赎均必须用现金，针对停牌或待剔除股票",[156,200,201,206],{},[171,202,203],{},[130,204,205],{},"退补",[171,207,208],{},"必须现金替代，按基金公司实际买卖成本多退少补",[116,210,211],{"id":211},"折溢价的形成",[120,213,214],{},"场内基金有两个价格：",[124,216,217,223],{},[127,218,219,222],{},[130,220,221],{},"IOPV（参考净值）","：实时计算的基金份额参考价值",[127,224,225,228],{},[130,226,227],{},"市价","：二级市场交易价格",[120,230,231,232,235,236,239],{},"当市价 > IOPV，即为",[130,233,234],{},"溢价","；反之则为",[130,237,238],{},"折价","。",[120,241,242],{},"套利机制是折溢价收敛的驱动力：",[124,244,245,251],{},[127,246,247,250],{},[130,248,249],{},"溢价套利","：T日买入一篮子股票 → 申购ETF份额 → 卖出ETF，全流程T+0完成",[127,252,253,256],{},[130,254,255],{},"折价套利","：T日买入ETF → 赎回为一篮子股票 → 卖出股票，同样T+0",[120,258,259],{},"正因为ETF套利链条畅通，折溢价通常控制在1%以内。而LOF因T+2转托管时滞，套利者需承担两天净值波动风险，折溢价常达5%以上。",[111,261,263],{"id":262},"跨境etf全现金替代与qdii额度约束","跨境ETF：全现金替代与QDII额度约束",[116,265,266],{"id":266},"一个常见误区",[120,268,269,270,273],{},"\"我有了一篮子股票，如何申购跨境ETF？\"——这个问题本身存在误区。跨境ETF的成分股在境外，境内投资者无法持有和交收这些股票，因此",[130,271,272],{},"跨境ETF不能实物申购，只能全现金替代","。投资者交付现金，由基金公司代为买入境外成分股。",[116,275,276],{"id":276},"现金申购流程",[278,279,280,283,286,289,292,295,298],"ol",{},[127,281,282],{},"确认券商具备跨境ETF申赎资格",[127,284,285],{},"T日盘前查阅PCF清单（现金替代标志全为\"退补\"）",[127,287,288],{},"核对当日QDII额度与开放状态（可能限购，极端情况单日仅100元）",[127,290,291],{},"计算所需现金（现金替代款 + 预估现金差额），最小单位50万份",[127,293,294],{},"T日交易时段通过券商端提交委托",[127,296,297],{},"T+1日日终份额确认，T+2日可用",[127,299,300],{},"基金公司代买完成后，进行现金差额多退少补",[116,302,303],{"id":303},"三层结构与溢价固化",[120,305,306],{},"跨境ETF的运作涉及三层主体：",[124,308,309,315,321],{},[127,310,311,314],{},[130,312,313],{},"外汇局","：审批QDII额度（总量约1708亿美元）",[127,316,317,320],{},[130,318,319],{},"基金公司","：在额度内换汇，代投资者买入境外成分股",[127,322,323,326],{},[130,324,325],{},"境内投资者","：只能通过现金提交申购申请",[120,328,329],{},"当额度充裕时，套利机制正常运行。但当额度耗尽时：",[278,331,332,335,338],{},[127,333,334],{},"基金公司暂停或限额申购（单日低至10元）",[127,336,337],{},"一级市场申购通道堵死，套利者无法创造新份额",[127,339,340],{},"二级市场资金只能抢存量份额，溢价飙升至10%-50%+",[120,342,343],{},"此外，现金申赎 + 代买模式下，跨时区汇率波动和境外开盘价差导致退补款不可预知，套利收益无法锁定，进一步抑制套利者进场意愿，固化高溢价。",[120,345,346],{},"典型场景：QDII ETF因外汇额度受限，一级市场申购通道关闭，套利链条断裂，溢价长期高达10%-40%。",[111,348,350],{"id":349},"商品期货持有成本模型与期限结构","商品期货：持有成本模型与期限结构",[116,352,353],{"id":353},"持有成本定价公式",[120,355,356],{},"商品期货的理论价格由持有成本模型决定：",[358,359,364],"pre",{"className":360,"code":361,"language":362,"meta":363,"style":363},"language-plain shiki shiki-themes github-light github-dark","F = S · e^((r + u − y) · T)\n","plain","",[62,365,366],{"__ignoreMap":363},[367,368,371],"span",{"class":369,"line":370},"line",1,[367,372,361],{},[120,374,375],{},"其中：",[124,377,378,384,390,396],{},[127,379,380,383],{},[130,381,382],{},"S","：现货价格",[127,385,386,389],{},[130,387,388],{},"r","：无风险利率（资金占用成本）",[127,391,392,395],{},[130,393,394],{},"u","：仓储保险成本率",[127,397,398,401],{},[130,399,400],{},"y","：便利收益率（convenience yield）",[120,403,404,407],{},[130,405,406],{},"便利收益","是持有实物库存的隐性收益——当供应紧张时，手上有货意味着生产不断线、客户不流失，这种\"随时可用\"的价值就是便利收益。它与库存水平成反比：库存越低，便利收益越高。",[116,409,410],{"id":410},"基差及其收敛",[120,412,413],{},[130,414,415],{},"基差 = 现货价格(S) − 期货价格(F)",[120,417,418],{},"随着交割日临近，持仓成本（r+u−y）T逐渐衰减趋零，期货价格向现货价格收敛，基差必然趋近于零。否则将触发无风险套利：买低卖高，交割平仓。",[116,420,422],{"id":421},"期限结构contango与backwardation","期限结构：Contango与Backwardation",[150,424,425,440],{},[153,426,427],{},[156,428,429,432,435,438],{},[159,430,431],{},"结构",[159,433,434],{},"形态",[159,436,437],{},"成因",[159,439,164],{},[166,441,442,458],{},[156,443,444,449,452,455],{},[171,445,446],{},[130,447,448],{},"Contango",[171,450,451],{},"S \u003C F近 \u003C F远",[171,453,454],{},"r+u > y，库存充足",[171,456,457],{},"常态结构，持有成本主导",[156,459,460,465,468,471],{},[171,461,462],{},[130,463,464],{},"Backwardation",[171,466,467],{},"S > F近 > F远",[171,469,470],{},"r+u \u003C y，库存紧张",[171,472,473],{},"供应短缺，现货溢价",[116,475,476],{"id":476},"品种实例",[124,478,479,485,491],{},[127,480,481,484],{},[130,482,483],{},"黄金","：投资性商品，便利收益y≈0，恒为Contango结构",[127,486,487,490],{},[130,488,489],{},"原油","：消费性商品，便利收益波动剧烈，常在Contango与Backwardation间切换。紧缺时深度Backwardation，过剩时转Contango",[127,492,493,496],{},[130,494,495],{},"农产品","：受季节性收获周期影响，仓储成本u与便利收益y交替主导曲线形态",[116,498,499],{"id":499},"套利操作",[124,501,502,508],{},[127,503,504,507],{},[130,505,506],{},"正向套利（Cash and Carry）","：当F实际 > F理论时，借钱买入现货 + 卖出期货，锁定差价",[127,509,510,513],{},[130,511,512],{},"反向套利（Reverse Cash and Carry）","：当F实际 \u003C F理论时，卖空现货 + 买入期货。但对消费性商品，卖空现货难以操作",[116,515,516],{"id":516},"远期与期货的凸性调整",[120,518,519,520,239],{},"期货合约每日盯市（mark-to-market），而远期合约到期才结算。当标的资产价格与利率正相关时，期货价格略高于远期价格，这一差异称为",[130,521,522],{},"凸性调整",[111,524,525],{"id":525},"串联",[120,527,528,529,532],{},"三个主题看似分散，实则共享一条逻辑主线：",[130,530,531],{},"机制决定效率，效率决定价格形态","。ETF的T+0实物申赎使折溢价瞬间收敛；跨境ETF的额度瓶颈使套利链条断裂、溢价固化；商品期货的持有成本模型则将仓储、利率、库存预期统一为一个数学框架，解释了曲线形态的成因。理解机制本身，比记住某个具体结论更重要。",[534,535,536],"style",{},"html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html.dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}",{"title":363,"searchDepth":538,"depth":538,"links":539},2,[540,545,550,558],{"id":113,"depth":538,"text":114,"children":541},[542,543,544],{"id":118,"depth":35,"text":118},{"id":145,"depth":35,"text":145},{"id":211,"depth":35,"text":211},{"id":262,"depth":538,"text":263,"children":546},[547,548,549],{"id":266,"depth":35,"text":266},{"id":276,"depth":35,"text":276},{"id":303,"depth":35,"text":303},{"id":349,"depth":538,"text":350,"children":551},[552,553,554,555,556,557],{"id":353,"depth":35,"text":353},{"id":410,"depth":35,"text":410},{"id":421,"depth":35,"text":422},{"id":476,"depth":35,"text":476},{"id":499,"depth":35,"text":499},{"id":516,"depth":35,"text":516},{"id":525,"depth":538,"text":525},"学习","2026-07-29","ETF实物申赎与LOF现金申赎的机制差异决定折溢价收敛速度，跨境ETF的QDII额度约束固化高溢价，商品期货持有成本模型统一解释期限结构形态。","md",false,{},"\u002Fwriting\u002F2026-07-29-etf-premium-discount-cost-of-carry","2026-07-29T10:51:17+08:00",{"title":106,"description":561},"etf-premium-discount-cost-of-carry","writing\u002F2026-07-29-etf-premium-discount-cost-of-carry",[571,572,573,574,575,576,577,578],"ETF","LOF","跨境ETF","QDII","商品期货","持有成本模型","期限结构","折溢价",null,"P-nL6PDPMB-K1dYMhb05-mjrddhVCF2rRa7sbCY8CXo",{"id":582,"title":583,"body":584,"category":559,"date":4030,"description":4031,"extension":562,"hidden":563,"meta":4032,"navigation":31,"path":4033,"publishedAt":4034,"seo":4035,"slug":4036,"stem":4037,"tags":4038,"updated":4043,"__hash__":4044},"writing\u002Fwriting\u002F2026-07-26-quilibra-complete-technical-handbook.md","Quilibra 个人主页完整技术手册：从页面架构到内容发布与生产部署",{"type":108,"value":585,"toc":3958},[586,589,592,613,617,620,623,631,647,661,664,668,671,691,694,697,701,704,798,801,807,813,827,831,834,840,843,876,891,895,901,935,953,964,970,1016,1023,1027,1030,1094,1113,1120,1155,1168,1172,1178,1210,1228,1267,1270,1281,1285,1288,1311,1330,1349,1352,1356,1359,1387,1390,1394,1401,1458,1469,1472,1498,1501,1507,1513,1517,1528,1534,1541,1551,1574,1578,1588,1591,1611,1614,1654,1660,1664,1675,1678,1681,1695,1716,1722,1746,1757,1761,1772,1775,1802,1813,1816,1831,1835,1838,1854,1857,1863,1877,1884,1902,1906,1916,1923,1926,1940,1954,1961,1965,1976,1982,1990,1996,2003,2007,2010,2096,2099,2105,2132,2155,2168,2178,2182,2191,2194,2216,2219,2227,2233,2239,2246,2253,2267,2271,2278,2281,2304,2323,2326,2330,2337,2343,2352,2365,2369,2372,2378,2381,2387,2390,2396,2399,2405,2411,2423,2455,2462,2468,2493,2496,2501,2510,2515,2527,2547,2551,2557,2563,2576,2593,2602,2621,2624,2630,2634,2670,2735,2741,2744,2750,2761,2772,2776,2827,2838,2844,2848,2851,2857,2860,2902,2922,2933,2944,2948,2951,2955,2961,2992,2996,3002,3036,3040,3046,3084,3087,3090,3094,3097,3114,3121,3124,3127,3168,3173,3177,3180,3187,3204,3207,3211,3215,3224,3227,3236,3239,3248,3251,3265,3268,3281,3284,3291,3294,3308,3311,3317,3321,3325,3344,3347,3350,3377,3382,3386,3466,3475,3478,3568,3571,3574,3602,3613,3617,3621,3644,3647,3663,3667,3678,3681,3689,3692,3698,3702,3712,3716,3725,3735,3739,3745,3749,3752,3758,3761,3767,3777,3781,3784,3787,3790,3793,3796,3802,3805,3809,3812,3866,3869,3889,3892,3895,3955],[120,587,588],{},"这是一份给自己看的项目说明书。它主要以 2026 年 7 月 27 日的实际代码和 VPS 配置为准，从浏览器里看到的页面一直追到内容文件、Git 分支、构建产物、静态服务器和版本化 release。以后忘了某段代码为什么存在、主页颜色为什么能保存、CMS 保存为什么只出现在测试站，或者 3000、3100、3101 三个端口分别在做什么，可以从这里重新建立完整认识。",[120,590,591],{},"本文记录的是一个具体版本的实现，不是一套永远不变的规范。最可靠的事实来源始终是仓库中的代码；本文的作用，是把分散在 Vue、CSS、YAML、脚本和运维文件里的设计意图串起来。",[593,594,595],"blockquote",{},[120,596,597,598,601,602,605,606,609,610,612],{},"2026 年 8 月 3 日更新：网站已经移除长期 ",[62,599,600],{},"staging"," 分支、远程测试站和 ",[62,603,604],{},"promote"," 流程，改为 CMS 直接提交 ",[62,607,608],{},"master","、代码在本地功能分支验证后推送 ",[62,611,608],{},"。下文关于双环境发布的内容保留为历史架构记录，当前操作以仓库 README 和运维手册为准。",[111,614,616],{"id":615},"一先用一句话理解整个网站","一、先用一句话理解整个网站",[120,618,619],{},"Quilibra（名字也是AI起的捏） 是一个由 Nuxt 生成的静态个人网站：页面结构写在 Vue 中，主页设置写在 YAML 中，文章写在 Markdown 中；发布时把这些源文件编译成普通 HTML、CSS、JavaScript 和图片，再由一个很小的 Node 静态服务器提供给浏览器。",[120,621,622],{},"它的静态生成核心是：",[358,624,629],{"className":625,"code":627,"language":628,"meta":363},[626],"language-text","Vue \u002F CSS \u002F YAML \u002F Markdown\n           |\n           | Nuxt generate\n           v\n      .output\u002Fpublic\n           |\n           | 复制到带时间戳的 release\n           v\n  releases\u002F\u003Crelease-id>\n           |\n           | 原子切换 current 符号链接\n           v\n     current -> 当前 release\n           |\n           | Node 静态服务器 :3000\n           v\n        浏览器 \u002F 反向代理\n","text",[62,630,627],{"__ignoreMap":363},[120,632,633,634,636,637,640,641,636,643,646],{},"现在这套链路有两份互不覆盖的实例：",[62,635,608],{}," 构建到 ",[62,638,639],{},"~\u002F.local\u002Fshare\u002Fpersonal-site\u002Fcurrent"," 并由 3000 提供正式站，",[62,642,600],{},[62,644,645],{},"~\u002F.local\u002Fshare\u002Fpersonal-site-staging\u002Fcurrent"," 并由 3100 提供测试站。两边都使用相同的生成和原子切换逻辑，但仓库、成功状态、release 目录和服务端口完全独立。",[120,648,649,650],{},"这里最重要的边界是：",[130,651,652,653,656,657,660],{},"Git 分支中的源码是长期事实，",[62,654,655],{},".output\u002Fpublic"," 是可重新生成的临时产物，各环境 ",[62,658,659],{},"current"," 指向的 release 才是该环境当前真正提供的版本。",[120,662,663],{},"因此，修改 Markdown 或 YAML 只改变源码；只有重新生成并切换 release，线上页面才会改变。网站没有生产数据库，也没有在访问文章时临时渲染 Markdown。",[111,665,667],{"id":666},"二为什么选择静态优先","二、为什么选择静态优先",[120,669,670],{},"个人主页的读取远多于写入，而且文章、简介和服务入口都不需要按访客实时计算。静态生成正好适合这种负载：",[124,672,673,676,679,682,685,688],{},[127,674,675],{},"访问时不查询数据库，也不运行 Vue 服务端渲染逻辑；",[127,677,678],{},"HTML 已经在发布阶段生成，首屏可以直接返回完整内容；",[127,680,681],{},"生产服务只需要读取文件，故障面比常驻 Nuxt 服务小；",[127,683,684],{},"每个 release 都是一份独立、完整、可回滚的目录；",[127,686,687],{},"Markdown 和 YAML 都在 Git 中，内容、配置和代码可以一起审查与恢复；",[127,689,690],{},"CMS 只是源码编辑器，不会成为网站运行时依赖。",[120,692,693],{},"代价也很明确：每次内容变化都要重新生成站点；文章越多，生成时间越长；需要登录、评论、实时状态或用户数据时，必须接入独立服务，而不能假装静态文件可以承担动态业务。",[120,695,696],{},"当前项目主动接受这个取舍，因为稳定、透明和容易备份比“保存后数据库立刻生效”更重要。",[111,698,700],{"id":699},"三技术栈与各自职责","三、技术栈与各自职责",[120,702,703],{},"当前主要依赖如下：",[150,705,706,716],{},[153,707,708],{},[156,709,710,713],{},[159,711,712],{},"技术",[159,714,715],{},"当前职责",[166,717,718,726,734,742,750,758,766,774,782,790],{},[156,719,720,723],{},[171,721,722],{},"Nuxt 4",[171,724,725],{},"应用框架、路由、预渲染、页面头信息和构建产物",[156,727,728,731],{},[171,729,730],{},"Vue 3",[171,732,733],{},"组件、响应式状态、生命周期和浏览器交互",[156,735,736,739],{},[171,737,738],{},"TypeScript",[171,740,741],{},"页面、组件、配置、内容脚本和测试的静态类型检查",[156,743,744,747],{},[171,745,746],{},"Nuxt Content 3",[171,748,749],{},"读取 YAML\u002FMarkdown、建立集合、查询文章并渲染正文",[156,751,752,755],{},[171,753,754],{},"Zod",[171,756,757],{},"约束站点设置与文章字段",[156,759,760,763],{},[171,761,762],{},"Lucide Vue",[171,764,765],{},"返回、搜索、服务、调色等界面图标",[156,767,768,771],{},[171,769,770],{},"原生 CSS",[171,772,773],{},"全部视觉、响应式布局、悬浮反馈和字标动画",[156,775,776,779],{},[171,777,778],{},"Sveltia CMS",[171,780,781],{},"在浏览器中编辑仓库里的 YAML、Markdown 和上传资源",[156,783,784,787],{},[171,785,786],{},"Playwright",[171,788,789],{},"真实浏览器中的交互、布局、响应式和回归测试",[156,791,792,795],{},[171,793,794],{},"Node.js",[171,796,797],{},"内容工具、同步与发布脚本、生产和测试静态服务器",[120,799,800],{},"没有引入 Tailwind、组件库、动画框架、运行时数据库或外部字体。页面使用系统无衬线字体和系统等宽字体回退，这减少了字体请求，也避免了字体加载完成时重新排版。",[120,802,803,806],{},[62,804,805],{},"package.json"," 中最常用的入口是：",[358,808,811],{"className":809,"code":810,"language":628,"meta":363},[626],"npm run dev              本地临时 Nuxt 开发服务\nnpm run generate         生成静态站点\nnpm run typecheck        Nuxt\u002FVue TypeScript 检查\nnpm run content:validate 校验全部文章与站点设置\nnpm run test:content     内容校验器与受限 writer 的单元测试\nnpm run test:release     release 工具的单元测试\nnpm run test:e2e         Playwright 浏览器测试\nnpm run publish          发布未提交的受管内容\nnpm run deploy           部署已经提交且工作区干净的代码版本\nnpm run sync             拉取指定 GitHub 分支并自动检查、构建和部署\nnpm run promote          把测试站确认过的 CMS 内容安全发布到生产\nnpm run rollback         切换回指定历史 release\n",[62,812,810],{"__ignoreMap":363},[120,814,815,818,819,822,823,826],{},[62,816,817],{},"build"," 与 ",[62,820,821],{},"preview"," 仍是 Nuxt 的常规命令，但当前生产链路以 ",[62,824,825],{},"generate"," 和自有静态服务器为准。",[111,828,830],{"id":829},"四目录结构与所有权边界","四、目录结构与所有权边界",[120,832,833],{},"理解这个项目，先要知道“改什么就去哪里”。",[358,835,838],{"className":836,"code":837,"language":628,"meta":363},[626],"personal-site\u002F\n├── app\u002F\n│   ├── app.vue                         全站外壳、主题初始化、动态 favicon\n│   ├── assets\u002Fcss\u002Fmain.css             全站视觉与响应式规则\n│   ├── components\u002F\n│   │   ├── ArtisticWordmark.vue        可编辑艺术字与重播控制\n│   │   ├── RgbAssembly.vue             RGB 滑杆、预设与重置\n│   │   ├── ServiceIcon.vue             服务图标名称到 Lucide 的映射\n│   │   └── ServiceStatusDot.vue        服务状态点\n│   ├── composables\u002F\n│   │   ├── useAccentTheme.ts           主题色状态、混色、对比色与持久化\n│   │   ├── useSiteSettings.ts          并行读取并组合五份站点设置\n│   │   └── useWordmarkAnimation.ts     跨组件字标重播信号\n│   ├── config\u002F                         文章分类、服务状态和图标枚举\n│   ├── pages\u002F                          首页、文章、服务、关于页面\n│   └── error.vue                       错误页面\n├── content\u002F\n│   ├── settings\u002F                       全站与四个页面的独立 YAML 配置\n│   └── writing\u002F*.md                    正式文章\n├── public\u002F\n│   ├── admin\u002F                          Sveltia CMS 入口与字段配置\n│   ├── brand\u002F                          字标位图资源\n│   ├── uploads\u002F                        文章上传资源\n│   └── favicon.svg                     静态 favicon 回退\n├── scripts\u002F\n│   ├── content\u002Fvalidate.ts             内容结构校验\n│   ├── content\u002Fwrite.ts                受限文章写入、更新与删除\n│   ├── release.ts                      测试、生成、提交、发布和回滚\n│   ├── promote.ts                      staging 内容安全合并到 master\n│   ├── sync.ts                         GitHub 拉取、代理、构建与部署\n│   ├── webhook.ts                      GitHub 签名校验、事件队列与部署触发\n│   └── static-server.mjs               生产与测试静态文件服务器\n├── tests\u002F                              单元、发布和浏览器测试\n├── ops\u002F\n│   ├── openclaw\u002F...\u002FSKILL.md           OpenClaw 文章发布 Skill\n│   ├── nginx\u002F                           正式域名、测试域名和默认拒绝站点\n│   └── systemd\u002F                         静态、Webhook 与同步服务\n├── content.config.ts                   Nuxt Content 集合\n├── content.schema.ts                   站点设置 Schema\n├── nuxt.config.ts                      Nuxt 与静态预渲染配置\n└── playwright.config.ts                E2E 临时服务与浏览器配置\n",[62,839,837],{"__ignoreMap":363},[120,841,842],{},"可以把这些文件分成四层：",[278,844,845,851,857,866],{},[127,846,847,850],{},[62,848,849],{},"content\u002F"," 是可频繁修改的数据层。",[127,852,853,856],{},[62,854,855],{},"app\u002F"," 是页面表现和交互层。",[127,858,859,818,862,865],{},[62,860,861],{},"scripts\u002F",[62,863,864],{},"ops\u002F"," 是发布和运行层。",[127,867,868,871,872,875],{},[62,869,870],{},".output\u002F","、",[62,873,874],{},".nuxt*"," 是构建缓存或产物，不是手工维护的源码。",[120,877,878,879,882,883,886,887,890],{},"CMS 默认只管理 ",[62,880,881],{},"content\u002Fsettings\u002F"," 中五份固定 YAML、",[62,884,885],{},"content\u002Fwriting\u002F"," 和 ",[62,888,889],{},"public\u002Fuploads\u002F","。Vue、CSS、CMS 配置、脚本或测试发生变化时，应当视为代码变更，走完整代码部署流程；设置目录中的未知文件也不会自动进入内容发布白名单。",[111,892,894],{"id":893},"五nuxt-配置与构建数据库","五、Nuxt 配置与构建数据库",[120,896,897,900],{},[62,898,899],{},"nuxt.config.ts"," 做了几件关键的事：",[124,902,903,910,916,919,922,929,932],{},[127,904,905,906,909],{},"加载 ",[62,907,908],{},"@nuxt\u002Fcontent","；",[127,911,912,913,909],{},"全局引入 ",[62,914,915],{},"app\u002Fassets\u002Fcss\u002Fmain.css",[127,917,918],{},"关闭开发工具；",[127,920,921],{},"设置中文页面语言和移动端 viewport；",[127,923,924,925,928],{},"使用 ",[62,926,927],{},"out-in"," 页面切换过渡；",[127,930,931],{},"允许 Nitro 爬取内部链接并预渲染，遇到错误时直接让构建失败；",[127,933,934],{},"把 Nuxt Content 的本地数据库放到与构建目录对应的位置。",[120,936,937,938,886,941,944,945,948,949,952],{},"Nuxt Content 3 在构建过程中会建立 SQLite 内容索引。开发环境默认使用 ",[62,939,940],{},".nuxt",[62,942,943],{},".data\u002Fcontent\u002Fcontents.sqlite","；release 构建传入 ",[62,946,947],{},"NUXT_BUILD_DIR=.nuxt-release","，E2E 使用 ",[62,950,951],{},".nuxt-e2e","。把三种构建目录分开，是为了避免开发服务器、正式生成和 Playwright 同时读写同一个内容缓存。",[120,954,955,956,959,960,963],{},"这里的 SQLite 是",[130,957,958],{},"构建时索引","，不是生产文章数据库。它帮助 Nuxt Content 查询 Markdown；静态页面生成完成后，生产服务器只负责输出构建结果。遇到 ",[62,961,962],{},"no such table: _content_writing"," 时，通常是本地 Nuxt Content 缓存被并发构建或中断破坏，不代表文章源文件丢失。",[120,965,966,969],{},[62,967,968],{},"content.config.ts"," 定义了六个集合：",[124,971,972,994],{},[127,973,974,871,977,871,980,871,983,871,986,989,990,993],{},[62,975,976],{},"site",[62,978,979],{},"homeSettings",[62,981,982],{},"writingSettings",[62,984,985],{},"servicesSettings",[62,987,988],{},"aboutSettings","：五个 ",[62,991,992],{},"data"," 集合，各自读取同名职责的 YAML；",[127,995,996,999,1000,1003,1004,1007,1008,1011,1012,1015],{},[62,997,998],{},"writing","：",[62,1001,1002],{},"page"," 类型，读取 ",[62,1005,1006],{},"writing\u002F**\u002F*.md","，因此每篇文章会拥有可路由的 ",[62,1009,1010],{},"path"," 和可供 ",[62,1013,1014],{},"ContentRenderer"," 使用的正文。",[120,1017,1018,1019,1022],{},"E2E 测试通过 ",[62,1020,1021],{},"NUXT_CONTENT_CWD=tests\u002Ffixtures\u002Fcontent"," 把文章集合切换到固定 fixture，测试不会依赖真实文章的标题和数量，也不会改动生产内容。",[111,1024,1026],{"id":1025},"六站点设置五份-yaml-如何保持页面边界","六、站点设置：五份 YAML 如何保持页面边界",[120,1028,1029],{},"站点设置按后台入口拆成五份文件：",[150,1031,1032,1042],{},[153,1033,1034],{},[156,1035,1036,1039],{},[159,1037,1038],{},"文件",[159,1040,1041],{},"管理内容",[166,1043,1044,1054,1064,1074,1084],{},[156,1045,1046,1051],{},[171,1047,1048],{},[62,1049,1050],{},"site.yml",[171,1052,1053],{},"站点名称、浏览器标题、SEO、位置、默认主题色、备案和署名",[156,1055,1056,1061],{},[171,1057,1058],{},[62,1059,1060],{},"home.yml",[171,1062,1063],{},"首页介绍、标题、最近文章、服务矩阵、RGB 模块和底部入口",[156,1065,1066,1071],{},[171,1067,1068],{},[62,1069,1070],{},"writing.yml",[171,1072,1073],{},"文章列表页介绍、SEO 和空状态",[156,1075,1076,1081],{},[171,1077,1078],{},[62,1079,1080],{},"services.yml",[171,1082,1083],{},"服务列表、状态、图标、主页显示和访问说明",[156,1085,1086,1091],{},[171,1087,1088],{},[62,1089,1090],{},"about.yml",[171,1092,1093],{},"关于页介绍、当前状态、关注主题和联系文案",[120,1095,1096,1097,1100,1101,1104,1105,1108,1109,1112],{},"拆分不只是 CMS 菜单分组。如果多个表单只声明同一 YAML 的部分字段，保存其中一个表单可能覆盖另一个表单未声明的字段；因此每个入口必须拥有独立源文件。",[62,1098,1099],{},"useSiteSettings()"," 使用固定异步数据键 ",[62,1102,1103],{},"site-settings","，通过 ",[62,1106,1107],{},"Promise.all"," 并行查询五个 data collection，再返回结构化的 ",[62,1110,1111],{},"site\u002Fhome\u002Fwriting\u002Fservices\u002Fabout"," 对象。任何一份缺失都会立即抛出 500，而不是让页面带着部分设置运行。",[120,1114,1115,1116,1119],{},"这些配置不是任意 YAML。",[62,1117,1118],{},"content.schema.ts"," 为每个文件提供独立严格 Schema，例如：",[124,1121,1122,1128,1131,1134,1143,1146,1152],{},[127,1123,1124,1125,909],{},"默认强调色必须是 ",[62,1126,1127],{},"#RRGGBB",[127,1129,1130],{},"最新文章数量只能是 1 到 3；",[127,1132,1133],{},"服务数量只能是 1 到 12；",[127,1135,1136,1137,871,1139,871,1141,909],{},"服务状态只能是 ",[62,1138,61],{},[62,1140,73],{},[62,1142,67],{},[127,1144,1145],{},"图标只能使用代码中已有的枚举；",[127,1147,1148,1149,1151],{},"服务链接只能是 ",[62,1150,78],{}," 或完整的 HTTPS URL；",[127,1153,1154],{},"对象使用严格模式，拼错字段不会被静默忽略。",[120,1156,1157,1160,1161,1163,1164,1167],{},[62,1158,1159],{},"public\u002Fadmin\u002Fconfig.yml"," 的表单选项、",[62,1162,1118],{}," 的运行时约束、",[62,1165,1166],{},"app\u002Fconfig\u002Fsite.ts"," 的 TypeScript 枚举应该同步修改。只改 CMS 下拉框，不改 Schema，保存后会校验失败；只改 Schema，不改组件映射，界面可能没有正确图标。",[111,1169,1171],{"id":1170},"七全站外壳与水合边界","七、全站外壳与水合边界",[120,1173,1174,1177],{},[62,1175,1176],{},"app\u002Fapp.vue"," 是每个路由外面的共同外壳。它负责：",[124,1179,1180,1183,1186,1189,1195,1198,1204,1207],{},[127,1181,1182],{},"在页面加载时取得站点设置；",[127,1184,1185],{},"判断当前是否为主页；",[127,1187,1188],{},"初始化和恢复主题色；",[127,1190,1191,1192,909],{},"把主题 CSS 变量挂到 ",[62,1193,1194],{},".site-shell",[127,1196,1197],{},"为非主页显示“返回”按钮与主题预设切换按钮；",[127,1199,1200,1201,909],{},"设置标题模板、站点描述、Open Graph 信息和 ",[62,1202,1203],{},"theme-color",[127,1205,1206],{},"根据当前强调色实时生成 data URL favicon；",[127,1208,1209],{},"显示 Nuxt 页面加载进度条。",[120,1211,1212,1215,1216,1219,1220,1223,1224,1227],{},[62,1213,1214],{},"hydrated"," 初始为 ",[62,1217,1218],{},"false","，在 ",[62,1221,1222],{},"onMounted"," 完成主题恢复和本地监听注册后变成 ",[62,1225,1226],{},"true","，最终反映为：",[358,1229,1233],{"className":1230,"code":1231,"language":1232,"meta":363,"style":363},"language-html shiki shiki-themes github-light github-dark","\u003Cdiv class=\"site-shell\" data-hydrated=\"true\">\n","html",[62,1234,1235],{"__ignoreMap":363},[367,1236,1237,1241,1245,1249,1252,1256,1259,1261,1264],{"class":369,"line":370},[367,1238,1240],{"class":1239},"sVt8B","\u003C",[367,1242,1244],{"class":1243},"s9eBZ","div",[367,1246,1248],{"class":1247},"sScJk"," class",[367,1250,1251],{"class":1239},"=",[367,1253,1255],{"class":1254},"sZZnC","\"site-shell\"",[367,1257,1258],{"class":1247}," data-hydrated",[367,1260,1251],{"class":1239},[367,1262,1263],{"class":1254},"\"true\"",[367,1265,1266],{"class":1239},">\n",[120,1268,1269],{},"这个属性既是测试可观察的“客户端已经接管页面”标志，也是字标动画的播放闸门。CSS 动画先建立，但在页面完成水合前保持暂停，防止服务端 HTML 刚显示就消耗掉一段动画，等 JavaScript 接管时只剩最终帧。",[120,1271,1272,1273,1276,1277,1280],{},"非主页的全局返回入口固定回到 ",[62,1274,1275],{},"\u002F","，文本只有“返回”，图标和 ",[62,1278,1279],{},"aria-label"," 补充了方向与完整语义。它与文章正文中的“返回文章”属于不同层级：前者返回网站主页，后者返回文章列表。",[111,1282,1284],{"id":1283},"八主页是一张单屏工作台","八、主页是一张单屏工作台",[120,1286,1287],{},"主页不是按多个营销区块向下滚动，而是一张固定在一个视口高度内的工作台。核心区域包括：",[124,1289,1290,1293,1296,1299,1302,1305,1308],{},[127,1291,1292],{},"顶部站点标识、上海时区时钟、指针坐标和主题按钮；",[127,1294,1295],{},"左上介绍、普通标题前缀与 Quilibra 字标；",[127,1297,1298],{},"右上服务矩阵；",[127,1300,1301],{},"左下最近三篇文章；",[127,1303,1304],{},"右下 RGB 调色器；",[127,1306,1307],{},"底部中央文章、服务、关于三个入口；",[127,1309,1310],{},"两侧备案与署名。",[120,1312,1313,1314,1317,1318,1321,1322,1325,1326,1329],{},"首页在 ",[62,1315,1316],{},"setup"," 阶段并行取得站点设置和最近文章。文章查询按 ",[62,1319,1320],{},"date DESC"," 排序，再按 YAML 中的 ",[62,1323,1324],{},"limit"," 截取。服务矩阵先筛选 ",[62,1327,1328],{},"showOnHome: true","，按 YAML 顺序最多取四个；服务页仍然展示完整列表。",[120,1331,1332,1333,1336,1337,1340,1341,1344,1345,1348],{},"顶部时钟通过 ",[62,1334,1335],{},"Intl.DateTimeFormat"," 固定使用 ",[62,1338,1339],{},"Asia\u002FShanghai","，每 30 秒更新一次。指针坐标不是每次 ",[62,1342,1343],{},"pointermove"," 都直接改 DOM：事件只保存最新坐标，然后在下一帧 ",[62,1346,1347],{},"requestAnimationFrame"," 中统一计算。元素边界在挂载与窗口缩放时缓存，触摸指针被忽略。这样可以减少高频事件中的布局读取和响应式更新。",[120,1350,1351],{},"工作台没有为了装饰引入 canvas 或 WebGL。网格、面板、条纹、阴影和入场效果全部由 CSS 完成，浏览器可以直接合成绝大多数变换。",[111,1353,1355],{"id":1354},"九响应式布局为何不只是按比例缩小","九、响应式布局为何不只是“按比例缩小”",[120,1357,1358],{},"主页有大量绝对定位元素，因此响应式的目标不是把桌面页面机械缩成手机版，而是维护清晰的空间约束：",[124,1360,1361,1368,1371,1374,1377,1384],{},[127,1362,1363,1364,1367],{},"桌面端通过 ",[62,1365,1366],{},"clamp()","、视口高度和稳定的面板高度控制上下关系；",[127,1369,1370],{},"最近文章与 RGB 面板在宽桌面上对齐顶部和底部；",[127,1372,1373],{},"小屏笔记本缩小间距和模块尺寸，仍避免重叠；",[127,1375,1376],{},"768 像素附近的紧凑布局隐藏无法舒适操作的 RGB 面板；",[127,1378,1379,1380,1383],{},"手机端重新排列主页元素，并使用 ",[62,1381,1382],{},"overflow: clip"," 防止装饰或过渡产生横向滚动；",[127,1385,1386],{},"固定格式组件使用明确的 grid 列、最小宽度和高度，标题悬浮时不会重新计算可用宽度。",[120,1388,1389],{},"Playwright 会在 768×1024、1024×768、1440×900 和 3440×1440 上读取真实元素几何信息，验证介绍不压住服务矩阵、上方面板不压住底部导航、RGB 与最近文章对齐、页面没有横向溢出。这里测试的是关系，而不是容易因一个像素改动就失效的整页截图。",[111,1391,1393],{"id":1392},"十主题色从一个-rgb-值扩展成整套界面","十、主题色从一个 RGB 值扩展成整套界面",[120,1395,1396,1397,1400],{},"主题逻辑集中在 ",[62,1398,1399],{},"useAccentTheme.ts","。唯一的核心状态是：",[358,1402,1406],{"className":1403,"code":1404,"language":1405,"meta":363,"style":363},"language-ts shiki shiki-themes github-light github-dark","interface RgbColor {\n  r: number\n  g: number\n  b: number\n}\n","ts",[62,1407,1408,1420,1433,1442,1452],{"__ignoreMap":363},[367,1409,1410,1414,1417],{"class":369,"line":370},[367,1411,1413],{"class":1412},"szBVR","interface",[367,1415,1416],{"class":1247}," RgbColor",[367,1418,1419],{"class":1239}," {\n",[367,1421,1422,1426,1429],{"class":369,"line":538},[367,1423,1425],{"class":1424},"s4XuR","  r",[367,1427,1428],{"class":1412},":",[367,1430,1432],{"class":1431},"sj4cs"," number\n",[367,1434,1435,1438,1440],{"class":369,"line":35},[367,1436,1437],{"class":1424},"  g",[367,1439,1428],{"class":1412},[367,1441,1432],{"class":1431},[367,1443,1445,1448,1450],{"class":369,"line":1444},4,[367,1446,1447],{"class":1424},"  b",[367,1449,1428],{"class":1412},[367,1451,1432],{"class":1431},[367,1453,1455],{"class":369,"line":1454},5,[367,1456,1457],{"class":1239},"}\n",[120,1459,1460,1461,1464,1465,1468],{},"三个内置预设是红、绿、蓝。站点设置里的 ",[62,1462,1463],{},"theme.defaultAccent"," 可以是任意合法十六进制颜色，并不要求与预设一致。当前颜色存放在 Nuxt ",[62,1466,1467],{},"useState"," 中，因此同一客户端的页面切换不会创建互相冲突的主题实例。",[120,1470,1471],{},"主题计算分为几步：",[278,1473,1474,1477,1486,1489,1495],{},[127,1475,1476],{},"把每个通道四舍五入并限制在 0 到 255。",[127,1478,1479,1480,1483,1484,239],{},"生成 CSS ",[62,1481,1482],{},"rgb(r g b)"," 与大写 ",[62,1485,1127],{},[127,1487,1488],{},"把强调色分别与白色、画布色和黑色混合，得到 soft、faint、canvas、grid、strong 等衍生色。",[127,1490,1491,1492,239],{},"计算 sRGB 相对亮度，对比黑白文字的对比度，自动选择更清晰的 ",[62,1493,1494],{},"--accent-ink",[127,1496,1497],{},"把结果以 CSS 变量挂到站点外壳，按钮、悬浮底色、网格、字标和 favicon 共同消费这些变量。",[120,1499,1500],{},"主题变量的意义大致如下：",[358,1502,1505],{"className":1503,"code":1504,"language":628,"meta":363},[626],"--accent          原始强调色\n--accent-ink      强调色背景上的黑或白文字\n--accent-soft     大面积悬浮反馈\n--accent-faint    更浅的面板背景\n--accent-canvas   轻微带主题倾向的页面画布\n--accent-grid     网格与线条色\n--accent-strong   向黑色混合后的强调色\n",[62,1506,1504],{"__ignoreMap":363},[120,1508,1509,1510,1512],{},"这样做比在 CSS 中到处硬编码“红色按钮、浅红背景、深红边框”更可靠。换成极亮或极暗的自定义颜色时，文字对比度仍会自动调整。E2E 会直接把颜色调到纯白和纯黑，验证 ",[62,1511,1494],{}," 分别变成深色和白色。",[111,1514,1516],{"id":1515},"十一主题持久化与旧黄色迁移","十一、主题持久化与旧黄色迁移",[120,1518,1519,1520,1523,1524,1527],{},"客户端挂载时，",[62,1521,1522],{},"restoreSavedAccent()"," 从 ",[62,1525,1526],{},"localStorage"," 读取：",[358,1529,1532],{"className":1530,"code":1531,"language":628,"meta":363},[626],"site-accent-rgb   完整 RGB 对象\nsite-accent       red \u002F green \u002F blue \u002F custom 等名称\n",[62,1533,1531],{"__ignoreMap":363},[120,1535,1536,1537,1540],{},"恢复后，深度监听 ",[62,1538,1539],{},"accentRgb","，后续每次变化都会重新保存。由于服务端无法读取浏览器存储，静态 HTML 首先使用 YAML 中的默认颜色；客户端挂载后再恢复访客上次的选择。",[120,1542,1543,1544,818,1547,1550],{},"旧版本曾使用黄色默认主题。为了避免已经访问过网站的浏览器永远被旧缓存锁在黄色，恢复逻辑专门识别 ",[62,1545,1546],{},"{255,255,2}",[62,1548,1549],{},"yellow"," 的组合，删除这两个旧值并回到当前 YAML 默认色。这是一次小型数据迁移：不是清空所有人的自定义配色，只清除能够明确识别的旧默认值。",[120,1552,1553,1554,1557,1558,1561,1562,1565,1566,1569,1570,1573],{},"动态 favicon 也跟随主题和站点名称。",[62,1555,1556],{},"app.vue"," 在内存中生成一个包含主题背景色与 ",[62,1559,1560],{},"site.name"," 首字符的 SVG，再编码为 ",[62,1563,1564],{},"data:image\u002Fsvg+xml","。因此 CMS 修改站点名称并重新构建后，标签页字母会同步改变；图标底色、字色和 ",[62,1567,1568],{},"meta[name=theme-color]"," 则继续与 RGB 面板同步。",[62,1571,1572],{},"public\u002Ffavicon.svg"," 只作为静态回退。",[111,1575,1577],{"id":1576},"十二rgb-调色器的交互细节","十二、RGB 调色器的交互细节",[120,1579,1580,1583,1584,1587],{},[62,1581,1582],{},"RgbAssembly.vue"," 不是独立维护另一份颜色，它调用同一个 ",[62,1585,1586],{},"useAccentTheme()","，因此滑杆、预设按钮、页面按钮和 favicon 始终共享状态。",[120,1589,1590],{},"三个 range input 分别控制 R、G、B：",[124,1592,1593,1599,1602,1605,1608],{},[127,1594,1595,1598],{},[62,1596,1597],{},"input"," 事件实时更新颜色，拖动时页面连续渐变；",[127,1600,1601],{},"每条轨道通过 CSS 变量计算已填充百分比；",[127,1603,1604],{},"输出区显示十六进制、十进制通道值，并采用自动对比文字；",[127,1606,1607],{},"点击 RED、GREEN、BLUE 立即加载预设；",[127,1609,1610],{},"重置按钮恢复 YAML 中的默认颜色，而不是写死某个预设。",[120,1612,1613],{},"字标动画不能在滑杆的每一个像素变化时重播，否则会不断重建动画并显得卡顿。组件因此区分“预览变化”和“提交变化”：",[124,1615,1616,1623,1629,1639,1646],{},[127,1617,1618,1619,1622],{},"指针按下后标记 ",[62,1620,1621],{},"pointerActive","，并捕获当前 pointer；",[127,1624,1625,1626,1628],{},"拖动中的 ",[62,1627,1597],{}," 只改变颜色；",[127,1630,1631,1634,1635,1638],{},[62,1632,1633],{},"pointerup"," 或 ",[62,1636,1637],{},"pointercancel"," 才请求重播一次字标；",[127,1640,1641,1642,1645],{},"键盘调整 range 时由 ",[62,1643,1644],{},"change"," 请求重播；",[127,1647,1648,1649,886,1651,1653],{},"一个零延时抑制标志防止同一次鼠标提交同时触发 ",[62,1650,1633],{},[62,1652,1644],{},"，造成双播。",[120,1655,1656,1657],{},"预设与重置属于离散操作，所以点击时立即换色并重播。这个模型可以概括为：",[130,1658,1659],{},"连续操作实时预览、松手提交动画；离散操作立即提交。",[111,1661,1663],{"id":1662},"十三quilibra-字标是可编辑的艺术字","十三、Quilibra 字标是可编辑的艺术字",[120,1665,1666,1667,1670,1671,1674],{},"当前字标不再依赖固定图片，而是由 ",[62,1668,1669],{},"content\u002Fsettings\u002Fhome.yml"," 中的 ",[62,1672,1673],{},"headline.emphasis"," 生成真实文本。CMS 的“首页 \u002F 艺术字文字”可以直接修改内容，Schema 将长度限制为 20 个字符；组件还会按照中英文字符宽度自动缩小过长文字，避免挤出首屏。",[120,1676,1677],{},"字形使用随构建产物一起发布的 Cormorant Garamond 600 Italic。页面只引入拉丁字符子集，既保留高对比衬线斜体的艺术感，也不依赖 Google Fonts 等站外服务；无法覆盖的字符会回退到本机衬线字体。",[120,1679,1680],{},"动画仍然采用“RGB 套色从偏移到合拢”，没有模拟笔尖逐笔书写。字标由四层相同文本组成：",[124,1682,1683,1686,1689,1692],{},[127,1684,1685],{},"红层从左下附近偏移进入；",[127,1687,1688],{},"绿层从上方偏移进入；",[127,1690,1691],{},"蓝层从右下附近偏移进入；",[127,1693,1694],{},"最终层使用当前主题色并带极轻的阴影。",[120,1696,1697,1698,1701,1702,871,1705,886,1708,1711,1712,1715],{},"前三层使用 ",[62,1699,1700],{},"mix-blend-mode: multiply","、动态模糊、透明度和不同位移。动画前段保留可见错版，中段快速靠近，后段降低彩色层透明度并让最终主题层聚焦。四层都只改变 ",[62,1703,1704],{},"opacity",[62,1706,1707],{},"transform",[62,1709,1710],{},"filter","，播放时临时声明 ",[62,1713,1714],{},"will-change","，结束后不长期占用合成资源。",[120,1717,1718,1721],{},[62,1719,1720],{},"ArtisticWordmark.vue"," 的加载控制解决了“首次打开没有动画”和字体中途替换的问题：",[278,1723,1724,1730,1737,1740,1743],{},[127,1725,1726,1729],{},[62,1727,1728],{},"@fontsource\u002Fcormorant-garamond"," 把字体文件交给 Vite 打包并生成带哈希的静态资源。",[127,1731,1732,1733,1736],{},"组件调用 ",[62,1734,1735],{},"document.fonts.load()","，等待艺术字体真正可用于绘制。",[127,1738,1739],{},"只有字体就绪、组件仍存活、页面可见且请求仍是最新时才开始播放。",[127,1741,1742],{},"字体加载失败时继续使用衬线回退字体，不阻断内容显示。",[127,1744,1745],{},"开启减少动态效果时直接展示最终状态。",[120,1747,1748,1749,1752,1753,1756],{},"每次重播都会增加 ",[62,1750,1751],{},"animationRun","，并把它放进四层的 Vue ",[62,1754,1755],{},"key","。这会让浏览器得到新的动画元素，可靠地从第 0 帧开始，而不是依赖移除 class 后强制读取布局。",[111,1758,1760],{"id":1759},"十四字标在什么时候重播","十四、字标在什么时候重播",[120,1762,1763,1764,1767,1768,1771],{},"全局 ",[62,1765,1766],{},"useWordmarkAnimation()"," 只维护一个数字信号。任何组件调用 ",[62,1769,1770],{},"requestReplay()","，数字加一；字标组件 watch 到变化后重播。这个很小的事件通道避免 RGB 组件直接引用字标 DOM。",[120,1773,1774],{},"当前重播场景包括：",[124,1776,1777,1780,1783,1786,1789,1792,1795],{},[127,1778,1779],{},"首次进入主页并且艺术字体加载完成；",[127,1781,1782],{},"点击主题预设或重置；",[127,1784,1785],{},"RGB 滑杆松手或键盘提交；",[127,1787,1788],{},"从文章、服务、关于页面返回主页，主页组件重新挂载；",[127,1790,1791],{},"浏览器标签页从隐藏变为可见；",[127,1793,1794],{},"窗口重新获得焦点；",[127,1796,1797,1798,1801],{},"浏览器的 ",[62,1799,1800],{},"pageshow","，包括可能来自往返缓存的恢复。",[120,1803,1804,871,1807,886,1810,1812],{},[62,1805,1806],{},"visibilitychange",[62,1808,1809],{},"focus",[62,1811,1800],{}," 可能在同一次切回中连续到达。组件使用一个 animation frame 合并激活请求，并设置 200ms 的最小间隔，防止一次切回连续播两三遍。页面变为隐藏时会取消待播放帧、使旧异步请求失效并结束当前播放。",[120,1814,1815],{},"这里还有两个无障碍与容错原则：",[124,1817,1818,1824],{},[127,1819,1820,1823],{},[62,1821,1822],{},"prefers-reduced-motion: reduce"," 时不播放套色，直接显示最终字标；",[127,1825,1826,1827,1830],{},"可读文字仍存在于 ",[62,1828,1829],{},"sr-only"," 中，视觉 mask 不承担标题语义。",[111,1832,1834],{"id":1833},"十五服务矩阵图标与状态点","十五、服务矩阵、图标与状态点",[120,1836,1837],{},"每个服务在 YAML 中有六个字段：名称、说明、链接、状态、图标、是否显示在主页。",[120,1839,1840,1843,1844,818,1846,1849,1850,1853],{},[62,1841,1842],{},"ServiceIcon.vue"," 把业务名称映射到 Lucide 图标。NAS 使用独立的 ",[62,1845,74],{},[62,1847,1848],{},"HardDrive","，不会复用影音播放图标。未知值虽然有 ",[62,1851,1852],{},"Server"," 回退，但正常内容会在 Schema 阶段被拒绝，因此回退只是组件级防御。",[120,1855,1856],{},"状态共有三种：",[358,1858,1861],{"className":1859,"code":1860,"language":628,"meta":363},[626],"online   在线\nprivate  仅限本人\nsoon     准备中\n",[62,1862,1860],{"__ignoreMap":363},[120,1864,1865,1868,1869,1872,1873,1876],{},[62,1866,1867],{},"ServiceStatusDot.vue"," 把状态写入 ",[62,1870,1871],{},"data-state","，CSS 用属性选择器决定颜色，",[62,1874,1875],{},"title"," 提供文字说明。主页和服务页都复用这个组件，因此 CMS 修改 YAML 状态后，重新构建的两个页面会同步变化，不需要分别维护配色。",[120,1878,1879,1880,1883],{},"状态点表达的是",[130,1881,1882],{},"人工配置的展示状态","，不是实时健康检查。它不会主动请求 Code、Photos、NAS 或 Status，也不会自动从监控系统同步。如果未来需要实时状态，应由独立状态 API 提供可信结果，再决定是在客户端请求还是构建前抓取；不能仅把绿色小点误解为自动监控。",[120,1885,1886,1887,1889,1890,1893,1894,1897,1898,1901],{},"链接为 ",[62,1888,78],{}," 时，主页服务节点转到 ",[62,1891,1892],{},"\u002Fservices","，服务页显示为不可点击行；完整 HTTPS 链接则在新标签页打开，并带 ",[62,1895,1896],{},"noopener noreferrer","。Schema 禁止 ",[62,1899,1900],{},"javascript:"," 和非 HTTPS 外部地址，避免 CMS 字段直接变成危险链接。",[111,1903,1905],{"id":1904},"十六文章列表筛选与搜索","十六、文章列表、筛选与搜索",[120,1907,1908,1911,1912,1915],{},[62,1909,1910],{},"\u002Fwriting"," 在构建阶段只查询 ",[62,1913,1914],{},"hidden = false"," 的文章，并按日期倒序排列。首页最近文章使用同样条件，浏览器端再对已经加载的公开数组做筛选，不需要为每个关键词请求服务器。",[120,1917,1918,1919,1922],{},"分类来自共享常量：随笔、学习、交易、观察。列表额外添加“全部”。搜索会把标题、摘要和标签拼成小写字符串，再做简单的 ",[62,1920,1921],{},"includes"," 匹配。这适合当前文章规模，特点是实现透明、中文可用、没有索引服务；但它不是分词搜索，也不会搜索正文。",[120,1924,1925],{},"文章行显示日期、标题、摘要、分类和箭头。悬浮一篇时：",[124,1927,1928,1931,1934,1937],{},[127,1929,1930],{},"只给当前行增加浅主题色背景；",[127,1932,1933],{},"日期与正文整体平移 8px；",[127,1935,1936],{},"箭头向右上轻移；",[127,1938,1939],{},"其他文章保持完全不变。",[120,1941,1942,1943,871,1946,1949,1950,1953],{},"标题容器的 grid 列不会在 hover 时改变，所以长标题不会因为悬浮突然获得更小宽度而换行。主页“最近写下”的标题使用 ",[62,1944,1945],{},"minmax(0,1fr)",[62,1947,1948],{},"overflow:hidden","、省略号和 ",[62,1951,1952],{},"white-space:nowrap","，确保固定高度面板不被长标题撑开。",[120,1955,1956,1957,1960],{},"搜索结果区使用 ",[62,1958,1959],{},"aria-live=\"polite\"","，筛选后的篇数和空状态可以被辅助技术感知。",[111,1962,1964],{"id":1963},"十七文章详情与相邻导航","十七、文章详情与相邻导航",[120,1966,1967,1968,1971,1972,1975],{},"动态路由文件是 ",[62,1969,1970],{},"app\u002Fpages\u002Fwriting\u002F[...slug].vue","。它使用当前 ",[62,1973,1974],{},"route.path"," 查询对应文章；找不到时立即抛出带中文说明的 404。",[120,1977,1978,1979,1981],{},"详情查询本身也要求 ",[62,1980,1914],{},"，所以隐藏文章不只是从列表消失，直接访问原 URL 也会得到真正的 404。详情页同时取得按日期倒序排列的全部公开文章，用当前文章的数组位置计算：",[124,1983,1984,1987],{},[127,1985,1986],{},"数组中下一项是时间上更旧的“上一篇”；",[127,1988,1989],{},"数组中上一项是时间上更新的“下一篇”。",[120,1991,1992,1993,1995],{},"页面展示分类、发布日期、可选的更新日期、标题、摘要、标签与正文。正文由 Nuxt Content 的 ",[62,1994,1014],{}," 生成。SEO 标题使用全站模板变成“文章标题 · Quilibra”，描述来自 frontmatter，Open Graph 类型设为 article。",[120,1997,1998,1999,2002],{},"正文样式集中在 ",[62,2000,2001],{},".article-prose","：限制阅读宽度、提高行高、分级处理标题、列表、引用、代码、链接和图片。文章页面可以自由使用 Markdown，不需要为每篇文章编写 Vue 模板。",[111,2004,2006],{"id":2005},"十八文章-frontmatter-合约","十八、文章 frontmatter 合约",[120,2008,2009],{},"一篇新文章最小结构如下：",[358,2011,2015],{"className":2012,"code":2013,"language":2014,"meta":363,"style":363},"language-yaml shiki shiki-themes github-light github-dark","---\ntitle: 清楚的文章标题\ndescription: 一句话说明文章实际记录了什么。\ndate: 2026-07-26\nhidden: false\ncategory: 学习\ntags:\n  - Nuxt\n---\n","yaml",[62,2016,2017,2022,2032,2042,2052,2062,2073,2082,2091],{"__ignoreMap":363},[367,2018,2019],{"class":369,"line":370},[367,2020,2021],{"class":1247},"---\n",[367,2023,2024,2026,2029],{"class":369,"line":538},[367,2025,1875],{"class":1243},[367,2027,2028],{"class":1239},": ",[367,2030,2031],{"class":1254},"清楚的文章标题\n",[367,2033,2034,2037,2039],{"class":369,"line":35},[367,2035,2036],{"class":1243},"description",[367,2038,2028],{"class":1239},[367,2040,2041],{"class":1254},"一句话说明文章实际记录了什么。\n",[367,2043,2044,2047,2049],{"class":369,"line":1444},[367,2045,2046],{"class":1243},"date",[367,2048,2028],{"class":1239},[367,2050,2051],{"class":1431},"2026-07-26\n",[367,2053,2054,2057,2059],{"class":369,"line":1454},[367,2055,2056],{"class":1243},"hidden",[367,2058,2028],{"class":1239},[367,2060,2061],{"class":1431},"false\n",[367,2063,2065,2068,2070],{"class":369,"line":2064},6,[367,2066,2067],{"class":1243},"category",[367,2069,2028],{"class":1239},[367,2071,2072],{"class":1254},"学习\n",[367,2074,2076,2079],{"class":369,"line":2075},7,[367,2077,2078],{"class":1243},"tags",[367,2080,2081],{"class":1239},":\n",[367,2083,2085,2088],{"class":369,"line":2084},8,[367,2086,2087],{"class":1239},"  - ",[367,2089,2090],{"class":1254},"Nuxt\n",[367,2092,2094],{"class":369,"line":2093},9,[367,2095,2021],{"class":1247},[120,2097,2098],{},"文件名必须是：",[358,2100,2103],{"className":2101,"code":2102,"language":628,"meta":363},[626],"YYYY-MM-DD-english-kebab.md\n",[62,2104,2102],{"__ignoreMap":363},[120,2106,2107,2108,871,2110,871,2112,871,2114,871,2117,871,2120,871,2122,871,2124,239,2126,2128,2129,2131],{},"允许字段只有 ",[62,2109,1875],{},[62,2111,2036],{},[62,2113,2046],{},[62,2115,2116],{},"updated",[62,2118,2119],{},"slug",[62,2121,2056],{},[62,2123,2067],{},[62,2125,2078],{},[62,2127,2056],{}," 只能是布尔值，省略时按 ",[62,2130,1218],{}," 处理。发布新文章时：",[124,2133,2134,2139,2145,2150],{},[127,2135,2136,2138],{},[62,2137,2046],{}," 必须是中国时区当天；",[127,2140,2141,2142,2144],{},"文件名日期必须与 ",[62,2143,2046],{}," 一致；",[127,2146,2147,2148,909],{},"不能包含 ",[62,2149,2116],{},[127,2151,2152,2154],{},[62,2153,2119],{}," 如果存在，必须与文件名后半段一致。",[120,2156,2157,2158,2160,2161,2163,2164,2167],{},"修订文章时保留原文件名和 ",[62,2159,2046],{},"，把 ",[62,2162,2116],{}," 设置为中国时区当天。writer 默认保留现有隐藏状态，只有修订内容明确给出 ",[62,2165,2166],{},"hidden: false"," 才会恢复。正文结构是自由的，但不能为空。若使用二级标题“来源与延伸阅读”，该节必须至少有一个 HTTP 或 HTTPS 链接。",[120,2169,2170,2173,2174,2177],{},[62,2171,2172],{},"scripts\u002Fcontent\u002Fvalidate.ts"," 使用 ",[62,2175,2176],{},"gray-matter"," 和 YAML 解析 frontmatter，再用 Markdown AST 检查正文与来源节。使用结构化解析而不是正则扫描全文，可以区分标题、链接与普通文本，并给出确定的错误。",[111,2179,2181],{"id":2180},"十九sveltia-cms-到底是什么","十九、Sveltia CMS 到底是什么",[120,2183,2184,2187,2188,2190],{},[62,2185,2186],{},"\u002Fadmin\u002Findex.html"," 只加载 Sveltia CMS 的前端脚本，",[62,2189,1159],{}," 描述后台字段。它不是另一个网站后端，也不存文章副本。",[120,2192,2193],{},"后台能维护：",[124,2195,2196,2199,2202,2205,2208,2211],{},[127,2197,2198],{},"站点、首页与栏目文案；",[127,2200,2201],{},"默认强调色和主页模块开关；",[127,2203,2204],{},"服务的增删、顺序、URL、状态、图标和主页显示；",[127,2206,2207],{},"文章的新建、搜索、筛选、修改和删除；",[127,2209,2210],{},"文章的隐藏和恢复；",[127,2212,2213,2215],{},[62,2214,889],{}," 中的文章资源。",[120,2217,2218],{},"CMS 有两种工作方式：",[278,2220,2221,2224],{},[127,2222,2223],{},"本地仓库模式：Chromium 通过 File System Access API 直接编辑本机选择的仓库。",[127,2225,2226],{},"GitHub 模式：用户经 GitHub 登录后，CMS 根据配置向私有仓库提交内容。",[120,2228,2229,2230,2232],{},"无论哪种模式，“保存”都只意味着源文件或远程仓库出现改动。它不会直接覆盖某个静态目录。远程 CMS 当前固定写入私人仓库的 ",[62,2231,600],{}," 分支，完整链路是：",[358,2234,2237],{"className":2235,"code":2236,"language":628,"meta":363},[626],"dev.quilibra.cn\u002Fadmin\n        |\n        | GitHub OAuth 保存\n        v\nGitHub staging\n        |\n        | GitHub push Webhook，HMAC-SHA256 签名\n        v\nVPS 事件队列 -> staging 同步 -> 快速或完整构建 -> staging release -> 127.0.0.1:3100\n        |\n        | 人工确认测试页面后 npm run promote\n        v\nGitHub master\n        |\n        | GitHub push Webhook，HMAC-SHA256 签名\n        v\nVPS 事件队列 -> master 同步 -> 快速或完整构建 -> production release -> 127.0.0.1:3000\n",[62,2238,2236],{"__ignoreMap":363},[120,2240,2241,2242,2245],{},"因此，在 CMS 打开“隐藏文章”并保存，只会先让测试站列表和原 URL 发生变化，正式站保持不动。确认后执行 ",[62,2243,2244],{},"npm run promote","，生产才接收同一个内容状态。这是分支、构建目录、release 和进程都真实隔离的预发布环境，不是给同一份生产内容换了一个域名。",[120,2247,2248,2249,2252],{},"GitHub OAuth 只控制“谁能通过 CMS 读写私人仓库”。本项目不使用 GitHub Actions 部署，也不开放公网 SSH；GitHub 只向现有 HTTPS 精确路径发送带签名的 push 通知，VPS 收到后再通过 Sing-box HTTP 代理主动拉取对应分支。Webhook secret 只在 VPS 和 GitHub 仓库设置中保存。私人仓库存放网站源码、文章、公开图片和不含密钥的配置；OAuth secret、访问令牌、Webhook secret、部署私钥、OpenClaw 会话、cookie 和 ",[62,2250,2251],{},".env"," 不进入仓库。",[120,2254,2255,2256,2259,2260,2263,2264,2266],{},"远程后台统一通过 ",[62,2257,2258],{},"https:\u002F\u002Fdev.quilibra.cn\u002Fadmin\u002Findex.html"," 使用。Nginx 在 TLS 之外再加一层 HTTP Basic Auth，并发送 ",[62,2261,2262],{},"noindex","；GitHub OAuth 负责仓库权限，Basic Auth 负责挡住后台入口，两者职责不同。后台路径和 ",[62,2265,2262],{}," 本身都不是访问控制。",[111,2268,2270],{"id":2269},"二十受限-writer-为什么存在","二十、受限 writer 为什么存在",[120,2272,2273,2274,2277],{},"普通编辑器可以修改仓库中的任何文件，但自动化发布工具不应该拥有同样宽的写入自由。",[62,2275,2276],{},"scripts\u002Fcontent\u002Fwrite.ts"," 把 OpenClaw 的写入范围压缩为三个明确操作：create、update、delete。",[120,2279,2280],{},"新建流程只接受草稿目录中的一个普通 Markdown 文件名和一个无日期 slug。writer 会检查：",[124,2282,2283,2286,2289,2292,2295,2298,2301],{},[127,2284,2285],{},"草稿名不能包含目录或路径穿越；",[127,2287,2288],{},"草稿必须是普通文件，不能是符号链接；",[127,2290,2291],{},"草稿不超过 1 MiB；",[127,2293,2294],{},"slug 必须是小写英文、数字和连字符；",[127,2296,2297],{},"frontmatter 与正文必须通过完整校验；",[127,2299,2300],{},"日期必须是中国时区当天；",[127,2302,2303],{},"目标文章不能已经存在。",[120,2305,2306,2307,2310,2311,2314,2315,2318,2319,2322],{},"写入时先以 ",[62,2308,2309],{},"wx"," 模式建立权限为 ",[62,2312,2313],{},"0640"," 的随机临时文件并 ",[62,2316,2317],{},"fsync","，再用硬链接创建最终文件，利用文件系统的 ",[62,2320,2321],{},"EEXIST"," 保证不会覆盖已有新文章。更新时先验证现有文件和发布日期，再用 rename 原子替换。删除只接受精确的完整 dated slug，并拒绝目录、符号链接和不存在的目标。",[120,2324,2325],{},"这不是为了让日常写作变复杂，而是为了让“从聊天自动发布”仍有可审计的硬边界。Skill 中的文字规则可能被模型误解，writer 的路径、日期和文件类型检查则由操作系统与代码强制执行。",[111,2327,2329],{"id":2328},"二十一openclaw-发布-skill-的实际状态机","二十一、OpenClaw 发布 Skill 的实际状态机",[120,2331,2332,2333,2336],{},"仓库只维护一个 ",[62,2334,2335],{},"personal-site-publisher"," Skill。它先读取文章合约，再按以下过程工作：",[358,2338,2341],{"className":2339,"code":2340,"language":628,"meta":363},[626],"链接或素材\n   |\n   v\n确定标题、摘要、日期、slug、分类、标签\n   |\n   v\n在私聊中返回完整草稿，不写仓库\n   |\n   +-- 修改：... --> 修改内存草稿\n   +-- 放弃 ------> 清除内存草稿\n   +-- 发布 ------> 保存到受限草稿目录\n                         |\n                         v\n                   content:write\n                         |\n                         v\n                  npm run publish\n                         |\n                         v\n              返回文章 URL、commit、release\n",[62,2342,2340],{"__ignoreMap":363},[120,2344,2345,2348,2349,239],{},[62,2346,2347],{},"直接发布"," 只跳过人工预览，不跳过 writer、内容校验和静态生成。更新文章必须保留 dated URL；删除必须先展示目标信息，再收到完全匹配的 ",[62,2350,2351],{},"确认删除 \u003Cdated-slug>",[120,2353,2354,2355,871,2358,1634,2361,2364],{},"发布 Skill 还规定：只接受所有者私聊中的发布命令；把网页、对话和搜索结果视为不可信内容；不把 API key、cookie、账号信息、私人对话细节和精确私人资产写入文章；不能用任意编辑器、",[62,2356,2357],{},"rm",[62,2359,2360],{},"git add",[62,2362,2363],{},"git commit"," 绕过 writer 和 release 脚本。",[111,2366,2368],{"id":2367},"二十二本地发布自动同步与环境晋级","二十二、本地发布、自动同步与环境晋级",[120,2370,2371],{},"当前有五个相关入口，名字接近但权限完全不同。",[116,2373,2375],{"id":2374},"npm-run-publish",[62,2376,2377],{},"npm run publish",[120,2379,2380],{},"用于受信本地流程中尚未提交的内容改动，例如 OpenClaw Skill。它只允许以下路径：",[358,2382,2385],{"className":2383,"code":2384,"language":628,"meta":363},[626],"content\u002Fsettings\u002Fsite.yml\ncontent\u002Fsettings\u002Fhome.yml\ncontent\u002Fsettings\u002Fwriting.yml\ncontent\u002Fsettings\u002Fservices.yml\ncontent\u002Fsettings\u002Fabout.yml\ncontent\u002Fwriting\u002F**\npublic\u002Fuploads\u002F**\n",[62,2386,2384],{"__ignoreMap":363},[120,2388,2389],{},"它验证内容、生成静态站、自动创建本地 Git commit、复制 release 并切换本地默认生产目录。若工作区混入 Vue、CSS、脚本、CMS 配置或文档改动，会拒绝执行。它是受限本地发布入口，不是远程 CMS 的预发布流程。",[116,2391,2393],{"id":2392},"npm-run-deploy",[62,2394,2395],{},"npm run deploy",[120,2397,2398],{},"用于已经提交的代码版本。它要求工作区完全干净，不创建 commit，并依次运行：",[358,2400,2403],{"className":2401,"code":2402,"language":628,"meta":363},[626],"类型检查\n内容与 writer 单元测试\nrelease 单元测试\n静态生成\n浏览器 E2E\n创建 release\n原子切换 current\n清理过旧 release\n",[62,2404,2402],{"__ignoreMap":363},[116,2406,2408],{"id":2407},"npm-run-sync",[62,2409,2410],{},"npm run sync",[120,2412,2413,2416,2417,2419,2420,2422],{},[62,2414,2415],{},"scripts\u002Fsync.ts"," 是两个 systemd oneshot 服务共用的自动同步器。环境变量决定它跟踪 ",[62,2418,608],{}," 还是 ",[62,2421,600],{},"、使用哪一份独立仓库、把 release 写到哪个数据根目录。每轮会：",[278,2424,2425,2428,2431,2441,2446,2452],{},[127,2426,2427],{},"从 Sing-box 配置读取带认证的本机 HTTP 代理；",[127,2429,2430],{},"重试 GitHub fetch，只接受能够快进的远端历史；",[127,2432,2433,2434,2437,2438,909],{},"根据 ",[62,2435,2436],{},"package-lock.json"," 哈希决定是否运行 ",[62,2439,2440],{},"npm ci",[127,2442,2443,2444,909],{},"比较上次已部署提交与目标提交：只有受管内容变化时执行快速内容部署，否则执行完整 ",[62,2445,2395],{},[127,2447,2448,2449,909],{},"只有部署成功才原子写入 ",[62,2450,2451],{},"deployed-commit",[127,2453,2454],{},"失败时保留旧 release，由持久化 Webhook 事件延迟重试。",[120,2456,2457,2458,2461],{},"纯文章、站点设置和上传资源变化仍会执行内容校验与静态生成，但跳过未变化代码的类型检查、单元测试和 E2E。生产和测试同步服务使用同一个 ",[62,2459,2460],{},"flock"," 文件串行执行，防止 2 GB 内存的 VPS 同时跑两份 Nuxt 构建和 Playwright。",[116,2463,2465],{"id":2464},"npm-run-webhook",[62,2466,2467],{},"npm run webhook",[120,2469,2470,2473,2474,2477,2478,2481,2482,2485,2486,2489,2490,239],{},[62,2471,2472],{},"scripts\u002Fwebhook.ts"," 只监听 ",[62,2475,2476],{},"127.0.0.1:3110","，Nginx 把 ",[62,2479,2480],{},"https:\u002F\u002Fquilibra.cn\u002F_hooks\u002Fgithub"," 的精确 POST 路由转给它。接收器先验证 HMAC-SHA256 签名、仓库名、push 类型和 ",[62,2483,2484],{},"staging\u002Fmaster"," 分支，再把事件以权限 ",[62,2487,2488],{},"0600"," 写入用户状态目录并返回 ",[62,2491,2492],{},"202",[120,2494,2495],{},"每个 GitHub delivery 都有独立队列文件。若构建期间出现第二次 push，第一轮完成后会再启动一轮同步；进程重启时也会恢复未完成事件。失败使用延迟重试，不需要周期性轮询 GitHub。Webhook 请求只能映射到两个固定 systemd unit，不能携带或执行任意命令。",[116,2497,2499],{"id":2498},"npm-run-promote",[62,2500,2244],{},[120,2502,2503,2504,2506,2507,2509],{},"这是远程 CMS 从测试进入生产的唯一显式关口。它要求本地 ",[62,2505,608],{}," 干净且等于最新远端，确认远端 ",[62,2508,600],{}," 的精确提交已经成功部署到测试站，并拒绝 staging 中的 Vue、CSS、脚本、文档或 CMS 配置改动。允许晋级的只有：",[358,2511,2513],{"className":2512,"code":2384,"language":628,"meta":363},[626],[62,2514,2384],{"__ignoreMap":363},[120,2516,2517,2518,2521,2522,886,2524,2526],{},"检查通过后，脚本在临时 Git worktree 中把 staging 合并到最新 master，再用一次 ",[62,2519,2520],{},"git push --atomic"," 让远端 ",[62,2523,608],{},[62,2525,600],{}," 同时指向同一个合并提交。若任一引用不能更新，两边都不更新。GitHub 随后发送 master Webhook 并触发正式部署。",[120,2528,2529,2530,2533,2534,2536,2537,2540,2541,2543,2544,2546],{},"因此，修改本文这样的文章有两种合法路径：本地受信流程可用 ",[62,2531,2532],{},"publish","；远程 CMS 则保存到 staging、检查测试站、再运行 ",[62,2535,604],{},"。修改 Vue\u002FCSS 并已经提交后使用 ",[62,2538,2539],{},"deploy"," 或由 master 同步器部署。不要用 ",[62,2542,2532],{}," 偷渡代码，也不要让 ",[62,2545,2539],{}," 带着未提交文件上线。",[111,2548,2550],{"id":2549},"二十三静态-release-如何做到切换时不中断","二十三、静态 release 如何做到切换时不中断",[120,2552,2553,2556],{},[62,2554,2555],{},"scripts\u002Frelease.ts"," 用 UTC 时间生成 release 名称，例如：",[358,2558,2561],{"className":2559,"code":2560,"language":628,"meta":363},[626],"20260726T144914-134Z\n",[62,2562,2560],{"__ignoreMap":363},[120,2564,2565,2566,2568,2569,2572,2573,2575],{},"生成结束后，把 ",[62,2567,655],{}," 递归复制到 ",[62,2570,2571],{},"releases\u002F\u003Cid>","。激活时不是先删 ",[62,2574,659],{}," 再新建，而是：",[278,2577,2578,2581,2584],{},[127,2579,2580],{},"创建一个带进程号的临时符号链接；",[127,2582,2583],{},"让临时链接指向新 release；",[127,2585,2586,2587,2590,2591,239],{},"用 ",[62,2588,2589],{},"rename"," 把临时链接原子替换成 ",[62,2592,659],{},[120,2594,2595,2596,2598,2599,2601],{},"对访问者来说，某个请求要么读取旧 release，要么读取新 release，不会遇到 ",[62,2597,659],{}," 暂时不存在的中间状态。静态 Node 进程也不需要重启，因为它每次请求都从 ",[62,2600,659],{}," 路径解析文件。",[120,2603,2604,2607,2608,2611,2612,2615,2616,886,2619,239],{},[62,2605,2606],{},"PERSONAL_SITE_DATA_ROOT"," 决定 release 根目录。生产不设置时使用 ",[62,2609,2610],{},"~\u002F.local\u002Fshare\u002Fpersonal-site","；测试同步服务显式设置为 ",[62,2613,2614],{},"~\u002F.local\u002Fshare\u002Fpersonal-site-staging","。因此相同的 release 代码可以复用，但两个环境不会碰到对方的 ",[62,2617,2618],{},"releases\u002F",[62,2620,659],{},[120,2622,2623],{},"脚本默认保留最近五个 release，并额外保证当前激活版本不被删掉。由于当前版本有可能是手工回滚到的较旧目录，保留“当前版本”比单纯保留时间最新的五个更重要。",[120,2625,2626,2627,2629],{},"回滚只调用同一个原子激活函数，把 ",[62,2628,659],{}," 指回已存在的 release。它不修改 Git、不重新构建、不删除较新的版本，也不重启生产服务。",[111,2631,2633],{"id":2632},"二十四静态服务器nginx-与-https","二十四、静态服务器、Nginx 与 HTTPS",[120,2635,2636,2639,2640,871,2643,871,2646,886,2649,2652,2653,2655,2656,871,2659,871,2662,2665,2666,2669],{},[62,2637,2638],{},"scripts\u002Fstatic-server.mjs"," 使用 Node 自带的 ",[62,2641,2642],{},"http",[62,2644,2645],{},"fs",[62,2647,2648],{},"stream",[62,2650,2651],{},"zlib","。监听地址、端口和 ",[62,2654,659],{}," 路径分别由 ",[62,2657,2658],{},"PERSONAL_SITE_HOST",[62,2660,2661],{},"PERSONAL_SITE_PORT",[62,2663,2664],{},"PERSONAL_SITE_ROOT"," 控制。两个 systemd unit 都把 host 设为 ",[62,2667,2668],{},"127.0.0.1","，所以 3000 和 3100 不直接接受公网连接。它没有框架中间件，职责非常窄：",[124,2671,2672,2675,2688,2694,2701,2704,2707,2710,2713,2716,2723,2729,2732],{},[127,2673,2674],{},"只接受 GET 和 HEAD，其他方法返回 405；",[127,2676,2677,2678,818,2681,2684,2685,2687],{},"解码 URL 后用 ",[62,2679,2680],{},"resolve",[62,2682,2683],{},"relative"," 检查目标仍在 ",[62,2686,659],{}," 内，阻止目录穿越；",[127,2689,2690,2691,909],{},"请求目录时返回该目录的 ",[62,2692,2693],{},"index.html",[127,2695,2696,2697,2700],{},"找不到文件时返回预生成的 ",[62,2698,2699],{},"404.html"," 和 404 状态；",[127,2702,2703],{},"根据扩展名发送正确的 Content-Type；",[127,2705,2706],{},"对大于等于 1 KiB 的文本资源协商 Brotli 或 gzip；",[127,2708,2709],{},"Brotli 使用质量 4，gzip 使用级别 6，在 CPU 与体积间取中间值；",[127,2711,2712],{},"使用读取流和 pipeline，不把大文件一次性读进内存；",[127,2714,2715],{},"根据文件大小和修改时间生成弱 ETag；",[127,2717,2718,2719,2722],{},"命中 ",[62,2720,2721],{},"If-None-Match"," 时返回 304；",[127,2724,2725,2728],{},[62,2726,2727],{},"_nuxt\u002F"," 哈希资源缓存一年并标记 immutable；",[127,2730,2731],{},"HTML、图片等非哈希路径使用 no-cache，确保 release 切换后会重新验证；",[127,2733,2734],{},"收到 SIGINT 或 SIGTERM 时停止接受新连接并正常退出。",[120,2736,2737,2738,2740],{},"如果 ",[62,2739,659],{}," 不可用，服务器返回 503，而不是把文件系统错误暴露给访问者。若响应流已经开始后出错，则销毁连接，避免发送一半文件后再拼接错误文本。",[120,2742,2743],{},"它不会处理 TLS、OAuth 或反向代理。公网入口由 Nginx 负责：",[358,2745,2748],{"className":2746,"code":2747,"language":628,"meta":363},[626],"quilibra.cn \u002F www.quilibra.cn -> HTTPS -> 127.0.0.1:3000\ndev.quilibra.cn               -> HTTPS + Basic Auth -> 127.0.0.1:3100\n公网 IP或未知 Host             -> 默认站点拒绝\n",[62,2749,2747],{"__ignoreMap":363},[120,2751,2752,2753,2756,2757,2760],{},"根域名和 ",[62,2754,2755],{},"www"," 共用正式站，证书由 Certbot 申请并续期；测试子域名使用自己的证书和密码文件。Nginx 把真实 Host、客户端地址和转发协议传给上游，测试站额外发送 ",[62,2758,2759],{},"X-Robots-Tag: noindex, nofollow, noarchive","。腾讯云安全组只需要开放 80 和 443，3000、3100 不对公网放行。",[120,2762,2763,2764,2767,2768,2771],{},"页脚备案号来自全站设置 ",[62,2765,2766],{},"content\u002Fsettings\u002Fsite.yml","，当前 ICP 号链接到 ",[62,2769,2770],{},"https:\u002F\u002Fbeian.miit.gov.cn\u002F","。备案展示、DNS、TLS 证书和反向代理是四个不同层次：备案号不会自动配置 HTTPS，证书也不会自动创建 DNS 记录。",[111,2773,2775],{"id":2774},"二十五300031003101-分别是什么","二十五、3000、3100、3101 分别是什么",[150,2777,2778,2791],{},[153,2779,2780],{},[156,2781,2782,2785,2788],{},[159,2783,2784],{},"端口",[159,2786,2787],{},"用途",[159,2789,2790],{},"生命周期",[166,2792,2793,2804,2816],{},[156,2794,2795,2798,2801],{},[171,2796,2797],{},"3000",[171,2799,2800],{},"当前生产静态 release",[171,2802,2803],{},"systemd 长期运行",[156,2805,2806,2809,2814],{},[171,2807,2808],{},"3100",[171,2810,2811,2813],{},[62,2812,600],{}," 当前静态 release",[171,2815,2803],{},[156,2817,2818,2821,2824],{},[171,2819,2820],{},"3101",[171,2822,2823],{},"Playwright 隔离测试服务",[171,2825,2826],{},"测试自动启动并结束",[120,2828,2829,2830,2833,2834,2837],{},"3100 过去曾运行当前工作区的 Nuxt Dev，容易受首次编译、热更新和 Nuxt Content 缓存损坏影响。现在它与 3000 一样只运行静态服务器，从独立 staging release 读取文件，空闲常驻约几十 MB，并由 ",[62,2831,2832],{},"https:\u002F\u002Fdev.quilibra.cn"," 提供远程预览。需要真正的热更新时，在开发机或 VPS 的另一个空闲端口临时运行 ",[62,2835,2836],{},"npm run dev","，不要覆盖常驻 3100。",[120,2839,2840,2841,2843],{},"3101 使用独立内容 fixture 和 ",[62,2842,951],{},"，不能拿它当日常预览端口。生产 3000、预发布 3100 和测试 3101 可以同时存在，因为 release、构建目录和端口都隔离。",[111,2845,2847],{"id":2846},"二十六systemd-用户服务","二十六、systemd 用户服务",[120,2849,2850],{},"当前有五个相关 unit：",[358,2852,2855],{"className":2853,"code":2854,"language":628,"meta":363},[626],"personal-site.service                 3000 生产静态服务\npersonal-site-dev.service             3100 staging 静态服务\npersonal-site-webhook.service         3110 签名 Webhook 接收与事件排队\npersonal-site-sync.service            master 单次同步与部署\npersonal-site-staging-sync.service    staging 单次同步与部署\n",[62,2856,2854],{"__ignoreMap":363},[120,2858,2859],{},"两个静态服务的关键设置包括：",[124,2861,2862,2868,2874,2880,2886,2895],{},[127,2863,2864,2867],{},[62,2865,2866],{},"Type=simple","：Node 进程本身就是主进程；",[127,2869,2870,2873],{},[62,2871,2872],{},"After\u002FWants=network-online.target","：网络就绪后启动；",[127,2875,2876,2879],{},[62,2877,2878],{},"Restart=on-failure"," 与 5 秒延迟：异常退出后自动恢复；",[127,2881,2882,2885],{},[62,2883,2884],{},"KillSignal=SIGINT","：与静态服务器的优雅关闭逻辑对应；",[127,2887,2888,871,2891,2894],{},[62,2889,2890],{},"NoNewPrivileges=true",[62,2892,2893],{},"PrivateTmp=true","：缩小运行时权限；",[127,2896,2897,2898,2901],{},"安装到用户级 ",[62,2899,2900],{},"default.target","，不要求整个服务以 root 运行。",[120,2903,2904,2905,2907,2908,2911,2912,818,2915,2917,2918,2921],{},"Webhook 服务是 ",[62,2906,2866],{}," 常驻轻量进程，只监听回环地址；两个同步服务仍是 ",[62,2909,2910],{},"Type=oneshot","，仅在收到对应分支的 push 后运行。生产和测试分别拥有独立 ",[62,2913,2914],{},"sync-repo",[62,2916,2451],{},"，但用同一个 ",[62,2919,2920],{},"\u002Fhome\u002Fuser\u002F.local\u002Fstate\u002Fpersonal-site-deploy.lock"," 串行构建。仓库没有周期性 GitHub timer；有事件时才 fetch，依赖锁变化时才安装依赖，纯内容提交使用快速构建。",[120,2923,2924,2925,2928,2929,2932],{},"unit 当前把 Node 可执行文件写成 NVM 下的明确路径。升级 Node 或切换 NVM 版本后，shell 中的 ",[62,2926,2927],{},"node"," 可能已经变化，但 systemd 仍引用旧路径，这是需要主动检查的运维陷阱。修改 unit 后必须 ",[62,2930,2931],{},"daemon-reload","，而普通文章或页面 release 不需要重启静态服务。",[120,2934,2935,2936,2939,2940,2943],{},"用户级服务要在 VPS 重启且用户未登录时自动启动，需要为运行网站的 Linux 用户启用 linger。管理它时应使用相同用户的 ",[62,2937,2938],{},"systemctl --user","，不应使用 ",[62,2941,2942],{},"sudo systemctl --user"," 去连接 root 的用户总线。",[111,2945,2947],{"id":2946},"二十七测试体系究竟覆盖什么","二十七、测试体系究竟覆盖什么",[120,2949,2950],{},"测试按风险边界分成三组。",[116,2952,2954],{"id":2953},"内容和-writer-单元测试","内容和 writer 单元测试",[120,2956,2957,2960],{},[62,2958,2959],{},"test:content"," 检查：",[124,2962,2963,2966,2969,2972,2975,2980,2983,2986,2989],{},[127,2964,2965],{},"合法文章和四种分类可以通过；",[127,2967,2968],{},"非法日期、分类、文件名、重复标签和空正文会失败；",[127,2970,2971],{},"来源节必须包含公共 HTTP(S) 链接；",[127,2973,2974],{},"CMS 可选 slug 必须与文件名一致；",[127,2976,2977,2979],{},[62,2978,2056],{}," 只能是布尔值，writer 更新时默认保留已有隐藏状态；",[127,2981,2982],{},"站点 YAML 满足 Schema；",[127,2984,2985],{},"writer 拒绝覆盖、穿越、符号链接和错误修订日期；",[127,2987,2988],{},"更新保留发布日期；",[127,2990,2991],{},"删除只接受精确存在的 dated slug。",[116,2993,2995],{"id":2994},"release-单元测试","release 单元测试",[120,2997,2998,3001],{},[62,2999,3000],{},"test:release"," 在临时目录中检查：",[124,3003,3004,3009,3012,3015,3018,3021,3024,3027,3030,3033],{},[127,3005,3006,3008],{},[62,3007,659],{}," 能原子切换；",[127,3010,3011],{},"清理历史版本时保留激活 release；",[127,3013,3014],{},"release 名称不能路径穿越；",[127,3016,3017],{},"受管内容路径不会扩大到应用代码；",[127,3019,3020],{},"自动同步失败后不写成功状态，后续重试仍会部署；",[127,3022,3023],{},"Webhook 拒绝无效签名、其他仓库和其他分支；",[127,3025,3026],{},"构建期间到达的第二个 push 会保留并追加同步；",[127,3028,3029],{},"纯内容提交走快速构建，代码提交走完整构建；",[127,3031,3032],{},"staging 未成功部署时不能晋级，晋级后 master 与 staging 原子对齐；",[127,3034,3035],{},"子命令失败时错误信息保留退出码。",[116,3037,3039],{"id":3038},"playwright-浏览器测试","Playwright 浏览器测试",[120,3041,3042,3045],{},[62,3043,3044],{},"test:e2e"," 在 Chromium 中检查：",[124,3047,3048,3051,3054,3057,3060,3063,3066,3069,3072,3075,3078,3081],{},[127,3049,3050],{},"首页成功水合且没有控制台错误；",[127,3052,3053],{},"动态 favicon、theme-color 和 RGB 输出同步；",[127,3055,3056],{},"自定义主题在纯黑纯白下仍可读；",[127,3058,3059],{},"旧黄色缓存会迁移；",[127,3061,3062],{},"mask 没加载完时字标不偷跑，加载后正常播放；",[127,3064,3065],{},"标签页激活、窗口 focus、换色、滑杆松手和返回主页会重播；",[127,3067,3068],{},"拖动期间不会反复播放；",[127,3070,3071],{},"服务状态、NAS 图标、最近文章、文章详情和更新日期正确；",[127,3073,3074],{},"隐藏文章不出现在公开查询中，原 URL 返回 404；",[127,3076,3077],{},"文章悬浮只影响当前行，长标题宽度不跳变；",[127,3079,3080],{},"手机页面无横向溢出，RGB 在小屏隐藏；",[127,3082,3083],{},"多种桌面尺寸下关键模块互不重叠。",[120,3085,3086],{},"Playwright 配置允许一次重试，等待时间 10 秒，临时 Nuxt 服务启动最长等待 120 秒。响应式几何测试启用 reduced motion，避免入场动画中的瞬时位置影响布局判断。",[120,3088,3089],{},"测试不是越多越好。这里保留的是曾经真实出错、或者一旦回归就很难靠类型系统发现的行为；字体文件数量、每个 CSS 颜色和每一段正文不需要分别写测试。",[111,3091,3093],{"id":3092},"二十八当前性能画像与做过的优化","二十八、当前性能画像与做过的优化",[120,3095,3096],{},"在当前版本的一次本机测量中：",[124,3098,3099,3102,3105,3108,3111],{},[127,3100,3101],{},"主 CSS 约 31.1 KB，gzip 后约 6.9 KB；",[127,3103,3104],{},"外部或本地字体文件由 98 个减少到 0；",[127,3106,3107],{},"首页一次传输约 252 KB；",[127,3109,3110],{},"模拟 4G 和 4 倍 CPU 降速时，LCP 约 0.75 秒，完整 load 约 1.37 秒；",[127,3112,3113],{},"CLS 为 0。",[120,3115,3116,3117,3120],{},"VPS 空闲状态下，生产与测试两个 Node 静态服务合计约 50 MB；Webhook 接收器也是单一轻量 Node 进程，不执行构建。整机仍有约 1.1 GB 可用内存。完整 Nuxt + Playwright 部署的峰值接近 1 GB，但两个同步器通过共享锁串行执行；内容快速构建不启动 Playwright。生产、测试和开发三份仓库合计约 1.5 GB，主要空间来自各自的 ",[62,3118,3119],{},"node_modules","；这是用磁盘换取工作区、缓存和发布故障互不污染。",[120,3122,3123],{},"这些数字是环境相关快照，不是永久承诺。浏览器缓存、网络、CPU、文章数量和依赖升级都会改变结果。",[120,3125,3126],{},"当前主要性能措施包括：",[124,3128,3129,3132,3135,3138,3145,3150,3153,3156,3159,3162,3165],{},[127,3130,3131],{},"静态预渲染，HTML 首次响应包含页面内容；",[127,3133,3134],{},"移除大批字体资源，改用系统字体；",[127,3136,3137],{},"只预加载首屏真正依赖的 30 KB 字标 mask；",[127,3139,3140,3141,3144],{},"字标等待 ",[62,3142,3143],{},"decode()","，避免资源未准备好时动画丢失；",[127,3146,3147,3149],{},[62,3148,1347],{}," 合并高频指针更新；",[127,3151,3152],{},"缓存元素边界，避免每次 pointermove 读取布局；",[127,3154,3155],{},"连续调色只改颜色，松手才重播动画；",[127,3157,3158],{},"用 transform\u002Fopacity 处理大多数动效；",[127,3160,3161],{},"生产服务器流式响应并支持 Brotli、gzip、ETag 和长期哈希缓存；",[127,3163,3164],{},"固定组件尺寸，避免动态文本造成布局偏移；",[127,3166,3167],{},"分离本地开发、生产同步、测试同步和 E2E 的工作目录与 Nuxt Content 数据库。",[120,3169,3170,3172],{},[62,3171,655],{}," 整体约 5.4 MB，其中包括 Nuxt Content 的客户端 SQLite\u002FWASM 相关资源；这不等于每个访客首屏都会下载整个目录。分析性能时应看浏览器实际请求和传输体积，不应把产物目录大小直接当作首页流量。",[111,3174,3176],{"id":3175},"二十九为什么首次交互偶尔会过一会儿才正常","二十九、为什么首次交互偶尔会“过一会儿才正常”",[120,3178,3179],{},"这个问题曾同时表现为字标不播放和 RGB 滑杆暂时失灵，根因方向不是滑杆 CSS 本身，而是客户端水合尚未完成或 Nuxt Dev 仍在首次编译。静态 HTML 可以先显示，但 Vue 事件只有在 JavaScript 加载、执行并成功水合后才生效。",[120,3181,3182,3183,3186],{},"判断方法是观察 ",[62,3184,3185],{},".site-shell[data-hydrated=\"true\"]","。如果页面已经显示但该属性迟迟没有变成 true，应检查：",[124,3188,3189,3192,3195,3198,3201],{},[127,3190,3191],{},"浏览器控制台是否有 JavaScript 错误；",[127,3193,3194],{},"本地 Nuxt Dev 是否还在首次编译；",[127,3196,3197],{},"本地内容 SQLite 缓存是否损坏；",[127,3199,3200],{},"大型依赖或资源是否阻塞客户端入口；",[127,3202,3203],{},"当前访问的是临时 Nuxt Dev，还是已经生成的 3000\u002F3100 静态站。",[120,3205,3206],{},"目前通过移除字体、减轻入口资源、预加载 mask、分离内容数据库和明确动画水合闸门改善了这个过程。远程测试站也已经改成静态 release，不再边访问边编译，因此它与正式站具有相同的水合特征。",[111,3208,3210],{"id":3209},"三十常见修改应该改哪里","三十、常见修改应该改哪里",[116,3212,3214],{"id":3213},"修改个人介绍栏目文案或服务","修改个人介绍、栏目文案或服务",[120,3216,3217,3218,3220,3221,3223],{},"优先通过 CMS 中对应的页面入口，或编辑 ",[62,3219,881],{}," 下对应 YAML；服务列表位于 ",[62,3222,1080],{},"。若新增服务状态或图标类型，还要同步修改 Schema、配置枚举、CMS 选项、组件映射、CSS 和测试。",[116,3225,3226],{"id":3226},"修改默认颜色",[120,3228,3229,3230,3232,3233,3235],{},"修改 ",[62,3231,1463],{},"。它可以是任意 ",[62,3234,1127],{},"。已有访客若保存过自定义颜色，会继续看到自己的选择；要做全体迁移，需要像旧黄色迁移一样明确识别并处理旧值，不能无条件清空 localStorage。",[116,3237,3238],{"id":3238},"修改红绿蓝预设",[120,3240,3229,3241,3243,3244,3247],{},[62,3242,1399],{}," 的 ",[62,3245,3246],{},"accentPresets","。RGB 面板和非主页调色按钮都复用它。修改后应测试纯黑纯白对比、localStorage 恢复和字标重播。",[116,3249,3250],{"id":3250},"修改艺术字",[120,3252,3253,3254,3243,3256,3258,3259,3261,3262,239],{},"在 CMS 中打开“站点设置 \u002F 首页”，修改“艺术字文字”即可。它最终写入 ",[62,3255,1060],{},[62,3257,1673],{},"，保存到测试分支后由 Webhook 自动重新构建测试站。字形由 ",[62,3260,899],{}," 引入，字体栈、字号和四层颜色位于 ",[62,3263,3264],{},"main.css",[116,3266,3267],{"id":3267},"修改字标动画",[120,3269,3270,3271,3273,3274,3277,3278,3280],{},"播放条件在 ",[62,3272,1720],{},"，跨组件触发在 ",[62,3275,3276],{},"useWordmarkAnimation.ts","，视觉关键帧在 ",[62,3279,3264],{},"。不要把三者混成一个大组件：字体状态、事件状态和视觉时间线是不同责任。",[116,3282,3283],{"id":3283},"修改文章分类",[120,3285,3286,3287,3290],{},"至少同步 ",[62,3288,3289],{},"app\u002Fconfig\u002Farticles.ts","、Nuxt Content Schema、CMS 选项、校验器测试与界面测试。文章中的旧分类是否迁移，需要单独决定。",[116,3292,3293],{"id":3293},"修改文章样式",[120,3295,3296,3297,3300,3301,3303,3304,3307],{},"文章列表看 ",[62,3298,3299],{},".article-row","，正文看 ",[62,3302,2001],{},"，详情头部看 ",[62,3305,3306],{},".article-hero","。长标题、手机宽度、hover 前后几何和其他文章 opacity 是必须复查的回归点。",[116,3309,3310],{"id":3310},"修改生产或测试服务",[120,3312,3313,3314,3316],{},"静态响应逻辑改 ",[62,3315,2638],{},"；监听端口、release 根目录、Node 路径和重启策略改对应 systemd unit。同步分支、代理、独立仓库和部署锁改两个 sync unit。只有静态服务器或 unit 变化需要重启\u002F重载，普通 release 切换不需要。",[111,3318,3320],{"id":3319},"三十一日常发布配方","三十一、日常发布配方",[116,3322,3324],{"id":3323},"通过远程-cms-修改内容","通过远程 CMS 修改内容",[278,3326,3327,3333,3336,3341],{},[127,3328,3329,3330,3332],{},"打开 ",[62,3331,2258],{}," 并保存。",[127,3334,3335],{},"等待 Webhook 触发 staging 构建，检查测试站主页、列表和具体 URL。",[127,3337,3338,3339,239],{},"在干净且最新的 master 工作区运行 ",[62,3340,2244],{},[127,3342,3343],{},"等待 master Webhook 触发生产构建，再检查正式站。",[120,3345,3346],{},"保存、预览、晋级和正式部署是四个明确阶段。隐藏文章也遵循同一流程。",[116,3348,3349],{"id":3349},"本地受信流程直接发布内容",[358,3351,3355],{"className":3352,"code":3353,"language":3354,"meta":363,"style":363},"language-bash shiki shiki-themes github-light github-dark","npm run content:validate\nnpm run publish\n","bash",[62,3356,3357,3368],{"__ignoreMap":363},[367,3358,3359,3362,3365],{"class":369,"line":370},[367,3360,3361],{"class":1247},"npm",[367,3363,3364],{"class":1254}," run",[367,3366,3367],{"class":1254}," content:validate\n",[367,3369,3370,3372,3374],{"class":369,"line":538},[367,3371,3361],{"class":1247},[367,3373,3364],{"class":1254},[367,3375,3376],{"class":1254}," publish\n",[120,3378,3379,3381],{},[62,3380,2532],{}," 成功后会输出 commit、release 和 current 路径。它用于 OpenClaw 等本地受限流程，会直接切换默认生产 release；是否推送 GitHub 是另一项操作。普通远程 CMS 编辑不要使用这条路径绕过 staging。",[116,3383,3385],{"id":3384},"发布-vuecss脚本或配置代码","发布 Vue、CSS、脚本或配置代码",[358,3387,3389],{"className":3352,"code":3388,"language":3354,"meta":363,"style":363},"npm run typecheck\nnpm run test:content\nnpm run test:release\nnpm run test:e2e\nnpm run generate\ngit diff --check\n# 明确检查并提交本次文件\ngit push origin master\n",[62,3390,3391,3400,3409,3418,3427,3436,3447,3453],{"__ignoreMap":363},[367,3392,3393,3395,3397],{"class":369,"line":370},[367,3394,3361],{"class":1247},[367,3396,3364],{"class":1254},[367,3398,3399],{"class":1254}," typecheck\n",[367,3401,3402,3404,3406],{"class":369,"line":538},[367,3403,3361],{"class":1247},[367,3405,3364],{"class":1254},[367,3407,3408],{"class":1254}," test:content\n",[367,3410,3411,3413,3415],{"class":369,"line":35},[367,3412,3361],{"class":1247},[367,3414,3364],{"class":1254},[367,3416,3417],{"class":1254}," test:release\n",[367,3419,3420,3422,3424],{"class":369,"line":1444},[367,3421,3361],{"class":1247},[367,3423,3364],{"class":1254},[367,3425,3426],{"class":1254}," test:e2e\n",[367,3428,3429,3431,3433],{"class":369,"line":1454},[367,3430,3361],{"class":1247},[367,3432,3364],{"class":1254},[367,3434,3435],{"class":1254}," generate\n",[367,3437,3438,3441,3444],{"class":369,"line":2064},[367,3439,3440],{"class":1247},"git",[367,3442,3443],{"class":1254}," diff",[367,3445,3446],{"class":1431}," --check\n",[367,3448,3449],{"class":369,"line":2075},[367,3450,3452],{"class":3451},"sJ8bj","# 明确检查并提交本次文件\n",[367,3454,3455,3457,3460,3463],{"class":369,"line":2084},[367,3456,3440],{"class":1247},[367,3458,3459],{"class":1254}," push",[367,3461,3462],{"class":1254}," origin",[367,3464,3465],{"class":1254}," master\n",[120,3467,3468,3469,3471,3472,3474],{},"master Webhook 会触发同步器再次执行完整 ",[62,3470,2395],{},"，前面的命令适合在提交前尽早发现问题。需要在 VPS 立即部署当前干净提交时也可以手工运行 ",[62,3473,2395],{},"。代码版本只进入 master 时，测试站可能暂时仍运行上一份代码；下一次内容晋级会把最新 master 与 staging 合并并重新对齐两边。",[116,3476,3477],{"id":3477},"查看当前生产状态",[358,3479,3481],{"className":3352,"code":3480,"language":3354,"meta":363,"style":363},"systemctl --user is-active personal-site.service\nsystemctl --user is-active personal-site-dev.service\nreadlink -f ~\u002F.local\u002Fshare\u002Fpersonal-site\u002Fcurrent\nreadlink -f ~\u002F.local\u002Fshare\u002Fpersonal-site-staging\u002Fcurrent\ncurl -fsS -o \u002Fdev\u002Fnull -w '%{http_code} %{content_type}\\n' http:\u002F\u002F127.0.0.1:3000\u002F\ncurl -fsS -o \u002Fdev\u002Fnull -w '%{http_code} %{content_type}\\n' http:\u002F\u002F127.0.0.1:3100\u002F\n",[62,3482,3483,3497,3508,3519,3528,3551],{"__ignoreMap":363},[367,3484,3485,3488,3491,3494],{"class":369,"line":370},[367,3486,3487],{"class":1247},"systemctl",[367,3489,3490],{"class":1431}," --user",[367,3492,3493],{"class":1254}," is-active",[367,3495,3496],{"class":1254}," personal-site.service\n",[367,3498,3499,3501,3503,3505],{"class":369,"line":538},[367,3500,3487],{"class":1247},[367,3502,3490],{"class":1431},[367,3504,3493],{"class":1254},[367,3506,3507],{"class":1254}," personal-site-dev.service\n",[367,3509,3510,3513,3516],{"class":369,"line":35},[367,3511,3512],{"class":1247},"readlink",[367,3514,3515],{"class":1431}," -f",[367,3517,3518],{"class":1254}," ~\u002F.local\u002Fshare\u002Fpersonal-site\u002Fcurrent\n",[367,3520,3521,3523,3525],{"class":369,"line":1444},[367,3522,3512],{"class":1247},[367,3524,3515],{"class":1431},[367,3526,3527],{"class":1254}," ~\u002F.local\u002Fshare\u002Fpersonal-site-staging\u002Fcurrent\n",[367,3529,3530,3533,3536,3539,3542,3545,3548],{"class":369,"line":1454},[367,3531,3532],{"class":1247},"curl",[367,3534,3535],{"class":1431}," -fsS",[367,3537,3538],{"class":1431}," -o",[367,3540,3541],{"class":1254}," \u002Fdev\u002Fnull",[367,3543,3544],{"class":1431}," -w",[367,3546,3547],{"class":1254}," '%{http_code} %{content_type}\\n'",[367,3549,3550],{"class":1254}," http:\u002F\u002F127.0.0.1:3000\u002F\n",[367,3552,3553,3555,3557,3559,3561,3563,3565],{"class":369,"line":2064},[367,3554,3532],{"class":1247},[367,3556,3535],{"class":1431},[367,3558,3538],{"class":1431},[367,3560,3541],{"class":1254},[367,3562,3544],{"class":1431},[367,3564,3547],{"class":1254},[367,3566,3567],{"class":1254}," http:\u002F\u002F127.0.0.1:3100\u002F\n",[116,3569,3570],{"id":3570},"回滚",[120,3572,3573],{},"先列出确实存在的 release，再执行：",[358,3575,3577],{"className":3352,"code":3576,"language":3354,"meta":363,"style":363},"npm run rollback -- \u003Cexact-release-id>\n",[62,3578,3579],{"__ignoreMap":363},[367,3580,3581,3583,3585,3588,3591,3594,3597,3600],{"class":369,"line":370},[367,3582,3361],{"class":1247},[367,3584,3364],{"class":1254},[367,3586,3587],{"class":1254}," rollback",[367,3589,3590],{"class":1431}," --",[367,3592,3593],{"class":1412}," \u003C",[367,3595,3596],{"class":1254},"exact-release-i",[367,3598,3599],{"class":1239},"d",[367,3601,1266],{"class":1412},[120,3603,3604,3605,3607,3608,3610,3611,239],{},"回滚后再次检查 ",[62,3606,659],{}," 和 3000 返回值。不要手动删除 ",[62,3609,659],{},"，也不要把它指向仓库的 ",[62,3612,655],{},[111,3614,3616],{"id":3615},"三十二故障排查顺序","三十二、故障排查顺序",[116,3618,3620],{"id":3619},"cms-保存后测试站看不到","CMS 保存后测试站看不到",[120,3622,3623,3624,3626,3627,3629,3630,871,3633,3636,3637,3640,3641,3643],{},"先确认提交是否进入 GitHub ",[62,3625,600],{},"，并在 GitHub Recent Deliveries 中确认 Webhook 返回 ",[62,3628,2492],{},"；再检查 ",[62,3631,3632],{},"personal-site-webhook.service",[62,3634,3635],{},"personal-site-staging-sync.service"," 日志、",[62,3638,3639],{},"~\u002F.local\u002Fstate\u002Fpersonal-site-staging-sync\u002Fdeployed-commit"," 和测试 ",[62,3642,659],{},"。构建失败不会覆盖旧预览；事件文件会保留并延迟重试，也可以修复后手工启动同步服务。",[116,3645,3646],{"id":3646},"测试站正确但正式站没变化",[120,3648,3649,3650,3652,3653,3655,3656,3659,3660,3662],{},"确认是否实际运行过 ",[62,3651,2244],{},"、远端 master 是否已更新以及 master Webhook 是否返回 ",[62,3654,2492],{},"，再检查 ",[62,3657,3658],{},"personal-site-sync.service"," 和生产 ",[62,3661,2451],{},"。CMS 保存只更新测试站是正常设计，不是同步故障。",[116,3664,3666],{"id":3665},"rgb-不能拖按钮不能点动画不播放","RGB 不能拖、按钮不能点、动画不播放",[120,3668,3669,3670,3673,3674,3677],{},"先看 ",[62,3671,3672],{},"data-hydrated","，再看控制台错误和网络请求。若只发生在临时 Nuxt Dev 的第一次编译，等待完成后重载；若持续发生，停止那个临时开发进程，运行 ",[62,3675,3676],{},"npx nuxt cleanup"," 后重启开发端口。常驻 3000 和 3100 都是静态服务器，不使用这份开发缓存。",[116,3679,3680],{"id":3680},"切回标签页没有动画",[120,3682,3683,3684,871,3686,3688],{},"检查浏览器是否启用 reduced motion、mask 图片是否加载失败，以及 ",[62,3685,1806],{},[62,3687,1809],{}," 是否触发。一次切回只播一次是正常防抖，不应去掉 200ms 合并后让三个事件连续触发。",[116,3690,3691],{"id":3691},"换色先闪回旧颜色",[120,3693,3694,3695,3697],{},"检查静态默认色、Nuxt ",[62,3696,1467],{}," 初始值和 localStorage 恢复顺序。服务端 HTML无法知道客户端保存颜色，完全避免首帧差异需要在页面渲染前执行极小的内联主题恢复脚本；当前实现选择保持静态生成简单，在水合时恢复。",[116,3699,3701],{"id":3700},"服务状态点不随-cms-变化","服务状态点不随 CMS 变化",[120,3703,3704,3705,3708,3709,3711],{},"确认 YAML 中 ",[62,3706,3707],{},"state"," 已保存、值属于三个枚举，并检查正在看的环境：CMS 保存后测试站应先变化，正式站要等 promote。若 DOM 属性已变而颜色没变，检查 CSS 状态选择器；若属性没变，检查对应环境的 ",[62,3710,659],{}," 是否仍是旧 release。",[116,3713,3715],{"id":3714},"_3000-无法访问","3000 无法访问",[120,3717,3718,3719,3721,3722,3724],{},"检查用户级 systemd 状态、日志、Node 固定路径、端口占用和 ",[62,3720,659],{}," 链接。服务器进程存在但 ",[62,3723,659],{}," 失效时会返回 503。不要在未确认进程归属前直接杀端口进程。",[120,3726,3727,3728,3731,3732,3734],{},"3100 使用相同排查方法，但服务是 ",[62,3729,3730],{},"personal-site-dev.service","，数据根目录是 ",[62,3733,2614],{},"。正式站正常而测试站异常时，不要重启 3000。",[116,3736,3738],{"id":3737},"管理页面提示只允许-https","管理页面提示只允许 HTTPS",[120,3740,3741,3742,3744],{},"这通常来自浏览器安全上下文要求，而不是 Git remote 配错。Git remote 只决定仓库同步地址，不会给 HTTP 页面增加 HTTPS。远程后台应使用已经配置可信证书和 Basic Auth 的 ",[62,3743,2258],{},"；本地仓库模式则从 localhost 打开。",[111,3746,3748],{"id":3747},"三十三安全与备份边界","三十三、安全与备份边界",[120,3750,3751],{},"至少要区分三类数据：",[358,3753,3756],{"className":3754,"code":3755,"language":628,"meta":363},[626],"Git 仓库       源码、文章、站点设置、公开静态资源\nOpenClaw 目录  Skill、草稿、会话和本地配置\nrelease 目录   生产与测试当前及历史静态构建结果\n",[62,3757,3755],{"__ignoreMap":363},[120,3759,3760],{},"Git 提交是版本历史，不是异地备份。私人远程仓库可以备份源码与文章，但 OpenClaw 配置和 release 数据需要单独备份到受控存储。",[120,3762,3763,3764,3766],{},"永远不要提交或写入公开文章的内容包括：API key、OAuth secret、部署私钥、QQ token、cookie、扫码状态、",[62,3765,2251],{},"、私人服务密码、内部地址清单和不适合公开的资产信息。",[120,3768,3769,3770,3773,3774,3776],{},"CMS 的 ",[62,3771,3772],{},"\u002Fadmin\u002F"," 路径和 ",[62,3775,2262],{}," 只能减少搜索引擎收录，不能阻止陌生人访问。当前远程后台同时依靠可信 HTTPS、Nginx Basic Auth 和 GitHub OAuth；生产\u002F测试上游只监听回环地址，公网 IP 与未知 Host 由默认 Nginx 站点拒绝。真正的保护来自这些边界和最小权限凭据，而不是隐藏 URL。",[111,3778,3780],{"id":3779},"三十四维护这套代码时应坚持的原则","三十四、维护这套代码时应坚持的原则",[120,3782,3783],{},"第一，内容、表现和发布边界分开。能在 YAML 解决的文案不要硬编码进 Vue；能由共享组件表达的状态不要在两个页面复制；生产切换不要混进页面代码。",[120,3785,3786],{},"第二，把浏览器状态当成显式状态。主题色、资源是否解码、页面是否可见、指针是否仍按下、水合是否完成，都应有清楚的变量和生命周期，而不是靠延时猜测。",[120,3788,3789],{},"第三，动画必须有静态最终状态。资源失败、JavaScript 失败或用户减少动态效果时，标题仍要可读，布局仍要成立。",[120,3791,3792],{},"第四，自动化写入必须比人工编辑权限更窄。Skill 负责工作流，writer 负责硬边界，validator 负责内容合约，release 负责上线，四者不能互相冒充。",[120,3794,3795],{},"第五，生产部署应该是“生成一个完整新版本，然后切换”，而不是在访问者正在读取的目录里逐个覆盖文件。原子 release 是这个小网站最值得长期保留的工程设计之一。",[120,3797,3798,3799,3801],{},"第六，测试站和正式站必须由分支、仓库、release 与进程共同隔离。域名不同不等于环境隔离，CMS 保存也不等于生产发布；",[62,3800,604],{}," 是有校验的明确边界。",[120,3803,3804],{},"第七，测试真实的关系和历史 bug。主题对比、滑杆松手、标签页重播、长标题 hover、隐藏文章 404、服务状态同步和多视口不重叠，都来自实际使用中的问题，比为了提高数字而堆大量脆弱测试更有价值。",[111,3806,3808],{"id":3807},"三十五重新上手时的最短阅读路径","三十五、重新上手时的最短阅读路径",[120,3810,3811],{},"如果未来很久没有维护这个项目，按下面顺序读，可以最快恢复上下文：",[278,3813,3814,3820,3828,3837,3843,3848,3860,3863],{},[127,3815,3816,3817,3819],{},"看 ",[62,3818,881],{}," 的五份 YAML，知道全站和各页面当前展示什么。",[127,3821,3816,3822,886,3825,3827],{},[62,3823,3824],{},"app\u002Fpages\u002Findex.vue",[62,3826,3264],{}," 的主页部分，理解首屏结构。",[127,3829,3816,3830,871,3832,871,3834,3836],{},[62,3831,1399],{},[62,3833,1582],{},[62,3835,1720],{},"，理解最复杂的交互。",[127,3838,3839,3840,3842],{},"看两个 writing 页面和 ",[62,3841,968],{},"，理解文章查询与渲染。",[127,3844,3816,3845,3847],{},[62,3846,1118],{},"、validator 和 writer，理解内容边界。",[127,3849,3816,3850,871,3853,871,3856,3859],{},[62,3851,3852],{},"release.ts",[62,3854,3855],{},"sync.ts",[62,3857,3858],{},"promote.ts"," 和 systemd unit，理解双环境发布链路。",[127,3861,3862],{},"看 Nginx 模板与运维文档，理解域名、HTTPS、Basic Auth 和回环上游。",[127,3864,3865],{},"最后看测试，把“哪些行为不能再坏”快速过一遍。",[120,3867,3868],{},"只要能重新回答下面五个问题，就已经掌握了这个项目：",[124,3870,3871,3874,3877,3880,3883,3886],{},[127,3872,3873],{},"当前页面内容的唯一来源在哪里？",[127,3875,3876],{},"浏览器中的主题色如何从 RGB 状态传到 CSS、字标和 favicon？",[127,3878,3879],{},"为什么 CMS 保存后只改变测试站？",[127,3881,3882],{},"publish、deploy、sync 和 promote 的权限、检查与 Git 行为有什么不同？",[127,3884,3885],{},"一个新 release 如何在不重启 3000 的情况下接管生产请求？",[127,3887,3888],{},"3000 与 3100 为什么不会覆盖彼此的仓库和 current？",[120,3890,3891],{},"这些问题就是 Quilibra 当前技术架构的骨架。",[111,3893,3894],{"id":3894},"来源与延伸阅读",[124,3896,3897,3906,3913,3920,3927,3934,3941,3948],{},[127,3898,3899],{},[3900,3901,3905],"a",{"href":3902,"rel":3903},"https:\u002F\u002Fnuxt.com\u002Fdocs",[3904],"nofollow","Nuxt 文档",[127,3907,3908],{},[3900,3909,3912],{"href":3910,"rel":3911},"https:\u002F\u002Fcontent.nuxt.com\u002F",[3904],"Nuxt Content 文档",[127,3914,3915],{},[3900,3916,3919],{"href":3917,"rel":3918},"https:\u002F\u002Fvuejs.org\u002Fguide\u002Fextras\u002Fcomposition-api-faq.html",[3904],"Vue Composition API",[127,3921,3922],{},[3900,3923,3926],{"href":3924,"rel":3925},"https:\u002F\u002Fplaywright.dev\u002Fdocs\u002Fintro",[3904],"Playwright 文档",[127,3928,3929],{},[3900,3930,3933],{"href":3931,"rel":3932},"https:\u002F\u002Fgithub.com\u002Fsveltia\u002Fsveltia-cms",[3904],"Sveltia CMS 文档",[127,3935,3936],{},[3900,3937,3940],{"href":3938,"rel":3939},"https:\u002F\u002Fdeveloper.mozilla.org\u002Fen-US\u002Fdocs\u002FWeb\u002FCSS\u002Fmask",[3904],"MDN：CSS mask",[127,3942,3943],{},[3900,3944,3947],{"href":3945,"rel":3946},"https:\u002F\u002Fdeveloper.mozilla.org\u002Fen-US\u002Fdocs\u002FWeb\u002FAPI\u002FPage_Visibility_API",[3904],"MDN：Page Visibility API",[127,3949,3950],{},[3900,3951,3954],{"href":3952,"rel":3953},"https:\u002F\u002Fdeveloper.mozilla.org\u002Fen-US\u002Fdocs\u002FWeb\u002FHTTP\u002FCaching",[3904],"MDN：HTTP 缓存",[534,3956,3957],{},"html pre.shiki code .sVt8B, html code.shiki .sVt8B{--shiki-default:#24292E;--shiki-dark:#E1E4E8}html pre.shiki code .s9eBZ, html code.shiki .s9eBZ{--shiki-default:#22863A;--shiki-dark:#85E89D}html pre.shiki code .sScJk, html code.shiki .sScJk{--shiki-default:#6F42C1;--shiki-dark:#B392F0}html pre.shiki code .sZZnC, html code.shiki .sZZnC{--shiki-default:#032F62;--shiki-dark:#9ECBFF}html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html.dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html pre.shiki code .szBVR, html code.shiki .szBVR{--shiki-default:#D73A49;--shiki-dark:#F97583}html pre.shiki code .s4XuR, html code.shiki .s4XuR{--shiki-default:#E36209;--shiki-dark:#FFAB70}html pre.shiki code .sj4cs, html code.shiki .sj4cs{--shiki-default:#005CC5;--shiki-dark:#79B8FF}html pre.shiki code .sJ8bj, html code.shiki .sJ8bj{--shiki-default:#6A737D;--shiki-dark:#6A737D}",{"title":363,"searchDepth":538,"depth":538,"links":3959},[3960,3961,3962,3963,3964,3965,3966,3967,3968,3969,3970,3971,3972,3973,3974,3975,3976,3977,3978,3979,3980,3981,3988,3989,3990,3991,3992,3997,3998,3999,4009,4016,4026,4027,4028,4029],{"id":615,"depth":538,"text":616},{"id":666,"depth":538,"text":667},{"id":699,"depth":538,"text":700},{"id":829,"depth":538,"text":830},{"id":893,"depth":538,"text":894},{"id":1025,"depth":538,"text":1026},{"id":1170,"depth":538,"text":1171},{"id":1283,"depth":538,"text":1284},{"id":1354,"depth":538,"text":1355},{"id":1392,"depth":538,"text":1393},{"id":1515,"depth":538,"text":1516},{"id":1576,"depth":538,"text":1577},{"id":1662,"depth":538,"text":1663},{"id":1759,"depth":538,"text":1760},{"id":1833,"depth":538,"text":1834},{"id":1904,"depth":538,"text":1905},{"id":1963,"depth":538,"text":1964},{"id":2005,"depth":538,"text":2006},{"id":2180,"depth":538,"text":2181},{"id":2269,"depth":538,"text":2270},{"id":2328,"depth":538,"text":2329},{"id":2367,"depth":538,"text":2368,"children":3982},[3983,3984,3985,3986,3987],{"id":2374,"depth":35,"text":2377},{"id":2392,"depth":35,"text":2395},{"id":2407,"depth":35,"text":2410},{"id":2464,"depth":35,"text":2467},{"id":2498,"depth":35,"text":2244},{"id":2549,"depth":538,"text":2550},{"id":2632,"depth":538,"text":2633},{"id":2774,"depth":538,"text":2775},{"id":2846,"depth":538,"text":2847},{"id":2946,"depth":538,"text":2947,"children":3993},[3994,3995,3996],{"id":2953,"depth":35,"text":2954},{"id":2994,"depth":35,"text":2995},{"id":3038,"depth":35,"text":3039},{"id":3092,"depth":538,"text":3093},{"id":3175,"depth":538,"text":3176},{"id":3209,"depth":538,"text":3210,"children":4000},[4001,4002,4003,4004,4005,4006,4007,4008],{"id":3213,"depth":35,"text":3214},{"id":3226,"depth":35,"text":3226},{"id":3238,"depth":35,"text":3238},{"id":3250,"depth":35,"text":3250},{"id":3267,"depth":35,"text":3267},{"id":3283,"depth":35,"text":3283},{"id":3293,"depth":35,"text":3293},{"id":3310,"depth":35,"text":3310},{"id":3319,"depth":538,"text":3320,"children":4010},[4011,4012,4013,4014,4015],{"id":3323,"depth":35,"text":3324},{"id":3349,"depth":35,"text":3349},{"id":3384,"depth":35,"text":3385},{"id":3477,"depth":35,"text":3477},{"id":3570,"depth":35,"text":3570},{"id":3615,"depth":538,"text":3616,"children":4017},[4018,4019,4020,4021,4022,4023,4024,4025],{"id":3619,"depth":35,"text":3620},{"id":3646,"depth":35,"text":3646},{"id":3665,"depth":35,"text":3666},{"id":3680,"depth":35,"text":3680},{"id":3691,"depth":35,"text":3691},{"id":3700,"depth":35,"text":3701},{"id":3714,"depth":35,"text":3715},{"id":3737,"depth":35,"text":3738},{"id":3747,"depth":538,"text":3748},{"id":3779,"depth":538,"text":3780},{"id":3807,"depth":538,"text":3808},{"id":3894,"depth":538,"text":3894},"2026-07-26","记录 Quilibra 个人主页 2026 年 7 月版本的技术选型、页面架构、内容系统、主题动画、双环境发布、HTTPS、测试体系和维护方法。",{},"\u002Fwriting\u002F2026-07-26-quilibra-complete-technical-handbook","2026-07-26T23:46:23+08:00",{"title":583,"description":4031},"quilibra-complete-technical-handbook","writing\u002F2026-07-26-quilibra-complete-technical-handbook",[4039,4040,738,4041,786,778,4042],"Nuxt","Vue","Nuxt Content","静态部署","2026-08-03","ILFf8HTh9BFuZakheSV0lJmjpNenfU1fBRtcsKT1umE",{"id":4046,"title":4047,"body":4048,"category":4198,"date":4030,"description":4199,"extension":562,"hidden":563,"meta":4200,"navigation":31,"path":4201,"publishedAt":4034,"seo":4202,"slug":4203,"stem":4204,"tags":4205,"updated":4030,"__hash__":4210},"writing\u002Fwriting\u002F2026-07-26-trading-cognition-and-compound-reality.md","交易是为了赚钱还是验证认知：从量化门槛到复利现实",{"type":108,"value":4049,"toc":4187},[4050,4053,4057,4060,4063,4067,4070,4073,4076,4079,4082,4085,4088,4092,4095,4115,4118,4129,4132,4135,4149,4152,4155,4158,4161,4164,4168,4171,4174,4178,4181,4184],[120,4051,4052],{},"刷到一个清华博士的视频，说想赚钱就去量化。但这对于普通人的门槛是不是太高？就算跨过去了，市场容量真的够赚到钱吗？带着这些问题和 AI 聊了一圈，从量化门槛一路聊到\"你到底为什么做交易\"，把思路理了一遍。",[111,4054,4056],{"id":4055},"机构量化-vs-系统化交易","机构量化 vs 系统化交易",[120,4058,4059],{},"机构量化（幻方、九坤级别）的门槛确实很高：博士学历、海量 tick 数据、专用算力、上亿起步资金，而且赛道内卷、alpha 衰减快、容量有限。",[120,4061,4062],{},"但普通人能做的是\"系统化交易\"而非机构量化。20 日均线 + 严格止损 + 行业 ETF，这套逻辑本质就是量化思维。真正的问题不是门槛，是把博士生的参照系错误地套用在自己身上。这类建议对清北学生可操作，对大多数人是废话，因为它省略了关键前提：清北学生的起点已经过滤掉 90% 的竞争。",[111,4064,4066],{"id":4065},"只是为了赚钱可能是对自己的贬低","\"只是为了赚钱\"可能是对自己的贬低",[120,4068,4069],{},"我说做交易只是为了赚钱。但仔细想想，我对系统和机制本身一直有探究欲--止损逻辑、去中心化的交易所架构、自己项目的技术选型会追求优雅和性能。真正纯粹为钱的人不会纠结止损后策略逻辑对不对。",[120,4071,4072],{},"如果账户明天清零，还会不会继续研究这套系统？答案可能是会的。因为做交易挣不挣钱是对我认知是否正确的检验，猜对了奖励，猜错了亏钱。我在市场里的目的是验证认知，想知道自己是怎样的人。",[120,4074,4075],{},"核心驱动不是钱（AI说的 我持怀疑态度），是\"认知闭环\"--市场是不会说谎的裁判，钱只是计分板。",[111,4077,4078],{"id":4078},"一个需要警惕的特质",[120,4080,4081],{},"对\"是否正确\"极度敏感的人，容易把坚持系统等同于坚持自我，把止损等同于承认\"我是错的\"。如果哪天开始扛单不是因为信号而是无法接受\"我看错了\"，这个特质就从优势变成风险。",[120,4083,4084],{},"关键区分：把\"验证认知\"和\"验证自我价值\"分开。市场说这笔交易错了，不等于整个判断体系错了。我相信市场大部分时间是对的，应该是我往市场靠去检验自己，而不是市场错的时候坚持自己。但空仓时说这话容易，真正重仓浮亏 5%、系统说止损但脑子里说\"只是短期波动\"的那一刻，这套认知还在不在才是真考验。",[120,4086,4087],{},"止损系统的价值不只是风控，更是强制执行那些理性认同但情绪会动摇的信念。",[111,4089,4091],{"id":4090},"_10-万到几百万数学可行执行淘汰大多数人","10 万到几百万：数学可行，执行淘汰大多数人",[120,4093,4094],{},"市场容量直接排除--A 股日均成交额 8000 亿到 1.2 万亿，几十万到几百万对市场影响约等于零。真实难度分三段：",[124,4096,4097,4103,4109],{},[127,4098,4099,4102],{},[130,4100,4101],{},"10 万到 100 万","：拼策略稳定性和纪律一致性",[127,4104,4105,4108],{},[130,4106,4107],{},"100 万到 500 万","：拼复利需要时间，以及账户变大后心态是否变化（100 万亏 10% 是 10 万，感受和 10 万亏 10% 完全不同）",[127,4110,4111,4114],{},[130,4112,4113],{},"500 万以上","：拼市场风格切换时系统能否不变形",[120,4116,4117],{},"参照现有系统严格执行，年化 15%-30% 的历史区间成立。三种情景的复利推算：",[124,4119,4120,4123,4126],{},[127,4121,4122],{},"**保守 15%**：10 万到 100 万约 17 年，到 500 万约 39 年",[127,4124,4125],{},"**中性 20%**：10 万到 100 万约 13 年，到 500 万约 21 年",[127,4127,4128],{},"**乐观 25%**：10 万到 100 万约 11 年，到 500 万约 15 年",[120,4130,4131],{},"数学上可行，但\"10 年严格执行\"淘汰的人比策略本身多。年化均值背后有巨大的方差，最大风险不是策略本身，而是震荡市连续止损后大多数人会改变规则。",[111,4133,4134],{"id":4134},"人群中能走到哪",[124,4136,4137,4140,4143,4146],{},[127,4138,4139],{},"能长期跑赢通胀：前 20%",[127,4141,4142],{},"年化 15%+ 持续 5 年以上：前 5%",[127,4144,4145],{},"系统化策略 10 年不变形：前 2-3%",[127,4147,4148],{},"10 万做到 500 万：前 1-2%",[120,4150,4151],{},"这个门槛不是天才门槛，而是纪律和时间门槛。输给认知的少，输给自己的多。",[111,4153,4154],{"id":4154},"交易不是生活的全部",[120,4156,4157],{},"正常认真上班拿现金流，有自己的爱好爱好，偶尔玩玩游戏，继续交易探索市场和世界。每个部分各司其职：工作管现金流，运动游戏管切换放松，交易是认知战场。",[120,4159,4160],{},"这个心态本身是优势。很多人把交易当生活全部，盯盘过度、情绪放大、决策变差。有工作提供现金流、有运动游戏切换状态，交易在这个结构里心理压力更小，压力小反而更容易执行系统。",[120,4162,4163],{},"但有一个前提：执行密度。想清楚和做到之间有 gap，关键不是今天想通了，而是明天还在做。",[111,4165,4167],{"id":4166},"一个佩服的-up-主","一个佩服的 UP 主",[120,4169,4170],{},"关注过一个 UP 主，清华毕业三十多岁，提过资产千万级。他的操作和认知确实让人佩服：航运信息差套利没记错一天挣了20w，6月8日暴跌开中证 500 期权多单为国护盘，科技股暴跌后判断主线仍是科技股事后看来也是对的。他还分享打新、股东福利等内容。",[120,4172,4173],{},"他的宏观判断和产业理解思路值得学，具体操作和套利思路也有参考价值。没有实盘记录这点确实无法验证，但判断以及操作确实很牛逼。",[111,4175,4177],{"id":4176},"a-股打新现状","A 股打新现状",[120,4179,4180],{},"查了一下 A 股打新的数据：2024 年新股首日平均涨幅 253%，单签平均收益约 2 万元；2025 年至 6 月，45 只新股无一破发。但主板网上中签率仅 0.03% 左右，参与人数超 1100 万户，普通人中签概率极低，更像是彩票。网下机构打新年化约 4.5%，但门槛是亿级资金账户。包括今年以来的一些大肉签（比如沐曦股份 摩尔线程 最近的长鑫存储）上市当日涨幅都很夸张，随便中几签都是几万块。可惜科创板门槛高啊。（我什么时候才能有50w）",[111,4182,4183],{"id":4183},"止损永远是最重要的",[120,4185,4186],{},"按照均线止损太死板，套到很多个股上买点太高了。但不管用什么方式入场，止损永远是第一位的。买点可以慢慢校准，进场理由可以有很多种，但止损必须进场前定好，而且不能因为浮亏就移动它。止损一旦守不住，什么策略都白搭。在市场里还是先活下来比较重要。",{"title":363,"searchDepth":538,"depth":538,"links":4188},[4189,4190,4191,4192,4193,4194,4195,4196,4197],{"id":4055,"depth":538,"text":4056},{"id":4065,"depth":538,"text":4066},{"id":4078,"depth":538,"text":4078},{"id":4090,"depth":538,"text":4091},{"id":4134,"depth":538,"text":4134},{"id":4154,"depth":538,"text":4154},{"id":4166,"depth":538,"text":4167},{"id":4176,"depth":538,"text":4177},{"id":4183,"depth":538,"text":4183},"交易","从清华博士的建议想要赚钱就去做量化出发，梳理普通人做系统化交易的现实路径、人群比例和自我认知驱动。",{},"\u002Fwriting\u002F2026-07-26-trading-cognition-and-compound-reality",{"title":4047,"description":4199},"trading-cognition-and-compound-reality","writing\u002F2026-07-26-trading-cognition-and-compound-reality",[4198,4206,4207,4208,4209],"量化","认知","复利","系统化交易","ncRskTdQt3kCImby9qKSkM5aUBbcdCb-MjUngbbkfEs",{"id":4212,"title":4213,"body":4214,"category":4198,"date":4030,"description":4390,"extension":562,"hidden":563,"meta":4391,"navigation":31,"path":4392,"publishedAt":4393,"seo":4394,"slug":4395,"stem":4396,"tags":4397,"updated":579,"__hash__":4404},"writing\u002Fwriting\u002F2026-07-26-btc-synthetic-futures-arbitrage.md","BTC期权合成期货套利：用定价偏差锁定无风险利润",{"type":108,"value":4215,"toc":4381},[4216,4219,4223,4226,4229,4233,4239,4247,4250,4253,4256,4262,4268,4271,4275,4278,4281,4285,4292,4298,4301,4304,4318,4323,4331,4337,4342,4353,4358,4368,4371,4375,4378],[120,4217,4218],{},"看到一套量化交易系统看板：年化 197%、极低回撤、多平仓少持仓。核心策略是利用 Deribit 期权市场合成的虚拟期货价格与 Binance 永续合约价格之间的定价偏差进行对冲套利。当时对着看板追问了 AI 几轮，才把这套合成期货套利的逻辑理清楚。这篇文章是给自己留的复盘笔记。",[111,4220,4222],{"id":4221},"deribit-是什么","Deribit 是什么",[120,4224,4225],{},"Deribit 是目前加密货币期权交易量最大的交易所，总部在巴拿马，2016 年上线。BTC 和 ETH 期权的主流流动性都在这里，行权价、到期日覆盖范围广，机构参与度高。它的期权以币本位结算（BTC 期权用 BTC 结算），也支持永续合约和交割期货。",[120,4227,4228],{},"正因为 Deribit 在期权市场的深度优势，它的期权定价成为合成期货策略的基础端。另一端选 Binance 永续合约，是因为 Binance 流动性最好、API 稳定、支持开空，适合做对冲腿。",[111,4230,4232],{"id":4231},"核心概念合成期货","核心概念：合成期货",[120,4234,4235,4236,239],{},"期权平价公式告诉我们：",[130,4237,4238],{},"买入 Call + 卖出 Put = 合成期货多头",[124,4240,4241,4244],{},[127,4242,4243],{},"买入 Call（看涨期权）：涨了赚，跌了不亏",[127,4245,4246],{},"卖出 Put（看跌期权）：涨了没事，跌了亏",[120,4248,4249],{},"两者组合后的盈亏轨迹，与直接持有 BTC 现货或期货完全一致——涨了赚、跌了亏。这就是\"合成期货\"。",[111,4251,4252],{"id":4252},"两种套利方向",[120,4254,4255],{},"关键在于：Deribit 期权合成的期货价格，和 Binance 永续合约的价格，经常不一致。",[120,4257,4258,4261],{},[130,4259,4260],{},"转换套利（Conversion \u002F SF+BS）","：当合成期货价格 > Binance 期货价格时，在 Deribit 卖出合成期货（卖出 Call + 买入 Put），同时在 Binance 买入永续合约。",[120,4263,4264,4267],{},[130,4265,4266],{},"反转套利（Reversal \u002F BF+SS）","：当合成期货价格 \u003C Binance 期货价格时，在 Deribit 买入合成期货（买入 Call + 卖出 Put），同时在 Binance 卖出永续合约。",[120,4269,4270],{},"本质上就是\"哪边便宜哪边买，哪边贵了哪边卖\"。",[111,4272,4274],{"id":4273},"对冲机制为什么涨跌都不怕","对冲机制：为什么涨跌都不怕",[120,4276,4277],{},"币安端永远做与 Deribit 完全相反的动作。Deribit 开合成多头，Binance 必开永续空头。BTC 暴涨暴跌时，两端的盈亏完全抵消，行情风险归零。",[120,4279,4280],{},"利润不来自方向判断，而是开仓瞬间两端的定价差。期权到期结算时，合成价格强制回归现货价，基差收敛完成无风险落袋。",[111,4282,4284],{"id":4283},"一个关键区分行权价-现价","一个关键区分：行权价 ≠ 现价",[120,4286,4287,4288,4291],{},"看板中的合约代码 ",[62,4289,4290],{},"BTC-10JUN26-62000","，62000 是行权价，不是当时的市场现价。当时 Binance 的标记价约为 62,991 美元。因为现价高于行权价，看涨期权呈浮盈状态，看跌期权的权利金已被吃满。",[120,4293,4294,4295,239],{},"比对套利机会时，标的不是行权价本身，而是",[130,4296,4297],{},"合成总成本 = 行权价 + 买Call权利金 - 卖Put权利金",[111,4299,4300],{"id":4300},"完整数值演练",[120,4302,4303],{},"设定场景：",[124,4305,4306,4309,4312],{},[127,4307,4308],{},"Binance 现价：$63,000",[127,4310,4311],{},"Deribit 行权价 $62,000 的期权：Call 权利金 $1,500，Put 权利金 $300",[127,4313,4314,4315],{},"合成空头总成本：$62,000 + $1,500 - $300 = ",[130,4316,4317],{},"$63,200",[120,4319,4320],{},[130,4321,4322],{},"开仓动作：",[124,4324,4325,4328],{},[127,4326,4327],{},"Binance 开多，$63,000",[127,4329,4330],{},"Deribit 合成空头（卖 Call + 买 Put），$63,200",[120,4332,4333,4334],{},"开仓瞬间锁定利润：$63,200 - $63,000 = ",[130,4335,4336],{},"$200",[120,4338,4339],{},[130,4340,4341],{},"极端行情 A - 暴涨至 $80,000：",[124,4343,4344,4347,4350],{},[127,4345,4346],{},"Binance 多头盈利：+$17,000",[127,4348,4349],{},"Deribit 合成空头亏损：-$16,800",[127,4351,4352],{},"合计：**+$200**",[120,4354,4355],{},[130,4356,4357],{},"极端行情 B - 暴跌至 $40,000：",[124,4359,4360,4363,4366],{},[127,4361,4362],{},"Binance 多头亏损：-$23,000",[127,4364,4365],{},"Deribit 合成空头盈利：+$23,200",[127,4367,4352],{},[120,4369,4370],{},"无论涨跌，总利润始终为开仓时锁定的 $200。到期自动结算收敛，整个过程是左手倒右手，利润在开仓那一下就已经确定了。",[111,4372,4374],{"id":4373},"模型不难难的是工程","模型不难，难的是工程",[120,4376,4377],{},"这套套利的交易系统作者说过一句话：套利模型倒是不难，难的是一些工程上的事情。",[120,4379,4380],{},"确实，逻辑上这就是一个低买高卖的价差捕捉，但实际跑起来要处理的问题远比模型复杂：两个交易所的 API 延迟差异、订单簿深度和滑点、手续费摩擦对利润空间的侵蚀、资金在两个平台之间的划转效率、期权到期时的自动结算对齐、极端行情下的风控（硬止损、Gamma 检查、行情降级）、以及资金容量上限——能套的价差就那么多，资金量大了反而吃不掉。这些工程细节才是决定系统能不能真正赚钱的关键。",{"title":363,"searchDepth":538,"depth":538,"links":4382},[4383,4384,4385,4386,4387,4388,4389],{"id":4221,"depth":538,"text":4222},{"id":4231,"depth":538,"text":4232},{"id":4252,"depth":538,"text":4252},{"id":4273,"depth":538,"text":4274},{"id":4283,"depth":538,"text":4284},{"id":4300,"depth":538,"text":4300},{"id":4373,"depth":538,"text":4374},"看到一套量化套利系统后追问AI，拆解Deribit合成期货与Binance永续合约之间的跨平台套利逻辑，含完整数值演练。",{},"\u002Fwriting\u002F2026-07-26-btc-synthetic-futures-arbitrage","2026-07-26T13:37:11+08:00",{"title":4213,"description":4390},"btc-synthetic-futures-arbitrage","writing\u002F2026-07-26-btc-synthetic-futures-arbitrage",[4398,4399,4400,4401,4402,4403],"BTC","期权","套利","合成期货","Deribit","Binance","o_rfqacyzAeRyNmp-ceWG6OvHBlEmjo5vFyZhRVC06A",{"id":4406,"title":4407,"body":4408,"category":559,"date":4030,"description":4573,"extension":562,"hidden":563,"meta":4574,"navigation":31,"path":4575,"publishedAt":4576,"seo":4577,"slug":4578,"stem":4579,"tags":4580,"updated":579,"__hash__":4584},"writing\u002Fwriting\u002F2026-07-26-why-vector-database.md","向量库到底有什么用",{"type":108,"value":4409,"toc":4566},[4410,4414,4417,4428,4431,4445,4449,4452,4466,4469,4473,4476,4479,4499,4506,4509,4512,4515,4533,4536,4539,4563],[111,4411,4413],{"id":4412},"sql-存个相同列-join-一下不就行了","SQL 存个相同列 join 一下不就行了？",[120,4415,4416],{},"这是我最初的问题。看起来很合理：embedding 不就是一串数字吗，存个字段，SQL join 一下就完事了。",[120,4418,4419,4420,4423,4424,4427],{},"但 SQL 擅长的是 ",[62,4421,4422],{},"WHERE A = B"," 这种精确匹配。Embedding 是高维浮点数组，代表语义特征。两句话语义相似，它们的向量数值却绝不相等。",[62,4425,4426],{},"WHERE Va = Vb"," 直接返回空。",[120,4429,4430],{},"所以向量库真正在做的事情有两层：",[278,4432,4433,4439],{},[127,4434,4435,4438],{},[130,4436,4437],{},"数学计算","：用余弦相似度等算法算高维空间的\"距离\"，而不是判等。",[127,4440,4441,4444],{},[130,4442,4443],{},"专属索引（ANN 算法）","：传统 B-Tree 索引对高维数据失效，会退化成全表扫描。向量库用 HNSW 之类的索引在高维空间建\"地图\"，做到毫秒级近似最近邻检索。",[111,4446,4448],{"id":4447},"那-rag-到底是怎么跑的","那 RAG 到底是怎么跑的",[120,4450,4451],{},"搞清楚向量库的作用之后，整个 RAG 链路就顺了：",[278,4453,4454,4457,4460,4463],{},[127,4455,4456],{},"用户提问 -> 经过 Embedding 模型 -> 转成向量",[127,4458,4459],{},"拿向量去向量库里找最近的文档片段",[127,4461,4462],{},"找到的相关资料 + 用户原问题一起拼成 Prompt 发给大模型",[127,4464,4465],{},"大模型结合资料回答，减少幻觉",[120,4467,4468],{},"核心就是：输入给大模型之前，先用向量检索把相关上下文捞回来，拼在一起再喂进去。",[111,4470,4472],{"id":4471},"全量召回还是选几条","全量召回还是选几条？",[120,4474,4475],{},"这是第二个直觉问题：如果数据库里相关的东西很多，比如 50 页文本都沾边，全部塞进大模型？还是挑几条最相关的？",[120,4477,4478],{},"答案是必须精选截断。原因有三个：",[124,4480,4481,4487,4493],{},[127,4482,4483,4486],{},[130,4484,4485],{},"上下文窗口有限","：大模型的 Context Window 有上限，塞不下就是塞不下。",[127,4488,4489,4492],{},[130,4490,4491],{},"中间迷失","：上下文太长时，大模型容易忽略中间的内容。",[127,4494,4495,4498],{},[130,4496,4497],{},"Token 费用","：输入越长越贵。",[120,4500,4501,4502,4505],{},"所以标准做法是设置 ",[62,4503,4504],{},"top_k","（比如 limit=5），只取相似度最高的前 N 个片段。入库之前也先把长文本切成小块（比如每段 500 字），精准匹配局部内容，避免带入无关段落。",[111,4507,4508],{"id":4508},"但我的数据量没那么大",[120,4510,4511],{},"说到这里我反应过来了--我的复盘日志根本没多少数据。几万字而已，全塞进去不就完了？",[120,4513,4514],{},"确实可以。小数据量下\"全上下文注入\"更简单有效：",[124,4516,4517,4523],{},[127,4518,4519,4522],{},[130,4520,4521],{},"逻辑完整","：保留完整的时间线和因果链，不会因为切片断章取义。",[127,4524,4525,4528,4529,4532],{},[130,4526,4527],{},"架构极简","：直接 SQL ",[62,4530,4531],{},"SELECT *","，全部喂给大模型，不需要向量索引和切片逻辑。",[111,4534,4535],{"id":4535},"那向量库还有没有意义",[120,4537,4538],{},"有。即便是小数据量，向量库（或 SQL 的向量插件）仍然有几个不可替代的能力：",[124,4540,4541,4551,4557],{},[127,4542,4543,4546,4547,4550],{},[130,4544,4545],{},"模糊语义匹配","：日志里写的是\"肝到两点\"或\"披星戴月\"，向量检索能匹配到\"加班\"的语义。传统 SQL ",[62,4548,4549],{},"LIKE"," 搜不到这种。",[127,4552,4553,4556],{},[130,4554,4555],{},"扩展性","：日志会越积越多，一两年后可能就塞不进上下文窗口了。向量检索的成本随数据量亚线性增长，全量注入则是线性上升。",[127,4558,4559,4562],{},[130,4560,4561],{},"聚类与挖掘","：基于向量距离可以做无标签的主题归类和情绪分析，这是全量注入给大模型做不到的。",[120,4564,4565],{},"所以比较务实的方案是：短周期（比如近一周）的分析直接 SQL 全量提取，喂给大模型；跨年度的特定问题搜索走向量匹配。两条路各管各的，不冲突。",{"title":363,"searchDepth":538,"depth":538,"links":4567},[4568,4569,4570,4571,4572],{"id":4412,"depth":538,"text":4413},{"id":4447,"depth":538,"text":4448},{"id":4471,"depth":538,"text":4472},{"id":4508,"depth":538,"text":4508},{"id":4535,"depth":538,"text":4535},"从\"SQL 加个列不就行了\"到理解向量检索和 RAG 的完整链路，以及小数据量场景下到底该怎么选。",{},"\u002Fwriting\u002F2026-07-26-why-vector-database","2026-07-26T00:09:14+08:00",{"title":4407,"description":4573},"why-vector-database","writing\u002F2026-07-26-why-vector-database",[4581,4582,4583],"向量数据库","Embedding","RAG","hdqIEfJHF7KE9cYD971ShCFoCR9FbJVBIvdlCmdrbf4",1785763813109]