Commit Graph

60 Commits

Author SHA1 Message Date
ship 7609f1a31b ship 1.4.59:Arcrun@f87260b1234f 2026-08-27 21:26:55 +08:00
ship f54c9d8df2 ship 1.4.59:Arcrun@f87260b1234f 2026-08-27 19:50:15 +08:00
ship 472407621d ship 1.4.58:Arcrun@ad60863a8017 2026-08-27 15:10:47 +08:00
ship b273692476 ship 1.4.57:Arcrun@9a9891a0dde7 2026-08-27 14:01:09 +08:00
ship 9dee6dcf5b ship 1.4.57:Arcrun@9a9891a0dde7 2026-08-27 12:49:58 +08:00
ship 45cf0865f0 ship 1.4.56:Arcrun@6521914df572 2026-08-26 20:51:57 +08:00
ship e523d3ba22 ship 1.4.55:Arcrun@d60cd1258f43 2026-08-26 17:13:14 +08:00
ship 3337980891 ship 1.4.54:Arcrun@d3019a52cb18 2026-08-26 08:00:50 +08:00
ship 389c6cdd8b ship 1.4.53:Arcrun@db33cbe907dd 2026-08-24 20:15:59 +08:00
ship 4f2830fb3f ship 1.4.52:Arcrun@f69d96ce8968 2026-08-24 19:07:32 +08:00
ship a925e2d7dd ship 1.4.51:Arcrun@86fc731f375d 2026-08-24 18:23:34 +08:00
ship 4324bba8b7 ship 1.4.49:Arcrun@1246d92ce791 2026-08-20 11:23:23 +08:00
ship 86508c4b79 ship 1.4.49:Arcrun@1246d92ce791 2026-08-18 17:55:08 +08:00
ship 9690223fc6 ship 1.4.48:Arcrun@466a59c5616f 2026-08-18 15:44:26 +08:00
ship e2ac12baa7 ship 1.4.48:Arcrun@466a59c5616f 2026-08-18 15:34:09 +08:00
ship 1aa8230509 ship 1.4.46:Arcrun@cacaa33f7d4e 2026-08-17 00:01:19 +08:00
ship 567e510b47 ship 1.4.46:Arcrun@cacaa33f7d4e 2026-08-16 23:51:56 +08:00
ship 957371f72c ship 1.4.46:Arcrun@cacaa33f7d4e 2026-08-16 16:15:14 +08:00
ship b85572cd73 ship 1.4.46:Arcrun@cacaa33f7d4e 2026-08-16 00:03:09 +08:00
ship 29a25315f8 ship 1.4.47:Arcrun@45169ab25e97 2026-08-15 01:09:45 +08:00
ship 64563a51fb ship 1.4.46:Arcrun@340b461f58ed 2026-08-15 00:09:52 +08:00
ship dcfd202bd9 ship 1.4.45:Arcrun@94d545242589 2026-08-14 13:36:53 +08:00
ship 9b106bf31c ship 1.4.44:Arcrun@1ccee0055ebd 2026-08-13 18:52:48 +08:00
ship df600d7246 ship 1.4.44:Arcrun@1ccee0055ebd 2026-08-13 18:30:46 +08:00
ship fed72ebeab ship 1.4.43:Arcrun@2fcae722e7d7 2026-08-13 00:28:42 +08:00
ship 94923e9ef1 ship 1.4.42:Arcrun@21293568d550 2026-08-12 22:26:44 +08:00
ship 643f8746d5 ship 1.4.41:Arcrun@89b80ff90e95 2026-08-12 20:24:44 +08:00
ship f2bb71112b ship 1.4.40:Arcrun@1791ffa4972b 2026-08-12 15:34:20 +08:00
ship 8c3fa0e116 ship 1.4.38:Arcrun@3eb8b31f2bfa 2026-08-12 10:44:11 +08:00
ship 026930dab6 ship 1.4.37:Arcrun@d8bbf2241bd6 2026-08-11 20:08:59 +08:00
ship 7b19b37924 ship 1.4.37:Arcrun@d8bbf2241bd6 2026-08-11 13:56:45 +08:00
ship 839a67c035 ship 1.4.36:Arcrun@788295e 2026-08-11 13:26:20 +08:00
ship 0e0186ed02 ship 1.4.36:Arcrun@797e7f7 2026-08-11 13:02:04 +08:00
ship d979f446dd ship 1.4.35:Arcrun@d1c44a5 2026-08-11 12:15:00 +08:00
ship aaa98a55bb ship 1.4.33:Arcrun@eebb691 2026-08-10 23:17:42 +08:00
ship c698ad4e41 ship 1.4.32:Arcrun@eebb691 2026-08-10 14:25:55 +00:00
ship 595a7c607e ship 1.4.30:Arcrun@c4cee35 2026-08-10 14:26:39 +08:00
ship b0a2f84eb4 ship 1.4.29:Arcrun@19c82df 2026-08-09 18:48:12 +08:00
ship 652f261183 ship 1.4.28:Arcrun@19c82df 2026-08-09 15:16:55 +08:00
ship 6878f7afbf ship 1.4.26:Arcrun@ebd4bf5 2026-08-09 13:43:14 +08:00
ship ab4ef01709 ship 1.4.24:Arcrun@466e56b 2026-08-08 23:17:07 +08:00
ship e0b3592ae6 ship 1.4.24:Arcrun@07cc7f5 2026-08-08 21:52:19 +08:00
Leo fc3c3cad06 1.4.24:CORS 自動放行同實例 portal(不再依賴 UI_ORIGINS)+診斷端點+portal 導流文案 2026-08-08 21:15:15 +08:00
Leo 31a6ccf455 staging daemon v0.18.24:dmg+exe 上架,manifest.daemon 同步 2026-08-08 17:16:22 +08:00
Leo 51f84bf4c3 staging 1.4.22: t213 診斷檔雲端半(新端點 GET /portal/daemon/diagnostics)+ portal 按鈕文案改導流
source Arcrun@8447165(93b1140 新端點 + 8447165 portal 文案)
InkStoneCo 總管交辦,走 stage-first 出貨鏈驗收
2026-08-08 13:31:02 +08:00
Leo e91e379530 manifest.source 修正:5388f40 → c7a0b31(同型病當天第二次)
build-bundles 全量重建時仍沿用舊 manifest 的 source。
早上已修過一次(0d49989→5388f40),下午又犯 => 這是腳本的缺陷不是人的疏忽,
該讓 source 由產物推導。已列為待修。
2026-08-07 23:04:33 +08:00
Leo 93c20e938e 1.4.20:今天全部修復一次到位(KV 額度/credential 自癒/檢修孔/靜默回空)
來源 Arcrun@c7a0b31(gitea/main),九筆 commit:
  60688c3 執行紀錄搬離 KV(Evan 事故止血)
  7ba7855 credential 目錄改走 KBDB API
  9344562 embed 自我檢查端點
  83aa1f6 /portal/data/diagnostics 檢修孔聚合端點
  5388f40 設定頁「匯出診斷檔給我們看」按鈕
  ac4fb56 portal 前端文案講人話
  046ceba credential 目錄自癒搬遷(修 youlin 20/20 全敗)
  c7a0b31 補 entries.ts 缺的自癒 hook

