chore: Runner 穩定性 + 封存目錄結構
Runner 穩定性: - 新增 setup-runner-watchdog.sh (5分鐘 Watchdog) - 新增 setup-runner-2.sh (第二個 Runner 安裝) 封存策略: - 建立 _archived/ 目錄結構 - 新增 ARCHIVE_LOG.md 封存紀錄模板 統帥裁示: 不要只是臨時解決,要徹底解決! Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
41
apps/api/src/services/_archived/ARCHIVE_LOG.md
Normal file
41
apps/api/src/services/_archived/ARCHIVE_LOG.md
Normal file
@@ -0,0 +1,41 @@
|
||||
# Archive Log
|
||||
|
||||
> Phase 16 封存紀錄 - 專業團隊不輕易刪除,改採封存策略
|
||||
|
||||
## 封存規則
|
||||
|
||||
1. 新代碼穩定運行 **48 小時** 後,才能封存舊代碼
|
||||
2. 封存檔案加上 `_v1` 後綴
|
||||
3. **90 天後** 無問題才真正刪除
|
||||
4. 所有封存必須記錄在此檔案
|
||||
|
||||
---
|
||||
|
||||
## 待封存清單 (Phase 16 R2)
|
||||
|
||||
| 檔案 | 行數 | 替代方案 | 預計封存日期 |
|
||||
|------|------|----------|--------------|
|
||||
| incident_memory.py | ~483 | lewooogo_brain.adapters.incident_memory | 48hr 驗證後 |
|
||||
| incident_engine.py | ~657 | lewooogo_brain.engines.incident_engine | 48hr 驗證後 |
|
||||
|
||||
---
|
||||
|
||||
## 已封存
|
||||
|
||||
目前無封存檔案。
|
||||
|
||||
<!--
|
||||
## 範例格式
|
||||
|
||||
### incident_memory_v1.py
|
||||
|
||||
| 欄位 | 值 |
|
||||
|------|-----|
|
||||
| 封存日期 | 2026-XX-XX |
|
||||
| 封存原因 | Phase 16 絞殺者模式,改用 lewooogo-brain |
|
||||
| 原始位置 | apps/api/src/services/incident_memory.py |
|
||||
| 替代方案 | lewooogo_brain.adapters.incident_memory |
|
||||
| 回復指令 | `git checkout a202a26 -- apps/api/src/services/incident_memory.py` |
|
||||
| 48hr 驗證通過 | 2026-XX-XX |
|
||||
| 最終刪除日期 | 2026-XX-XX (封存後 90 天) |
|
||||
-->
|
||||
Reference in New Issue
Block a user