openpond 0.0.67 → 0.0.69

package/dist/skills/openpond-refiner-authoring/SKILL.md

@@ -0,0 +1,29 @@
+---
+name: openpond-refiner-authoring
+description: Inspect, extend, validate, activate, or roll back the OpenPond Refiner Review Profile. Use when invoked as $openpond-refiner-authoring or for ordinary requests to change what the Refiner emphasizes or understands.
+---
+
+# OpenPond Refiner Authoring
+
+Update the separately versioned Review Profile through a normal Work turn. The active Refiner never edits itself during trace review.
+
+Invoke this Skill explicitly with `$openpond-refiner-authoring` followed by the requested change. It uses the same profile-skill loading path as every other shipped Skill; it is not a slash command or a separate authoring mode.
+
+## Workflow
+
+1. Call `refiner_profile_inspect` before proposing any change.
+2. Preserve the profile identity and unrelated instructions. Increment `version` for a changed profile.
+3. Translate the user's request into the smallest clear instruction, objective change, or route restriction. Do not invent a severity taxonomy or new schema field.
+4. Call `refiner_profile_update` with the complete profile and a specific reason.
+5. Set `activate` to `true` for an explicit imperative change in a personal workspace. Set it to `false` when the user asks for a draft or when host policy requires review.
+6. Report the old and new release hashes, the exact instruction-level change, validation, and activation state.
+
+Read [Review Profile contract](references/review-profile.md), [Core boundary](references/core-boundary.md), and [validation and activation](references/validation-and-activation.md) before updating.
+
+## Rules
+
+- Use `refiner_profile_*` tools; do not guess or directly edit app-data paths.
+- The Review Profile may specialize objective, instructions, and allowed routes. It may not weaken Core evidence admission, privacy, ownership, validation, or activation rules.
+- Keep instructions behavioral and reusable. Do not copy customer data, raw traces, credentials, task answers, or one-off facts.
+- Do not modify Harness source as a substitute for changing the Refiner.
+- Do not claim activation until the returned binding points at the new release.

package/dist/skills/openpond-refiner-authoring/references/core-boundary.md

@@ -0,0 +1,5 @@
+# Refiner Core boundary
+
+The Refiner Core defines evidence admission, structured decisions, privacy, ownership routing, deterministic validation, and immutable activation. A Review Profile is composed after that Core and cannot override it.
+
+Harness and Refiner releases are adjacent identities. A Work turn pins both. The Refiner may propose a new Harness release; a later authoring turn may create a new Refiner release. Never let the acting release mutate its own definition during the same review.

package/dist/skills/openpond-refiner-authoring/references/review-profile.md

@@ -0,0 +1,7 @@
+# Review Profile contract
+
+The canonical managed source is `openpond.review.json`, validated as `openpond.refinerReviewProfile.v1`.
+
+Required fields are `schemaVersion`, `id`, `version`, `name`, `objective`, `instructions`, `allowedProposalRoutes`, and `allowedExternalRoutes`. Each instruction is `{ "id": "stable-kebab-id", "text": "A behavioral instruction." }`.
+
+Keep the profile small. Put policy prose in instruction text instead of adding fields for every domain concept. JSON is the portable artifact; TypeScript helpers may produce the same JSON but are not the stored contract.

package/dist/skills/openpond-refiner-authoring/references/validation-and-activation.md

@@ -0,0 +1,5 @@
+# Validation and activation
+
+`refiner_profile_update` validates the complete JSON profile, writes an immutable release, records the authoring skill hash, and optionally advances the active binding atomically. Invalid profiles do not produce an active release.
+
+Activation is host policy, not a profile field. Personal explicit changes may activate immediately. Draft requests and review-gated team or production environments create a candidate release without changing the binding. Rollback creates a new transition receipt; old Work remains pinned to its original release.