出貨前八項複驗(grep 產物,不假設):
  ANALYTICS_KV.put 殘留 0/execution_log 2
  credential 自癒 3/empty_reason 5
  diagnostics 端點 1/檢修孔按鈕 1
  天書詞只在 admin_hint 與 OFF_HINT(用戶欄位 capability_hint 四種全人話)
  manifest release=1.4.20 core=24 顆

真機驗證(youlin 實例):
  第一輪 20 次 17 成功/3 失敗(自癒暖機)
  第二輪 20 次 20 成功/0 失敗
  兩輪共 40 次後 stats: key 663 → 663,增加 0

⚠️ 打包踩到的坑:用 git worktree 打會 0/4 bundled(沒有 .component-builds
的預編 wasm,那是 gitignore 產物)=> 必須用主工作區,且先還原部署注入的 KV id。
2026-08-07 23:03:29 +08:00
Leo 4ba73815bf staging 1.4.18:檢修孔按鈕進 UI bundle(Oscar 按得到了)
build-ui-bundle.mjs 把 console-ui/public 重打進 tier2/ui/index.js。
複驗(grep 產物,不假設):
  「匯出診斷檔給我們看」 1 處
  createObjectURL        1 處(按一下下載一個 JSON 檔)
  /portal/data/diagnostics 3 處
  owner_id 外露          0 處

背景:build-bundles.mjs 只打 4 顆核心(cypher/kbdb/http_request/code),
UI 屬「沿用非本腳本產的 20 顆」不重打 => 只跑 build-bundles 的話
檢修孔前端永遠送不出去。這支要另外跑。
2026-08-07 18:55:36 +08:00
Leo 8eedce55fe manifest.source 修正:0d49989 → 5388f40(宣告要由產物推導)
抓到的缺陷:build-bundles 全量重建時沒有更新 manifest.source,
沿用了 staging repo 裡 07-31 那次留下的舊值
=> 產物實際來自 5388f40,卻宣告成 0d49989。

這是 CP 08-06「版本號手寫=說謊的溫床,凡宣告版本一律由產物推導」
同型病的第二次——上次是版本號,這次是來源 commit。
後果:追「這個產物是哪個 commit 打的」會被誤導。
2026-08-07 18:48:09 +08:00
Leo ea9690692a staging 1.4.17:執行紀錄不再吃 KV 額度(Evan 事故止血)
來源 matrix/arcrun main(60688c3 KV 搬離 + 7ba7855 credential 走 API)。
打包後 grep 複驗(不假設):
  ANALYTICS_KV.put 殘留 = 0   ← 舊行為清乾淨
  execution_log       = 2 處   ← 新行為在 bundle 裡

版本處理:staging manifest 原本沒有 release 欄位,每次重打都從 1.4.0 起算
=> 版本會倒退、安裝器判成不用更新。先對齊 prod 的 1.4.16 再重打 => bump 成 1.4.17。
(這是 stage/prod 又一個漂移,已記入 wiki。)

僅 staging,不影響 prod。
2026-08-07 18:46:14 +08:00