hypomnema 1.3.1 → 1.3.3

package/scripts/resume.mjs

@@ -18,7 +18,11 @@
  *                              ~/Documents/{hypomnema,wiki,notes}) that contains
  *                              a hypo-config.md marker.
  *                           3. else the default ~/hypomnema.
- *   --project=<name>      Project name (default: most recently active from hot.md)
+ *   --project=<name>      Project name. When omitted, resolveActiveProject()
+ *                         prefers the project whose working_dir contains the
+ *                         current directory (cwd-first), and only falls back to
+ *                         the most recently active hot.md row when nothing under
+ *                         cwd matches.
  *   --json                Output as JSON
  */
 
@@ -58,7 +62,8 @@ function parseFrontmatterField(content, key) {
 
 // Among `slugs`, return the one whose projects/<slug>/index.md `working_dir`
 // is the LONGEST prefix of cwd (so /repo/sub wins over /repo). Returns null
-// when cwd is falsy or matches none. Used only as a same-date tie-breaker.
+// when cwd is falsy or matches none. resume gives this authority OVER recency
+// (ADR 0044): a cwd↔working_dir match wins regardless of which row is newest.
 function pickByCwd(hypoDir, slugs, cwd) {
   if (!cwd) return null;
   let best = null;
@@ -78,6 +83,33 @@ function pickByCwd(hypoDir, slugs, cwd) {
   return best;
 }
 
+// When cwd is set but no project's working_dir matches it, resume falls back to
+// recency silently — the user lands in an unrelated project with no clue why.
+// Emit a one-line stderr diagnostic (stdout `Project:`/`--json` contract is untouched)
+// naming why each candidate failed: missing index.md, missing working_dir, or a
+// working_dir that simply doesn't contain cwd. Logic mirrors pickByCwd's lookup.
+function warnCwdFallback(hypoDir, slugs, cwd) {
+  // No cwd, or no candidate rows at all (fresh-init / no real project): there is
+  // nothing to "fall back to most-recent" toward, so stay silent — the caller
+  // surfaces the real "no active project found" error instead.
+  if (!cwd || slugs.length === 0) return;
+  const reasons = [];
+  for (const slug of slugs) {
+    const indexPath = join(hypoDir, 'projects', slug, 'index.md');
+    if (!existsSync(indexPath)) {
+      reasons.push(`${slug} (no index.md)`);
+      continue;
+    }
+    const wd = parseFrontmatterField(readFileSync(indexPath, 'utf-8'), 'working_dir');
+    if (!wd) reasons.push(`${slug} (no working_dir)`);
+    // else: has working_dir but didn't contain cwd — expected, not flagged.
+  }
+  const detail = reasons.length ? ` Candidates missing cwd metadata: ${reasons.join(', ')}.` : '';
+  process.stderr.write(
+    `note: cwd "${cwd}" matched no project working_dir; falling back to most-recent.${detail}\n`,
+  );
+}
+
 function resolveActiveProject(hypoDir, cwd = null) {
   const hotPath = join(hypoDir, 'hot.md');
   if (!existsSync(hotPath)) return null;
@@ -93,38 +125,62 @@ function resolveActiveProject(hypoDir, cwd = null) {
     ),
   ].map((m) => ({ name: m[1].trim(), date: m[2] || '', slug: m[3] }));
   if (wikiRows.length > 0) {
-    wikiRows.sort((a, b) => b.date.localeCompare(a.date));
-    // Same-date tie-break (ISSUE-1): when the top date is shared by >1 row,
-    // prefer the project whose working_dir contains cwd. No cwd / no match →
-    // keep the stable-sort winner (the legacy "first table row" behavior).
-    const topDate = wikiRows[0].date;
-    const tied = wikiRows.filter((r) => r.date === topDate);
-    if (cwd && tied.length > 1) {
+    // cwd-first (ADR 0044): a cwd↔working_dir match wins over recency, across
+    // ALL rows (not just a same-date tie). The user is physically in that
+    // project, so cwd is a stronger intent signal than "some other project was
+    // touched more recently". This reverses the earlier tie-breaker-only
+    // semantics now that resume=cwd-positive (ADR 0043). Tradeoff: a stale cwd
+    // match can mask a genuinely newer project; `--project` overrides. close
+    // callers pass null → recency path below (resume=cwd-positive / close=no-pick).
+    if (cwd) {
       const picked = pickByCwd(
         hypoDir,
-        tied.map((r) => r.slug),
+        wikiRows.map((r) => r.slug),
         cwd,
       );
       if (picked) return picked;
     }
+    // No cwd match → most recent by date (stable-sort keeps the first table row
+    // on a tie, the legacy behavior).
+    if (cwd)
+      warnCwdFallback(
+        hypoDir,
+        wikiRows.map((r) => r.slug),
+        cwd,
+      );
+    wikiRows.sort((a, b) => b.date.localeCompare(a.date));
     return wikiRows[0].slug;
   }
   // Legacy markdown-link rows: | [name](projects/name/...) | ...
-  const mdRow = content.match(/\|\s*\[([^\]]+)\]\(projects\/([^/)]+)/);
-  if (mdRow) return mdRow[2];
+  const mdSlugs = [...content.matchAll(/\|\s*\[([^\]]+)\]\(projects\/([^/)]+)/g)].map((m) => m[2]);
+  if (mdSlugs.length > 0) {
+    if (cwd) {
+      const picked = pickByCwd(hypoDir, mdSlugs, cwd);
+      if (picked) return picked;
+      warnCwdFallback(hypoDir, mdSlugs, cwd);
+    }
+    return mdSlugs[0]; // legacy: first table row
+  }
 
-  // fallback: most recently modified project with a session-state.md
+  // fallback: a cwd-matched project, else the most recently modified one with a
+  // session-state.md. (mtime is only a heuristic once hot.md can't name a
+  // project — an explicit working_dir match is safer, so cwd-first here too.)
   const projectsDir = join(hypoDir, 'projects');
   if (!existsSync(projectsDir)) return null;
 
+  // Skip the scaffold project init.mjs writes — it isn't a real active project.
+  const candidates = readdirSync(projectsDir).filter(
+    (p) => p !== '_template' && existsSync(join(projectsDir, p, 'session-state.md')),
+  );
+  if (cwd) {
+    const picked = pickByCwd(hypoDir, candidates, cwd);
+    if (picked) return picked;
+    warnCwdFallback(hypoDir, candidates, cwd);
+  }
   let latest = null;
   let latestMtime = 0;
-  for (const p of readdirSync(projectsDir)) {
-    // Skip the scaffold project init.mjs writes — it isn't a real active project.
-    if (p === '_template') continue;
-    const ssPath = join(projectsDir, p, 'session-state.md');
-    if (!existsSync(ssPath)) continue;
-    const mtime = statSync(ssPath).mtimeMs;
+  for (const p of candidates) {
+    const mtime = statSync(join(projectsDir, p, 'session-state.md')).mtimeMs;
     if (mtime > latestMtime) {
       latestMtime = mtime;
       latest = p;

package/scripts/uninstall.mjs

@@ -15,7 +15,7 @@
  *   --force-extensions   Remove user-modified extension files (hypo-ext-*) instead of preserving them
  *   --hooks-dir=<path>   Override Claude hooks directory (default: ~/.claude/hooks)
  *
- * Extensions (ADR 0024 fix #34): hypo-ext-* hard-copies under
+ * Extensions (ADR 0024): hypo-ext-* hard-copies under
  * ~/.claude/{hooks,commands,skills,agents}/ and ~/.codex/{hooks,commands}/ (with
  * --codex) are removed when their on-disk SHA matches the recorded one in
  * ~/.claude/hypo-pkg.json#extensions.<target>. User-modified copies are preserved

package/scripts/upgrade.mjs

@@ -16,12 +16,12 @@
  *   --force-extensions  Overwrite user-modified / conflicting extension copies (creates .bak)
  *   --codex             Mirror to ~/.codex/{hooks,commands,settings.json} — core
  *                       hook drift/apply, settings.json registration, the
- *                       wiki-*.mjs → hypo-*.mjs rename migration (fix #48), and
- *                       the user-extensions companion sync (E4 / fix #32).
+ *                       wiki-*.mjs → hypo-*.mjs rename migration, and
+ *                       the user-extensions companion sync (E4).
  *   --json              Output results as JSON
  *   --allow-downgrade   Override the guard that refuses to overwrite a NEWER
  *                       active install with an older package (ADR 0038)
- *   --allow-dual-install  Override the ISSUE-8 guard: register the Claude core
+ *   --allow-dual-install  Override the dual-install guard: register the Claude core
  *                       surface even though the Hypomnema plugin is also enabled
  *                       (knowingly accept the double-registration risk)
  */
@@ -412,7 +412,7 @@ function applyHookNameMigration(oldRefs, settingsPath, hooksDir) {
   if (applied.length > 0) {
     writeFileSync(settingsPath, JSON.stringify(settings, null, 2) + '\n');
     // Copy renamed hook files to the target hooks dir (~/.claude/hooks or
-    // ~/.codex/hooks per the caller — fix #48 mirror).
+    // ~/.codex/hooks per the caller — codex mirror).
     for (const [oldName, newName] of Object.entries(HOOK_RENAMES)) {
       const oldPath = join(hooksDir, oldName);
       const newPath = join(hooksDir, newName);
@@ -761,7 +761,7 @@ function applyCommands(commandResults, force) {
   return applied;
 }
 
-// ISSUE-6: in plugin mode `applyCommands` is skipped (no command copy), but the
+// In plugin mode `applyCommands` is skipped (no command copy), but the
 // runtime still needs hypo-pkg.json to resolve PKG_ROOT for lint/feedback scripts
 // (hooks/hypo-shared.mjs → hypo-personal-check). Write minimal metadata pointing
 // at the plugin's package root, preserving any existing fields (e.g. `extensions`)
@@ -797,7 +797,7 @@ const claudeSettingsPath = join(HOME, '.claude', 'settings.json');
 const codexHooksDir = join(HOME, '.codex', 'hooks');
 const codexSettingsPath = join(HOME, '.codex', 'settings.json');
 
-// ISSUE-6: when `/hypo:upgrade` runs as the Claude Code PLUGIN, the 15 core hooks
+// When `/hypo:upgrade` runs as the Claude Code PLUGIN, the 15 core hooks
 // and 14 slash commands are provided by the plugin's hooks.json + commands/
 // (auto-wired by Claude Code), NOT copied into ~/.claude/. The manual/npm health
 // check below would then report all of them "missing" and recommend `--apply`,
@@ -806,20 +806,21 @@ const codexSettingsPath = join(HOME, '.codex', 'settings.json');
 // every hook fires TWICE. The decisive signal: the plugin command runs the
 // PLUGIN's upgrade.mjs, so PKG_ROOT lives under ~/.claude/plugins/. (A manual/npm
 // upgrade.mjs run while the plugin is ALSO enabled is a different failure mode —
-// dual install — tracked as ISSUE-8.)
+// dual install — handled by the guard below.)
 // Match the Claude plugin cache shape specifically (`~/.claude/plugins/…`), NOT a
 // generic `/plugins/` substring — this flag now GATES install behavior, so a
 // legitimate npm/dev checkout under some unrelated `…/plugins/…` path must not be
 // misclassified and silently stop managing its hooks. (detectChannel's broad
 // `/plugins/` test is fine for the notifier's display-only use, but too loose here.)
 const pluginMode = PKG_ROOT.replace(/\\/g, '/').includes('/.claude/plugins/');
-// ISSUE-8 (dual install): the OTHER way the same double-registration can happen.
+// Dual install: the OTHER way the same double-registration can happen.
 // Here the MANUAL/npm upgrade.mjs is running (pluginMode=false), but the Hypomnema
 // plugin is ALSO enabled in ~/.claude/settings.json — so the plugin loader already
 // provides the core hooks/commands/settings. A manual/npm `--apply` would copy and
 // register them on top, and every core hook fires twice. The detector is fail-open
 // (see lib/plugin-detect.mjs): a false positive would wrongly alter a legitimate
-// npm-only user's upgrade, so it only fires on an exact `hypomnema@<mp>: true`.
+// npm-only user's upgrade, so it only fires on an exact `hypo@<mp>: true` (or the
+// legacy `hypomnema@<mp>: true`, matched across the plugin-rename migration window).
 const hypomnemaPluginEnabled = !pluginMode && isHypomnemaPluginEnabled(claudeSettingsPath);
 const dualInstallCoreConflict = hypomnemaPluginEnabled;
 // Surface policy: the Claude core surface (hooks/settings/commands/hook-name
@@ -864,7 +865,7 @@ const extCheck = syncExtensions({
   force: args.forceExtensions,
 });
 
-// E4 (fix #32): --codex mirrors the extensions sync into ~/.codex (hooks + commands
+// E4: --codex mirrors the extensions sync into ~/.codex (hooks + commands
 // only; skills/agents skipped with a notice). The per-target SHA map lives in the
 // same ~/.claude/hypo-pkg.json under extensions.codex, so pkgPath is unchanged.
 const extCodexSettingsPath = codexSettingsPath;
@@ -897,7 +898,7 @@ const invalidSettingsCodex = settingsCodex
   ? settingsCodex.some((s) => s.status === 'invalid-json')
   : false;
 const schemaDrift = schema.bump !== 'none' && schema.bump !== 'unknown' && schema.bump !== 'ahead';
-// ISSUE-8 dual-install: when core is skipped, hypo-pkg.json is deliberately left
+// Dual-install: when core is skipped, hypo-pkg.json is deliberately left
 // pointing at the PLUGIN's package root (preserved identity), so checkPkgJson()
 // reports it 'stale' relative to this npm/manual PKG_ROOT. That mismatch is
 // INTENTIONAL — `--apply` will not (and must not) rewrite it — so it must not
@@ -958,7 +959,7 @@ if (args.apply) {
     migrationPath = writeMigrationReport(args.hypoDir, schema.installed, schema.current, {
       // Use the core-skipped predicate, not raw pluginMode: in a dual-install skip
       // the core surface is plugin-owned too, so the report must not claim the
-      // core hooks/settings were applied (ISSUE-8, W2 review note).
+      // core hooks/settings were applied.
       pluginMode: !managesClaudeCore,
     });
   }
@@ -976,7 +977,7 @@ if (args.apply) {
     appliedCommands = applyCommands(commands, args.forceCommands);
     appliedPkgJson = true;
   } else if (pluginMode) {
-    // ISSUE-6 plugin mode: the plugin loader owns the core hooks/commands and
+    // Plugin mode: the plugin loader owns the core hooks/commands and
     // settings.json wiring — copying them here would double-register. Skip those,
     // but STILL write minimal package metadata so the runtime can resolve PKG_ROOT
     // for lint/feedback scripts (hooks/hypo-shared.mjs → hypo-personal-check). The
@@ -984,7 +985,7 @@ if (args.apply) {
     // is the plugin's own path here, so this metadata is authoritative.
     appliedPkgJson = writePluginModeMetadata();
   } else {
-    // ISSUE-8 dual-install skip: a manual/npm run while the plugin is enabled. We
+    // Dual-install skip: a manual/npm run while the plugin is enabled. We
     // skip the core surface (the plugin owns it), but — unlike true plugin mode —
     // PKG_ROOT here is the npm/manual path while the ACTIVE runtime hooks are the
     // PLUGIN's. Rewriting a VALID hypo-pkg.json.pkgRoot to this npm path would
@@ -1029,7 +1030,7 @@ if (args.apply) {
     apply: true,
     force: args.forceExtensions,
   });
-  // E4 (fix #32): codex apply runs AFTER the claude apply so it reads the freshly
+  // E4: codex apply runs AFTER the claude apply so it reads the freshly
   // written hypo-pkg.json and merges extensions.codex alongside extensions.claude
   // (the per-target spread in syncExtensions preserves the other target's map).
   if (args.codex) {
@@ -1089,7 +1090,7 @@ if (args.json) {
     JSON.stringify(
       {
         pluginMode,
-        // ISSUE-8 dual-install signals.
+        // Dual-install signals.
         hypomnemaPluginEnabled,
         dualInstallCoreConflict,
         coreManagedBy: managesClaudeCore ? 'self' : pluginMode ? 'plugin' : 'plugin-enabled',
@@ -1138,7 +1139,7 @@ if (args.json) {
 // Human-readable report
 const lines = [];
 
-// ISSUE-6: lead with the plugin-mode banner so the user understands why the core
+// Lead with the plugin-mode banner so the user understands why the core
 // hook/command/settings sections read "managed by plugin" and that `--apply` will
 // NOT touch them (only vault-side migrations + package metadata).
 if (pluginMode) {
@@ -1155,7 +1156,7 @@ if (pluginMode) {
   );
 }
 
-// ISSUE-8: a manual/npm upgrade.mjs is running while the Hypomnema plugin is ALSO
+// Dual install: a manual/npm upgrade.mjs is running while the Hypomnema plugin is ALSO
 // enabled — a dual install. Lead with a loud banner: the core surface is owned by
 // the plugin and is intentionally skipped, so `--apply` will not double-register.
 if (dualSkip) {
@@ -1202,7 +1203,7 @@ if (schema.bump === 'none') {
   );
 }
 
-// Hook files (target-aware so --codex can mirror the same block; fix #48).
+// Hook files (target-aware so --codex can mirror the same block).
 function pushHookSummary(hookList, label, targetPath) {
   const colHook = `Hook files${label}`.padEnd(20);
   const up = hookList.filter((h) => h.status === 'up-to-date').length;
@@ -1235,7 +1236,7 @@ if (managesClaudeCore) {
 }
 if (hooksCodex) pushHookSummary(hooksCodex, ' (codex)', '~/.codex/hooks/');
 
-// settings.json registrations (target-aware mirror; fix #48).
+// settings.json registrations (target-aware mirror).
 function pushSettingsSummary(sList, label, invalidFlag) {
   const colS = `settings.json${label}`.padEnd(20);
   const reg = sList.filter((s) => s.status === 'registered').length;
@@ -1262,7 +1263,7 @@ if (settingsCodex) pushSettingsSummary(settingsCodex, ' (codex)', invalidSetting
 
 // Package metadata
 if (dualSkip && pkgJson.status === 'stale') {
-  // ISSUE-8: the 'stale' here is the preserved plugin identity (pkgRoot points at
+  // Dual-install: the 'stale' here is the preserved plugin identity (pkgRoot points at
   // the plugin, not this npm/manual copy). That is intentional — not actionable.
   lines.push(
     `✓ Package metadata  hypo-pkg.json plugin-owned (preserved — not rewritten in a dual install)`,
@@ -1386,7 +1387,7 @@ function pushExtSummary(check, label) {
     for (const c of check.conflicts) lines.push(`    ✗ ${c.file}  [${c.action} — left untouched]`);
     for (const d of check.drifts) lines.push(`    ⚠ ${d.file}  [drift — left untouched]`);
   }
-  // E3 (fix #31): a hard conflict blocks install (exit 1, even under --apply); drift is
+  // E3: a hard conflict blocks install (exit 1, even under --apply); drift is
   // resolvable advisory. Emit the spec'd WIKI messages so the user knows the recovery.
   if (nConflicts > 0) {
     lines.push('  [WIKI: existing file conflicts. Backup and retry, or use --force-extensions]');
@@ -1502,11 +1503,11 @@ const totalDrift =
   extCheck.actions.filter(
     (a) => a.action === 'create' || a.action === 'update' || a.action === 'force-update',
   ).length +
-  // E3 (fix #31): unresolved drift/conflict is pending work too — without these the
+  // E3: unresolved drift/conflict is pending work too — without these the
   // summary printed "up to date" while the exit code was 1.
   extCheck.conflicts.length +
   extCheck.drifts.length +
-  // E4 (fix #32): codex-target pending work counts identically (same message/exit
+  // E4: codex-target pending work counts identically (same message/exit
   // consistency the E3 review caught — a codex conflict must not read "up to date").
   (extCheckCodex
     ? extCheckCodex.actions.filter(
@@ -1547,7 +1548,7 @@ if (totalDrift === 0) {
 
 console.log(lines.join('\n'));
 
-// E3 (fix #31): a hard extension conflict blocks even under --apply (unlike ordinary
+// E3: a hard extension conflict blocks even under --apply (unlike ordinary
 // drift, which only fails check mode). --force-extensions clears the resolvable
 // cases; an unfollowable symlink/non-regular dest still counts and stays exit 1.
 const extBlocked = extCheck.conflicts.length > 0 || (extCheckCodex?.conflicts.length ?? 0) > 0;

package/skills/crystallize/SKILL.md

@@ -1,5 +1,5 @@
 ---
-description: Close a session (steps 1~6) and, on request, consolidate scattered wiki knowledge into stable pages (steps 7~11)
+description: Close a session by capturing what happened into the wiki (steps 1-6), and on request consolidate scattered notes into stable pages (steps 7-11). Use when the user explicitly signals session end, asks to save or crystallize the session, or before a /compact. Task completion alone is not a close signal.
 ---
 
 You are running `/hypo:crystallize`. The command serves two modes (spec §5.2.7 / §8.3):
@@ -7,11 +7,11 @@ You are running `/hypo:crystallize`. The command serves two modes (spec §5.2.7
 1. **Session close (steps 1~6)** — gate the 5 mandatory memory files plus open-questions (conditional) so `/compact` can pass.
 2. **Synthesis (steps 7~11)** — surface tag clusters, orphan pages, and drafts that are ready to consolidate.
 
-When invoked at the end of a session (or with phrases like "세션 종료", "wrap up"), run the session-close checklist first. The synthesis scan only runs after close is confirmed and the user agrees.
+When invoked to close a session — via an explicit close signal ("세션 종료", "wrap up"), an accepted proactive-offer [세션 마무리], or `/compact` — run the session-close checklist first. Task completion alone does not put you in close mode. The synthesis scan only runs after close is confirmed and the user agrees.
 
 ## What this does
 
-- **Close mode**: walks the checklist (session-state, project hot.md, root hot.md, session-log, open-questions(변경 시), log.md) plus a lint step, then writes via `crystallize.mjs --apply-session-close --payload=<path>` — which runs the lint gate automatically, **scoped to the files it writes** (debt elsewhere is a non-blocking notice). `--check-session-close` remains a read-only probe (freshness only). The PreCompact gate runs the same scoped lint, judging the session on the files it touched.
+- **Close mode**: walks the checklist (session-state, project hot.md, root hot.md, session-log, open-questions(변경 시), log.md) plus a lint step, then writes via `crystallize.mjs --apply-session-close --payload=<path>` — which runs the lint gate automatically, **scoped to the files it writes** (debt elsewhere is a non-blocking notice). `--check-session-close` is a read-only dry-run of the **full** PreCompact gate (ADR 0046) — close files + scoped lint + design-history + feedback projection — sharing one function (`precompactGateStatus`) with the gate. A green check means no gate blocker needs a human fix, so it is the signal to declare the session closed (pass `--transcript-path` to widen the lint scope to this session's edited files exactly as the interactive hook does). It is not a hard guarantee: the live `/compact` can still differ on a context-≥70% prompt, `HYPO_SKIP_GATE`, or a transcript-scoped lint error the check did not see.
 - **Synthesis mode**: finds tag clusters (≥ N pages), orphan pages (no outbound `[[wikilinks]]`), and draft / stub pages, then guides consolidation into `pages/syntheses/<topic>.md` with back-links and `index.md` updates.
 
 ---
@@ -50,8 +50,8 @@ If `/hypo:crystallize` was invoked as a session-close action, run through this c
 Surface each of these four to the user first. Every one is **advisory** (ADR 0029 identity guard): the user confirms or declines, and none performs an automatic action, writes a file on its own, or bypasses the mandatory gate.
 
 - **Trivial-session check (#44)** — Was this session trivial (a single bug fix, a single-file edit, or Q&A with no durable artifact)? If so, recommend skipping session-close: *"이 세션은 trivial해 보입니다 — session-close를 건너뛸까요?"* A trivial skip is a recommendation, **not** a bypass: it must not mark the session closed, must not run `--mark-session-closed`, and must not claim `/compact` can pass. Any real close still requires all 5 mandatory files.
-- **ADR-candidate check (#41)** — Did this session make an architectural or design decision (a new pattern, a tradeoff, a convention)? If yes, ask whether it warrants an ADR and capture that intent in the session-log entry. If nothing rose to ADR level, record `ADR 없음 — <one-line reason>` in that same session-log entry. **Never auto-write an ADR file** — the session-log note is the only action here.
-- **design-history staleness check (#42)** — If `projects/<name>/design-history.md` exists and this session changed design decisions it does not yet reflect, recommend updating it (W8 lint flags this mechanically; an active-project W8 can also block at PreCompact). If the file does not exist, skip silently — do **not** create it just for this check. Never auto-update it.
+- **ADR-candidate check (#41)** — Did this session make an architectural or design decision (a new pattern, a tradeoff, a convention)? If yes, ask whether it warrants an ADR and capture that intent in the session-log entry. If nothing rose to ADR level, you may record the literal marker `ADR 없음 — <one-line reason>` in that same session-log entry — but gate it on #42's bar, not this one: the marker is machine-read and W8 treats a session-log entry carrying `ADR 없음` (and no ADR reference) as a *no-design* session, excluding it from the design-history staleness check. So write `ADR 없음` only when the session had no design change at all. If it had a sub-ADR design shift (background / tradeoff / differentiation), append to design-history (#42a) instead — writing the marker there would suppress the W8 nudge that shift needs. **Never auto-write an ADR file** — the session-log note is the only action here.
+- **design-history staleness check (#42)** — Two branches, so a stale W8 never blocks a clean close: (a) if this session changed design decisions that `projects/<name>/design-history.md` does not yet reflect — including background / tradeoff / differentiation shifts that are below ADR level but still belong in the ledger — recommend appending to it now (W8 flags this mechanically; an active-project W8 hard-blocks at PreCompact — append before you commit, not after the gate fires). (b) only if this session made **no** design change at all does the `ADR 없음` marker from #41 exempt the entry from W8 — do **not** touch design-history. Caution: `ADR 없음` means "no design change," which is a stricter bar than "no ADR-level decision." A session with a sub-ADR design shift should take branch (a) and append; writing `ADR 없음` there would suppress the W8 nudge it actually needs. If the file does not exist, skip silently — do **not** create it just for this check. Never auto-update it.
 - **Ingest check (#43)** — Did this session consume trustworthy external knowledge (a fetched URL, official docs, or code you verified directly)? If so, recommend running `/hypo:ingest` to capture it under `sources/`. Proceed only on the user's confirmation.
 
 When uncertain, surface the question rather than skip it. None of the four blocks the close or writes on its own.
@@ -59,7 +59,7 @@ When uncertain, surface the question rather than skip it. None of the four block
 1. **session-state.md** — update `projects/<name>/session-state.md` with the next tasks list (what to tackle first next time).
 2. **hot.md (project)** — update `projects/<name>/hot.md` with a session snapshot: what changed and decisions made. Keep under 500 words. Do not put next-step tasks here; those belong in session-state.md.
 3. **hot.md (root)** — update `<wiki-root>/hot.md` active-projects pointer table: set the `Last Session` date for this project to today.
-4. **session-log** — append a session entry to `projects/<name>/session-log/YYYY-MM.md` (create the file if it does not exist for this month).
+4. **session-log** — append a session entry to `projects/<name>/session-log/YYYY-MM-DD.md` (daily shard; the apply path creates today's file with seeded frontmatter if it does not exist yet).
 5. **open-questions** — only if `pages/open-questions.md` exists and questions were raised or resolved this session: move resolved ones out; add newly raised ones. Skip if unchanged.
 6. **log.md** — append a `session` entry to `<wiki-root>/log.md`.
 
@@ -69,9 +69,12 @@ After completing the checklist, verify it before reporting:
 node <package-root>/scripts/crystallize.mjs --check-session-close [--hypo-dir="<path>"]
 ```
 
-This runs the same strict check as the PreCompact hard gate (fix #17). Fix any
-file reported `missing` or `stale` and re-run until it passes — otherwise
-`/compact` will be blocked.
+This runs the **full** PreCompact gate via the shared `precompactGateStatus`
+(ADR 0046): close files (`missing` / `stale`) plus lint blockers, stale
+design-history, and feedback projection over-cap/conflict. Fix every `✗` it
+reports and re-run until it prints **"Compact-ready"** — that is the signal the
+session is closed. A close-files-only pass is not enough; the real `/compact`
+also blocks on those other checks.
 
 Once it passes, report each item with ✓ and ask: "Session closed. Would you like to also run knowledge synthesis now, or stop here?"
 

package/skills/graph/SKILL.md

@@ -1,5 +1,5 @@
 ---
-description: Generate a wikilink dependency graph from wiki pages
+description: Generate a wikilink dependency graph from wiki pages (json, mermaid, or dot). Use when the user asks to visualize wiki structure, find orphan or hub pages, or map how notes link together.
 ---
 
 You are running `/hypo:graph`. Build a wikilink dependency graph from all pages under `pages/` and `projects/` and output it in the requested format.

package/skills/ingest/SKILL.md

@@ -1,5 +1,5 @@
 ---
-description: Add a source document to the wiki and synthesize a source-summary page
+description: Add an external source (URL, doc, article, command output) to the wiki and synthesize a citable summary page. Use when the user shares a source to capture, asks to ingest something, or wants reliable external knowledge saved for reuse.
 ---
 
 You are running `/hypo:ingest`. Add a new source document to `sources/` and create (or update) its corresponding `source-summary` page under `pages/`.

package/skills/lint/SKILL.md

@@ -1,5 +1,5 @@
 ---
-description: Lint wiki pages for frontmatter and broken wikilinks
+description: Lint wiki pages for frontmatter errors and broken wikilinks. Use when the user asks to check or validate the wiki health, before a commit, or after bulk edits or renames.
 ---
 
 You are running `/hypo:lint`. Validate all wiki pages for frontmatter correctness and broken `[[wikilink]]` references.

package/skills/query/SKILL.md

@@ -1,5 +1,5 @@
 ---
-description: Search wiki pages by keyword and retrieve relevant knowledge
+description: Search the wiki by keyword and synthesize an answer from the relevant pages. Use when the user asks what the wiki knows about a topic, wants to recall a past decision, or needs prior context before starting work.
 ---
 
 You are running `/hypo:query`. Full-text search across all wiki pages and projects, then synthesize an answer from the matching pages.

package/skills/verify/SKILL.md

@@ -1,5 +1,5 @@
 ---
-description: Check wiki pages for stale or unverified knowledge and prompt review
+description: Surface wiki knowledge that is stale or past its verify-by date and prompt review. Use when the user asks what needs re-checking, wants to audit knowledge freshness, or is reviewing the wiki for rot.
 ---
 
 You are running `/hypo:verify`. Check all wiki pages for `verify_by` and `verify_by_date` fields, surface overdue pages, and guide a review pass.

package/templates/SCHEMA.md

@@ -30,7 +30,7 @@ Read this before any wiki operation (ingest / query / lint).
 | `weekly-journal` | `journal/weekly/YYYY-Www.md` | Weekly session/ingest summary | append-only |
 | `prd` | `projects/*/prd.md` | Project purpose, success criteria, constraints | mutable |
 | `adr` | `projects/*/decisions/NNNN-*.md` | Architecture decision records | immutable |
-| `session-log` | `projects/*/session-log/YYYY-MM.md` | Chronological session narrative (monthly) | append-only |
+| `session-log` | `projects/*/session-log/YYYY-MM-DD.md` | Chronological session narrative (daily shard) | append-only |
 | `session-state` | `projects/*/session-state.md` | Next-session handoff — overwritten each close | overwrite |
 | `project-index` | `projects/*/index.md` | Project overview + progress checklist | mutable |
 | `open-questions` | `pages/open-questions.md` | Unresolved question queue | append+resolve |
@@ -54,7 +54,7 @@ Files responsible for session continuity — separate from the type taxonomy abo
 | `hot.md` (root) | Active project pointer table + last session date | Pointers only. No session content. |
 | `projects/<name>/hot.md` | Last session snapshot — "what was done" | 500-word cap. No next-tasks. Overwrite each close. |
 | `projects/<name>/session-state.md` | Next-session handoff — "what to do next" | Overwrite each close. Read at session start. |
-| `projects/<name>/session-log/YYYY-MM.md` | Append-only narrative timeline (monthly) | No edits to existing entries. |
+| `projects/<name>/session-log/YYYY-MM-DD.md` | Append-only narrative timeline (daily shard; legacy `YYYY-MM.md` still read) | No edits to existing entries. |
 | `pages/open-questions.md` | Cross-project unresolved question queue | Append + mark resolved. |
 
 **Operations**:

package/templates/hypo-config.md

@@ -1,7 +1,7 @@
 ---
 title: Hypomnema Config
 type: config
-version: "1.3.1"
+version: "1.3.3"
 created: YYYY-MM-DD
 ---
 
@@ -36,6 +36,6 @@ HYPO_SKIP_GATE=1
 │   └── <name>/
 │       ├── index.md    ← project overview (working_dir: field)
 │       ├── hot.md      ← project-scoped session snapshot
-│       └── session-log/    ← monthly logs (YYYY-MM.md)
+│       └── session-log/    ← daily shards (YYYY-MM-DD.md)
 └── sources/            ← raw ingested sources (read-only)
 ```

package/templates/hypo-guide.md

@@ -74,16 +74,37 @@ Trigger: explicit close mention, `/compact` request, or context limit approachin
 
 Do **not** treat these as completion: plan approvals, clarification answers, permission grants, progress updates, partial findings, or mid-task checkpoints. A "좋아요" / "감사합니다" / "ok" following any of those is *not* a close signal — only offer after a genuine final completion/verification report.
 
+**Proactive offer means offer, not close.** In this path (task done, no close signal) do not run the close checklist, write the `session-closed` marker, or declare the session ended on your own. Fire `AskUserQuestion` and proceed only after the user picks [세션 마무리]. Task completion is not a close trigger; closing without asking violates this procedure. This scopes the proactive path only: a real close signal, `/compact`, or context limit still closes via the triggers above.
+
 Ask: *"이 작업이 마무리되었나요? 세션을 정리(crystallize)할까요?"* with options **[세션 마무리 / 계속 작업]**. On **세션 마무리** → run the session close checklist (or invoke `/hypo:crystallize`). On **계속 작업** → continue and do not re-ask until the next task completes. Ask at most once per completed task; never loop. (Decline simply ends the turn — Layer 3's Stop-chain only blocks on an explicit close signal, so no repeated prompts occur.)
 
 1. Update `projects/<name>/session-state.md` (next tasks, overwrite)
 2. Update `projects/<name>/hot.md` (what was done, ≤500 words, overwrite)
-3. Append to `projects/<name>/session-log/YYYY-MM.md` (narrative entry, append-only)
+3. Append to `projects/<name>/session-log/YYYY-MM-DD.md` (daily shard, narrative entry, append-only)
 4. Update root `hot.md` pointer table + date
 5. Run `scripts/lint.mjs` and fix errors in files **you** touched — debt in other
    projects / shared pages you did not author is reported as a non-blocking
    notice, not a gate. (The documented `crystallize.mjs --apply-session-close`
    path runs this lint automatically, scoped to the files it writes.)
+6. Verify with `scripts/crystallize.mjs --check-session-close`: a dry-run of the
+   **full** PreCompact gate (close files + lint + design-history + feedback
+   projection, ADR 0046), sharing one function with the gate. Only declare the
+   session closed once it prints **"Compact-ready"**. A "close files updated"
+   check alone is not enough — the real `/compact` gate also blocks on a lint
+   error in a close file or a feedback projection over-cap. (Not a hard
+   guarantee: the live gate can still differ on a context-≥70% prompt,
+   `HYPO_SKIP_GATE`, or a transcript-scoped lint error — pass `--transcript-path`
+   to include the last.) Pass `--session-id=<id>` to also see `marker_present`
+   (step 7).
+7. Record the session-closed marker (ADR 0047). The Stop hook blocks until this
+   session's per-session marker exists, and a hand-edit close (writing the files
+   directly + committing) never writes it; the marker is written only by the
+   crystallize writer, never by the hook (ADR 0022 bypass guard). Normal path:
+   close via `crystallize.mjs --apply-session-close --session-id=<id> --transcript-path=<path>`,
+   which writes the marker once the gate is green. Hand-edit recovery: after
+   committing the files, run `crystallize.mjs --mark-session-closed --session-id=<id> --transcript-path=<path>`.
+   Both writers gate the marker on the SAME `precompactGateStatus` as `/compact`,
+   so the marker only lands when step 6 would print **"Compact-ready"**.
 
 Skip session close for: single bug fix, single-file edit, Q&A only.
 

package/templates/hypo-help.md

@@ -42,6 +42,7 @@ Quick reference for all `/hypo:*` commands.
 | `/hypo:verify` | Review overdue verify_by deadlines |
 | `/hypo:lint` | Validate frontmatter and `[[wikilinks]]` |
 | `/hypo:graph` | Generate link graph (json / mermaid / dot) |
+| `/hypo:rename` | Rename a page or directory, rewriting inbound `[[wikilinks]]` |
 
 ---
 

package/templates/projects/_template/index.md

@@ -28,7 +28,7 @@ tags: [project]
 | `prd.md` | Purpose and success criteria |
 | `hot.md` | Session snapshot and background |
 | `session-state.md` | Next-session handoff |
-| `session-log/` | Monthly work narrative |
+| `session-log/` | Daily-sharded work narrative (YYYY-MM-DD.md) |
 | `decisions/` | Architecture decision records |
 
 ---