@remembrance-ai/opencode-plugin 0.2.1 → 0.2.3

package/skills/remembrancer/SKILL.md

@@ -38,6 +38,19 @@ as their hooks from `~/.config/remembrance/config.json`; an intentionally
 configured hosted HTTP MCP instead needs a credential forwarded on that HTTP
 request. See `references/remembrance-setup.md` for exact host steps.
 
+With an organization key, raise "Highly Recommended: approve private
+submissions" from `references/remembrance-setup.md` only after the host, in
+this session, denied a private submit or retry call or stopped it to ask for
+approval, or did the same to a `capture_learning` call on a host whose step
+approves `capture_learning`. Codex is not such a host: under its managed
+`writes` mode a reviewed capture is expected, and approving `capture_learning`
+there is an optional administrator decision, never a required step. Tell the
+user once per such event that the step is required for Remembrance to work
+fully with an organization key; do not raise it at other times or in later
+sessions without a new event. Never change host approval settings or answer
+the host's approval yourself; edit a settings file only after the user asks
+you to.
+
 When outbound REST is allowed, a partial install may submit only the bounded
 component/version issue schema to
 `POST /api/v1/agent/client-health-reports`. Never attach prompts, repository
@@ -548,6 +561,22 @@ clients that do not advertise the capability retain the optional lesson and
 `next_step.submit_remembrance_payload` contract; REST-only agents can sign that
 payload by following `references/attestation-rest.md`.
 
+Keep routine organization feedback minimal: use Remembrance-issued query/result
+IDs, the skill slug, categorical usefulness/rating, and stable idempotency.
+Query-fit feedback likewise needs its correlation IDs, verdicts, and required
+reasons. Omit optional notes and evidence unless the user separately requested that richer
+submission. Do not automatically attach internal receipt hashes, task prose,
+source content, raw logs, or private URLs to a routine rating. Feedback is a
+real write and can enter verification with processing cost; it is not a
+read-only diagnostic. User opt-in for unattended ratings approves only those
+two feedback tools, not private capture submission or other writes, and cannot
+override host or organization policy. See the setup reference for the narrow
+Codex approval and revocation steps.
+
+Tool overrides persist when authentication or schemas change. Remove or
+re-review both approvals before switching to anonymous or hosted transport,
+enabling legacy broad writes, or changing the organization or destination.
+
 Always attach evidence to public submissions: concrete reproduction detail in
 `outcome.failure_modes`, `evidence.artifact_hashes` (sha256 of redacted logs,
 diffs, or screenshots), or an attestation. Evidence-less public reports are not