@remembrance-ai/opencode-plugin 0.2.0 → 0.2.1

package/opencode.json

@@ -6,7 +6,7 @@
       "command": [
         "npx",
         "-y",
-        "@remembrance-ai/mcp-server@0.2.0"
+        "@remembrance-ai/mcp-server@0.2.1"
       ],
       "enabled": true,
       "environment": {
@@ -16,6 +16,6 @@
     }
   },
   "plugin": [
-    "@remembrance-ai/opencode-plugin@0.2.0"
+    "@remembrance-ai/opencode-plugin@0.2.1"
   ]
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@remembrance-ai/opencode-plugin",
-  "version": "0.2.0",
+  "version": "0.2.1",
   "license": "Apache-2.0",
   "description": "opencode plugin for Remembrance session hooks, tool observation, and contribution nudges.",
   "type": "module",

package/servers/remembrance-mcp.mjs

@@ -67273,7 +67273,7 @@ function inspectPrivateLearningOutbox2(input, dependencies = {}) {
 }
 var MAX_REMOTE_RESPONSE_BYTES = 4 * 1024 * 1024;
 var DOCTOR_PROBE_TIMEOUT_MS = 7500;
-var SERVER_VERSION = true ? "0.2.0" : "0.0.0-dev";
+var SERVER_VERSION = true ? "0.2.1" : "0.0.0-dev";
 var tools = toolDefinitions;
 var doctorCliRequested = process.argv[2] === "doctor";
 var nativeContextCliRequested = process.argv[2] === "--native-context";

package/skills/remembrancer/SKILL.md

@@ -339,7 +339,8 @@ Remembrance independently classifies the evidence after static safety,
 duplicate search, target existence, risk, verifier, and organization-policy
 checks:
 
-- a universal correction or reusable detail can **amend** the target;
+- a universal correction or reusable detail can **amend** the target when an
+  explicit authored instruction body or catalog change is supplied;
 - a stable runtime, version, platform, framework, scale, or task-stage
   condition can become a scoped **specialization**;
 - a genuinely different approach can become a **strategy fork**;
@@ -560,14 +561,22 @@ Repeated substantive feedback for the same skill may also return
 evidence candidate from the recent pattern and queued it for topology routing,
 normal verification, quality gates, versioning, and admin/enterprise review.
 Treat it as a receipt; it does not mean the live skill changed or predetermine
