@litfamily/litopencode 1.0.35 → 1.0.37

package/skills/start-work/SKILL.md

@@ -340,3 +340,7 @@ in your first response and continue with the one that injected you.
 It says nothing about how to execute — the sections above own that. Its only job is to answer three
 questions a skill body cannot answer for itself: how was I reached, have I already been reached, and
 whose contract am I under.
+
+## Native goal on OpenCode 2
+
+On OpenCode 2.2 and later, start-work gets a native `/goal` from LitOpenCode itself, set once when none exists and carrying the approved plan's completion conditions. A goal the user made is reported and left alone, and a host without `/goal` records `native-goal-unavailable`. The goal never widens the run's authority: scope roots, grants and the bounded-authority journal decide what the work may touch. Done needs OpenCode's verdict and the ledger together. See `native-goal-verdict`.

package/skills/workflow-loop/SKILL.md

@@ -389,3 +389,7 @@ a smaller task only if the deliverable is still required.
 
 A child's own done-claim is a claim, not verification. Silence is not failure and it is not success;
 it is absence of signal, and it must be recorded as such.
+
+## Native goal on OpenCode 2
+
+On OpenCode 2.2 and later, lit-loop gets a native `/goal` from LitOpenCode itself: it is set when none exists, carries the completion conditions of this ledger, and is resumed or cleared only when LitOpenCode created it. Do not type `/goal` for the user, and leave a goal the user made alone; the `LitOpenCode goal:` line reports what happened. A host without `/goal` records `native-goal-unavailable` and the ledger carries the loop. Done needs both OpenCode's verdict and the ledger, so never report done while a criterion, the real-surface check or the cleanup receipt is open. See `native-goal-verdict`.