@adamchanadam/agent-handoff-kit 0.3.15 → 0.3.16
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +2 -2
- package/docs/whatsnew/v0.3.16.md +25 -0
- package/package.json +1 -1
- package/runtime-core/AGENTS.core.md +2 -2
package/README.md
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
# Agent Handoff Kit
|
|
2
2
|
|
|
3
|
-
狀態:目前版本為 `v0.3.
|
|
3
|
+
狀態:目前版本為 `v0.3.16`。這是早期可用版本,仍在持續完善中。
|
|
4
4
|
|
|
5
5
|

|
|
6
6
|
|
|
@@ -261,7 +261,7 @@ Agent Handoff Kit 可與 [Adam-AI-Instructions](https://github.com/prompt-templa
|
|
|
261
261
|
|
|
262
262
|
## 目前限制
|
|
263
263
|
|
|
264
|
-
- 目前版本為 `v0.3.
|
|
264
|
+
- 目前版本為 `v0.3.16`。
|
|
265
265
|
- 這是早期可用版本,仍在持續完善中。
|
|
266
266
|
- 升級合併屬窄範圍策略,不是完整的複雜合併工具。
|
|
267
267
|
- `doctor` 能檢查結構,不能代替 AI 對專案內容的理解。
|
|
@@ -0,0 +1,25 @@
|
|
|
1
|
+
# v0.3.16
|
|
2
|
+
|
|
3
|
+
## 本版新加了甚麼
|
|
4
|
+
|
|
5
|
+
本版修正收工交接流程中一個容易漏過的同步坑:AI 可能只在對話表面顯示下一次開工提示,卻沒有先把同一份內容寫回 `START_NEXT_SESSION_PROMPT.txt`。
|
|
6
|
+
|
|
7
|
+
現在核心收工規則改為先從 `dev/SESSION_HANDOFF.md` 的權威 opening message 重生 `START_NEXT_SESSION_PROMPT.txt`,再讀回這份便利副本,最後才把讀回內容貼給使用者。這樣 handoff、便利副本、final response 不會變成三份各自手寫的提示。
|
|
8
|
+
|
|
9
|
+
本版同時把這條收工次序加入發佈前驗收與舊核心升級驗收。若未來 runtime core 退回「先表面輸出、後重生 prompt」的舊次序,`qa:release` 或 `qa:upgrade` 會在 publish 前擋下。
|
|
10
|
+
|
|
11
|
+
## 對你已有檔案的影響
|
|
12
|
+
|
|
13
|
+
既有項目不用重裝。升級後,`AGENTS.md` 的 closeout contract 會帶入新的 read-back discipline;本地既有規則仍會保留。
|
|
14
|
+
|
|
15
|
+
`START_NEXT_SESSION_PROMPT.txt` 仍只是下次開工方便複製的副本,權威內容仍在 `dev/SESSION_HANDOFF.md`。session 進行中若便利副本落後,普通 `doctor` 仍只會提醒;真正要求一致的是 full closeout 完成前。
|
|
16
|
+
|
|
17
|
+
## 建議下一步
|
|
18
|
+
|
|
19
|
+
已安裝舊版的項目可先預演:
|
|
20
|
+
|
|
21
|
+
```bash
|
|
22
|
+
npx --yes @adamchanadam/agent-handoff-kit@latest upgrade --dry-run
|
|
23
|
+
```
|
|
24
|
+
|
|
25
|
+
如果預演沒有 conflict,再執行正式升級。之後請在每次完成工作時直接叫 AI「收工」,讓它更新 handoff、重生 `START_NEXT_SESSION_PROMPT.txt`,並把同一份讀回內容交給你下次開工使用。
|
package/package.json
CHANGED
|
@@ -91,8 +91,8 @@ At full closeout:
|
|
|
91
91
|
6. Complete the `State Reconciliation Check`: it must state when reconciliation happened, which state sections were rewritten or confirmed current, whether stale snapshots remain, whether completed / pending / risk / opening-message lifecycle conflicts were resolved, and whether the opening message matches current state. In the same step, run the handoff lifecycle consistency check before declaring handoff ready: compare `Completed This Session`, `Validation / QC`, `Next Priorities`, `Risks / Blockers`, and `Next Session Opening Message`. A completed or verified item must not remain as an unresolved next priority, active risk, or startup instruction unless it is explicitly reclassified as monitor-only, follow-up scope, blocked, or reopened with the missing evidence or trigger condition stated.
|
|
92
92
|
7. Run the handoff sufficiency check: the next AI should be able to continue from `AGENTS.md`, `dev/SESSION_HANDOFF.md`, `dev/PROJECT_INDEX.md`, and needed rule packs without searching old log history.
|
|
93
93
|
8. If either check fails, fix `dev/SESSION_HANDOFF.md` first; do not push current-state responsibility into `dev/SESSION_LOG.md`.
|
|
94
|
-
9.
|
|
95
|
-
10.
|
|
94
|
+
9. Regenerate `START_NEXT_SESSION_PROMPT.txt` from the fenced opening message in `dev/SESSION_HANDOFF.md`, then read it back or run the project's prompt mirror check before declaring closeout ready. `dev/SESSION_HANDOFF.md` is authoritative; `START_NEXT_SESSION_PROMPT.txt` is only a convenience copy for the user to paste at the next startup. During an active session, do not regenerate it just to silence `doctor`; normal `doctor` may warn about drift, but closeout must make the copy match before handoff is declared ready.
|
|
95
|
+
10. Show a short closeout card, then provide the copy-paste-ready next-session opening message by pasting the read-back `START_NEXT_SESSION_PROMPT.txt` content inside a fenced `text` code block. Do not compose a separate final-response prompt; the final response is a display of the persisted prompt, not a third source of truth.
|
|
96
96
|
11. Advance the SESSION_LOG N-rule (R-010 SESSION_LOG handoff-role discipline). After prepending the new closeout entry, count `## YYYY-MM-DD` H2 entries in `dev/SESSION_LOG.md`. Any entry now at position N ≥ 11 (oldest end) must be moved into `dev/SESSION_LOG_archive/archive_<batch>_<low_date>_to_<high_date>.md` with raw content preserved. Maintain `dev/SESSION_LOG_archive/INDEX.md` (master index of all archive batches; create on first archive). Entries at N=4–10 whose core facts are already absorbed into HANDOFF / PROJECT_INDEX / requirements / decision records collapse to a short-index line using structural anchors, not line numbers. Entries with unique narrative not yet absorbed must first be ported into the relevant durable source, then collapsed. This is mandatory; do not skip. Handoff capability rests on `dev/SESSION_HANDOFF.md`; `dev/SESSION_LOG.md` is trace-back / audit trail and does not carry handoff responsibility.
|
|
97
97
|
|
|
98
98
|
12. Maintain `dev/PROJECT_DECISIONS.md` per R-028 project narrative discipline. Each closeout must run the following checks with equal mechanical rigor as the SESSION_LOG N-rule (step 11):
|