-whether the result will amend, specialize, fork, create, or remain evidence.
-
-`suggested_update` on a remembrance is honored: when the remembrance itself is
-accepted, Remembrance promotes it into a reviewed suggestion (`amend_skill`,
-`metadata_update`, `deprecate_skill`) or a new skill idea (`new_skill`) riding
-the normal verification and review pipeline. The promotion is a receipt too —
-the live skill changes only after review. `score_adjustment` is ignored:
-Remembrance computes all scoring deterministically.
+the selected route. Synthesized review prose is not an authored parent
+instruction or catalog patch; reviewed distinct-child routes stay separate.
+
+On a remembrance, `suggested_update` hints of `amend_skill` or
+`metadata_update` stay with the accepted evidence; they do not create an empty
+publication suggestion. Explicit `deprecate_skill` and `new_skill` requests
+still enter their existing reviewed lifecycles. A receipt never means the live
+skill changed. `score_adjustment` is ignored: scoring is deterministic.
+
+When you intend to change a parent's instructions or catalog, read
+[the authored amendment examples](references/remembrance-payloads.md#authored-parent-amendments).
+Submit the explicit change through the existing suggestion/idea review lane;
+summary, diff and verifier prose are review context, not parent edits. A
+missing authored parent change stays recoverable for review, and an identical
+complete-body/catalog result creates no new skill version or semantic refresh.
+Existing audience, consent, protection, target and review policy still apply.
 
 Legacy/raw MCP equivalent: `submit_remembrance`. Organization-capable local
 clients use `capture_learning.lesson`; broad remembrance submission is hidden
@@ -612,8 +621,8 @@ Good triggers include: the agent admits it missed a required step, the user
 catches a mistake, CI/deploy fails, a smoke/probe exposes a regression, or a
 release/versioning miss is fixed. Put the reusable lesson in `lesson`, the
 concrete failure class in `outcome.failure_modes`, and use
-`suggested_update.kind` only when an existing skill or a new skill should change
-after review.
+`suggested_update.kind` only to describe an intended reviewed operation, not as
+a substitute for an authored parent change.
 
 Use `agent.provider: "claude"` for a skill-only Claude install. Use
 `evidence.attestation.provider: "other"` for independent REST TOFU

package/skills/remembrancer/references/remembrance-payloads.md

@@ -44,16 +44,77 @@ use categorical `submit_feedback` independently.
 
 Legacy `attestation_token_hash` is no longer accepted. Verified trust uses `POST /api/v1/agent/attest/challenge` followed by a plugin-signed `evidence.attestation` object.
 
-`suggested_update` describes a requested content operation; it does not decide
-the final skill topology. When the remembrance itself is accepted, Remembrance
-creates reviewable evidence through the normal verification pipeline. The
-topology router may amend the target, create a scoped specialization, create a
-strategy fork or independent skill, record a typed preference, retain evidence
-without mutation, or hold for review. The live skill changes only after the
+`suggested_update` describes an intended operation; it does not decide the
+final topology or supply a parent edit. An accepted remembrance retains
+`amend_skill` and `metadata_update` hints as evidence without creating an empty
+publication suggestion. Explicit `deprecate_skill` and `new_skill` requests
+still enter their existing reviewed lifecycles. For an authored parent change,
+use the suggestion/idea lane below. The live skill changes only after the
 selected route clears its safety, quality, target, policy, and version guards.
 `score_adjustment` is ignored (scoring is deterministic); use `kind: "none"`
 when no content operation is proposed.
 
+## Authored parent amendments
+
+For `submit_suggestion` / `POST /api/v1/agent/suggestions`, send the complete
+intended instruction body in `payload.skill_md`, `payload.proposed_skill_md`
+or `payload.full_skill_md`. Start from the current authorized skill body and
+preserve instructions you are not changing; do not send only a diff or an
+isolated addition as the replacement body. For a parent amendment, `summary`,
+`diff_text` and a verifier's `proposed_patch` explain the review, but are never
+appended as instructions or implicitly saved as catalog guidance.
+
+This synthetic example replaces the complete body of a small public skill:
+
+```json
+{
+  "skill_slug": "synthetic-state-check",
+  "suggestion_type": "amend_skill",
+  "summary": "Check the response status before interpreting the result.",
+  "diff_text": "Review context: add the response-status check.",
+  "payload": {
+    "skill_md": "# State check\n\nRead the current state. Check the response status before interpreting the result. Compare it with the expected state and report any difference.\n"
+  }
+}
+```
+
+For a catalog-only change, submit the existing structured catalog fields
+explicitly. For example:
+
+```json
+{
+  "skill_slug": "synthetic-state-check",
+  "suggestion_type": "metadata_update",
+  "summary": "Describe the skill's existing response-status check.",
+  "payload": {
+    "summary": "Compare the current and expected state after checking the response status."
+  }
+}
+```
+
+These are payload-shape examples, not permission to submit public content.
+Keep organization authentication and private protection on organization
+requests; never remove a key to make a private amendment public. Current
+organization-capable clients still use their authorized local capture/router
+and only its returned actions. These examples do not add a direct mutation
+tool or bypass that contract. Preserve the existing organization array
+replacement/merge rules for catalog updates.
+
+For an idea routed to amend a parent, use its existing `proposed_skill_md` or
+explicit `proposed_metadata` fields. Authored input does not remove an existing
+target-resolution or protection hold. A parent amendment without authored input
+is retained in a recoverable review hold: resubmit the complete intended body
+or structured catalog change through the same authorized review lane. A changed
+payload is a new logical submission and needs its own idempotency key; retries
+of that submission reuse its key. A reviewer may instead select `evidence_only`
+to retain the comment without publishing. Do not report a replacement as
+submitted or a skill as changed until the corresponding receipt proves it.
+
+An accepted identical body/catalog result is an audited no-op: it preserves
+the live version and does not enqueue semantic refresh. Explicit deprecation,
+new-skill proposals and reviewed distinct-child routes retain their existing
+contracts; they are not universally held by the parent-amendment rule.
+
 Provider fields are intentionally split:
 
 - `agent.provider` describes the calling runtime: `codex`, `cursor`, `claude`,
@@ -213,9 +274,11 @@ predetermined metadata update or a live mutation:
 }
 ```
 
-Do not submit a duplicate suggestion for the same pattern. Wait for the
-topology, verification, review, and versioning result before assuming the
-active skill changed.
+Do not submit a duplicate suggestion for the same pattern. Its review prose
+does not supply an authored parent catalog patch or instruction body. If you
+separately intend a parent change, use the authored amendment lane above and
+the existing review policy; do not assume the evidence receipt changed the
+active skill.
 
 Local identity recovery: the persisted key file
 `~/.config/remembrance/agent-key.json` is a private key. Back it up like an