oh-my-second-brain 0.14.0 → 0.15.0

package/.claude-plugin/marketplace.json

@@ -10,7 +10,7 @@
     {
       "name": "oms",
       "description": "Oh My Second Brain convention layer for Obsidian vaults — capture, retrieve, and validate knowledge under a declared semantic convention.",
-      "version": "0.14.0",
+      "version": "0.15.0",
       "author": {
         "name": "gobeumsu",
         "email": "gobeumsu@gmail.com"
@@ -37,5 +37,5 @@
       ]
     }
   ],
-  "version": "0.14.0"
+  "version": "0.15.0"
 }

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "oms",
-  "version": "0.14.0",
+  "version": "0.15.0",
   "description": "Oh My Second Brain convention layer for Obsidian vaults — seven shared skills and five MCP tools under a declared semantic convention.",
   "author": {
     "name": "gobeumsu"

package/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "oms",
-  "version": "0.14.0",
+  "version": "0.15.0",
   "description": "Oh My Second Brain convention layer for Obsidian vaults — Codex native rules, skills, and MCP adapter.",
   "_note": "oms host install writes Codex MCP config and provenance, installs ~/.codex/rules/oms.md, and installs the seven shared skills under ~/.codex/skills/oms-*.",
   "skills": "./assets/skills/",

package/CHANGELOG-assets.md

@@ -4,6 +4,10 @@ Skills, agents, templates, and host guidance changes belong here.
 
 ## [Unreleased]
 
+## [0.15.0] - 2026-09-19
+
+- **Host guidance now teaches selected-folder template sources instead of per-file registration or folder modes.** It documents the exact `템플릿에 변경이 있습니다` / `확인하기` / `나중에` notice, host-only deferral, long-lived `templateNotice` results, and the resumable `interview-next` → `interview-answer` → `commit-contracts` flow that publishes only user-confirmed controls. Placement is write-time only (explicit destination, then taxonomy default, then `ask`); source review preserves Markdown bytes and does not invent a registration prerequisite, widget, or host configuration.
+
 ## [0.14.0] - 2026-09-05
 
 - Shared skills and runtime guidance use the final command families and exclusive MCP operations, with no obsolete command aliases. Authored assets and the shipped root skill mirror remain byte-identical. (#125)

package/CHANGELOG-cli.md

@@ -4,6 +4,10 @@ Changes to the `oms` command surface belong here.
 
 ## [Unreleased]
 
+## [0.15.0] - 2026-09-19
+
+- **Breaking: the template CLI now exposes a selected-folder census and linear review flow.** The exact leaves are `scan|list|show|add|update|move|remove|default|check|regenerate-types|review|answer|commit`; `scan` is read-only, `add <folder>` selects source scope, and `add --id <id> --from <file>` remains explicit source authoring rather than contract review. `answer <question-id> --answer <JSON> --census-digest <digest> --ledger-digest <digest|null>` forwards server-returned CAS fields, while `commit` adds the existing dry-run or `--yes --approved-digest` guard. This removes the per-file registration ritual without weakening verified-target writes; note creation considers `--folder <note-folder>` before a taxonomy default and then `ask`, with no template-creation target-folder form.
+
 ## [0.14.0] - 2026-09-05
 
 - HTTP routes reject malformed bodies and fields instead of coercing them into empty queries. Status retains unaffected component evidence when convention, history, engine, or graph health is unavailable. (#125)

package/CHANGELOG-kernel.md

@@ -4,6 +4,11 @@ Domain logic changes belong here.
 
 ## [Unreleased]
 
+## [0.15.0] - 2026-09-19
+
+- **Breaking: template contracts now reconcile from an explicit selected-folder census instead of per-file registration or auto/manual modes.** Every `.md` beneath the selected scope is classified for add, edit, delete, or rename; source bytes stay in place and only user-confirmed `.oms` controls publish. The two-tier freshness gate hashes raw shared authorities first and then isolates changed templates as pending while preserving unrelated note writes. Metadata and bounded body-node contracts (with per-node requiredness/order) replace opaque body assumptions; anchored resumable questions and a locked CAS preserve unaffected answers. Historical ledger census is not blanket stale rejection: current request CAS and per-answer anchors govern validity. Ambiguous repeated body nodes remain contextualized, missing required-body rules require explicit disposition, and placement is optional during review then resolves at note creation by explicit destination, taxonomy default, or `ask`.
+- **Review approval is bound to independently recorded source/body evidence, the exact captured controls, and the complete selected census.** Derived descriptors alone cannot transfer template identity; approved raw-body evidence preserves confirmation-only rename hints after restart without inferring body requirements. New unbound sources invalidate the reviewed scope, other template operations cannot absorb pending sibling edits, and deferred deletions remain actionable. Mutation and taxonomy identities normalize before routing so NFC/NFD spelling cannot lose source updates or authored placement. Public confirmation omits raw source/control byte arrays.
+
 ## [0.14.0] - 2026-09-05
 
 - Read-only engine connections use stable vault-external SQLite snapshots, including committed WAL content, so source sidecars remain untouched even while the reader is open. Store rebuild/drop repairs share verified-target admission and server-checked postconditions across entrypoints. (#125)

package/CHANGELOG-mcp.md

@@ -4,6 +4,13 @@ MCP server tools and resources belong here.
 
 ## [Unreleased]
 
+## [0.15.0] - 2026-09-19
+
+- The bundled MCP SDK now resolves `hono` 4.13.8, clearing the moderate advisory group that affected its HTTP transport's body and query parsing. Only the lockfile moves; no declared dependency is added or changed.
+- Pending body contracts and incomplete fresh projection coverage also surface the generic template notice when no new raw source diff exists, so successful source authoring cannot hide the remaining contract confirmation.
+
+- **Template review now uses exactly `interview-next`, `interview-answer`, and `commit-contracts` under `write { op: "template" }`, with a minimal notice and long-lived carrier.** Selected-folder census changes preserve source bytes and publish only user-confirmed controls through the guarded flow; an affected template is pending without blocking unrelated templates, while shared-authority drift still fails closed vault-wide. The initial display is exactly `템플릿에 변경이 있습니다` with exactly `확인하기` and `나중에`; `나중에` is host-only with no server call or ledger mutation, and `templateNotice` is surfaced on tool results even when boot instructions are stale. The five-tool surface is unchanged.
+
 ## [0.14.0] - 2026-09-05
 
 ### Changed

package/CHANGELOG-vendors.md

@@ -4,6 +4,10 @@ Per-host adapter and installer changes belong here.
 
 ## [Unreleased]
 
+## [0.15.0] - 2026-09-19
+
+- **Claude, Codex, and Hermes guidance now aligns with folder-sourced template contracts.** Each native host surface explains selected-folder census without per-file registration or folder modes, the exact minimal notice and host-only `나중에`, and the resumable `interview-next` → `interview-answer` → `commit-contracts` flow. Review preserves source bytes and publishes only user-confirmed controls; affected-template pending remains scoped while shared-authority failures stay fail-closed globally. Note creation uses explicit folder, taxonomy default, then `ask`, without changing the host-specific skill/tool asymmetry.
+
 ## [0.14.0] - 2026-09-05
 
 - Native host launch manifests use `oms serve mcp`; registrations retain seven shared skills and exactly five MCP tools. Host synchronization updates OMS assets independently of package installation and never upgrades the host application. (#125)

package/CHANGELOG.md

@@ -10,6 +10,14 @@ This aggregate changelog contains changes that span multiple layers.
 
 ## [Unreleased]
 
+## [0.15.0] - 2026-09-19
+
+- **Breaking: a selected template folder, not a per-file registration step, is what makes a template usable.** Every `.md` beneath a folder you explicitly select is a census candidate tracked by content hash, so adding, editing, deleting, or renaming a source is picked up without registering each file and without the retired auto/manual folder modes. This spans layers deliberately: the kernel owns the census, contract derivation, interview ledger, and guarded reconcile; the CLI gains `oms template review|answer|commit`; MCP gains the matching `interview-next`, `interview-answer`, and `commit-contracts` modes plus the notice carrier; and the shared skills and host guidance describe one vocabulary. The five MCP tools and seven skills are unchanged.
+
+  Your files stay yours. Review reads and verifies source bytes where they already are and publishes only `.oms` control files through the existing exact-digest transaction — it never rewrites a template or an existing note. A change surfaces as exactly `템플릿에 변경이 있습니다` with `확인하기` and `나중에`, naming nothing; `나중에` is handled by the host alone. Confirming opens one linear interview that asks only what it must, keeps confirmed answers that the edit did not touch, resumes after an interruption, re-asks only the answers whose anchored part of the source actually changed, and still ends at an explicit final confirmation even when nothing is left to ask. Contracts now describe frontmatter *and* a bounded body grammar with per-node requiredness and order; what OMS observed and what you confirmed stay separate, so an ambiguous source asks rather than inventing a rule.
+
+  A changed template no longer stalls the rest of the vault: shared authority files still fail closed vault-wide, but a single edited source makes only its own template pending while unrelated notes keep writing. Approval records independently derived source and body evidence, so a hand-edited projection can never transfer a template's identity. Note placement is no longer a precondition for having a contract — it is resolved when a note is created, from an explicit destination, then the taxonomy default, then by asking. See ADR-013.
+
 ## [0.14.0] - 2026-09-05
 
 - **Breaking: commands have one noun-and-verb home across CLI, MCP, skills, and host launchers.** (#125) Note, template, wikilink, bridge, index, graph, host, package, and model operations no longer overlap through legacy top-level aliases. The five MCP tools remain; exclusive operations retain the underlying capabilities. See `docs/cli-map.md` for the full map. Native MCP launch is `oms serve mcp`.

package/README.ko.md

@@ -8,14 +8,16 @@ Oh My Second Brain(`oms`)은 기존 Obsidian/Markdown 볼트를 노트 소유권
 - 각 템플릿은 경로·digest와 독립적인 안정적 `templateId`를 가지며, 볼트 전체의 `BaseContract` 하나를 상속한다.
 - `.obsidian/types.json`은 읽기 전용 타입 권위다.
 - 사용자 소유 온톨로지는 계속 활성 상태다. `.oms/template-policy.json`은 노트·필드 의미와 필수값, 형식, 허용값, 기본값, 이름 규칙, 정체성, 바인딩을 기록한다.
-- `.oms/taxonomy.json`은 폴더·링크 의미와 배치를 소유하며, 작성된 폴더 의미는 `folder-ontology` 검색 축으로 노출된다. runtime의 유일한 권위이며, setup이 레거시 YAML을 한 번 변환한다.
+- `.oms/taxonomy.json`은 폴더·링크 의미와 배치를 소유하며, 작성된 폴더 의미는 `folder-ontology` 검색 축으로 노출된다. runtime의 유일한 권위다.
 - `.oms/types.json`은 쓰기·검색용 검증된 파생 projection이다. 직접 편집하지 않는다.
 
 제거된 것은 노트 정체성으로서의 `concept`와 번들 runtime 기본값이지, 의미 계층으로서의 온톨로지가 아니다.
 
 ## 설정
 
-Setup은 기존 템플릿을 재귀 탐색하고 migration을 제안한다. 노트 타입 기본값을 번들로 강요하지 않으며 노트를 수정하지 않는다.
+Setup은 명시적으로 선택한 템플릿 폴더 안의 기존 템플릿을 재귀 탐색하고
+migration을 제안한다. 노트 타입 기본값을 번들로 강요하지 않으며 노트를
+수정하지 않는다.
 
 ```bash
 oms setup --vault /path/to/vault --dry-run
@@ -24,11 +26,57 @@ oms setup --vault /path/to/vault --yes --approved-digest <표시된-digest>
 
 관리 템플릿 변경도 dry-run, 호출자가 검토한 정확한 digest, CAS, transaction, 사후조건 receipt를 거친다.
 
+## 템플릿 흐름
+
+명시적으로 선택한 템플릿 폴더 아래의 모든 `.md`는 템플릿 원본
+후보가 된다. review는 원본을 검증하고 같은 위치의 바이트를 보존하며,
+파일별 등록 절차나 auto/manual 폴더 mode는 필요하지 않다. OMS는
+메타데이터 계약(frontmatter key·type·requiredness·`filledBy`)과 제한된
+본문 구조(ATX heading, fence code block, fence 밖의 ordered/unordered list
+run, `<!-- oms:content -->`, 문서 순서/EOL/BOM/final-newline)를 함께
+도출한다. paragraph, setext heading, 모든 Markdown을 강제한다고 주장하지
+않는다. 원본이 바뀌면 의존하는 템플릿만 pending이 되므로 다른 템플릿
+쓰기는 계속 가능하며, shared authority 변경이나 불일치는 볼트 전체를
+fail-closed 한다.
+
+선택한 폴더의 원본이 바뀌면 호스트에 처음 표시할 알림은 정확히
+`템플릿에 변경이 있습니다`이며, 동작은 정확히 `확인하기`와 `나중에`다.
+처음 알림에는 템플릿 이름·hash·change class를 표시하지 않는다.
+`나중에`는 host-only로 server를 호출하지 않고 interview ledger도 바꾸지
+않는다. `확인하기`는 MCP `write { op: "template", mode: "interview-next" }`로
+선형 resumable interview를 시작한다. 서버가 반환한 다음 질문을 따라
+진행하고 영향 없는 confirmed answer는 보존한다. 모든 필요한 질문 뒤에는
+정확한 최종 digest를 보여주고 사용자가 승인한 경우에만
+`mode: "commit-contracts"`로 `.oms` control만 publish한다. self-approve하지
+않는다. `status`와 search는 계속 읽기 전용이며 boot instruction이 stale한
+long-lived host도 반환된 `templateNotice`를 표시해야 한다.
+
+정확한 CLI review 흐름은 다음과 같다.
+
+```text
+oms template review
+oms template answer <question-id> --answer <JSON> --census-digest <digest> --ledger-digest <digest|null>
+oms template commit --census-digest <digest> --ledger-digest <digest|null> --dry-run
+oms template commit --census-digest <digest> --ledger-digest <digest|null> --yes --approved-digest <digest>
+```
+
+answer는 서버가 반환한 question과 CAS 값을 사용한다. commit은 같은 CAS
+값과 기존 dry-run 또는 yes/approved-digest guard를 함께 사용한다.
+
+정확한 note 생성 사용법은 다음과 같다.
+
+```text
+oms note create [template-id] --body <text>|--body-file <file> [--frontmatter <json>|--frontmatter-file <file>] [--folder <note-folder>]
+```
+
+노트 생성 시 배치 우선순위는 명시적 caller folder, taxonomy default, `ask`
+순서이며, 배치가 없다고 contract review를 막지 않는다.
+
 ## CLI
 
 ```text
 oms setup                                      기존 볼트 템플릿 탐색 및 채택
-oms template scan|list|show|add|update|move|remove|default|check|regenerate-types
+oms template scan|list|show|add|update|move|remove|default|check|regenerate-types|review|answer|commit
 oms note create|append|update|audit|backfill|get
 oms link check|suggest|apply                   노트 wikilink 점검·제안·적용
 oms bridge add|remove|status                   저장소-볼트 target bridge 관리
@@ -45,15 +93,6 @@ oms status                                     읽기 전용 종합 상태 표
 
 `oh-my-second-brain`은 전체 명령이고 `oms`는 짧은 별칭이다.
 
-`oms template add`에는 세 형태가 있다. 폴더를 넘기면 그 안의 템플릿을
-등록하고, 파일과 `--id`를 넘기면 기존 템플릿을 등록하며, `--id`와
-`--from`을 함께 쓰면 새 템플릿을 만든다. `--from` 형태는 등록된
-`templateFolders[].default` 위치에 쓰며, 이 템플릿 폴더는 노트 배치
-위치를 제한하지 않는다. `oms template default <id>`가 기본 바인딩을
-선언한다. 명시적 템플릿 없이 노트를 만들 때는 이 바인딩만 사용하며,
-없으면 첫 템플릿을 임의 선택하지 않고 `TEMPLATE_DEFAULT_UNDECLARED`로
-실패한다.
-
 ### 도움말 계약
 
 인식된 모든 명령은 `--help`와 `-h`를 받아들이며, exit 0으로 종료하고
@@ -91,6 +130,13 @@ Setup에서는 로컬 검증 acquisition 정책 하나를 선택한다:
 
 쓰기는 하나의 `ResolvedTemplate`을 해석해 create, append, update를 수행한다. 템플릿 변경, projection 재생성, 한 노트 정체성 backfill은 검증된 target과 명시적 승인 digest가 필요하다. `status`와 모든 검색 동작은 읽기 전용이다.
 
+템플릿 contract review는 `oms_write`의 `op: "template"`에서 정확히
+`interview-next`, `interview-answer`, `commit-contracts` mode를 사용한다.
+정확한 CLI 대응은 `oms template review`, `oms template answer`,
+`oms template commit`이다. answer는 서버가 반환한 question, request, CAS
+field를 그대로 사용하며 parameter 이름을 만들지 않는다. 질문이 0개면
+곧바로 최종 확인으로 간다.
+
 일반 lexical 검색은 projection과 독립적이다. 템플릿·선언 필드·폴더·링크 축은 쓰기와 같은 projection을 사용하며 누락·stale 상태를 크게 실패시킨다. 관리 템플릿 원본은 검색 대상에서 제외한다. Vector/HyDE는 provider와 model이 모두 설정되지 않으면 가짜 대체 없이 실패한다.
 
 ## 설치

package/README.md

@@ -8,14 +8,16 @@ Oh My Second Brain (`oms`) connects an existing Obsidian or Markdown vault to AI
 - Each template has a stable `templateId`, independent of its path and digest, and inherits one vault-wide `BaseContract`.
 - `.obsidian/types.json` is read-only type authority.
 - The user-owned ontology remains active: `.oms/template-policy.json` records note/field meaning alongside requiredness, formats, allowed values, defaults, naming, identity, and bindings.
-- `.oms/taxonomy.json` records folder/link meaning and owns placement; authored folder intents are exposed through the `folder-ontology` search axis. It is the sole runtime authority; setup performs the one-time legacy YAML conversion.
+- `.oms/taxonomy.json` records folder/link meaning and owns placement; authored folder intents are exposed through the `folder-ontology` search axis. It is the sole runtime authority.
 - `.oms/types.json` is a validated derived write/search projection. Never hand-edit it.
 
 The retired model is `concept` as note identity and bundled runtime defaults—not ontology as semantic meaning.
 
 ## Setup
 
-Setup recursively discovers existing templates and proposes migration. It ships no note-type defaults and never modifies notes.
+Setup recursively discovers existing templates within explicitly selected
+template folders and proposes migration. It ships no note-type defaults and
+never modifies notes.
 
 ```bash
 oms setup --vault /path/to/vault --dry-run
@@ -24,11 +26,56 @@ oms setup --vault /path/to/vault --yes --approved-digest <shown-digest>
 
 Managed-template changes use the same dry-run, exact caller approval, compare-and-swap, transaction, and postcondition receipt boundary.
 
+## Template workflow
+
+An explicitly selected template folder makes every `.md` beneath it a template
+source candidate. Review verifies the source and preserves its bytes in place;
+no per-file registration or auto/manual folder mode is required. OMS derives
+both metadata (frontmatter keys, types, requiredness, and `filledBy`) and a
+bounded body structure (ATX headings, fenced code blocks, ordered/unordered
+list runs outside fences, `<!-- oms:content -->`, and document
+order/EOL/BOM/final-newline details). It does not claim to enforce paragraphs,
+setext headings, or all Markdown. A changed source makes only its dependent
+template pending, so unrelated writes remain available; shared-authority
+changes or mismatches fail closed for the whole vault.
+
+When a selected-folder source changes, the initial host notice is exactly
+`템플릿에 변경이 있습니다` with exactly `확인하기` and `나중에`; it names no
+template and shows no hash or change class. `나중에` is host-only and makes no
+server call or ledger mutation. `확인하기` starts a linear, resumable interview
+through MCP `write { op: "template", mode: "interview-next" }`. Continue with
+the server-returned next question, preserving unaffected confirmed answers.
+After all necessary questions, show the exact final digest and publish only
+`.oms` controls after the user approves it with `mode: "commit-contracts"`; never
+self-approve. `status` and search remain read-only, and long-lived hosts
+surface a returned `templateNotice` even when boot instructions are stale.
+
+The exact CLI review flow is:
+
+```text
+oms template review
+oms template answer <question-id> --answer <JSON> --census-digest <digest> --ledger-digest <digest|null>
+oms template commit --census-digest <digest> --ledger-digest <digest|null> --dry-run
+oms template commit --census-digest <digest> --ledger-digest <digest|null> --yes --approved-digest <digest>
+```
+
+Answer uses the server-returned question and CAS values. Commit uses the same
+CAS values plus the existing dry-run or yes/approved-digest guard.
+
+The exact note-create usage is:
+
+```text
+oms note create [template-id] --body <text>|--body-file <file> [--frontmatter <json>|--frontmatter-file <file>] [--folder <note-folder>]
+```
+
+At note creation, placement is explicit caller folder, then the taxonomy
+default, then `ask`; missing placement does not block contract review.
+
 ## CLI
 
 ```text
 oms setup                                      Discover and adopt existing vault templates
-oms template scan|list|show|add|update|move|remove|default|check|regenerate-types
+oms template scan|list|show|add|update|move|remove|default|check|regenerate-types|review|answer|commit
 oms note create|append|update|audit|backfill|get
 oms link check|suggest|apply                   Check, suggest, or apply note wikilinks
 oms bridge add|remove|status                   Manage repository-to-vault target bridges
@@ -45,14 +92,6 @@ oms status                                     Show the read-only aggregate stat
 
 `oh-my-second-brain` is the full command; `oms` is its short alias.
 
-`oms template add` has three forms: a folder registers its templates, a file
-with `--id` registers that existing template, and `--id` with `--from` creates
-one. The `--from` form writes to the registered `templateFolders[].default`
-destination; that template folder does not constrain where notes are placed.
-`oms template default <id>` declares the default binding. Creating a note
-without an explicit template uses only that binding and otherwise fails with
-`TEMPLATE_DEFAULT_UNDECLARED`; it never silently selects the first template.
-
 ### Help contract
 
 Every recognized command accepts `--help` and `-h`, exits 0, and performs no
@@ -88,6 +127,13 @@ The seven skills (`write`, `search`, `link`, `distill`, `status`, `doctor`, `tem
 
 Writes resolve one `ResolvedTemplate` and support create, append, and update. Template mutation, projection regeneration, and one-note identity backfill require a verified target and explicit approval digest. `status` and every search operation are read-only.
 
+Template contract review uses `oms_write` with `op: "template"` and exactly
+`interview-next`, `interview-answer`, and `commit-contracts` modes. The exact
+CLI counterparts are `oms template review`, `oms template answer`, and
+`oms template commit`. Answer submissions use the server-returned question,
+request, and CAS fields; hosts must not invent parameter names. A zero-question
+response proceeds directly to final confirmation.
+
 Plain lexical search is projection-independent. Typed template/declared-field/folder/link axes use the same projection as writes and fail loudly when it is missing or stale. Managed template sources are excluded. Vector and HyDE requests fail loudly unless both embedding provider and model are configured.
 
 ## Install

package/assets/claude/CLAUDE.md

@@ -13,6 +13,11 @@ Writes:
 - Use `/write` and MCP `oms_write`; never host Write/Edit for vault notes or managed templates.
 - Notes use `op: "note"` with a stable template ID.
 - Template changes use `op: "template"`: dry-run first, then apply only with the exact reviewed `approvalDigest`.
+- An explicitly selected template folder makes every `.md` beneath it a source candidate; no per-file registration or folder mode is required. Contract review verifies the source and leaves its bytes in place.
+- A changed source makes only its dependent template pending; unrelated template writes remain available, while shared-authority failures fail closed for the whole vault.
+- Surface the initial source-change notice exactly as `템플릿에 변경이 있습니다` with exactly `확인하기` and `나중에`; do not render a template name, hash, or change taxonomy. `나중에` is host-only and makes no server call or interview-ledger mutation. Surface returned `templateNotice` data in long-lived sessions even when boot instructions are stale.
+- `확인하기` starts MCP `write { op: "template", mode: "interview-next" }`; answer with `interview-answer` and commit with `commit-contracts` only after all required questions and the user's approval of the exact final digest. Use server-returned next/request/CAS fields without inventing parameter names. The exact CLI counterparts are `oms template review`, `oms template answer`, and `oms template commit`; never self-approve.
+- At note creation, choose placement by explicit caller folder, then taxonomy default, then `ask`; registration is not required and there is no Inbox fallback.
 
 Retrieval:
 - Use `/search`; discover identities with `op: "templates"`.

package/assets/codex/AGENTS.md

@@ -14,6 +14,14 @@ The vault is governed by user-owned template conventions in `.oms/`.
 
 **Write:** Use `$oms-write` and MCP `oms_write`, never host Write/Edit for vault notes or managed templates. Notes use `op: "note"`. Template changes use `op: "template"`, first as a dry-run and then only with the exact reviewed `approvalDigest`.
 
+An explicitly selected template folder makes every `.md` beneath it a source candidate; no per-file registration or folder mode is required. Contract review verifies the selected source and preserves its bytes in place. A changed source makes only its dependent template pending; writes for other templates remain available, while a shared-authority failure remains fail-closed for the whole vault.
+
+When a source-change notice is returned, surface the initial notice exactly as `템플릿에 변경이 있습니다` with exactly `확인하기` and `나중에`; do not add a template name, hash, or change taxonomy. `나중에` is host-only and performs no server call or interview-ledger mutation. Surface a returned `templateNotice` in long-lived sessions even when boot guidance is stale.
+
+`확인하기` starts MCP `write { op: "template", mode: "interview-next" }`; submit answers with `interview-answer` and commit only with `commit-contracts`, forwarding the server-returned next/request/CAS fields without inventing parameter names. The exact CLI counterparts are `oms template review`, `oms template answer`, and `oms template commit`. Continue through every required question, preserve unaffected confirmed answers, and never self-approve the final digest.
+
+At note creation, choose placement by explicit caller folder, then taxonomy default, then `ask`; do not require template registration or invent an Inbox fallback.
+
 **Retrieve:** Use `$oms-search`; discover stable IDs with `op: "templates"`, then use template, declared field, folder, and link axes.
 
 **Maintain:** `$oms-status` is read-only. `$oms-doctor` diagnoses and performs explicit repairs.

package/assets/codex/rules/oms.md

@@ -22,3 +22,28 @@ Actual Obsidian Markdown templates own note shape and body scaffolding. The user
 - Never use direct file tools for vault notes or managed templates.
 - Never invent required values or self-approve a repair digest.
 - `status` and search are read-only; mutation requires a verified target.
+
+## Template source and review
+
+An explicitly selected template folder makes every `.md` beneath it a source
+candidate; no per-file registration or folder mode is required. Review verifies
+the source and leaves its bytes in place. A changed source makes only the
+dependent template pending, so unrelated template writes remain available;
+shared-authority failures still fail closed for the whole vault.
+
+Surface a source-change notice exactly as `템플릿에 변경이 있습니다` with
+exactly `확인하기` and `나중에`. Do not render a template name, hash, or change
+taxonomy in the initial notice. `나중에` is host-only: it makes no server call
+and does not mutate the interview ledger. Surface a returned `templateNotice`
+in long-lived sessions even when boot instructions are stale.
+
+`확인하기` starts MCP `write { op: "template", mode: "interview-next" }`.
+Submit answers with `interview-answer`, then use `commit-contracts` only after
+all required questions and the user's approval of the exact final digest.
+Forward the server-returned next/request/CAS fields without inventing parameter
+names. The exact CLI counterparts are `oms template review`, `oms template
+answer`, and `oms template commit`; never self-approve.
+
+At note creation, placement is explicit caller folder, then the taxonomy
+default, then `ask`. Template registration is not a placement prerequisite, and
+there is no invented Inbox fallback.

package/assets/hermes/SOUL.md

@@ -11,6 +11,29 @@ Before vault work:
 
 **Write:** Use the `write` skill and MCP `oms_write`; never direct file tools for vault notes or managed templates. Notes use `op: "note"`. Template changes use `op: "template"`, dry-run first, then exact reviewed `approvalDigest`.
 
+An explicitly selected template folder makes every `.md` beneath it a source
+candidate; no per-file registration or folder mode is required. Contract review
+verifies the source and preserves its bytes in place. A changed source makes
+only its dependent template pending; unrelated template writes remain
+available, while shared-authority failures fail closed for the whole vault.
+
+Surface the initial source-change notice exactly as `템플릿에 변경이 있습니다`
+with exactly `확인하기` and `나중에`; do not render a template name, hash, or
+change taxonomy. `나중에` is host-only and makes no server call or
+interview-ledger mutation. Surface returned `templateNotice` data in long-lived
+sessions even when boot instructions are stale.
+
+`확인하기` starts MCP `write { op: "template", mode: "interview-next" }`;
+submit answers with `interview-answer`, then use `commit-contracts` only after
+all required questions and the user's approval of the exact final digest.
+Forward server-returned next/request/CAS fields without inventing parameter
+names. The exact CLI counterparts are `oms template review`, `oms template
+answer`, and `oms template commit`; never self-approve.
+
+At note creation, choose placement by explicit caller folder, then taxonomy
+default, then `ask`; template registration is not required and there is no
+Inbox fallback.
+
 **Retrieve:** Use `search`, discover IDs through `op: "templates"`, and filter by template, declared fields, folder, or links.
 
 **Maintain:** `status` is read-only. `doctor` diagnoses and performs explicit repairs. Hermes installs the same seven write, search, link, distill, status, doctor, and tool-less template skills.

package/assets/hermes-manifest.json

@@ -1,6 +1,6 @@
 {
   "name": "oms",
-  "version": "0.14.0",
+  "version": "0.15.0",
   "description": "Oh My Second Brain convention layer for Obsidian vaults — Hermes skill bundle and MCP adapter.",
   "_note": "oms host install writes ~/.hermes/config.yaml mcp_servers.oms and installs the seven shared skills with provenance under ~/.hermes/skills/knowledge-management/oms/."
 }

package/assets/skills/search/SKILL.md

@@ -20,7 +20,7 @@ Retrieve vault knowledge without changing the vault.
 
 - `query` requires `mode: "query" | "search" | "vsearch"` and exactly one of `query` or `searches`. Plain `mode: "query"` is projection-independent lexical retrieval and remains available when no embedding provider is configured.
 - `context` retrieves the declared search context.
-- `template-scan` reports template candidates without registering or writing them.
+- `template-scan` is a read-only census and pending view; it never registers or writes a source.
 - `templates` lists templates when `templateId` is absent and shows one template when `templateId` is present.
 - `index-status` requires `view: "status" | "collections" | "contexts"`.
 - `get-document` requires exactly one of `target`, `targets`, or `notePath` with its window.
@@ -35,3 +35,25 @@ Use `search { op: "templates" }` to list stable template IDs and declared axes,
 - `axes.link` follows observed wikilinks.
 
 Axes intersect. They require current authority and fail loudly on an undeclared field or stale signature; remove the typed axis or run template diagnosis rather than guessing. Vector or HyDE retrieval also fails loudly without a configured embedding provider and model. Missing results and history are unobserved, not proof of absence or non-use.
+
+## Template-change notices
+
+Search is read-only, including census and notice handling. A result may carry a
+machine `templateNotice` for a selected-folder source change. Surface the first
+notice exactly as `템플릿에 변경이 있습니다` with exactly `확인하기` and
+`나중에`; do not render a template name, hash, or change taxonomy. This
+requirement applies to long-lived sessions even when boot instructions are
+stale. `status` returns the full notice on every poll; `search` emits it once
+per process and pending digest, and again when that digest changes.
+
+`나중에` is host-only: it performs no server call and does not mutate the
+interview ledger. `확인하기` starts the linear interview with
+`write { op: "template", mode: "interview-next" }`. Answers use
+`interview-answer` and the server-returned question, request, and CAS values;
+resume from the server-returned next question rather than inventing fields.
+Unchanged confirmed answers are preserved. A zero-question response proceeds to
+final confirmation, and `commit-contracts` is sent only after the user approves
+the exact final digest; never self-approve.
+
+The surface remains five MCP tools and seven skills. Search never mutates
+templates, notes, controls, or the interview ledger.

package/assets/skills/status/SKILL.md

@@ -18,3 +18,25 @@ With `status` op absent, show the combined read-only view: resolved template cou
 A malformed or missing projection is reported as invalid with an actionable doctor operation. Status never regenerates controls, rebuilds indexes, repairs notes, edits controls, or writes the vault. Use `oms graph build` / `doctor { op: "build-graph" }` for graph construction and `oms index sync|embed|repair` for embedding work.
 
 Report runtime history separately: events live outside the vault and are scoped to the current host and vault. A missing event means unobserved, never unused. Distinguish actual mutation time from observation time; external drift gives a changed-between interval, not an invented modification timestamp. Every use/check verifies current authority instead of applying an age-based expiry rule. Surface `LEDGER_APPEND_FAILED` explicitly without claiming a successful vault write failed.
+
+## Template-change notices
+
+`status` is the read-only polling channel for selected-folder template changes.
+When a machine `templateNotice` is present, return the full notice on every
+poll and surface the initial display exactly as `템플릿에 변경이 있습니다`
+with exactly `확인하기` and `나중에`. Do not render a template name, hash, or
+change taxonomy in that first notice. A census failure yields no notice and no
+tool error.
+
+`나중에` is host-only: it performs no server call and leaves the pending set and
+interview ledger unchanged. `확인하기` starts
+`write { op: "template", mode: "interview-next" }`; subsequent answers use
+`interview-answer` with the server-returned question, request, and CAS values.
+Resume from the returned next question, preserve unaffected confirmed answers,
+and proceed directly to final confirmation when there are zero questions.
+`commit-contracts` publishes only after the user approves the exact final
+digest; never self-approve.
+
+Long-lived sessions must surface this tool-result notice even if boot
+instructions are stale. The five-MCP-tool/seven-skill surface and read-only
+status contract remain unchanged.

package/assets/skills/template/SKILL.md

@@ -7,15 +7,24 @@ description: Design, migrate, and safely apply vault-resident Obsidian templates
 
 Turn the user's natural-language note design into an actual Obsidian Markdown template and the smallest matching policy change. People and agents follow the same template contract; never introduce personas.
 
-## Authority
+## Authority and source scope
 
 - The actual `.md` template owns frontmatter order/default scaffolding and body shape.
 - `.obsidian/types.json` is read-only property-type authority.
 - The user-owned ontology remains active: `.oms/template-policy.json` owns note/field `intent` plus BaseContract inheritance, requiredness, formats, allowed values, naming, stable identity, and bindings.
 - `.oms/taxonomy.json` owns folder/link `intent`, note placement, and global axes.
 - `.oms/types.json` is derived state. Never edit it directly.
+- Every `.md` beneath an explicitly selected template folder is a template candidate. The source bytes stay at their existing vault-relative path; contract review reads and verifies them but does not rewrite them.
+- Selecting a folder is the only scope-widening act. A candidate does not need a per-file registration step or a folder mode.
 
-Use an existing stable `templateId` when updating or moving a template. A path or digest change never creates a new identity. New OMS-managed templates default to `<sourceFolder>/<templateId>.md` inside a registered template folder (the folder marked `default: true` unless you name another registered folder); registered existing templates keep their explicitly verified `sourcePath`.
+Use an existing stable `templateId` when updating or moving a template. A path or digest change never creates a new identity; the server derives an ID for a newly discovered source. For note creation, choose a destination in this order: an explicit caller folder, the taxonomy default for that template, then `ask`. Placement is not a contract-review prerequisite and there is no implicit Inbox fallback.
+
+## Derived contracts
+
+OMS derives both parts of the contract from the selected source:
+
+- The metadata contract records frontmatter keys, types, requiredness, and `filledBy`. Unknown frontmatter and policy extensions remain preserved.
+- The body-format contract records supported nodes: ATX headings, fenced code blocks, contiguous ordered or unordered list runs outside fences, and the `<!-- oms:content -->` placeholder. It also records document order, EOL, BOM, and final-newline details. This bounded scanner does not claim to enforce paragraphs, setext headings, or all Markdown; an ambiguous source fact becomes an interview question rather than an inferred rule.
 
 ## Renderers
 
@@ -27,16 +36,35 @@ Every binding carries `renderer`. Obsidian renders; OMS validates.
 
 You may **propose** an `obsidian-core` copy of a Templater template when the mapping is exact: `tp.date.now("FMT")` -> `{{date:FMT}}` / `{{time:FMT}}`, `tp.file.title` -> `{{title}}`. Anything else has no faithful mapping; do not invent one. Submit the converted bytes as a new template through the guarded flow; the kernel validates syntax, contract, path, signatures, and CAS, and the user approves the digest.
 
+## Source-change notice and interview
+
+A selected-folder source census detects pending adds, edits, deletes, and renames. The first displayed notice is exactly:
+
+```text
+템플릿에 변경이 있습니다
+```
+
+It has exactly `확인하기` and `나중에` actions. Do not render a template name, hash, or change taxonomy in that initial notice. A machine `templateNotice` may carry richer state for the host, but the host must keep the first display generic.
+
+- `나중에` is host-only: dismiss or defer locally. Do not call the server or mutate the interview ledger.
+- `확인하기` starts the one linear interview with `write { op: "template", mode: "interview-next" }`.
+- Submit each answer with `mode: "interview-answer"` using the question, request, and CAS values returned by the server. Do not invent parameter names, questions, or digests.
+- Resume from the next question returned by each answer. Opening a new review reopens deferred deletion decisions without editing the draft or erasing other confirmed answers. This is distinct from host-only `나중에`; a zero-question response still requires final confirmation.
+- After every required question is answered, show the server's final proposal and exact final approval digest. Call `mode: "commit-contracts"` only after the user approves that exact digest; never self-approve.
+
+Long-lived hosts must surface `templateNotice` on `write`, `search`, and `status` results even when boot instructions are stale. Emit it once per process and pending digest (and again when that digest changes); `status` remains the polling view and writes nothing.
+
 ## Workflow
 
-1. Read `search { op: "templates" }` to list bindings, or `search { op: "templates", templateId }` to show one, then read the user's requested shape. Use `search { op: "template-scan" }` for candidates. Do not guess existing IDs or fields, and never auto-register a scan result.
+1. Read `search { op: "templates" }` to list bindings, or `search { op: "templates", templateId }` to show one. Use `search { op: "template-scan" }` for the read-only census and pending view; never treat that view as a write.
 2. Draft the exact Markdown and policy/taxonomy intent. Preserve unknown frontmatter, policy extensions, body bytes, and Obsidian property types.
-3. Call `write { op: "template", ..., dryRun: true }` for create, update, reclassify, relocate-folder, register-folder, remove, or default. Regeneration is not a write-template mode: use `doctor { op: "regenerate-types", dryRun: true }`. Current signatures are derived and verified by the server, not hand-assembled by the host.
-4. To adopt a template that already exists in the vault, call `write { op: "template", mode: "register-existing", templateId, sourceFolder, sourcePath, renderer, filledBy, contract, naming, dryRun: true }` instead. `filledBy` lists Obsidian-filled field names (an empty array for a Core template). The server verifies the proposed metadata against the source and derives every signature itself; you supply no `expected*` digests and no template bytes.
-5. Show the proposal, paths, diagnostics, and `approvalDigest` to the user.
-6. Apply only after the caller explicitly approves that exact digest. Submit the same request with `dryRun: false` and `approvedDigest`.
-7. Report the server-verified receipt and postconditions.
+3. Use guarded template operations with a dry run for source authoring and for separate update, move, remove, reclassify, relocate, folder-scope, or default changes. Explicit source authoring is `oms template add --id <id> --from <source>`; it is not contract review. Contract review never writes source bytes. Current signatures are derived and verified by the server, not hand-assembled by the host.
+4. Show the proposal, paths, diagnostics, and `approvalDigest` to the user. Apply a guarded operation only after the caller explicitly approves that exact digest, then report the server-verified receipt and postconditions.
+
+CLI uses the noun leaves `oms template scan|list|show|add|update|move|remove|default|check|regenerate-types|review|answer|commit`.
 
-CLI uses the noun leaves `oms template scan|list|show|add|update|move|remove|default|check|regenerate-types`. Mutations require `--dry-run`, then the same request with `--yes --approved-digest`; resume uses `oms template update --resume` with the exact `transactionId` and `approvedDigest`. `add <folder>` registers a source folder; `add <file> --id` registers existing bytes; `add --id --from` proposes a new source inside an explicitly registered creation folder. `default <id>` chooses the default note binding, not the source creation folder. Removal keeps registered-existing files; `--delete-source` applies only to managed sources. Never remove the current default without selecting another binding first.
+- `oms template add <folder>` adds an explicit source scope; `oms template add --id <id> --from <source>` authorizes new source authoring.
+- `oms template review`, `answer`, and `commit` are the exact CLI counterparts of MCP `interview-next`, `interview-answer`, and `commit-contracts`.
+- `scan` is read-only. Update, move, remove, and other template mutations remain separate guarded operations; none is a substitute for contract review.
 
-Reject unsupported expressions, unsafe paths, unresolved legacy mappings, stale signatures, and identity changes. Preserve non-observed proposal gaps explicitly. Never self-approve, silently fall back to a legacy Concept reader, or directly mutate managed template/control files.
+Reject unsupported expressions, unsafe paths, stale signatures, and identity changes. Preserve non-observed proposal gaps explicitly. Never self-approve, use a stale-contract fallback or compatibility reader, or directly mutate managed template/control files.