crystallize

You are running /hypo:crystallize. This command serves two purposes:

1. Session close — if invoked at the end of a session, run the session-close mechanical-apply path
2. Knowledge synthesis — consolidate draft or scattered wiki pages into stable, well-linked pages

---

Step 1 — Detect context

If /hypo:crystallize was invoked to close a session (via an explicit close signal like "세션 종료" / "오늘 작업 마무리" / "session close" / "wrap up", an accepted proactive-offer [세션 마무리], or /compact), run Step 1a (advisory reflections) then Steps 2–4 (session-close mechanical apply + recovery) before the synthesis scan. Task completion alone does not put you in close mode. Otherwise skip to Step 5.

---

Step 1a — Session-close advisory reflections

Before composing the payload (Step 2), run these four reflections and surface each to the user. Every one is advisory (identity guard): the user confirms or declines, and none performs an automatic action, writes a file on its own, or bypasses the mandatory gate.

1. 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를 건너뛸까요?" and proceed only if the user wants a 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.
2. ADR-candidate check (#41). Did this session make an architectural or design decision (a new pattern, a tradeoff chosen, a convention established)? If yes, ask whether it warrants an ADR and, if so, capture that intent in the sessionLog entry you compose in Step 2. If nothing rose to ADR level, you may record ADR 없음: <one-line reason> in that same sessionLog entry, but gate it on #42's bar: the marker is machine-read and W8 excludes an entry carrying ADR 없음 (with no ADR reference) from the design-history staleness check. Write it only when the session had no design change at all; a sub-ADR design shift takes #42a (append) instead, since the marker would suppress the W8 nudge it needs. Never auto-write an ADR file. Recording the decision (or its absence) in the session-log payload is the only action here. This check carries no decisions/ directory precondition: run it whether or not that directory exists.
3. design-history staleness check (#42). Two branches, so a stale W8 never blocks a clean close: (a) if this session changed design decisions projects/<name>/design-history.md does not yet reflect (including sub-ADR background, tradeoff, or differentiation shifts), recommend appending now: the W8 lint warning flags this mechanically, and an active-project W8 still counts as a --check-session-close blocker even though the PreCompact hook no longer stops /compact on it, so append before you commit. If the file does not exist yet and this session had a design change, recommend creating it now with that change as the first entry; lint separately flags a missing-but-needed file as W14, a warning that never blocks. (b) only if the session made no design change does the ADR 없음 marker (#41) exempt the entry from W8; do not touch design-history, and do not create the file just to satisfy this branch's check. ADR 없음 means "no design change," a stricter bar than "no ADR-level decision." Never auto-write the file yourself in either branch: recommend it, and let the user decide.
4. 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.