neo-agent-skills 0.1.78 → 0.1.79

package/.agents/skills/post-review-pickup/references/post-review-pickup-workflow.md

@@ -112,6 +112,13 @@ decision.**
 - Legitimate defer: name the artifact to re-read, the check to run, the peer
   signal awaited, or the external unblock condition. "Do it fresh next turn" or
   "await steer" name nothing.
+- A turn never ends into an unbounded wait: when the next step waits on an
+  external condition, run every owned bounded lane, then end with a wake
+  scheduled inside the provider's cache TTL (≤ 50 min on Anthropic, naming the
+  condition) or a subscription its message triggers. `AGENT:*` broadcasts do
+  not wake, and the plane defers wakes above its context gate (neo-agent-brain
+  `ai/daemons/wake/contextGatePolicy.mjs`); "waits on X" alone is the hold
+  state §L3 forbids.
 - Deferring the same positive-ROI lane twice while busy elsewhere is drift.
   Resolve it: execute, hand off to a named peer with the collision state, or
   downgrade it with evidence that it is no longer positive-ROI.

package/.agents/skills/session-sunset/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: session-sunset
-description: "Protocol for ending an agent session without Zero-State Amnesia; use at >75% context window, ~2x post-recovery session size at a quiet point, a macro-semantic pivot, or human directive (never task completion/wait)."
+description: "End a session without Zero-State Amnesia; use at ≤200k context tokens (the wake plane's gate; >75% window only without a gauge), a macro-semantic pivot, or human directive (never task completion/wait)."
 ---
 
 # Session Sunset Skill

package/.agents/skills/session-sunset/references/session-sunset-workflow.md

@@ -15,7 +15,7 @@ To an LLM, yielding a prompt resolution feels like a "termination," but to a Hum
 You are strictly **FORBIDDEN** from executing the Sunset Protocol simply because you finished a prompt and yielded control back to the human. You MUST only execute the Sunset Protocol when a true **Session Boundary** is reached.
 
 A true Session Boundary is defined by:
-1. **Context Exhaustion or Cost.** *Exhaustion:* over 75 % of the window, or context-pressure signals (forgetfulness). *Cost:* every call re-reads the whole context (cached reads are cheap, not free), so cost follows tokens, not the window's share. Rule of thumb, unvalidated: from about twice a session's post-recovery size on the harness's token gauge (1M-window Claude seat, 2026-10: ~150k, so ~300k), a `solo-refresh` is your own call; whether it pays depends on the handover work and the calls that follow. For this arm only: a quiet point (nothing of yours uncommitted, unpushed, unposted or unanswered); what comes next needs little of the context (a different area, or a wait that outlives the prompt cache); an operator-free way back verified on this seat (Auto-Wakeup note above). Without gauge or way back, this arm only recommends (trigger 4).
+1. **Context Exhaustion or Cost.** *Gate:* the wake plane defers every wake into a session above 250k context tokens and warns at 200k (neo-agent-brain `ai/daemons/wake/contextGatePolicy.mjs`); the seat never sees that warning, so its gauge is the instrument (`get_usage` on Claude Desktop, the harness's reading elsewhere): sunset at or before 200k, never run above 250k; only a harness without a gauge falls back to 75 % of the window or context-pressure signals. *Cost:* every call re-reads the whole context (cached reads are cheap, not free), so cost follows tokens, not the window's share, and below the gate a `solo-refresh` is your own call. For this arm only: a quiet point (nothing of yours uncommitted, unpushed, unposted or unanswered); what comes next needs little of the context (a different area, or a wait that outlives the prompt cache); an operator-free way back verified on this seat (Auto-Wakeup note above). Without gauge or way back, this arm only recommends (trigger 4).
 2. **Macro-Semantic Pivot:** The human explicitly shifts focus to a completely new domain, epic, or architectural phase (e.g., switching from Database Layer substrate work to UI Framework component design), requiring a clean slate. *Asymmetry Tiebreaker: The cost of a premature sunset is greater than a late sunset; when in doubt, lean conservative and keep the session open.*
 3. **Explicit Human Directive:** The Human Commander explicitly instructs you to terminate the session (e.g., "let's wrap", "time to sunset", or `/sunset`).
 4. **Proactive Agent Recommendation:** You recognize a natural, logical break point in the work stream and explicitly **RECOMMEND** sunsetting to the human (e.g. "We've reached a logical break point. Should we sunset the session?"). **NEVER unilaterally execute the protocol based solely on this.**
@@ -141,7 +141,7 @@ To preserve "hot" thread visibility across sessions (Option B), agents do NOT `m
 ### Step 8: The A2A Continuity Ping & Reward Signal (Future-Self Routing)
 You MUST use the `add_message` MCP tool to send an A2A message to your own agent identity (e.g., `to: '@me'` or your explicit handle). The body of this message MUST contain the **full Sunset Protocol markdown payload** (the output from Steps 1-6), alongside the `Origin Session ID`.
 
-Set `wakeSuppressed: true` and `taggedConcepts: ['sunset-protocol-handover']` on this self-DM: self-addressed, it is the one quiet agent-to-agent direct message the rule allows (a peer address always wakes, neo-agent-brain#1250; a human or system address keeps its own policy) — mailbox-only, unread at the next boot check, no `SENT_TO_ME` wake into the closing session. Do not mark this continuity ping read in the same sunset flow. Peer broadcasts may stay quiet for `scope: solo-refresh` unless a cross-peer handoff needs them.
+Set `wakeSuppressed: true` and `taggedConcepts: ['sunset-protocol-handover']` on this self-DM: self-addressed, it is the one quiet agent-to-agent direct message the rule allows (a peer address always wakes, neo-agent-brain#1250) — mailbox-only, no `SENT_TO_ME` wake into the closing session. Do not mark this continuity ping read in the same sunset flow. Peer broadcasts may stay quiet for `scope: solo-refresh` unless a cross-peer handoff needs them. This self-DM is the sunset receipt neomjs/neo-agent-brain#1383 reads at the context gate before asking neomjs/neo-agent-institution#842 for the fresh session: at night the seat writes it and ends; by day the sunset stays its call.
 
 **Seat memory layer — conditional mention only:** the seat's loader owns the boot/compaction load, so the ping does NOT routinely tell the next session to read the layer (that procedural fallback silently becomes the real path again). Name the layer in the ping ONLY when the load is known degraded — Kimi: the `<seat-memory-layer>` marker was absent this session (diagnosis route: seat `config.toml` `[[hooks]]` entries, emitted hook script, sentinel state dir); OpenCode: the boot files' content was absent (diagnosis route: the `instructions` array in `opencode.jsonc`) — or a seat memory migration is actively in progress.
 

package/.agents/skills/skills.manifest.json

@@ -151,7 +151,7 @@
     },
     "session-sunset": {
       "name": "session-sunset",
-      "description": "Protocol for ending an agent session without Zero-State Amnesia; use at >75% context window, ~2x post-recovery session size at a quiet point, a macro-semantic pivot, or human directive (never task completion/wait).",
+      "description": "End a session without Zero-State Amnesia; use at ≤200k context tokens (the wake plane's gate; >75% window only without a gauge), a macro-semantic pivot, or human directive (never task completion/wait).",
       "routerByteBudget": 17
     },
     "structural-pre-flight": {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "neo-agent-skills",
-  "version": "0.1.78",
+  "version": "0.1.79",
   "description": "Install the workflow substrate a cross-model AI team actually runs on: ticket intake, PR review gates, lane coordination and guards, versioned as a package. The skills Neo.mjs maintainers load every session — materialized into your repo, not copied.",
   "type": "module",
   "license": "MIT",