hypomnema 1.8.0 → 1.8.2

package/scripts/verify.mjs

@@ -22,12 +22,32 @@ import { loadHypoIgnore, isScanIgnored } from './lib/hypo-ignore.mjs';
 
 // ── arg parsing ──────────────────────────────────────────────────────────────
 
+const ALLOWED_FLAGS = ['--hypo-dir=<path>', '--file=<path>', '--json'];
+
 function parseArgs(argv) {
   const args = { hypoDir: null, file: null, json: false };
   for (const arg of argv.slice(2)) {
-    if (arg.startsWith('--hypo-dir=')) args.hypoDir = expandHome(arg.slice(11));
-    else if (arg.startsWith('--file=')) args.file = expandHome(arg.slice(7));
+    if (arg.startsWith('--hypo-dir=')) {
+      // See lint.mjs's parseArgs for why an empty raw value (--hypo-dir=,
+      // or --hypo-dir="$VAULT" with VAULT unset) is rejected instead of
+      // falling through to the default-resolution branch below.
+      const raw = arg.slice(11);
+      if (!raw) {
+        console.error(`verify.mjs: --hypo-dir requires a non-empty value (got '${arg}')`);
+        console.error(`verify.mjs accepts: ${ALLOWED_FLAGS.join(', ')}`);
+        process.exit(2);
+      }
+      args.hypoDir = expandHome(raw);
+    } else if (arg.startsWith('--file=')) args.file = expandHome(arg.slice(7));
     else if (arg === '--json') args.json = true;
+    else {
+      // No positional arguments here either, so an unmatched arg is rejected
+      // rather than dropped. See lint.mjs's parseArgs for the background
+      // this closes.
+      console.error(`verify.mjs: unrecognized argument '${arg}'`);
+      console.error(`verify.mjs accepts: ${ALLOWED_FLAGS.join(', ')}`);
+      process.exit(2);
+    }
   }
   if (!args.hypoDir) args.hypoDir = resolveHypoRoot();
   return args;

package/templates/SCHEMA.md

@@ -2,7 +2,7 @@
 title: Wiki Schema
 type: schema
 updated: YYYY-MM-DD
-version: 2.1
+version: 2.2
 ---
 
 # Wiki Schema
@@ -85,6 +85,16 @@ tags: [tag1, tag2]
 ---
 ```
 
+**`updated` is the day the content or structure changed**, not the day the file was
+last written. Adding a backlink, fixing a typo, or reflowing a line does not move it.
+Staleness comparisons read this field, so a date bumped for a cross-link makes the
+page look fresher than its claims are.
+
+**Nothing enforces this.** `lint` checks only that the field exists (W3), and `--fix`
+fills a missing one with today's date, which records when the gap was closed rather
+than when the content changed. The rule holds only where whoever edits the page
+applies it.
+
 Optional fields (add as needed):
 
 ```yaml
@@ -95,8 +105,20 @@ visibility_scope: shared | machine:<device>
 source: <slug or URL>
 verify_by: <question to re-check at next review>
 verify_by_date: YYYY-MM-DD
+sources_consulted: [slug1, slug2]
 ```
 
+`sources_consulted` belongs on a `synthesis` page and names the pages it condenses.
+`lint` reads it: when the newest `updated` among those sources is later than the
+synthesis's own `updated`, the page is reported as stale (W15), so a synthesis that
+has not absorbed what its sources learned since surfaces without anyone diffing dates
+by hand. A bare slug is enough when it is unique. Resolution covers `pages/`,
+`projects/` and `journal/`, which is narrower than what a wikilink target
+accepts, so a name outside those (a directory, a `sources/` file, a path into
+a code repo) does not resolve. An unresolved name is left out of the staleness
+comparison and reported separately (W16), because a name this field cannot
+resolve is either a typo or a value the field is not meant to hold.
+
 `visibility_scope` is a different axis from `scope`: `scope` is memory lifetime,
 `visibility_scope` is where a page may surface. Omitting it means `shared` (the
 implicit default of every pre-existing page), so lookup/query/injection stay

package/templates/hypo-automation.md

@@ -31,8 +31,10 @@ All 15 hooks registered in `hooks/hooks.json` are listed below, in registration
 | `hypo-session-record.mjs` | `Stop` | Appends the completed session to the session index |
 | `hypo-auto-commit.mjs` | `Stop` | Stages, commits, and pushes this session's touched wiki paths |
 | `hypo-auto-minimal-crystallize.mjs` | `Stop` | Blocks `Stop` when the session did substantial work, the user signalled wrap-up, and no close was recorded. A substantial session with no close signal is let through |
-| `hypo-cwd-change.mjs` | `CwdChanged` | Re-injects the matching project's `hot.md` when the working directory changes mid-session |
-| `hypo-file-watch.mjs` | `FileChanged` | Re-injects any vault file changed on disk outside the session, once it passes the ignore and visibility filters |
+| `hypo-cwd-change.mjs` | `CwdChanged` | Builds `additionalContext` with the matching project's `hot.md` when the working directory changes mid-session, but `CwdChanged` has no field Claude Code forwards to the model, so this output does not currently reach Claude |
+| `hypo-file-watch.mjs` | `FileChanged` | Builds `additionalContext` for a changed vault file once it passes the ignore and visibility filters. Nothing in this package registers watch paths, so the event has no trigger here, and `FileChanged` output does not reach Claude either way |
+
+This file is copied into a vault only at `init` time, and no update channel pushes a later fix here into a vault that already exists. So this copy can be older than the shipped one. `hooks/hooks.json` in the package is the source of truth for which hook runs on which event; when this table disagrees with it, the table is what went stale.
 
 Two hooks reach the network; the rest compute locally. There are two separate kinds of
 network traffic here, and only one of them can be turned off.

package/templates/hypo-config.md

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

package/templates/hypo-guide.md

@@ -164,7 +164,7 @@ Add to root `hot.md` active projects table.
 
 #### Auto-project offer
 
-When SessionStart / CwdChanged injects a line like
+When SessionStart injects a line like
 `[WIKI: cwd '<name>'에 매칭되는 프로젝트가 없습니다. 자동 생성할까요? (Y/n)]`,
 the current working directory is a real project (git repo + a project marker
 like `package.json`) that has no matching wiki project. **Act on it — do not

package/skills/crystallize/SKILL.md

@@ -1,189 +0,0 @@
----
-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):
-
-1. **Session close (steps 1-6)** — walk the 5 mandatory memory files plus open-questions (conditional). `/compact` no longer waits on this; `--check-session-close` is the actual go/no-go signal for calling the session closed.
-2. **Synthesis (steps 7-11)** — surface tag clusters, orphan pages, and drafts that are ready to consolidate.
-
-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 `/hypo:crystallize` in `--apply-session-close --payload=<path> --session-id=<id>` mode, which runs the lint gate automatically, **scoped to the files it writes** (debt elsewhere is a non-blocking notice). **`--session-id` is required.** Before writing a byte, the apply resolves that session's transcript and refuses the whole close, exit 1 and nothing on disk, unless the **user** asked for it (`session-id-required` / `transcript-unresolved` / `no-user-close-signal`). A refusal is the answer, not an obstacle: ask the user, and re-run only if they say yes. `--check-session-close` is a read-only dry-run of the **full** PreCompact gate: close files + scoped lint + design-history + feedback projection, sharing one function (`precompactGateStatus`) with the `hypo-personal-check.mjs` PreCompact hook. That hook itself no longer blocks `/compact`; it only turns a red result into a `systemMessage`. So a green check here is not "the gate that will stop `/compact`" but the same signal the hook would have surfaced, checked ahead of time: no close-file gap, lint blocker, stale design-history, or feedback-projection issue needs a human fix, which is the practical bar for declaring 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 even at that lower bar: the live PreCompact run can still differ on a context-≥70% prompt, `HYPO_SKIP_GATE`, or a transcript-scoped lint error the check did not see, and none of that differs `/compact` itself, which proceeds either way.
-- **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.
-
----
-
-## Step 1 — Locate package root
-
-Bundled scripts here run via `${CLAUDE_PLUGIN_ROOT}/scripts/`. To resolve that package root: if `${CLAUDE_PLUGIN_ROOT}` is already an absolute path, use it; otherwise read `pkgRoot` from `~/.claude/hypo-pkg.json` (only when non-empty and the target script exists under it); otherwise use the `hypo@hypomnema` (or legacy `hypomnema@hypomnema`) installPath in `~/.claude/plugins/installed_plugins.json`; if none resolve, stop and tell the user to run `hypomnema upgrade --apply` (or `/hypo:upgrade` on a plugin install) or reinstall instead of guessing the cache layout.
-
-If the user specified a Hypomnema directory, pass it as `--hypo-dir="<path>"`. Otherwise omit the flag and the script resolves the Hypomnema root automatically via `HYPO_DIR` → `hypo-config.md` scan → `~/hypomnema`.
-
----
-
-## Step 2 — Run crystallize scan
-
-```bash
-node ${CLAUDE_PLUGIN_ROOT}/scripts/crystallize.mjs \
-  [--hypo-dir="<path>"] \
-  [--min-group=<n>] \
-  [--json]
-```
-
-Options:
-- `--min-group=<n>` — minimum pages per tag group to report (default: 2)
-- `--json` — output results as JSON
-
-Show the output verbatim.
-
----
-
-## Step 3 — Session-close checklist (if triggered at session end)
-
-If `/hypo:crystallize` was invoked as a session-close action, run through this checklist before synthesizing. The mechanical checklist items (1–6 below) proceed automatically without confirmation unless the user has not said "auto"; the advisory reflections that precede them (#41~#44) always surface to the user for confirmation — they are recommendations, never auto-actions.
-
-### Advisory reflections (run before the checklist below — advisory only)
-
-Surface each of these four to the user first. 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.
-
-- **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, 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, or 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. This check carries no `decisions/` directory precondition: run it whether or not that directory exists.
-- **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, or differentiation shifts that are below ADR level but still belong in the ledger), recommend appending to it now: W8 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, not after the check flags it. **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 this session made **no** design change at all does the `ADR 없음` marker from #41 exempt the entry from W8; do **not** touch design-history, and do not create the file just to satisfy this branch's check. 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. Never auto-write the file yourself in either branch: recommend it, and let the user decide.
-- **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.
-
-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-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.
-
-> Do **not** hand-write the root `log.md` session entry, and do **not** put a `log` field in the apply payload. The `## [date] session | <project>` entry is a derivable artifact: `--apply-session-close` calls `deriveRootLogEntries` after writing the session-log, reconstructing the canonical line from the session-log heading. (Supply `log` only for a deliberately custom line; it is now an optional payload field.)
-
-After completing the checklist, verify it before reporting:
-
-```bash
-node ${CLAUDE_PLUGIN_ROOT}/scripts/crystallize.mjs --check-session-close [--hypo-dir="<path>"]
-```
-
-This runs the **full** set of checks the `hypo-personal-check.mjs` PreCompact
-hook itself runs, via the shared `precompactGateStatus`: 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 to earn that signal; the other checks
-still gate it here, even though the live `/compact` no longer blocks on any
-of them (that hook now only turns a red result into a `systemMessage`).
-
-Optional `--project=<slug>` narrows the check to ONE project (close status plus
-lint scope). It is a project-scoped **diagnostic**, not the compact-ready
-signal. A green `--project` result (JSON `scope: "project"`) means only that
-project is close-complete; another today-active project can still block
-`/compact`. Use the plain `--check-session-close` (no `--project`) for the
-go/no-go close signal.
-
-**When using `--apply-session-close --session-id=<id>`** (the payload-driven
-path), the `--session-id` must be the main conversation's session id. Do NOT
-extract it from a background task or Agent output path (e.g., a UUID from
-`/tmp/.../<uuid>/tasks/...`). Such a UUID is a background task id, not the
-main conversation id. Passing the wrong id causes `markerWritten: false` with
-`markerSkipReason: "transcript-unresolved"` or `"no-user-close-signal"`: the
-5 mandatory files are written (ok: true) but the Stop-chain marker is withheld,
-so the session is not actually closed and the Stop hook re-prompts. The correct
-id comes from the `[WIKI_AUTOCLOSE]` block reason or the injected
-`$CLAUDE_CODE_SESSION_ID` (accept the legacy spelling via
-`${CLAUDE_CODE_SESSION_ID:-$CLAUDE_SESSION_ID}`).
-
-Once it passes, report each item with ✓:
-- ✓ session-state.md
-- ✓ hot.md (project + root)
-- ✓ session-log entry
-- ✓ open-questions (or skipped if unchanged)
-- ✓ log.md entry
-- **marker written?** (required): check `markerWritten` in the JSON output. If `true`, report "session-close marker written." If `false`, do NOT declare the session closed or complete; recover per the branches below.
-
-If `markerWritten: true`, ask: "Session closed. Would you like to also run knowledge synthesis now, or stop here?"
-
-**If `ok: false` with an authority `reason`, the close did not happen at all.** No file was written, nothing was committed. Do not report a partial close, and do not write the files by hand to get around it.
-
-- `session-id-required`: `--session-id` was omitted. Pass the main conversation's id and re-run.
-- `transcript-unresolved`: the id resolved no transcript, so it is most likely a background-task or Agent-thread uuid rather than the main conversation's. Get the right one and re-run.
-- `no-user-close-signal`: the transcript is this session's, and the user never asked to close in wording the gate recognizes (e.g. "세션 마무리까지 진행해줘" falls outside the close-signal set). Re-running the same id changes nothing. Confirm intent once with `AskUserQuestion` (header "세션", one option **세션 마무리**); if the user picks it, that answer becomes a recognized close signal, so the same command now applies everything: writes, commit, and marker. If the user declines, the session stays open and nothing is written. Do NOT change the close-signal matcher.
-
-**If `ok: false` with `stage: "session-id-mismatch"`,** the payload carries a `sessionId` that is not the `--session-id` you passed, so this file was authored for a different session (a reused or overwritten temp path). Nothing was written. Do not force it: rebuild the payload for THIS session (write it to a session-scoped path, e.g. `/tmp/hypo-session-close-<session-id>.json`) and re-run.
-
-If the apply succeeded but `markerWritten: false`, branch on `markerSkipReason` (`compact-gate-not-ok`, `commit-failed: …`, `marker-did-not-land`): surface it verbatim and resolve the underlying blocker before re-running.
-
-### If the close came back `ok: false, stage: "proposal-pending"`
-
-A concurrent session wrote one of the pages this close wants to replace, so the close
-withheld the bytes rather than clobber that session's work, and parked them. Nothing is
-lost and nothing is broken. The close is waiting on a decision only the user makes:
-whether to replace the other session's bytes.
-
-Do NOT write the pages with the Write tool and mark the session closed. That path skips
-the store entirely and silently destroys the other session's edits. Drive it out properly:
-
-1. **Look at `proposals`.** If the array is EMPTY, no page was parked. The only conflicts
-   were append-lock timeouts, which the next close re-reads and re-appends by itself. Just
-   re-run the same close command.
-2. **`hypomnema proposal challenge --session-id <id> --ids <id,...>`** with the ids from
-   `proposals`. It re-reads each page from disk and prints the diff between what is there
-   now and what this close wants to write.
-3. **Show the user those diffs** and tell them plainly what would be overwritten. Then give
-   them the approval line the command printed, and ask them to type it:
-
-       apply-proposals <nonce>
-
-   They have to TYPE it. A click on `AskUserQuestion` does not approve an overwrite (you
-   author the option labels, so a click cannot prove they approved this specific write),
-   and the command refuses it. If they would rather keep the other session's page, run
-   `hypomnema proposal discard <id>` instead and re-run the close.
-4. **`hypomnema proposal resolve --session-id <id>`** once they have typed it. It verifies
-   the approval in the transcript, checks the pages have not moved since they saw the diff,
-   and writes them.
-5. **Re-run the close.** `resolve` writes the pages; it does NOT close the session. The
-   re-run skips what already landed and finishes the close.
-6. **Check `markerWritten` again** before you say the session is closed. It is never
-   automatic.
-
----
-
-## Step 4 — Pick a synthesis target
-
-Present the top candidates from the script output:
-- Tag clusters with the most pages
-- Long-standing orphans
-- Pages marked `status: draft`
-
-Ask: "Which of these would you like to crystallize now? (or 'all' / 'skip')"
-
----
-
-## Step 5 — Synthesize
-
-For the chosen target:
-
-1. Read all pages in the cluster.
-2. Write a new synthesis page at `pages/syntheses/<slug>.md` with:
-
-```yaml
----
-title: <synthesis title>
-type: synthesis
-tags: [<shared tags>]
-updated: <today YYYY-MM-DD>
-evidence_strength: inferred
----
-```
-
-3. Cross-link all source pages back to the synthesis with `[[wikilink]]`.
-4. Add the synthesis to `index.md` under `## Pages — Syntheses`.
-
----
-
-> **Citation convention.** When you reference a wiki page in your response, link it as `[[page-slug]]` so it stays connected in the graph. The observability audit scores sessions on search / ingest / feedback activity (recorded by `hypo-session-record`), not on these inline citations; run `/hypo:audit` to inspect and see [[pages/observability/_index]].

package/skills/graph/SKILL.md

@@ -1,58 +0,0 @@
----
-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.
-
-## What this produces
-
-- **json** (default) — adjacency list with in/out-degree counts per node, sorted by total edges
-- **mermaid** — `graph TD` Mermaid diagram (paste into any Mermaid renderer)
-- **dot** — Graphviz DOT format (pipe to `dot -Tsvg` for an SVG)
-
----
-
-## Step 1 — Locate package root
-
-Bundled scripts here run via `${CLAUDE_PLUGIN_ROOT}/scripts/`. To resolve that package root: if `${CLAUDE_PLUGIN_ROOT}` is already an absolute path, use it; otherwise read `pkgRoot` from `~/.claude/hypo-pkg.json` (only when non-empty and the target script exists under it); otherwise use the `hypo@hypomnema` (or legacy `hypomnema@hypomnema`) installPath in `~/.claude/plugins/installed_plugins.json`; if none resolve, stop and tell the user to run `hypomnema upgrade --apply` (or `/hypo:upgrade` on a plugin install) or reinstall instead of guessing the cache layout.
-
-If the user specified a Hypomnema directory, pass it as `--hypo-dir="<path>"`. Otherwise omit the flag and the script resolves the Hypomnema root automatically via `HYPO_DIR` → `hypo-config.md` scan → `~/hypomnema`.
-
----
-
-## Step 2 — Ask for output format (optional)
-
-If the user did not specify a format, ask:
-
-> "Output format? (json / mermaid / dot) [json]"
-
-Default: `json`
-
-Optionally ask:
-
-> "Minimum edges to include a node? (0 = all) [0]"
-
----
-
-## Step 3 — Run graph
-
-```bash
-node ${CLAUDE_PLUGIN_ROOT}/scripts/graph.mjs \
-  [--hypo-dir="<path>"] \
-  [--format=json|mermaid|dot] \
-  [--min-edges=<n>]
-```
-
----
-
-## Step 4 — Present results
-
-- **json**: summarise the top 10 most-connected nodes (by `in + out`), then offer to show the full JSON.
-- **mermaid**: wrap the output in a fenced code block tagged `mermaid` so it renders inline.
-- **dot**: wrap the output in a fenced code block tagged `dot` and suggest the user pipe it to `dot -Tsvg -o graph.svg`.
-
-If the graph has 0 edges, note that no `[[wikilinks]]` were found between pages.
-
----
-
-> **Citation convention.** When you reference a wiki page in your response, link it as `[[page-slug]]` so it stays connected in the graph. The observability audit scores sessions on search / ingest / feedback activity (recorded by `hypo-session-record`), not on these inline citations; run `/hypo:audit` to inspect and see [[pages/observability/_index]].

package/skills/ingest/SKILL.md

@@ -1,107 +0,0 @@
----
-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/`.
-
-## What this does
-
-- Checks which files in `sources/` are missing a `source-summary` page
-- Reports pages that reference a source file that does not exist in `sources/`
-- After the script runs, guides you to synthesize a summary for any un-ingested source
-
----
-
-## Step 1 — Locate package root
-
-Bundled scripts here run via `${CLAUDE_PLUGIN_ROOT}/scripts/`. To resolve that package root: if `${CLAUDE_PLUGIN_ROOT}` is already an absolute path, use it; otherwise read `pkgRoot` from `~/.claude/hypo-pkg.json` (only when non-empty and the target script exists under it); otherwise use the `hypo@hypomnema` (or legacy `hypomnema@hypomnema`) installPath in `~/.claude/plugins/installed_plugins.json`; if none resolve, stop and tell the user to run `hypomnema upgrade --apply` (or `/hypo:upgrade` on a plugin install) or reinstall instead of guessing the cache layout.
-
-If the user specified a Hypomnema directory, pass it as `--hypo-dir="<path>"`. Otherwise omit the flag and the script resolves the Hypomnema root automatically via `HYPO_DIR` → `hypo-config.md` scan → `~/hypomnema`.
-
----
-
-## Step 2 — Run ingest status check
-
-```bash
-node ${CLAUDE_PLUGIN_ROOT}/scripts/ingest.mjs [--hypo-dir="<path>"] [--json]
-```
-
-Options:
-- `--json` — output results as JSON (useful for tooling)
-
-Show the output verbatim.
-
----
-
-## Step 3 — Privacy guard (`.hypoignore`)
-
-Before touching any source content, refuse to ingest secrets (`.env`, SSH keys, credentials). Run the guard for **both** the input path and the destination path:
-
-1. **If the user provided a file path**, check it (use an absolute path):
-
-   ```bash
-   node ${CLAUDE_PLUGIN_ROOT}/scripts/ingest.mjs [--hypo-dir="<path>"] --check="<absolute-input-path>"
-   ```
-
-2. **Always** check the destination `sources/<slug>.<ext>`:
-
-   ```bash
-   node ${CLAUDE_PLUGIN_ROOT}/scripts/ingest.mjs [--hypo-dir="<path>"] --check="sources/<slug>.<ext>"
-   ```
-
-If either command exits non-zero, **stop**: surface the `Refused: ...` message to the user and do not download, read, or save the source. The slug check matters because a user could rename a `.env` to an innocuous slug — the destination must still be blocked.
-
----
-
-## Step 4 — Handle the source file
-
-**If the user provided a file or URL to ingest:**
-
-1. Copy or download the source into `<wiki-root>/sources/<slug>.<ext>` (e.g., `sources/2026-05-07-article-title.md`).
-2. Confirm the file is now present.
-
-**If no file was provided:**
-
-List un-ingested sources from the script output and ask which one to process now.
-
----
-
-## Step 5 — Synthesize a source-summary page
-
-For the chosen source, read its content and create `pages/<slug>.md` with the following frontmatter:
-
-```yaml
----
-title: <descriptive title>
-type: source-summary
-source: <filename>
-tags: [<relevant tags>]
-updated: <today YYYY-MM-DD>
-evidence_strength: direct   # or inferred
----
-```
-
-Then write a concise summary:
-- Key ideas (bullet list)
-- Why this source matters to the wiki
-- Any open questions or follow-up items
-
-Cross-reference existing pages with `[[wikilink]]` syntax where relevant.
-
----
-
-## Step 6 — Update log.md
-
-Append an ingest entry to `<wiki-root>/log.md`:
-
-```
-## <YYYY-MM-DD> ingest — <slug>
-
-- source: sources/<filename>
-- summary: pages/<slug>.md
-- tags: <tags>
-```
-
----
-
-> **Citation convention.** When you reference a wiki page in your response, link it as `[[page-slug]]` so it stays connected in the graph. The observability audit scores sessions on search / ingest / feedback activity (recorded by `hypo-session-record`), not on these inline citations; run `/hypo:audit` to inspect and see [[pages/observability/_index]].

package/skills/lint/SKILL.md

@@ -1,59 +0,0 @@
----
-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.
-
-## What this checks
-
-- Every `.md` file under `pages/` and `projects/` should have `---` frontmatter (missing frontmatter is a warning, not an error)
-- Required fields: `title`, `type`
-- `type` must be one of the recognised values (concept, source-summary, learning, adr, …)
-- `updated` field should be present
-- All `[[wikilinks]]` must resolve to an existing page slug
-
----
-
-## Step 1 — Locate package root
-
-Bundled scripts here run via `${CLAUDE_PLUGIN_ROOT}/scripts/`. To resolve that package root: if `${CLAUDE_PLUGIN_ROOT}` is already an absolute path, use it; otherwise read `pkgRoot` from `~/.claude/hypo-pkg.json` (only when non-empty and the target script exists under it); otherwise use the `hypo@hypomnema` (or legacy `hypomnema@hypomnema`) installPath in `~/.claude/plugins/installed_plugins.json`; if none resolve, stop and tell the user to run `hypomnema upgrade --apply` (or `/hypo:upgrade` on a plugin install) or reinstall instead of guessing the cache layout.
-
-If the user specified a Hypomnema directory, pass it as `--hypo-dir="<path>"`. Otherwise omit the flag and the script resolves the Hypomnema root automatically via `HYPO_DIR` → `hypo-config.md` scan → `~/hypomnema`.
-
----
-
-## Step 2 — Run lint
-
-```bash
-node ${CLAUDE_PLUGIN_ROOT}/scripts/lint.mjs [--hypo-dir="<path>"] [--json] [--fix]
-```
-
-Options:
-- `--json` — output results as JSON (useful for tooling)
-- `--fix` — auto-add missing `updated` field (safe repairs only; no other fields are modified)
-
-Show the output verbatim.
-
----
-
-## Step 3 — Interpret results
-
-- `✓ No lint issues found` — wiki is clean
-- `✗ <file>: <message>` — error (missing required field or malformed frontmatter); must be fixed
-- `⚠ <file>: <message>` — warning (unknown type, missing `updated`, broken link); worth fixing
-
-A non-zero exit code means at least one **error** was found (warnings alone do not produce a non-zero exit code).
-
----
-
-## Step 4 — Offer to fix
-
-For **broken wikilinks**: list the affected files and ask if the user wants help correcting the links now.
-
-For **missing `updated`**: suggest running with `--fix` to auto-add `updated: <today>` to each affected page's frontmatter. Note: `--fix` only repairs files that already have a valid, closed frontmatter block — files with no frontmatter or malformed frontmatter are skipped.
-
-For **missing required fields** (`title`, `type`): open the affected files and help the user fill them in.
-
----
-
-> **Citation convention.** When you reference a wiki page in your response, link it as `[[page-slug]]` so it stays connected in the graph. The observability audit scores sessions on search / ingest / feedback activity (recorded by `hypo-session-record`), not on these inline citations; run `/hypo:audit` to inspect and see [[pages/observability/_index]].

package/skills/query/SKILL.md

@@ -1,62 +0,0 @@
----
-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.
-
-## What this does
-
-- Searches `pages/` and `projects/` for the given query terms
-- Returns matching files with a context excerpt and frontmatter summary
-- You then read the top results and synthesize an answer
-
----
-
-## Step 1 — Locate package root
-
-Bundled scripts here run via `${CLAUDE_PLUGIN_ROOT}/scripts/`. To resolve that package root: if `${CLAUDE_PLUGIN_ROOT}` is already an absolute path, use it; otherwise read `pkgRoot` from `~/.claude/hypo-pkg.json` (only when non-empty and the target script exists under it); otherwise use the `hypo@hypomnema` (or legacy `hypomnema@hypomnema`) installPath in `~/.claude/plugins/installed_plugins.json`; if none resolve, stop and tell the user to run `hypomnema upgrade --apply` (or `/hypo:upgrade` on a plugin install) or reinstall instead of guessing the cache layout.
-
-If the user specified a Hypomnema directory, pass it as `--hypo-dir="<path>"`. Otherwise omit the flag and the script resolves the Hypomnema root automatically via `HYPO_DIR` → `hypo-config.md` scan → `~/hypomnema`.
-
----
-
-## Step 2 — Extract the query
-
-Use the search terms from the user's message. If no query was provided, ask:
-
-> "What would you like to search for in your wiki?"
-
----
-
-## Step 3 — Run query
-
-```bash
-node ${CLAUDE_PLUGIN_ROOT}/scripts/query.mjs \
-  --q="<search terms>" \
-  [--hypo-dir="<path>"] \
-  [--limit=<n>] \
-  [--json]
-```
-
-Options:
-- `--q=<query>` — search query (required)
-- `--limit=<n>` — max results (default: 10)
-- `--json` — output results as JSON
-
-Show the output verbatim.
-
----
-
-## Step 4 — Synthesize an answer
-
-Read the top matching pages (up to 5) and produce a synthesized response:
-
-1. **Direct answer** — if the query has a clear answer from the wiki, state it first.
-2. **Supporting pages** — list the relevant pages with one-line descriptions and `[[wikilink]]` references.
-3. **Gaps** — if the wiki lacks coverage on the topic, note what is missing and suggest an ingest target.
-
-If zero results are returned, say so and offer to broaden the search or suggest using `/hypo:ingest` to add relevant sources.
-
----
-
-> **Citation convention.** When you reference a wiki page in your response, link it as `[[page-slug]]` so it stays connected in the graph. The observability audit scores sessions on search / ingest / feedback activity (recorded by `hypo-session-record`), not on these inline citations; run `/hypo:audit` to inspect and see [[pages/observability/_index]].