hypomnema 1.6.1 → 1.6.2

package/.claude-plugin/marketplace.json

@@ -11,7 +11,7 @@
       "name": "hypo",
       "source": "./",
       "description": "LLM-native personal wiki — session-aware knowledge base for Claude Code",
-      "version": "1.6.1",
+      "version": "1.6.2",
       "homepage": "https://github.com/sk-lim19f/Hypomnema"
     }
   ]

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "hypo",
-  "version": "1.6.1",
+  "version": "1.6.2",
   "description": "LLM-native personal wiki system — session-aware knowledge base for Claude Code",
   "author": {
     "name": "sk-lim19f",

package/README.ko.md

@@ -25,7 +25,7 @@ Andrej Karpathy의 "LLM 네이티브 위키" 스케치에서 출발했습니다.
 
 ### 지금 어디까지 자동인가
 
-현재 릴리스는 v1.6.1입니다. 조건부나 유예된 세션 마무리에서 미커밋이나 진행 중인 작업이 남아 문구가 모호할 때 조기 nag 대신 지금 닫을지 되묻고, `working_dir` provenance를 강화해 앵커가 없던 프로젝트도 `cwd`-first resume이 앵커하도록 고쳤습니다. 그 앞 v1.6.0은 역방향 확장 capture를 완성했습니다. `hypomnema capture`(그리고 `/hypo:capture` 슬래시 커맨드)가 `~/.claude/` 아래에 보통 방식으로 만든 command·agent·hook을 위키로 끌어와, forward-sync가 다른 머신에 원래 이름 그대로 전파합니다. 손으로 만든 확장의 "한 머신에서 등록, 다른 머신에서 동기화" 갭을 데몬 없이 메웁니다. 그 앞 v1.5.1은 위키가 자기 신선도를 알리는 방식을 다듬었습니다. `verify_by_date`가 지난 페이지는 주입되는 순간 `[STALE ...]`로 표시되고, lookup 사용을 로컬에서 추적해 링크됐지만 한 번도 주입되지 않은 페이지를 crystallize가 cold 후보로 표면화하며, 표준 `session | project: title` 콜론 로그 포맷을 stale로 오진하던 세션 마무리도 견고해졌습니다. 다시 그 앞 v1.5.0은 머신 간 안정성에 집중했습니다. git 동기화 볼트의 `cwd`-first resume와 코드 레포 세션에 위키 위치를 안내하는 것이었습니다.
+현재 릴리스는 v1.6.2입니다. 세션종료 재확인이 백그라운드 셸 작업이나 예약된 wake도 진행 중 작업으로 보게 해, 백그라운드 명령을 기다리며 유예된 close("퍼블리시 하고 세션 마무리")가 매 턴 마커를 조르지 않습니다. 그 앞 v1.6.1은 조건부나 유예된 세션 마무리에서 미커밋이나 진행 중인 작업이 남아 문구가 모호할 때 조기 nag 대신 지금 닫을지 되묻고, `working_dir` provenance를 강화해 앵커가 없던 프로젝트도 `cwd`-first resume이 앵커하도록 고쳤습니다. 그 앞 v1.6.0은 역방향 확장 capture를 완성했습니다. `hypomnema capture`(그리고 `/hypo:capture` 슬래시 커맨드)가 `~/.claude/` 아래에 보통 방식으로 만든 command·agent·hook을 위키로 끌어와, forward-sync가 다른 머신에 원래 이름 그대로 전파합니다. 손으로 만든 확장의 "한 머신에서 등록, 다른 머신에서 동기화" 갭을 데몬 없이 메웁니다. 그 앞 v1.5.1은 위키가 자기 신선도를 알리는 방식을 다듬었습니다. `verify_by_date`가 지난 페이지는 주입되는 순간 `[STALE ...]`로 표시되고, lookup 사용을 로컬에서 추적해 링크됐지만 한 번도 주입되지 않은 페이지를 crystallize가 cold 후보로 표면화하며, 표준 `session | project: title` 콜론 로그 포맷을 stale로 오진하던 세션 마무리도 견고해졌습니다. 다시 그 앞 v1.5.0은 머신 간 안정성에 집중했습니다. git 동기화 볼트의 `cwd`-first resume와 코드 레포 세션에 위키 위치를 안내하는 것이었습니다.
 
 위키 작업(자료 정리·검색·세션 마무리)은 아직 `/hypo:*` 명령이나 자연어로 시작합니다. v2의 목표는 Claude가 시키지 않아도 위키를 읽고 쓰고 합성하는 완전 자율 동작이고, 지금 그쪽으로 가는 중입니다.
 

package/README.md

@@ -25,7 +25,7 @@ New to the terms below? Keep the [Term decoder](#term-decoder) open in another t
 
 ### Where automation stands today
 
-The current release is v1.6.1. It fixes session close so a conditional or deferred wrap-up ("once X is done, wrap up") that still has uncommitted or in-flight work asks you whether to close now instead of nagging prematurely, and it hardens `working_dir` provenance so `cwd`-first resume can anchor a project that was missing its anchor. The v1.6.0 release before it completed reverse extension capture: `hypomnema capture` (and the `/hypo:capture` slash command) pulls a command, agent, or hook you created the normal way under `~/.claude/` into the wiki, so forward-sync propagates it to your other machines under its original name. That closes the "register on one machine, sync on another" gap for extensions you author by hand, without a daemon. The v1.5.1 release before it sharpened how the wiki signals its own freshness: a page whose `verify_by_date` has passed is flagged `[STALE ...]` the moment it is injected, lookup usage is tracked locally so crystallize can surface a linked-but-never-injected page as a cold candidate, and session close was made robust to the standard `session | project: title` colon log format that had been misread as stale. The v1.5.0 line before that turned to cross-machine reliability: `cwd`-first resume on a git-synced vault and a code-repo session told where the wiki lives.
+The current release is v1.6.2. It teaches session-close reconfirm to treat a background shell task or a scheduled wake as work still in flight, so a deferred close ("publish, then wrap up") waiting on a background command no longer nags for the marker on every turn. The v1.6.1 release before it fixes session close so a conditional or deferred wrap-up ("once X is done, wrap up") that still has uncommitted or in-flight work asks you whether to close now instead of nagging prematurely, and it hardens `working_dir` provenance so `cwd`-first resume can anchor a project that was missing its anchor. The v1.6.0 release before it completed reverse extension capture: `hypomnema capture` (and the `/hypo:capture` slash command) pulls a command, agent, or hook you created the normal way under `~/.claude/` into the wiki, so forward-sync propagates it to your other machines under its original name. That closes the "register on one machine, sync on another" gap for extensions you author by hand, without a daemon. The v1.5.1 release before it sharpened how the wiki signals its own freshness: a page whose `verify_by_date` has passed is flagged `[STALE ...]` the moment it is injected, lookup usage is tracked locally so crystallize can surface a linked-but-never-injected page as a cold candidate, and session close was made robust to the standard `session | project: title` colon log format that had been misread as stale. The v1.5.0 line before that turned to cross-machine reliability: `cwd`-first resume on a git-synced vault and a code-repo session told where the wiki lives.
 
 Wiki work (ingest, query, session-close) still starts from an explicit `/hypo:*` command or plain language. The v2 goal is full autonomy: Claude reading, writing, and synthesizing the wiki without being asked, which is the direction this is heading.
 

package/hooks/hypo-auto-minimal-crystallize.mjs

@@ -36,8 +36,9 @@
  * gate above was found to be unable to distinguish "close now" from "close
  * once X is done" by regex alone — same sentence shape either way). When the
  * close-intent gate above fires AND the session has a work-incomplete signal
- * (an uncommitted wiki, or an in-flight delegated subagent per
- * hasInFlightSubagent), step 6's block reason is replaced with an
+ * (an uncommitted wiki, or pending background work — a non-terminal
+ * background task or a scheduled cron wake — per hasPendingBackgroundWork),
+ * step 6's block reason is replaced with an
  * AskUserQuestion instruction instead of a crystallize command — the model
  * asks the user "close now?" rather than deciding for them. A correlated
  * "아직"/"나중"/"not yet"/"later" answer (isCloseReconfirmDeclined) suppresses
@@ -65,7 +66,7 @@ import {
   isClosePattern,
   isGateSkipped,
   precompactGateStatus,
-  hasInFlightSubagent,
+  hasPendingBackgroundWork,
   isCloseReconfirmDeclined,
   CLOSE_RECONFIRM_MARK,
 } from './hypo-shared.mjs';
@@ -95,8 +96,8 @@ function emitBlock(sessionId, transcriptPath, gate = null, opts = {}) {
       JSON.stringify({
         decision: 'block',
         reason:
-          `[WIKI_AUTOCLOSE] close 신호가 잡혔지만 아직 커밋되지 않은 변경(또는 진행 중인 ` +
-          `위임 작업)이 있어 지금 닫을지 뒤로 미룰지 모호합니다 (session_id=${sessionId}). ` +
+          `[WIKI_AUTOCLOSE] close 신호가 잡혔지만 아직 커밋되지 않은 변경 또는 진행 중인 ` +
+          `백그라운드·위임 작업이 있어 지금 닫을지 뒤로 미룰지 모호합니다 (session_id=${sessionId}). ` +
           `임의로 닫지 말고 AskUserQuestion으로 사용자에게 지금 세션을 닫을지 물어보세요. ` +
           `선택지는 "${CLOSE_RECONFIRM_MARK}"와 "아직, 계속"으로 제시합니다. 사용자가 ` +
           `"${CLOSE_RECONFIRM_MARK}"를 고른 뒤에만 세션 마무리를 진행하세요. 그전에는 ` +
@@ -250,14 +251,16 @@ process.stdin.on('end', () => {
     // "work-incomplete" together are exactly the case where the transcript's
     // NL close phrase can't tell "close now" from "close once X is done" —
     // regex can't disambiguate this (see spec background). Narrowed to the
-    // two work-incomplete signals only: an uncommitted wiki (`git` blocker;
-    // real unsaved work) OR an in-flight delegated subagent. `hot` / `lint` /
-    // `close` / `design-history` / `feedback` blockers are real close
-    // blockers but not evidence of "later" intent, so they keep the existing
-    // wording (unchanged from before this feature).
+    // work-incomplete signals only: an uncommitted wiki (`git` blocker; real
+    // unsaved work) OR pending background work — a non-terminal background task
+    // (delegated subagent OR shell, e.g. a deferred push/CI wait) or a
+    // scheduled cron wake (hasPendingBackgroundWork). `hot` / `lint` / `close`
+    // / `design-history` / `feedback` blockers are real close blockers but not
+    // evidence of "later" intent, so they keep the existing wording (unchanged
+    // from before this feature).
     const workIncomplete =
       (gate && gate.blockers && gate.blockers.some((b) => b.type === 'git')) ||
-      hasInFlightSubagent(payload);
+      hasPendingBackgroundWork(payload);
     if (workIncomplete && isCloseReconfirmDeclined(transcriptPath)) {
       // The user already answered "아직" to the ambiguous close signal that
       // triggered this Stop turn — suppressing is a continue, not a

package/hooks/hypo-shared.mjs

@@ -2758,29 +2758,50 @@ export function hasUserCloseSignal(transcriptPath) {
 }
 
 /**
- * True iff the Stop payload's `background_tasks` names an in-flight (not yet
- * terminal) delegated subagent. Read-only: used to widen the autoclose
- * reconfirm trigger (see hypo-auto-minimal-crystallize.mjs) to "work is
- * demonstrably still running", not just "the wiki has uncommitted changes".
+ * True iff the Stop payload shows work still pending in the background —
+ * either a non-terminal `background_tasks` entry OR a scheduled `session_crons`
+ * wake. Read-only: used to widen the autoclose reconfirm trigger (see
+ * hypo-auto-minimal-crystallize.mjs) to "work is demonstrably still running",
+ * not just "the wiki has uncommitted changes".
+ *
+ * ANY non-terminal `background_tasks` entry counts, not just delegated
+ * subagents. A Stop payload captured from a real session confirmed the field
+ * is genuinely sent (the older "grep turns up nothing / may not be sent" note
+ * is retired): a background Bash appears as
+ * `{id, type:'shell', status:'running', description, command}`, alongside
+ * `type:'subagent'` for delegations. Restricting to `type==='subagent'` missed
+ * shell background work (e.g. a `git push` / CI wait deferred behind a close
+ * signal), letting the reconfirm branch mis-classify the session as idle and
+ * re-nag every Stop turn.
  *
  * Defined as the NEGATION of a terminal status, not an enumeration of
- * "running" states — this repo has no `background_tasks` type definition
- * (grep turns up nothing), so the real status vocabulary is unverified. An
- * unrecognized/absent status is treated as in-flight; only a recognized
- * terminal status clears it.
+ * "running" states: the observed non-terminal status is "running", and a
+ * finished task is removed from the array entirely (it does NOT linger in a
+ * terminal state — the next Stop simply reports `background_tasks:[]`). An
+ * unrecognized/absent status is therefore treated as in-flight; only a
+ * recognized terminal status clears an entry that is still present.
+ *
+ * `session_crons`: a non-empty array means the session is waiting on a
+ * scheduled wake, which is itself pending work. A missing / non-array
+ * `session_crons` is ignored (fail-open).
  *
- * Fail-open: a missing or non-array `background_tasks` is treated as "no
- * in-flight subagent" (the field may simply not be sent by this Stop event),
- * so in-flight detection degrades gracefully to the git-uncommitted signal
- * alone rather than spuriously blocking.
+ * Fail-open overall: a missing or non-array `background_tasks` contributes no
+ * pending signal, so detection degrades gracefully to the git-uncommitted
+ * signal alone rather than spuriously blocking.
  */
-export function hasInFlightSubagent(payload) {
-  const tasks = payload && payload.background_tasks;
-  if (!Array.isArray(tasks)) return false;
+export function hasPendingBackgroundWork(payload) {
+  if (!payload || typeof payload !== 'object') return false;
   const TERMINAL = /^(completed|complete|done|finished|failed|error|errored|cancelled|canceled)$/i;
-  return tasks.some(
-    (t) => t && t.type === 'subagent' && (t.status == null || !TERMINAL.test(String(t.status))),
-  );
+  const tasks = payload.background_tasks;
+  if (
+    Array.isArray(tasks) &&
+    tasks.some((t) => t && (t.status == null || !TERMINAL.test(String(t.status))))
+  ) {
+    return true;
+  }
+  const crons = payload.session_crons;
+  if (Array.isArray(crons) && crons.length > 0) return true;
+  return false;
 }
 
 // The reconfirm reason (hypo-auto-minimal-crystallize.mjs emitBlock's

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "hypomnema",
-  "version": "1.6.1",
+  "version": "1.6.2",
   "description": "LLM-native personal wiki system for Claude Code",
   "type": "module",
   "license": "MIT",

package/templates/hypo-config.md

@@ -1,7 +1,7 @@
 ---
 title: Hypomnema Config
 type: config
-version: "1.6.1"
+version: "1.6.2"
 created: YYYY-MM-DD
 ---