novahiz 0.8.2 → 0.9.1

package/CHANGELOG.md

@@ -3,6 +3,69 @@
 All notable changes to Novahiz are documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
 
+## [0.9.1] - 2026-10-10
+
+### Fixed
+
+- **Fresh-install scan stops reporting missing skill roots** — the default
+  `skillRoots` include `~/.agents/skills`, which most profiles do not have.
+  The first `sync` (run by the installer) used to surface it as a scan error
+  on every new machine; a declared root that does not exist yet now simply
+  contributes nothing (`scanErrors: []`).
+- **README install banner aligned with the shipped version** (0.8.0 → 0.9.0).
+
+### Notes
+
+- The npm installer path is verified end-to-end on npm 12.2: install with the
+  `postinstall` blocked by `allowScripts`, first `novahiz` run finishes the
+  setup itself (auto-install, `NOVAHIZ_AUTOINSTALL=0` to opt out), second run
+  clean. `novahiz doctor` exits 0 on the fresh sandbox.
+
+## [0.9.0] - 2026-10-10
+
+### Added
+
+- **`second-memory project-init`** — gives a new project its vault folders
+  (`docs/journal/decisions/<project>/`, each with a real `_MOC.md`, never
+  `memory/`) and binds the project to its branch. Dry-run by default,
+  `--branch Domain/Branch` validates against the catalog, idempotent, and
+  `--apply` writes the `vault.json` binding (slug → domain/branch) in the
+  memory root.
+- **`novahiz init` Obsidian step** — when a vault exists and the project has
+  a name, init creates the project's folders through the same logic; no
+  vault, no name or no branch signal means the step skips with an advice and
+  never invents a folder. Honors `--dry-run`.
+- **`journal` and `decisions` leaves** in `catalog/vault-structure.json` for
+  every `memory|docs` branch (19 branches, 38 leaves), with root
+  `journalKeywords` / `decisionsKeywords`. `routePath` resolves the leaf
+  `decisions` > `journal` > `docs` > `memory`, and the project level extends
+  to the new leaves.
+- **Project binding in `routePath`** — a note carrying a `project:` bound by
+  `project-init` lands in the project's branch whatever the keywords say;
+  stale or missing bindings fall back to the historic keyword routing.
+
+### Changed
+
+- **`second-memory sync` is archive-only** — project memory stays local
+  (`MEMORY.md` + `project-memory/` slots); the bidirectional slot ↔ vault
+  mirror (pull / push / rebuild, last-writer-wins) is retired. `sync` now
+  lists (dry-run) and archives (`--apply`, backed up under `Archive/.backup`)
+  the notes the old mirror generated (`novahiz_slot_id`), while keeping the
+  opt-in inverse import (`novahiz_slot_sync: true` → slot in local memory).
+  `status` / `doctor` report the leftovers as `project-memory note(s) in the
+  vault`.
+- **Skills and instructions follow** — `novahiz-memory` / `memory` are
+  local-only (no vault write, no routing table); `novahiz-second-memory`
+  documents the new leaves, `project-init`, the binding and the archive-only
+  sync; `instructions.md` adds the local-memory rule and the
+  no-speculative-folders rule.
+
+### Removed
+
+- Mirror helpers and constants of the retired sync (`renderSlotNote`,
+  `slotBody`, `parseIso`, `SYNC_TOLERANCE_MS`, and the `readIndex` usage in
+  sync).
+
 ## [0.8.2] - 2026-10-10
 
 ### Fixed

package/README.md

@@ -4,7 +4,7 @@
 
 17 catégories, 94 skills, 13 gate rules, 8 MCP providers — tout déterministe, tout local, tout JSON.
 
-> **Version 0.8.0** — publiée sur npm (`npm install -g --allow-scripts=novahiz novahiz` installe et configure tout : core, plugin, agent, skills packs et Playwright MCP). `CHANGELOG.md` et `scripts/` sont dans le tarball.
+> **Version 0.9.0** — publiée sur npm (`npm install -g --allow-scripts=novahiz novahiz` installe et configure tout : core, plugin, agent, skills packs et Playwright MCP). `CHANGELOG.md` et `scripts/` sont dans le tarball.
 
 ```
 ┌──────────────────────────────────────────────────────────────────────────┐

package/adapters/opencode/instructions.md

@@ -17,13 +17,14 @@ Search it yourself (`novahiz second-memory search "<terms>"`, then read the note
 Do **not** consult it for trivial edits, unrelated questions, or when the prompt already carries the needed context.
 
 ### Rules
-1. When the user asks to **save / memorize / update** memory, load the `memory` skill (alias for `novahiz-memory`) and follow its procedure without exception. For vault-only writes and structure questions, load `novahiz-second-memory` instead: it owns the vault's fixed, predefined arborescence.
-2. Vault routing comes from the predefined structure (`catalog/vault-structure.json`, surfaced by the `novahiz-second-memory` skill) — never guess a location. When ambiguous, ask the user, and display the chosen path before writing.
+1. When the user asks to **save / memorize / update** memory, load the `memory` skill (alias for `novahiz-memory`) and follow its procedure without exception. Project memory is local to the project (`MEMORY.md` + `project-memory/` slots) and **never goes into the vault**. For vault-only writes and structure questions, load `novahiz-second-memory` instead: it owns the vault's fixed, predefined arborescence.
+2. Vault routing comes from the predefined structure (`catalog/vault-structure.json`, surfaced by the `novahiz-second-memory` skill) — never guess a location. A note belongs to a project when its frontmatter carries `project:`; its leaf is `decisions` on a `decisionsKeywords` hit, else `journal` on a `journalKeywords` hit, else `docs`, else `memory`. When ambiguous, ask the user, and display the chosen path before writing.
 3. Search before you write: `novahiz second-memory search "<terms>"` — merge into an existing note rather than creating a duplicate. Link pages with `[[wikilinks]]`.
 4. Never write to `index.md`, `log.md`, `hot.md`, `.manifest.json`, `_meta/`, or `.obsidian/`. If the user asks for it, do it step by step in front of them, with a backup first for anything under `.obsidian/`.
 5. Never create a root domain on your own: every new domain requires user agreement and a structure update.
 6. Include mandatory frontmatter: `title, category, tags, sources, created, updated, summary`.
-7. Structure maintenance is CLI work: `novahiz second-memory [init|doctor|fix|sync|status]` (dry-run by default, `--apply` to write).
+7. Structure maintenance is CLI work: `novahiz second-memory [init|doctor|fix|sync|project-init|status]` (dry-run by default, `--apply` to write). `sync` only archives notes the old memory mirror left in the vault — it never mirrors memory into the vault.
+8. Folders are never created speculatively: a folder appears on the first write, or when `second-memory project-init` (the same logic behind the `Obsidian project folder` step of `novahiz init`) creates a project's `docs/journal/decisions` folders on request — never `memory/<project>/`.
 
 ## Playwright Browser — Persistent Profile