oh-my-second-brain 0.12.2 → 0.14.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.12.2",
+      "version": "0.14.0",
       "author": {
         "name": "gobeumsu",
         "email": "gobeumsu@gmail.com"
@@ -37,5 +37,5 @@
       ]
     }
   ],
-  "version": "0.12.2"
+  "version": "0.14.0"
 }

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "oms",
-  "version": "0.12.2",
-  "description": "Oh My Second Brain convention layer for Obsidian vaults — capture, retrieve, and validate knowledge under a declared semantic convention.",
+  "version": "0.14.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,8 +1,8 @@
 {
   "name": "oms",
-  "version": "0.12.2",
+  "version": "0.14.0",
   "description": "Oh My Second Brain convention layer for Obsidian vaults — Codex native rules, skills, and MCP adapter.",
-  "_note": "oms install writes Codex MCP config, installs ~/.codex/rules/oms.md, and installs ~/.codex/skills/oms-*.",
+  "_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/",
   "mcpServers": "./.mcp.codex.json"
 }

package/.mcp.codex.json

@@ -3,6 +3,7 @@
     "oms": {
       "command": "oms",
       "args": [
+        "serve",
         "mcp",
         "--vault",
         "."

package/.mcp.json

@@ -2,7 +2,7 @@
   "mcpServers": {
     "oms": {
       "command": "oms",
-      "args": ["mcp"]
+      "args": ["serve", "mcp"]
     }
   }
 }

package/CHANGELOG-assets.md

@@ -4,6 +4,16 @@ Skills, agents, templates, and host guidance changes belong here.
 
 ## [Unreleased]
 
+## [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)
+- Template and write guidance share the guarded CLI/MCP verbs and distinguish default note bindings from source-folder creation defaults. (#124)
+- Status guidance distinguishes permanent external observation history from vault-owned convention files and avoids claiming inactivity from missing events. (#123)
+- **Template and write skills distinguish external renderers from OMS note creation.** (#122) Hosts propose converted copies or observed contracts for user approval; the kernel validates them without executing scripts. Guidance explains missing Obsidian-filled values, external-body refusals, and unobserved contracts.
+## [0.13.0] - 2026-09-05
+
+- **The npm package now ships a generated root `skills/` mirror of the single authored `assets/skills/` source for Gajae-Code, whose convention scan previously found zero OMS skills silently.**
+
 ## [0.12.2] - 2026-09-01
 
 ## [0.12.1] - 2026-09-01

package/CHANGELOG-cli.md

@@ -4,6 +4,21 @@ Changes to the `oms` command surface belong here.
 
 ## [Unreleased]
 
+## [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)
+- **CLI operations now have explicit, non-overlapping families.** (#125) `note`, `template`, `link`, `bridge`, `search`, `index`, `graph`, `host`, `package`, `model`, `serve`, `hook`, and `status` retain real capabilities without retired aliases. Package updates no longer force host synchronization; read-only health and server startup do not create a vault store.
+- **The template command family exposes guarded convention management.** (#124) Inspect, scan, register, create, update, move, remove, check, and select default bindings through shared kernel operations. Mutations require a reviewed dry-run digest rather than direct vault edits.
+
+- **Breaking: `oms setup --template-folder <path>` is repeatable and template folders are always selected explicitly.** (#120) Repeated paths are registered in `auto` scan/proposal mode, with the first explicit path becoming the template-creation default (separate from the note `defaultTemplate`). Without flags, setup reuses saved v3 folder registrations only; Obsidian and Templater settings are displayed as numbered dry-run candidates but are never selected automatically. An unresolved selection is blocked with `TEMPLATE_FOLDER_SELECTION_REQUIRED` and no approval digest.
+- **Setup dry-runs now expose `diagnostics` and `starterTemplates` instead of failing at the first incompatible file.** (#121) Each excluded template names its error, path, field when applicable, and remediation, while compatible files remain reviewable; an all-incompatible selection is blocked with `TEMPLATE_CANDIDATE_INCOMPATIBLE`. When the selected default folder is empty, `starterTemplates` shows the proposed `note.md`, which is written only by an approved apply.
+- **Doctor now reports template drift one file at a time.** (#121) Every `TEMPLATE_SOURCE_DRIFT` result includes the path, expected and actual SHA-256 signatures, remediation, and the registered template ID when available, making `regenerate-types` review specific rather than generic.
+
+## [0.13.0] - 2026-09-05
+
+- **`oms doctor` now verifies Claude hook events plus the managed Codex and Hermes MCP registrations, preserving unreadable or syntactically malformed registration evidence as explicit inspection errors.**
+- **`oms doctor` now reports structured and text install-asset health, naming dangling Claude hook symlinks with the reinstall command instead of allowing a silent command-not-found failure at tool time.**
+
 ## [0.12.2] - 2026-09-01
 
 ## [0.12.1] - 2026-09-01

package/CHANGELOG-kernel.md

@@ -4,6 +4,30 @@ Domain logic changes belong here.
 
 ## [Unreleased]
 
+## [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 installation is independent of host registration synchronization, preserving a clear upgrade boundary instead of invoking a retired reconciliation command. Read-only entrypoints continue to resolve existing stores or ephemeral cores without creating vault state. (#125)
+- **Folder registration, binding removal, and default selection share template transaction safeguards.** (#124) Server-derived current signatures, exact approval and readback protect every mode. Existing source files survive binding removal; only explicit deletion of managed sources is permitted. Note creation uses an explicitly declared default binding when no ID is supplied, never the first available template.
+- **Runtime template and note observations are retained outside the vault.** (#123) A host-and-vault-scoped SQLite journal preserves individual invocation and mutation events without note bodies, keeps unknown external change times explicit, and never participates in approval digests. Authoritative contracts are reverified on use rather than trusted for a fixed number of days; logging failures remain visible without undoing successful writes. Completed transactions remove staging payloads while retaining replay evidence.
+- **Template renderer contracts distinguish OMS-renderable sources from external Obsidian templates.** (#122) Templater fields require caller-supplied values instead of copying raw tags, and external bodies are rejected. Script-first sources can propose contracts from existing notes with sample counts and field coverage; missing observations are reported as unobserved. Source and sample limits fail visibly rather than silently truncating proposals; OMS never executes or transpiles Templater scripts.
+- **Breaking: template policy v3 replaces singular `templateFolder` with structured `templateFolders` registrations.** (#120) Each folder records `path`, `auto|manual` mode, and at most one template-creation default; template bindings retain their source folder, while note placement remains explicit JSON taxonomy authority through the separate `defaultTemplate`. The runtime no longer invents an `Inbox` or template directory, and unsupported older policy versions stay protected and fail closed while setup produces an explicit v3 proposal.
+- **Template discovery now reports incompatible files without hiding compatible siblings.** (#121) Setup emits per-file `TEMPLATE_EXPRESSION_UNSUPPORTED`, `TEMPLATE_SOURCE_INVALID`, and `TEMPLATE_ID_DUPLICATE` diagnostics with the affected path, field when applicable, and remediation; only the named file is excluded, while a selection with no compatible candidates is blocked as `TEMPLATE_CANDIDATE_INCOMPATIBLE`. Proposed IDs also remove `.template` and `.eta` suffixes before slugging, so common template filenames keep useful stable identities.
+- **Obsidian core formatted date and time tags are validated instead of rejected as unknown expressions.** (#121) `{{date:FMT}}` and `{{time:FMT}}` accept the tokens `YYYY YY MM M DD D HH H hh h mm m ss s A a` with `-`, `/`, `.`, `:`, space, or `T` separators; bracket literals remain unsupported. Date and datetime properties containing these tags no longer produce false type-conflict diagnostics.
+- **Template source drift is now actionable per changed file.** (#121) Doctor reports one `TEMPLATE_SOURCE_DRIFT` item per changed authority or registered template, including its template ID when available, path, projected and actual SHA-256 signatures, and regeneration remediation, so independent changes are no longer collapsed into one generic failure.
+- **An empty selected default template folder now yields an explicit starter proposal.** (#121) Setup dry-runs include the starter `note.md` and diagnostics without writing the vault; the starter is created only after approval through the same guarded transaction as the rest of setup.
+
+## [0.13.0] - 2026-09-05
+
+- **Replaying an identical completed template registration now returns a verified `already-complete` receipt instead of failing, while conflicting template IDs remain rejected.** Replay recomputes the canonical input and every current physical output, including every registered source, before accepting the completed marker; any drift requires a new dry-run. Template input authority construction is shared by registration, resolution, and repair to prevent digest drift.
+- **Axis-query reranking now applies `minScore` once after reranking, so hit counts and facets are calculated from the same final ranked set.** Graph-neighbour priority is now expressed as reason-count then lexical-score ordering, rather than a unit-dependent weighted scalar.
+- **Install asset health now classifies vendor-neutral host evidence injected by the CLI, including explicit inspection errors rather than mistaking unreadable or corrupt registration evidence for an absent installation.**
+- **Axis-narrowed search now ranks with a continuous coverage score, using title, declared-axis, and term-specificity signals to resolve equal coverage instead of integer token-count ties and alphabetical paths.** Zero-score padding is refused, and `minScore` filters hits and facets identically. Scores are now fractional: a previously meaningful `minScore: 1` ("at least one token") effectively requires perfect coverage, so callers must re-tune thresholds.
+- **Install asset health inspection now classifies missing, non-executable, and dangling hook symlinks explicitly, and validates generic skill-tree digests and recorded source versions against injected provenance evidence.**
+- **Template policies can declare a user-owned writer registry in `.oms/template-policy.json`.** Agent writes with an unregistered writer identifier are refused at admission; vaults without a `writers` block are unaffected. Active registries require policy `version: 2`: migrate a v1 policy by setting `version` to `2` and retaining or adding its `writers` block.**
+- **The exported template-policy JSON Schema now treats `writers` as a preserved extension for v1 policies and validates the managed writer registry only for v2 policies.**
+- **An existing vault template can be registered in place and have its OMS contract derived from the file itself.** The kernel reads the Markdown template as the shape authority — frontmatter key order, literal and token defaults, body scaffold and body signature, supported template expressions — and composes it with `.obsidian/types.json`, the base contract, `.oms/template-policy.json`, and `.oms/taxonomy.json` into the generated `.oms/types.json`. Semantics stay where they belong: intent, requiredness, allowed values, formats, naming, and stable identity remain user-authored policy input and are never guessed from Markdown literals, so registering against a contract you have not authored fails with `TEMPLATE_CONTRACT_UNKNOWN` instead of inventing one. Registration runs through the existing guarded transaction, so a source that changes between dry-run and apply is rejected by CAS and the user's template is verified in place rather than published.
+
 ## [0.12.2] - 2026-09-01
 
 - **Setup preserves generated taxonomy template bindings and incrementally registers newly discovered templates.** (#104)

package/CHANGELOG-mcp.md

@@ -4,6 +4,30 @@ MCP server tools and resources belong here.
 
 ## [Unreleased]
 
+## [0.14.0] - 2026-09-05
+
+### Changed
+
+- Conflicting index mutations are serialized within each MCP server through engine disposal, so repair cannot move a store still owned by another request. A failed close returns `ENGINE_LIFECYCLE_FAILED` and blocks further index mutations until server restart; read-only requests remain independent. (#125)
+- `status { op: "graph" }` returns graph-only health, while omitted `op` retains aggregate health. Doctor `sync-embeddings` repair mode requires `repairMode: "rebuild"` or `"drop"`, matching CLI store repair rather than silently forcing embeddings. (#125)
+- **MCP detail capabilities have exclusive operation and mode boundaries.** (#125) Document lookup, index views, template inspection and embedding synchronization no longer overlap through duplicate operations or booleans. All capabilities remain under the same five tools, with schema and dispatch validated together.
+- Template operations include guarded `register-folder`, `remove`, and `default` modes, with current signatures derived by the server. Update move strategies are validated consistently; note creation may omit its ID only when a default binding is declared. No additional MCP tool is introduced. (#124)
+- Status and template listings expose local runtime observation history separately from the vault contract. Missing observations are reported as gaps, not inactivity; reading history never creates a vault store. (#123)
+- Template writes respect renderer and Obsidian-filled field contracts, rejecting external bodies and unresolved values without copying raw Templater tags. The five-tool surface and digest-approved transaction boundary are unchanged. (#122)
+- The search receipt field `drift` was renamed to `indexDrift`; no compatibility alias is retained.
+- **`write { op: "template", mode: "register-existing" }` now requires `sourceFolder` together with `sourcePath`.** The folder must be a registered v3 template source folder containing the existing Markdown file. This keeps template source identity distinct from taxonomy note placement while retaining the existing dry-run, approval-digest, and compare-and-swap flow. The MCP surface remains exactly five public tools.
+
+## [0.13.0] - 2026-09-05
+
+### Added
+
+- **`write { op: "template", mode: "register-existing" }` registers a template that already lives in your vault.** Point it at a vault-relative Markdown path with an explicit stable `templateId`, the contract you authored, and a naming rule; the server reads the file as the shape authority and derives every control and source signature itself, so you no longer hand-assemble four expected digests and re-send the template's own bytes to register a file that is already on disk. The dry-run → `approvalDigest` → apply contract and its CAS checks are unchanged, and the source template is verified in place — never copied, rewritten, moved, or renamed. Re-registering an identical binding is refused as `TEMPLATE_ALREADY_REGISTERED` rather than a bare identity collision.
+
+### Changed
+
+- **`status.writeTools` response values were renamed from `oms_write-*` to `write-*` with the capability-only tool surface.** Raw MCP clients that consume this diagnostic field must migrate those response strings alongside the five public tool names.
+- **MCP local tool names are now capability-only.** The `oms` server advertises `write`, `search`, `link`, `status`, and `doctor`, so qualifying hosts display `oms_write`, `oms_search`, `oms_link`, `oms_status`, and `oms_doctor` rather than `oms_oms_*`. Raw MCP callers must migrate `oms_write` → `write`, `oms_search` → `search`, `oms_link` → `link`, `oms_status` → `status`, and `oms_doctor` → `doctor`.
+
 ## [0.12.2] - 2026-09-01
 
 ## [0.12.1] - 2026-09-01

package/CHANGELOG-vendors.md

@@ -4,6 +4,21 @@ Per-host adapter and installer changes belong here.
 
 ## [Unreleased]
 
+## [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)
+## [0.13.0] - 2026-09-05
+
+- **The shipped GJC skills mirror is now checked file-for-file against authored skills, with drift failures directing contributors to `npm run sync:skills`.**
+
+### Changed
+
+- **Supported host guidance now names the single-qualified OMS tools.** Hermes, Claude, and Codex users see `oms_write`, `oms_search`, `oms_link`, `oms_status`, and `oms_doctor`, never `oms_oms_*`; raw MCP integrations must replace local calls `oms_write`/`oms_search`/`oms_link`/`oms_status`/`oms_doctor` with `write`/`search`/`link`/`status`/`doctor`.
+
+### Added
+
+- **Gajae-Code now has a marketplace-plugin skill channel at the package-root `skills/` convention path; previously it installed OMS successfully while silently discovering zero skills.**
+
 ## [0.12.2] - 2026-09-01
 
 ## [0.12.1] - 2026-09-01

package/CHANGELOG.md

@@ -10,6 +10,15 @@ This aggregate changelog contains changes that span multiple layers.
 
 ## [Unreleased]
 
+## [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`.
+## [0.13.0] - 2026-09-05
+
+- **Breaking: the OMS namespace now renders exactly once. Tools appear as `oms_write`, not `oms_oms_write`.** The server was registered under the id `oms` while its tools were *also* named `oms_write`, `oms_search`, `oms_link`, `oms_status`, and `oms_doctor`, so every host that qualifies a tool as `<server>_<tool>` displayed the product namespace twice — Hermes showed `oms_oms_write`, internally `mcp__oms__oms_write`. The MCP-local names are now capability-only: `write`, `search`, `link`, `status`, `doctor`. Qualifying hosts render `oms_write` and its peers; Claude and Codex render `mcp__oms__write`. This spans layers deliberately — the tool surface, the bundled skills' `mcp_tool` values, the host manifests, and every piece of host guidance moved together, so there is one coherent five-capability surface and no aliases. **Raw MCP clients must migrate**: `oms_write` → `write`, `oms_search` → `search`, `oms_link` → `link`, `oms_status` → `status`, `oms_doctor` → `doctor`, and the `status.writeTools` response strings from `oms_write-*` → `write-*`. Hosts that qualify tool names need no change. The demoted operations behind `op` are untouched, and a parity gate now fails the build if any advertised tool name carries the `oms_` prefix or if a supported host would render a doubled namespace. (#107)
+
+- **The shipped dependency tree no longer carries known advisories.** `npm run audit` had begun failing on every pull request for a reason none of them introduced: `fast-uri` picked up four host-confusion and SSRF advisories across its whole `3.x` range, and `qs` two more through Express. Both are pinned forward through the existing `overrides` block — `fast-uri` to `^4.1.4` and a new `qs` pin to `^6.16.0` — so the audit gate reports zero vulnerabilities and CI can tell a real regression from inherited noise again.
+
 ## [0.12.2] - 2026-09-01
 
 ### Fixed

package/README.ko.md

@@ -27,34 +27,46 @@ oms setup --vault /path/to/vault --yes --approved-digest <표시된-digest>
 ## CLI
 
 ```text
-oms setup      기존 볼트 템플릿 탐색 및 채택
-oms install    호스트 어댑터와 관리형 MCP 등록 설치
-oms uninstall  호스트 어댑터와 관리형 MCP 등록 제거
-oms update     패키지 업데이트 확인/적용 후 어댑터 재조정
-oms reconcile  엄격한 전역 볼트 포인터로 호스트 재기록
-oms doctor     템플릿 권위와 파생 상태 진단
-oms lint       깨진 [[wikilink]]와 고아 노트 점검
-oms search <text>  일반 lexical 검색; --vec, --hyde, --expand, --max-queries 1..32, --rerank은 명시적 선택
-oms embed      색인된 노트의 임베딩 생성
-oms index sync|status|repair|cleanup|collections|contexts
-oms doc get|multi-get
-oms serve      로컬 검색 HTTP 서버 시작
-oms mcp        stdio MCP 서버 시작
-oms hook       Claude pre/post tool-use 볼트 가드 실행
+oms setup                                      기존 볼트 템플릿 탐색 및 채택
+oms template scan|list|show|add|update|move|remove|default|check|regenerate-types
+oms note create|append|update|audit|backfill|get
+oms link check|suggest|apply                   노트 wikilink 점검·제안·적용
+oms bridge add|remove|status                   저장소-볼트 target bridge 관리
+oms search query|context                       명시적 query 실행 또는 구조화 context 조회
+oms index sync|embed|repair|status|clean       파생 검색 상태 관리
+oms graph build|status                         노트 그래프 생성 또는 조회
+oms host install|remove|sync|status            호스트 asset과 MCP 등록 관리
+oms package check|update                       OMS 패키지 확인 또는 업데이트
+oms model install|select|waive|status          로컬 모델 선택 관리
+oms serve mcp|http                             stdio MCP 또는 로컬 HTTP 서버 시작
+oms hook pre|post                              pre/post-tool-use 볼트 가드 실행
+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으로 종료하고
 부작용을 수행하지 않는다. 알 수 없는 명령에 `--help`를 함께 주면 exit 1로 종료한다.
 
-`oms search <text>`는 lexical-only다. `--vec`, `--hyde`는 각각의 typed
-channel을 선택하고, `--expand`는 G004 expansion을 명시적으로 켜며,
-`--max-queries`는 1부터 32까지의 정수만 받는다. `--rerank`도 opt-in이다.
-`oms embed`가 유일한 embedding 명령이며 `oms index`에는 embedding
-subcommand가 없다.
+`oms search query <text>`는 lexical-only다. `--vec`, `--hyde`는 각각의
+typed channel을 선택하고, `--expand`는 G004 expansion을 명시적으로
+켜며, `--max-queries`는 1부터 32까지의 정수만 받는다. `--rerank`도
+opt-in이다. `oms search context`는 별도의 구조화 context 표면이다.
+Embedding은 명시적으로 `oms index embed`를 사용하며 sync와 repair는
+서로 다른 index mode다. `oms index status --view status|collections|contexts`는
+세 읽기 전용 view를 모두 보존하고, `oms index clean`은 제거 가능한 파생
+상태를 정리한다.
 
 Vector 검색에는 검증된 로컬 embedding capability가 필요하다. 선택 경로는
 완전한 `OMS_EMBEDDING_PROVIDER`/`OMS_EMBEDDING_MODEL` 쌍, vault의
@@ -71,9 +83,9 @@ Setup에서는 로컬 검증 acquisition 정책 하나를 선택한다:
 
 ## MCP 도구
 
-`oms mcp`는 정확히 다섯 개의 공개 도구를 노출한다:
+`oms serve mcp`는 정확히 다섯 개의 공개 도구를 노출한다:
 
-`oms_write` · `oms_search` · `oms_link` · `oms_status` · `oms_doctor`
+`write` · `search` · `link` · `status` · `doctor`
 
 일곱 스킬(`write`, `search`, `link`, `distill`, `status`, `doctor`, `template`)은 워크플로 안내이며 MCP 도구와 같은 집합이 아니다. 세부 기능은 다섯 도구의 `op` 값으로 제공한다.
 
@@ -87,10 +99,23 @@ Node.js 20 이상이 필요하다.
 
 ```bash
 npm install -g oh-my-second-brain
-oms install --runtime all --vault /path/to/vault --yes
+oms host install --runtime all --vault /path/to/vault --yes
 ```
 
-호스트 설치는 canonical 볼트를 `${XDG_CONFIG_HOME:-~/.config}/oms/vault.json`에 기록하고 각 관리형 등록에 `oms mcp --vault /path/to/vault`를 넣는다. `install`, `update`, `reconcile`, `uninstall`만 이 서명된 포인터를 호스트 stamp 관리에 사용한다. 런타임 쓰기·검색 target 해석은 포인터를 읽지 않으며 명시적 target, 로컬 볼트 control, bridge, `OMS_VAULT`, 읽기 전용 cwd fallback 순서를 유지한다.
+Gajae-Code에서는 npm 패키지를 marketplace plugin으로 설치한다: `gjc plugin install oms@oms`. GJC는 패키지 루트의 `skills/` convention path에서 일곱 OMS skill을 발견한다.
+
+호스트 설치는 canonical 볼트를
+`${XDG_CONFIG_HOME:-~/.config}/oms/vault.json`에 기록하고 각 관리형
+등록에 `oms serve mcp --vault /path/to/vault`를 넣는다.
+`oms host install|remove|sync|status`만 이 서명된 포인터로 호스트 통합을
+관리한다.
+`oms package update`는 패키지만 업데이트하고 호스트를 암묵적으로
+동기화하지 않는다. `oms host sync`는 별도로 실행한다.
+
+런타임 쓰기·검색 target 해석은 호스트 관리 포인터를 읽지 않는다.
+우선순위는 명시적 target, 로컬 볼트 control, bridge, `OMS_VAULT`, 그리고
+안전한 읽기 전용 fallback으로서의 cwd 순서다. 변경 작업은 cwd fallback을
+사용할 수 없다.
 
 `OMS_VAULT`는 명시적·로컬·bridge target이 없을 때 사용하는 지원 환경변수 fallback이다.
 

package/README.md

@@ -27,33 +27,44 @@ Managed-template changes use the same dry-run, exact caller approval, compare-an
 ## CLI
 
 ```text
-oms setup      Discover and adopt existing vault templates
-oms install    Install host adapters and managed MCP registration
-oms uninstall  Remove host adapters and managed MCP registration
-oms update     Check/apply a package update and reconcile adapters
-oms reconcile  Re-stamp hosts from the strict global vault pointer
-oms doctor     Diagnose template authority and derived state
-oms lint       Check broken [[wikilinks]] and orphan notes
-oms search <text>  Plain lexical search; --vec, --hyde, --expand, --max-queries 1..32, and --rerank are explicit
-oms embed      Generate embeddings for indexed notes
-oms index sync|status|repair|cleanup|collections|contexts
-oms doc get|multi-get
-oms serve      Start the local search HTTP server
-oms mcp        Start the stdio MCP server
-oms hook       Run Claude pre/post tool-use vault guards
+oms setup                                      Discover and adopt existing vault templates
+oms template scan|list|show|add|update|move|remove|default|check|regenerate-types
+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
+oms search query|context                       Run an explicit query or retrieve structured context
+oms index sync|embed|repair|status|clean       Manage derived search state
+oms graph build|status                         Build or inspect the note graph
+oms host install|remove|sync|status            Manage host assets and MCP registrations
+oms package check|update                       Check or update the OMS package
+oms model install|select|waive|status          Manage local model selection
+oms serve mcp|http                             Start the stdio MCP or local HTTP server
+oms hook pre|post                              Run pre- or post-tool-use vault guards
+oms status                                     Show the read-only aggregate status
 ```
 
 `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
 side effects. An unknown command combined with `--help` exits 1.
 
-`oms search <text>` is lexical-only. `--vec` and `--hyde` select their respective
-typed channels; `--expand` explicitly enables G004 expansion, `--max-queries`
-accepts an integer from 1 through 32, and `--rerank` is opt-in. `oms embed` is
-the sole embedding command; `oms index` has no embedding subcommand.
+`oms search query <text>` is lexical-only. `--vec` and `--hyde` select their
+respective typed channels; `--expand` explicitly enables G004 expansion,
+`--max-queries` accepts an integer from 1 through 32, and `--rerank` is opt-in.
+`oms search context` is the separate structured-context surface. Embedding is
+explicitly `oms index embed`; sync and repair are distinct index modes.
+`oms index status --view status|collections|contexts` preserves all three
+read-only views, while `oms index clean` removes eligible derived state.
 
 Vector search requires a verified local embedding capability, selected by a
 complete `OMS_EMBEDDING_PROVIDER`/`OMS_EMBEDDING_MODEL` pair, the vault's
@@ -69,9 +80,9 @@ During setup, choose one local verified acquisition policy:
 
 ## MCP tools
 
-`oms mcp` exposes exactly five public tools:
+`oms serve mcp` exposes exactly five public tools:
 
-`oms_write` · `oms_search` · `oms_link` · `oms_status` · `oms_doctor`
+`write` · `search` · `link` · `status` · `doctor`
 
 The seven skills (`write`, `search`, `link`, `distill`, `status`, `doctor`, `template`) are workflow guidance, not a tool-equality list. Detail capabilities remain `op` values under the five tools.
 
@@ -85,10 +96,17 @@ Node.js 20 or later is required.
 
 ```bash
 npm install -g oh-my-second-brain
-oms install --runtime all --vault /path/to/vault --yes
+oms host install --runtime all --vault /path/to/vault --yes
 ```
 
-Host installation records the canonical vault in `${XDG_CONFIG_HOME:-~/.config}/oms/vault.json` and stamps `oms mcp --vault /path/to/vault` into each managed host entry. `install`, `update`, `reconcile`, and `uninstall` use that signed pointer only to maintain host stamps. Runtime write/search target resolution never reads it and keeps this precedence: explicit target, local vault controls, bridge, `OMS_VAULT`, then read-only cwd fallback.
+For Gajae-Code, install the npm package as a marketplace plugin: `gjc plugin install oms@oms`. GJC discovers the seven OMS skills at the package-root `skills/` convention path.
+
+Host installation records the canonical vault in `${XDG_CONFIG_HOME:-~/.config}/oms/vault.json` and stamps `oms serve mcp --vault /path/to/vault` into each managed host entry. `oms host install|remove|sync|status` use that signed pointer only to maintain host integrations. `oms package update` updates the package but never syncs hosts implicitly; run `oms host sync` separately.
+
+Runtime write/search target resolution never reads the host-maintenance pointer.
+Its precedence is explicit target, local vault controls, bridge, `OMS_VAULT`,
+then cwd only as a safe read-only fallback. Mutations cannot use the cwd
+fallback.
 
 `OMS_VAULT` is the supported environment fallback when no explicit, local, or bridge target exists.
 

package/assets/claude/hooks/oms-guard.mjs

@@ -3,7 +3,7 @@
  * oms-guard — thin PreToolUse wrapper for Claude Code settings.json.
  *
  * Filters vault-relevant Write/Edit tool calls and delegates to
- * `oms hook pre-tool-use --vault <vault>` only when the target path is
+ * `oms hook pre --vault <vault>` only when the target path is
  * inside a configured vault. Vault 무관 호출은 spawn 없이 즉시 통과.
  *
  * Configuration (env vars set by the settings.json hook definition):
@@ -103,12 +103,12 @@ async function main() {
   );
   if (!targetVault) { allow(); return; }
 
-  // Spawn `oms hook pre-tool-use --vault <vault>` with the raw stdin payload.
+  // Spawn `oms hook pre --vault <vault>` with the raw stdin payload.
   try {
     const { cmd, prefix } = resolveOmsCommand();
     const result = spawnSync(
       cmd,
-      [...prefix, "hook", "pre-tool-use", "--vault", targetVault],
+      [...prefix, "hook", "pre", "--vault", targetVault],
       { input: rawInput, encoding: "utf-8", timeout: 10000 },
     );
     if (result.status === 0 && result.stdout && result.stdout.trim()) {

package/assets/claude/hooks/oms-post-guard.mjs

@@ -3,8 +3,8 @@
  * oms-post-guard — thin PostToolUse wrapper for Claude Code settings.json.
  *
  * Filters vault-relevant Write/Edit completions and delegates to
- * `oms hook post-tool-use --vault <vault>` for frontmatter audit and
- * graph cache debounce. Vault 무관 호출은 spawn 없이 즉시 통과.
+ * `oms hook post --vault <vault>` for advisory frontmatter audit.
+ * Vault 무관 호출은 spawn 없이 즉시 통과.
  *
  * Configuration (env vars set by the settings.json hook definition):
  *   OMS_VAULT        — primary vault path
@@ -92,16 +92,16 @@ async function main() {
     const { cmd, prefix } = resolveOmsCommand();
     const result = spawnSync(
       cmd,
-      [...prefix, "hook", "post-tool-use", "--vault", targetVault],
+      [...prefix, "hook", "post", "--vault", targetVault],
       { input: rawInput, encoding: "utf-8", timeout: 30000 },
     );
-    // Forward any additionalContext output from the post-tool-use hook.
+    // Forward any additionalContext output from the post hook.
     if (result.status === 0 && result.stdout && result.stdout.trim()) {
       process.stdout.write(result.stdout);
     }
     if (result.stderr) process.stderr.write("[oms-post-guard] " + result.stderr);
   } catch {
-    // Fail silently — post-tool-use is advisory.
+    // Fail silently — the post hook is advisory.
   }
 }
 

package/assets/codex/AGENTS.md

@@ -18,4 +18,4 @@ The vault is governed by user-owned template conventions in `.oms/`.
 
 **Maintain:** `$oms-status` is read-only. `$oms-doctor` diagnoses and performs explicit repairs.
 
-`oms install --runtime codex` installs seven skills: `$oms-write`, `$oms-search`, `$oms-link`, `$oms-distill`, `$oms-status`, `$oms-doctor`, and tool-less `$oms-template`, plus managed MCP configuration.
+`oms host install --runtime codex` installs seven skills: `$oms-write`, `$oms-search`, `$oms-link`, `$oms-distill`, `$oms-status`, `$oms-doctor`, and tool-less `$oms-template`, plus managed MCP configuration using `oms serve mcp`.

package/assets/codex/rules/oms.md

@@ -11,8 +11,8 @@ Actual Obsidian Markdown templates own note shape and body scaffolding. The user
 | User intent | Preferred surface |
 |---|---|
 | inspect and adopt templates | `oms setup --vault <path> --dry-run`, then `--yes --approved-digest <digest>` |
-| install host integration | `oms install --runtime codex --vault <path> --yes` |
-| diagnose or repair | `$oms-doctor` or `oms doctor --vault <path>` |
+| install host integration | `oms host install --runtime codex --vault <path> --yes` |
+| diagnose or repair | `$oms-doctor` or `oms template check --vault <path>`; repairs require an approved digest |
 | write a note | `$oms-write` / MCP `oms_write` with a stable `templateId` |
 | retrieve knowledge | `$oms-search` / MCP `oms_search`; discover IDs with `op: "templates"` |
 

package/assets/hermes/README.md

@@ -1,10 +1,10 @@
 # Oh My Second Brain Hermes Adapter
 
-Installed by `oms install --runtime hermes` into:
+Installed by `oms host install --runtime hermes` into:
 
 - `~/.hermes/skills/knowledge-management/oms/`
 - `~/.hermes/config.yaml` as `mcp_servers.oms`
 
-The skill bundle contains Oh My Second Brain's `write`, `search`, `link`, `distill`, `status`, and `doctor` skills and uses the Oh My Second Brain MCP server for runtime operations.
+The shared skill bundle contains `write`, `search`, `link`, `distill`, `status`, `doctor`, and tool-less `template`; runtime operations use the five MCP tools through `oms serve mcp`.
 
-Unlike Claude Code (`claude plugin install`), Hermes exposes no native marketplace or plugin-update command, so this adapter stays OMS-managed: `oms update` reconciles it by re-running the same install path. `mcp_servers.oms` is edited surgically, leaving the rest of `~/.hermes/config.yaml` — including comments and key ordering — untouched.
+Unlike Claude Code (`claude plugin install`), Hermes exposes no native marketplace or plugin-update command, so this adapter stays OMS-managed. `oms package update` updates OMS; `oms host sync --runtime hermes` separately refreshes registrations. Neither upgrades Hermes. `mcp_servers.oms` is edited surgically, leaving the rest of `~/.hermes/config.yaml` — including comments and key ordering — untouched. Existing profiles retain their own configuration and registration scope.

package/assets/hermes-manifest.json

@@ -1,6 +1,6 @@
 {
   "name": "oms",
-  "version": "0.12.2",
+  "version": "0.14.0",
   "description": "Oh My Second Brain convention layer for Obsidian vaults — Hermes skill bundle and MCP adapter.",
-  "_note": "oms install writes ~/.hermes/config.yaml mcp_servers.oms and installs skills under ~/.hermes/skills/knowledge-management/oms/."
+  "_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/distill/SKILL.md

@@ -5,7 +5,9 @@ description: Analyze a target as read-only input and return a structured absorpt
 
 # distill
 
-Analyze a repository, document, skill, or concept as inert read-only input. This is a recipe skill; it has no backing MCP engine and does not write to the vault.
+Analyze a repository, document, skill, or concept as inert read-only input. This
+is a host recipe skill: it has no MCP tool or CLI command and does not write to
+the vault.
 
 ## Use when
 
@@ -17,4 +19,8 @@ Use this skill to extract reusable patterns, identify risks, and preserve attrib
 /distill <target-path-or-text>
 ```
 
-Do not execute the target. Produce a report with exactly three sections: Patterns, Risks, and Attribution. The report is the output; write it only when explicitly requested outside this skill.
+Do not execute the target, including embedded scripts or Templater expressions.
+Do not send private target content to another tool or surface unless the user
+explicitly approved that disclosure. Produce a report with exactly three
+sections: Patterns, Risks, and Attribution. The report is the output; write it
+only when explicitly requested outside this skill.

package/assets/skills/doctor/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: doctor
 description: Diagnose template authority and index problems, then run explicit repairs.
-mcp_tool: oms_doctor
+mcp_tool: doctor
 mcp_args:
   op: "validate"
 ---
@@ -19,6 +19,8 @@ Diagnose vault template and derived-index state, then run only the named repair.
 - `validate` is read-only. It reports policy/projection/source-signature drift, migration marker state, managed source exclusions, and unresolved legacy notes.
 - `regenerate-types` recomputes the derived `.oms/types.json` from actual templates, policy, taxonomy, and read-only Obsidian types.
 - `backfill-defaults` updates exactly one explicit note with stable template identity while preserving unrelated frontmatter and body bytes.
-- `build-graph`, `cleanup`, and `sync-embeddings` repair derived indexes.
+- `audit` checks notes, optionally scoped by `folder`.
+- `build-graph` and `cleanup` repair their derived indexes.
+- `sync-embeddings` requires exactly one `mode`: `sync`, `embed`, or `repair`. Repair additionally requires `repairMode: "rebuild"` or `"drop"` and accepts `dryRun`; it backs up the engine store and verifies the resulting rebuilt/absent state. It does not mean forced embedding. Do not send retired boolean `embed` or `force` switches or repair-only fields with sync/embed.
 
-Every note/control repair requires a verified target. Run a dry-run, review the receipt, then submit its exact `approvalDigest`; never self-approve or repair all notes implicitly.
+Every note/control repair requires a verified target and current authority. Run a dry-run, review the exact paths, diagnostics, and receipt, then submit its exact `approvalDigest`; never self-approve, repair all notes implicitly, edit controls directly, or treat an unobserved condition as healthy.

package/assets/skills/link/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: link
-description: Suggest or apply safe wikilinks between vault notes.
-mcp_tool: oms_link
+description: Check, suggest, or apply safe vault wikilinks without changing repository bridges.
+mcp_tool: link
 mcp_args:
   op: "suggest"
   notePath: "$1"
@@ -9,11 +9,14 @@ mcp_args:
 
 # link
 
-Suggest or apply `[[wikilinks]]` between a note and the vault's term notes.
+Check, suggest, or apply `[[wikilinks]]` between vault notes. Repository bridge
+configuration is a separate CLI-only capability.
 
 ## Use when
 
-Use `suggest` before writing or revising a note, or use `apply` to add accepted links to an existing note.
+Use CLI `oms link check` for read-only link validation. Use MCP `link` with
+`op: "suggest"` before writing or revising a note, or `op: "apply"` to add only
+accepted suggestions to an existing note.
 
 ## Usage
 
@@ -22,3 +25,9 @@ Use `suggest` before writing or revising a note, or use `apply` to add accepted
 ```
 
 Link targets are term notes only. Suggestions are surface-anchored, add at most one link per target in a body, and report ambiguous matches rather than resolving them. Applying suggestions writes through the vault write kernel and requires the suggestion's `baseContentHash` and accepted candidate IDs.
+
+`oms bridge add|remove|status` manages repository bridges and has no MCP
+operation. Do not route bridge work through `link`, and do not use retired
+command aliases. Checking and suggesting are read-only. Apply only links the
+user accepted; never infer consent from a suggestion and never expose private
+note content.