memgineering 0.15.0 → 0.15.1

package/CHANGELOG.md

@@ -11,6 +11,24 @@ language the reader wants. The bilingual rule the monorepo applies to
 
 ## [Unreleased]
 
+## [0.15.1] — 2026-08-29
+
+### Fixed
+
+- The 128-character cap on `scope` and `asked_from` is now spelled once, in
+  the engine both sides already read, instead of living as three hand-copies
+  that each admitted nothing would catch their drift. Same number everywhere;
+  no behaviour change.
+
+### Agent guidance
+
+- The hub's reflex table gains a fourth row: a vague opening — a new folder,
+  "where were we", picking work back up — is now a `memgineering resurface`
+  reflex, not just a bullet further down. Measured before and after on a
+  fast-tier model in the lab: the same session that skipped resurface twice
+  runs it first with the row in place, and the project-aware opening lands.
+  Restart your agent session after upgrading so the new hub is what gets read.
+
 ## [0.15.0] — 2026-08-29
 
 ### Added

package/assets/MEMGINEERING.md

@@ -2,7 +2,7 @@
 name: memgineering
 description: Use whenever the user refers to something they told you before, asks what was decided, tells you something worth keeping, or settles something that should hold next time. The memory lives in their own folder and outlives this session; check it before answering from guesswork, and write to it when you learn something durable.
 type: skill
-version: 0.15.0
+version: 0.15.1
 ---
 
 # memgineering
@@ -26,19 +26,19 @@ rule; an instruction scoped to "this file" or "here" ends with the task). Judge
 | they settled something that should hold beyond this session (however phrased — e.g. "from now on…", "always…", "never…") | `memgineering remember "<their words>" --rule --reason "<why>"` |
 | they corrected what you made, for this task (e.g. "again", "no, like this", showed the right way) | `memgineering remember "<what turned out right>" --reason "<their correction>"` — and if the correction is meant to hold beyond this session, that is the row above: add `--rule` |
 | they asked about something that sounds already settled (e.g. "what did we decide", "how do we do this again") | `memgineering recall "<their words>"` FIRST, answer second |
+| they opened vaguely — a new folder, "where were we", picking work back up | `memgineering resurface` FIRST — no query; answer from it |
 
 When the words could mean just-this-task or from-now-on, do not guess a
 binding rule: record it WITHOUT `--rule`, do the task, and ask in one line
 whether it should hold from now on. A wrong rule silently binds every future
 session; the question costs a second.
 
-These are SHELL commands — run them with your shell tool. Opening a memgineering
-skill page saves nothing; measured: a model passed the command as
-a skill argument, told the user it was saved, and nothing was stored. Done
-means the CLI printed `Remembered.` and an undo id.
+These are SHELL commands — run them with your shell tool; measured: a model
+passed one as a skill argument and told the user it was saved when nothing was
+stored. Done means the CLI printed `Remembered.` and an undo id.
 
-Durable facts about the user never go into this tool's own memory files —
-the brain is the one store every tool they use shares.
+Durable user facts never go in this tool's own memory files — the brain is
+the store every tool they use shares.
 
 ## When to reach for it
 
@@ -51,7 +51,6 @@ the brain is the one store every tool they use shares.
   what you did and said it was right: `memgineering remember "<it>" --reason
 "<why>"`. Reversible by design, so do not ask permission for ordinary
   observations — but first `open boundaries`: it says what never to store.
-- **A new folder, or "where were we"** — `memgineering resurface`, no query.
 - **Their notes have piled up** — duplicates, notes that disagree:
   `memgineering consolidate` finds candidates and changes nothing; changes are
   proposed, then approved by them.