oh-my-second-brain 0.20.1 → 0.20.2

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.20.1",
+      "version": "0.20.2",
       "author": {
         "name": "gobeumsu",
         "email": "gobeumsu@gmail.com"
@@ -37,5 +37,5 @@
       ]
     }
   ],
-  "version": "0.20.1"
+  "version": "0.20.2"
 }

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "oms",
-  "version": "0.20.1",
+  "version": "0.20.2",
   "description": "Oh My Second Brain convention layer for Obsidian vaults — six shared skills and four MCP tools under a user-owned contract.",
   "author": {
     "name": "gobeumsu"

package/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "oms",
-  "version": "0.20.1",
+  "version": "0.20.2",
   "description": "Oh My Second Brain convention layer for Obsidian vaults — Codex native rules, skills, and MCP adapter.",
   "_note": "oms setup host install writes Codex MCP config and provenance, installs ~/.codex/rules/oms.md, and installs the six 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.20.2] - 2026-09-30
+
+- **The doctor skill names `oms interview` for a missing seal.** It still sent every broken or missing seal to `oms setup`, while the `contract-open` write warning and `oms doctor status` name `oms interview` for a missing contract, and `oms doctor status` names `oms doctor contract` for a tampered or unreadable store. A Hermes trial on 0.20.1 read the two routes as conflicting; the skill now matches the receipt.
+
 ## [0.20.1] - 2026-09-30
 
 - **Host guidance names `oms interview` for a missing seal.** The Claude, Codex and Hermes guidance used to send the user to `oms setup` for a broken or missing seal. A missing seal is now sealed with `oms interview`, the command the write warning names, and a broken one is checked with `oms doctor contract`.

package/CHANGELOG-cli.md

@@ -4,6 +4,8 @@ Changes to the `oms` command surface belong here.
 
 ## [Unreleased]
 
+## [0.20.2] - 2026-09-30
+
 ## [0.20.1] - 2026-09-30
 
 - **`oms write` prints the next command with its warnings.** The stderr warnings line ends with `Run: <command>` (for an unsealed vault, `Run: oms interview`).

package/CHANGELOG-kernel.md

@@ -4,6 +4,8 @@ Domain logic changes belong here.
 
 ## [Unreleased]
 
+## [0.20.2] - 2026-09-30
+
 ## [0.20.1] - 2026-09-30
 
 - **A write receipt with warnings names the command that resolves them.** The receipt gains `next`, the guidance for its first warning, so a note saved into a vault with no sealed contract (`contract-open`) now says to run `oms interview` instead of carrying only the warning kind. `next` is absent when there are no warnings, so a clean receipt is unchanged.

package/CHANGELOG-mcp.md

@@ -4,6 +4,8 @@ MCP server tools and resources belong here.
 
 ## [Unreleased]
 
+## [0.20.2] - 2026-09-30
+
 ## [0.20.1] - 2026-09-30
 
 - **`write`'s receipt carries `next`.** It is the command for the receipt's first warning (`oms interview` for an open contract) and is left out when there are no warnings.

package/CHANGELOG-vendors.md

@@ -4,6 +4,8 @@ Per-host adapter and installer changes belong here.
 
 ## [Unreleased]
 
+## [0.20.2] - 2026-09-30
+
 ## [0.20.1] - 2026-09-30
 
 ## [0.20.0] - 2026-09-30

package/CHANGELOG.md

@@ -10,6 +10,8 @@ This aggregate changelog contains changes that span multiple layers.
 
 ## [Unreleased]
 
+## [0.20.2] - 2026-09-30
+
 ## [0.20.1] - 2026-09-30
 
 ## [0.20.0] - 2026-09-30

package/assets/hermes-manifest.json

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

package/assets/skills/doctor/SKILL.md

@@ -26,7 +26,7 @@ Report vault health, diagnose the seal and derived indexes, then run only the re
 - `revert-propose` (`targetDigest`) proposes a kept generation's contract as a new forward candidate. It never rewrites history. A revert always requires owner approval: it has no maker, so every revert, tightening, neutral or loosening, waits for the owner at `oms setup` whatever the autonomy policy says, and `evolve-verdict` is refused on it (`EVOLUTION_REQUEST_CLOSED`). Stage 1 and stage 2 run when it is proposed: a revert that would add a refusal is refused with `EVOLUTION_REVERT_REFUSED`, and one that overlaps in meaning or drifts past 0.3 from the first sealed generation with `EVOLUTION_STAGE2_REFUSED`; nothing is proposed.
 - `reclaim-evolution-lock` and `lineage-reanchor` belong to the owner at a terminal; over MCP they are refused. Tell the user to run `oms doctor reclaim-evolution-lock` or `oms doctor lineage-reanchor` themselves. Requests awaiting the owner are approved or rejected only at `oms setup`, and autonomy is turned on only with `oms setup --autonomy on`.
 
-A broken or missing seal is recovered by the user running `oms setup` at a terminal; recovery is never done through the `setup` skill. The only automatic seal repair is `oms doctor contract --fix`, which re-indexes a moved or unindexed vault and nothing else. `oms doctor contract` also names the unexpected `.oms` entries for the person at the CLI.
+A missing seal is sealed by the user running `oms interview` at a terminal, the command the `contract-open` write warning names. A broken seal (a tampered or unreadable contract store) is diagnosed with `oms doctor contract` first, then resealed by the user at a terminal; recovery is never done through the `setup` skill. The only automatic seal repair is `oms doctor contract --fix`, which re-indexes a moved or unindexed vault and nothing else. `oms doctor contract` also names the unexpected `.oms` entries for the person at the CLI.
 
 Index repairs run only when explicitly requested and do not edit notes. There is no default-value backfill: OMS never rewrites a note.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "oh-my-second-brain",
-  "version": "0.20.1",
+  "version": "0.20.2",
   "description": "Oh My Second Brain: a host-agnostic, user-owned convention layer for Obsidian and plain-markdown knowledge vaults.",
   "type": "module",
   "license": "MIT",

package/skills/doctor/SKILL.md

@@ -26,7 +26,7 @@ Report vault health, diagnose the seal and derived indexes, then run only the re
 - `revert-propose` (`targetDigest`) proposes a kept generation's contract as a new forward candidate. It never rewrites history. A revert always requires owner approval: it has no maker, so every revert, tightening, neutral or loosening, waits for the owner at `oms setup` whatever the autonomy policy says, and `evolve-verdict` is refused on it (`EVOLUTION_REQUEST_CLOSED`). Stage 1 and stage 2 run when it is proposed: a revert that would add a refusal is refused with `EVOLUTION_REVERT_REFUSED`, and one that overlaps in meaning or drifts past 0.3 from the first sealed generation with `EVOLUTION_STAGE2_REFUSED`; nothing is proposed.
 - `reclaim-evolution-lock` and `lineage-reanchor` belong to the owner at a terminal; over MCP they are refused. Tell the user to run `oms doctor reclaim-evolution-lock` or `oms doctor lineage-reanchor` themselves. Requests awaiting the owner are approved or rejected only at `oms setup`, and autonomy is turned on only with `oms setup --autonomy on`.
 
-A broken or missing seal is recovered by the user running `oms setup` at a terminal; recovery is never done through the `setup` skill. The only automatic seal repair is `oms doctor contract --fix`, which re-indexes a moved or unindexed vault and nothing else. `oms doctor contract` also names the unexpected `.oms` entries for the person at the CLI.
+A missing seal is sealed by the user running `oms interview` at a terminal, the command the `contract-open` write warning names. A broken seal (a tampered or unreadable contract store) is diagnosed with `oms doctor contract` first, then resealed by the user at a terminal; recovery is never done through the `setup` skill. The only automatic seal repair is `oms doctor contract --fix`, which re-indexes a moved or unindexed vault and nothing else. `oms doctor contract` also names the unexpected `.oms` entries for the person at the CLI.
 
 Index repairs run only when explicitly requested and do not edit notes. There is no default-value backfill: OMS never rewrites a note.