@pennixrv/trellis 0.7.0-beta.29 → 0.7.0-beta.31

package/dist/migrations/manifests/0.7.0-beta.16.json

@@ -1,9 +1,9 @@
 {
   "version": "0.7.0-beta.16",
-  "description": "Use Hindsight for coordinator memory and isolate subnode memory hooks",
+  "description": "Refresh coordinator handoff and worker extension boundaries",
   "breaking": false,
   "recommendMigrate": false,
-  "changelog": "**Workflow fixes:**\n- Subnode templates disable Hindsight hooks and MCP tools so evidence workers do not create or consume unsupervised memory.\n- Coordinator-owned Hindsight handoff remains available for explicit project memory writes.\n- The bundled handoff contract is aligned with the Hindsight-backed Pennix workflow.",
+  "changelog": "Refresh bundled coordinator handoff and subnode extension-isolation guidance. These release notes describe the legacy update; current behavior follows the selected workflow.",
   "migrations": [],
   "notes": "Run npm install -g @pennixrv/trellis@beta then trellis update. No --migrate required."
 }

package/dist/migrations/manifests/0.7.0-beta.18.json

@@ -1,6 +1,6 @@
 {
   "version": "0.7.0-beta.18",
-  "description": "Clarify Hindsight retrieval proof in the Codex subnode workflow",
+  "description": "Clarify formal-handoff verification in the Codex subnode workflow",
   "breaking": false,
   "recommendMigrate": false,
   "changelog": "**Handoff contract clarification:**\n- The Codex subnode workflow distinguishes same-document retrieval verification from canonical content persistence.\n- Marketplace workflow content hashes remain synchronized with the published workflow.\n- No project migration is required.",

package/dist/migrations/manifests/0.7.0-beta.21.json

@@ -1,14 +1,14 @@
 {
   "version": "0.7.0-beta.21",
-  "description": "Remove the obsolete Hindsight-only subnode environment asset",
+  "description": "Remove the obsolete subnode environment asset",
   "breaking": false,
   "recommendMigrate": false,
-  "changelog": "Subnode isolation is now implemented by the Codex adapter and worker environment boundary. The generated Hindsight-only `.trellis/agents/subnode.env` is no longer part of the workflow template.",
+  "changelog": "Subnode isolation is now implemented by the Codex adapter and worker environment boundary. The generated `.trellis/agents/subnode.env` is no longer part of the workflow template.",
   "migrations": [
     {
       "type": "safe-file-delete",
       "from": ".trellis/agents/subnode.env",
-      "description": "Remove the obsolete Hindsight-only subnode environment file",
+      "description": "Remove the obsolete subnode environment file",
       "reason": "The same child isolation contract is now enforced by the Trellis Codex adapter and environment builder; only the unmodified generated file is safe to delete.",
       "allowed_hashes": ["b34ec77e748c1fab09e96d9fd6ca4af6ab993472b9d060d89375460d9740ca1f"]
     }

package/dist/migrations/manifests/0.7.0-beta.22.json

@@ -3,7 +3,7 @@
   "description": "Preserve native session identity when no task is active",
   "breaking": false,
   "recommendMigrate": false,
-  "changelog": "task current --json now exposes session_source independently of the task-pointer source. Taskless formal handoffs can keep their native session identity without creating a task. The Pennix Marketplace workflow uses Cognee exact retrieval proof instead of the retired Hindsight contract.",
+  "changelog": "task current --json now exposes session_source independently of the task-pointer source. Taskless formal handoffs can keep their native session identity without creating a task. The Pennix Marketplace workflow updates formal-handoff verification.",
   "migrations": [],
   "notes": "Run trellis update to refresh task.py. Existing source semantics and exit codes are unchanged. Explicitly refresh the selected Marketplace workflow to its approved commit."
 }

package/dist/migrations/manifests/0.7.0-beta.23.json

@@ -1,9 +1,9 @@
 {
   "version": "0.7.0-beta.23",
-  "description": "Correct the bundled subnode memory isolation guidance",
+  "description": "Correct the bundled subnode extension-isolation guidance",
   "breaking": false,
   "recommendMigrate": false,
-  "changelog": "The trellis-channel worker reference now matches implemented Cognee isolation: the native Codex adapter disables the official plugin for subnodes, and no memory-specific env_file is generated.",
+  "changelog": "The trellis-channel worker reference now matches the native extension-isolation guidance: the Codex adapter disables the retired extension for subnodes, and no extension-specific env_file is generated.",
   "migrations": [],
   "notes": "Run trellis update to refresh the bundled trellis-channel reference. No runtime behavior or migration task changes."
 }

package/dist/migrations/manifests/0.7.0-beta.27.json

@@ -1,9 +1,9 @@
 {
   "version": "0.7.0-beta.27",
-  "description": "Adopt the official Cognee memory contract and isolate subnode access",
+  "description": "Align coordinator handoff and subnode extension boundaries",
   "breaking": false,
   "recommendMigrate": false,
-  "changelog": "The Codex channel now uses the official Cognee plugin contract for coordinator memory, verifies formal handoffs through authenticated dataset/data UUID and raw-content proof, and disables the plugin plus COGNEE_* environment inheritance for subnodes.",
+  "changelog": "Align the coordinator formal-handoff verification contract with the selected workflow and isolate child extension configuration and environment inheritance.",
   "migrations": [],
   "notes": "Run trellis update to refresh the selected workflow and bundled worker guidance. No task or ownership migration is required."
 }

package/dist/migrations/manifests/0.7.0-beta.28.json

@@ -1,9 +1,9 @@
 {
   "version": "0.7.0-beta.28",
-  "description": "Apply the native Codex Cognee plugin override correctly",
+  "description": "Apply the native Codex extension override correctly",
   "breaking": false,
   "recommendMigrate": false,
-  "changelog": "Codex subnodes now pass the unquoted dotted plugin key that the native -c parser recognizes, so the official Cognee plugin is actually disabled for the child process.",
+  "changelog": "Codex subnodes now pass the unquoted dotted plugin key that the native -c parser recognizes, so the retired extension is actually disabled for the child process.",
   "migrations": [],
   "notes": "Upgrade the CLI to receive the adapter fix. No task or ownership migration is required."
 }

package/dist/migrations/manifests/0.7.0-beta.30.json

@@ -0,0 +1,9 @@
+{
+  "version": "0.7.0-beta.30",
+  "description": "Refresh legacy migration descriptions and retain safe cleanup",
+  "breaking": false,
+  "recommendMigrate": false,
+  "changelog": "Bundled legacy migration metadata uses neutral extension and handoff descriptions. Version identifiers, migration targets, hash-guarded cleanup, and native task/session behavior remain unchanged.",
+  "migrations": [],
+  "notes": "Upgrade the CLI and refresh project assets. Selected workflow sources and local task/history records are preserved. No task or ownership migration is required."
+}

package/dist/migrations/manifests/0.7.0-beta.31.json

@@ -0,0 +1,9 @@
+{
+  "version": "0.7.0-beta.31",
+  "description": "Clarify local conversation recall and curated knowledge ownership",
+  "breaking": false,
+  "recommendMigrate": false,
+  "changelog": "The shared session-insight skill selects current project facts, raw local dialogue, and curated knowledge by user intent. It keeps external knowledge writes and promotions explicit, with no mandatory preload or automatic synchronization. Runtime and mem behavior are unchanged.",
+  "migrations": [],
+  "notes": "Upgrade the CLI and refresh generated project assets. Preserve selected workflows, project contracts, tasks and history; no runtime migration is required."
+}

package/dist/templates/common/bundled-skills/trellis-session-insight/SKILL.md

@@ -5,7 +5,7 @@ description: "Reach into past AI conversation history through the `trellis mem`
 
 # Trellis Session Insight
 
-This skill teaches an AI **how to call `trellis mem`** — the project's cross-session memory feedstock — and **when reaching for it is the right move**.
+This skill teaches an AI **how to call `trellis mem`** for local conversation history and **when reaching for it is the right move**.
 
 It is intentionally a **capability skill, not a workflow**. There is no fixed output file, no required write-back step, no "always run after finish-work" rule. What to do with what `mem` returns is a judgement call made in the moment of the conversation. The skill exists so the AI knows the capability is there and can decide.
 
@@ -15,6 +15,14 @@ A local CLI that indexes the user's past Claude Code, Codex, Devin CLI, Grok, Op
 
 Nothing in `mem` is uploaded. All reads are local.
 
+`mem` returns historical discussion, not a curated knowledge base or an automatic
+preference/summary writer. Current source, task artifacts, `AGENTS.md`, and specs
+own current facts. If the user asks for maintained knowledge or reusable notes,
+use that environment's configured native knowledge tool instead. Select the
+source by intent and add a targeted second lookup only for a specific evidence
+gap; there is no required sequence through all sources. A knowledge tool's
+absence or failure does not block Trellis tasks, local recall, or handoff.
+
 ## When to reach for it
 
 The bar is "would a senior teammate ask 'didn't we already talk about this?'" — those are the moments. Some concrete patterns:
@@ -40,13 +48,21 @@ If none of these apply, don't call `mem`. It is a tool, not a ceremony.
 Treat the output as **raw material**, not a deliverable. Once you have it, decide based on the live conversation:
 
 - **Quote inline in your reply** if a specific past exchange answers the user's current question — and cite the session-id / phase so the user can verify.
-- **Update `<task>/prd.md` or `<task>/design.md`** if `mem` surfaced a load-bearing decision that should have been written down but wasn't. Surface the proposed edit to the user first.
+- **Update `<task>/prd.md` or `<task>/design.md`** if `mem` surfaced a load-bearing decision that should have been written down but wasn't. Verify against current facts and follow the active task's authorization; material changes return to its planning gate.
 - **Append to a task-local notes file** (e.g. `<task>/notes.md` or extending an existing one) if the finding belongs to the current task's record but doesn't fit the PRD.
 - **Update `.trellis/spec/`** if the finding is a project-wide convention or gotcha that would help future tasks. Run the `trellis-update-spec` skill for that — `session-insight` ends at the discovery.
 - **Just absorb it** for the next few turns and answer better, without writing anything. This is often the right move for one-off recall.
 
 Trellis does not prescribe a single destination. Forcing every recall into a fixed file makes the file grow into noise. Let the situation decide.
 
+Reusable experience can be proposed for a user-maintained knowledge tool;
+executable project contracts go through `trellis-update-spec`, stable methods
+through the source Skill owner, and cross-project rules require an explicit
+common scope. External knowledge writes or new promotions require concrete user
+intent, including any minimal source-note status/version/target-link update.
+Existing authorized task/spec duties do not acquire an extra confirmation gate.
+Verify each target independently; do not introduce automatic synchronization.
+
 ## How to call it
 
 Full CLI reference is in `references/cli-quick-reference.md`. The 80% case is one of:

package/dist/templates/common/bundled-skills/trellis-session-insight/references/triggering-patterns.md

@@ -1,6 +1,8 @@
 # Triggering Patterns
 
-Verbatim user phrasings that should make an AI reach for `trellis mem`. Calibrate instinct against these — if a user message hits one of these patterns and you do not reach for `mem`, you probably missed an obvious recall.
+Verbatim user phrasings that suggest local conversation recall. Check the intent
+and available current evidence before calling `trellis mem`; these examples do
+not require an unconditional history search.
 
 Patterns are grouped by the *intent* behind the phrasing, not the surface words. The same intent shows up in different languages and registers.
 
@@ -32,7 +34,8 @@ Reach: `trellis mem search "<decision keyword>"` to find the session, then `extr
 
 ## Cross-session continuation
 
-The user resumed work after a gap and the context is implicit.
+The user resumed work after a gap and the context is implicit. Read the active
+task and current files first; use raw history only for missing discussion.
 
 - "Where were we?"
 - "Continue from last time."
@@ -84,6 +87,11 @@ Reach: identify the current task's session id (from `.trellis/.runtime/sessions/
 
 ## Anti-patterns: do NOT reach for `mem` here
 
+- "Find our maintained deployment notes" → the configured native knowledge tool.
+- "Save this reusable result to my notebook" → explicit knowledge write through its owner.
+- "Promote this method into a Skill" → verify the evidence, then the source Skill owner.
+- Current task artifacts already answer the question → use those artifacts.
+
 - "What does this function do?" → read the file.
 - "Why is this test failing?" → read the test output and the file.
 - "What's the right pattern for X in our codebase?" → grep / read spec files.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pennixrv/trellis",
-  "version": "0.7.0-beta.29",
+  "version": "0.7.0-beta.31",
   "description": "AI capabilities grow like ivy — Trellis provides the structure to guide them along a disciplined path",
   "type": "module",
   "main": "./dist/index.js",
@@ -34,7 +34,7 @@
     "inquirer": "^9.3.7",
     "undici": "^6.21.0",
     "zod": "^4.4.2",
-    "@pennixrv/trellis-core": "0.7.0-beta.29"
+    "@pennixrv/trellis-core": "0.7.0-beta.31"
   },
   "devDependencies": {
     "@eslint/js": "^9.18.0",