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