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