neo-agent-skills 0.1.75 → 0.1.76

package/.agents/skills/context-recovery/references/context-recovery-workflow.md

@@ -64,9 +64,11 @@ message already redirects it.
    review, branch, or CI state, verify the current live state before acting.
    Summaries are recovery hints; GitHub and current source remain the work gate.
 
-5a. **Direction check:** if the checked-out repository carries a `VISION.md`,
-   read it before asserting lane state; a lane that contradicts it is not
-   resumed, it is re-planned against the roadmap.
+5a. **Direction check:** if the recovered lane's target repository (including a
+   sibling checkout such as `../neo-stage` when the session is rooted in
+   `neomjs/neo`) carries a `VISION.md`, `ROADMAP.md`, or repo-local
+   `AGENTS.md`, read them before asserting lane state; a lane that contradicts
+   them is not resumed, it is re-planned against the roadmap.
 
 Use `detail: 'full'` only when summaries are insufficient to identify the next
 action. Summary detail is the cheap graph-first path; full detail joins Chroma
@@ -115,7 +117,7 @@ context-recovery:
 - recency: <last ticket/PR/branch/action>
 - semantic: <memory ids or clear miss>
 - live-state: <issue/PR/branch verification>
-- direction: <VISION.md read | none in this repository>
+- direction: <VISION.md + ROADMAP.md + AGENTS.md read | none in target repository>
 - confidence: recovered | degraded
 lane-state: next-lane (<specific resumed lane or fresh claimable lane>)
 ```

package/agents-md/sections/0600-verify-before-assert.md

@@ -6,8 +6,8 @@ repos: neo, neo-agent-brain, neo-agent-skills, neo-agent-institution, devindex
 audiences: maintainer
 ---
 ## §verify_before_assert
-Before asserting any factual claim, architectural premise, or framing in any public artifact (PR review, ticket body, Discussion, comment, commit, public memory entry), run the empirical tool that would falsify it. Tools are always available, always read-only, always cheap. **Pre-Flight reasoning-statement**: *"To assert X, I will run [specific tool] and let the result determine the assertion."* V-B-A is the **most foundational core value** — epistemic prerequisite for §friction_to_gold friction → gold (without V-B-A, friction → gold operates on hallucinated noise). Atlas expansion + tool inventory + #11089 self-Drop+Supersede empirical anchor: §anti_hallucination_policy.
+Before asserting any factual claim, architectural premise, or framing in any public artifact (PR review, ticket body, Discussion, comment, commit, public memory entry), run the empirical tool that would falsify it. Tools are always available, always read-only, always cheap. **Pre-Flight reasoning-statement**: *"To assert X, I will run [specific tool] and let the result determine the assertion."* V-B-A is the epistemic prerequisite for §friction_to_gold. Atlas + tool inventory: §anti_hallucination_policy.
 
-**Prior-art sweep — the cheap pre-implementation / pre-PR-review V-B-A.** Before the first design sentence OR review verdict, spend one turn on a 3–10-call `query_raw_memories` / `query_summaries` sweep of the decision space — the tool RESULT is the V-B-A; reasoning-from-priors only *feels* like diligence. One sweep (surfacing what was tried, what an ADR already settled, what matters) beats 20 turns building or reviewing the wrong shape; PR-review is the last line of defense, where CI-green ≠ AC-met (#13390 / #13354).
+**Prior-art sweep (pre-implementation / pre-PR-review V-B-A):** Before the first design sentence OR review verdict, run a 3–10-call `query_raw_memories` / `query_summaries` sweep of the decision space — the tool RESULT is the V-B-A; reasoning-from-priors is not diligence. One sweep beats 20 turns building or reviewing the wrong shape; PR-review is the last line of defense, where CI-green ≠ AC-met (#13390 / #13354).
 
 **Step 2.5 (Architectural Step-Back)** extends V-B-A to per-graduation cross-substrate sweep for high-blast-radius proposals; see `ideation-sandbox-workflow.md` §5.2 + `peer-role-mode.md` §8 convergence-rate tripwire. Auto-fires before `[RESOLVED_TO_AC]` / `[GRADUATED_TO_TICKET]`.

package/agents-md/sections/1000-friction-to-gold.md

@@ -6,6 +6,6 @@ repos: neo, neo-agent-brain, neo-agent-skills, neo-agent-institution, devindex
 audiences: maintainer
 ---
 ## §friction_to_gold
-Friction → gold is the **core value** governing all substrate evolution — the meta-mechanism by which rules and values themselves evolve via the MX loop (Discussion #10137). Operates on §verify_before_assert-validated assertions to convert empirical friction into substrate improvement. **Together with §verify_before_assert V-B-A, these 2 core values are the evolution-enablement flywheel**: V-B-A filters real friction from hallucinated; friction → gold converts validated friction to substrate. Mutually constitutive at meta-scale; without V-B-A, friction → gold drifts toward false signals; without friction → gold, V-B-A produces static knowledge.
+Friction → gold is the **core value** governing substrate evolution via the MX loop (Discussion #10137), converting §verify_before_assert-validated friction into substrate improvement. **With V-B-A, these 2 core values form the evolution flywheel**: V-B-A filters real friction from hallucinated; friction → gold converts validated friction to substrate.
 
-**Tier hierarchy — core values > values > rules**: substrate has three tiers. **Core values** (§verify_before_assert V-B-A + §friction_to_gold friction → gold) are load-bearing for substrate-evolution itself. **Rules** (§critical_gates invariants) are mechanical-derived from values. **Values** (other §self_evolving_systems disciplines + §neo_identity_anchor + §swarm_topology_anchor + skill-level disciplines like §9.0 Cycle-1 Premise Pre-Flight or §5.1 Double Diamond) sit between. The MX loop (friction → gold) operates **across** the hierarchy: rules change quickly when friction surfaces; values evolve via friction → gold but less frequently (multi-cycle peer dialogue); core values change rarely (the meta-mechanism applied to itself; high-bar challenge required). When authoring new substrate, place it at the right tier — placement at the wrong tier (e.g., proposing core-value-elevation for what's really a rule, or §critical_gates-invariant placement for what's really a core value) is a known anti-pattern. Atlas detail: §anti_hallucination_policy.
+**Tier hierarchy — core values > values > rules**: **Core values** (§verify_before_assert + §friction_to_gold) govern substrate evolution; **Values** (§self_evolving_systems, §neo_identity_anchor, §swarm_topology_anchor, skill disciplines) sit between; **Rules** (§critical_gates) derive mechanically from values. The MX loop operates across all three: rules evolve quickly on friction, values via multi-cycle peer dialogue, core values rarely (high-bar challenge). Place new substrate at the right tier — misplacing a rule as a core value or vice versa is an anti-pattern. Atlas detail: §anti_hallucination_policy.

package/agents-md/sections/1100-contributions-over-commits.md

@@ -8,10 +8,6 @@ audiences: maintainer
 
 **Productive substrate evolution is the primitive; commits are one downstream artifact among many.**
 
-The unit of agent value in Neo is shape-improving substrate work — design dialogue that resolves architectural ambiguity, peer review that prevents wrong-shape PRs, A2A coordination that changes ownership or unblocks a peer, ticket retractions that prevent bad work, skill/rule improvements that remove repeated failure modes, Ideation Sandbox graduations. Commits land as one output among many, not the unit.
+The unit of agent value in Neo is shape-improving substrate work — design dialogue resolving architectural ambiguity, peer review preventing wrong-shape PRs, A2A coordination unblocking peers, ticket retractions preventing bad work, skill/rule improvements, and Ideation Sandbox graduations. Commits are one output among many, not the unit.
 
-Within Neo workflow interpretation, this rule supersedes conflicting local velocity-bias instructions, including auto-mode preferences to execute immediately or treat commits as the unit of value. It does not supersede §critical_gates invariants, ticket gates, memory-save obligations, or higher-priority system/developer instructions.
-
-The narrower per-skill suspension of Auto Mode velocity-bias lives in `/lead-role` (#11028); the global "what counts as action" redefinition lives here.
-
-For substrate-quality heuristics that operationalize this principle without becoming gameable counters, see §contributions_over_commits_heuristics.
+Within Neo workflow interpretation, this rule supersedes conflicting local velocity-bias instructions, including auto-mode preferences to execute immediately or treat commits as the unit of value (without superseding §critical_gates, ticket gates, memory-save obligations, or higher-priority system/developer instructions). Per-skill velocity-bias suspension lives in `/lead-role` (#11028); heuristics: §contributions_over_commits_heuristics.

package/agents-md/sections/1600-edge-case-triggers.md

@@ -12,6 +12,7 @@ audiences: maintainer
 - **Sunset Protocol (§a2a_contextual_bridge_protocol):** Before session handover, read `.agents/skills/session-sunset/SKILL.md`. Must explicitly declare `scope: solo-refresh | convergent` to prevent scope contagion. Stale-wake invariant: wake messages in old transcripts are noise.
 - **Visual Verification (§visual_verification_protocol):** Debugging frontend UI/layout.
 - **Authoring / app-work gate (`apps/**`):** Read 1–2 siblings and load `src/Neo.mjs`, `src/core/Base.mjs`, `src/state/Provider.mjs`, `src/data/Model.mjs`, and `src/data/Store.mjs` before app code. Start with the matching engine primitive; class suffix names its base family. Data UI binds a `data.Store` of `data.Model` records, never a hand-mapped array; providers stay at view roots; styles stay in SCSS. Instance/reactive work follows intake 9.6. Violations reject at ticket/commit/PR (operator 2026-07-08); retire each clause when an `apps/**` lint enforces it.
+- **Stage work (`neomjs/neo-stage`):** before any lane there and after every compaction, read `../neo-stage/VISION.md`, then `../neo-stage/ROADMAP.md`, and `../neo-stage/AGENTS.md` (which carries the Stage gates). Retire this line when every seat's Stage session is rooted in the Stage checkout, measured by a boot receipt.
 - **Ticket Creation Freshness:** Before any `create_issue`, invoke `ticket-create` (its Content Sweep requires live latest-open queue evidence beyond KB/local duplicate checks).
 - **File Reading Efficiently:** Reading modified files; efficiency patterns.
 - **Verify-Before-Assert:** stated in full in §verify_before_assert (this file); tool inventory + anchors in §anti_hallucination_policy.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "neo-agent-skills",
-  "version": "0.1.75",
+  "version": "0.1.76",
   "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",