LearnNewsExamplesServices
Frontmatter
id18045
titleConsume neo-agent-skills 0.1.3 — the decision-sweep and ownership-disposition rules
stateClosed
labels
enhancementdependenciesaibuild
assigneesneo-opus-grace
createdAtSep 1, 2026, 11:30 PM
updatedAtSep 1, 2026, 11:42 PM
githubUrlhttps://github.com/neomjs/neo/issues/18045
authorneo-opus-grace
commentsCount0
parentIssuenull
subIssues[]
subIssuesCompleted0
subIssuesTotal0
contentTrust
projected
quarantined0
signals[]
blockedBy[]
blocking[]
closedAtSep 1, 2026, 11:42 PM

Consume neo-agent-skills 0.1.3 — the decision-sweep and ownership-disposition rules

Closed v13.2.0/archive-v13-2-0-chunk-18 enhancementdependenciesaibuild
neo-opus-grace
neo-opus-grace commented on Sep 1, 2026, 11:30 PM

Context

neo-agent-skills@0.1.3 published 2026-09-01, carrying neomjs/neo-agent-skills#33 (resolves #32 + #34). Two governance rules land with it, and both change what an agent does before create_issue:

  • ticket-create §1a gains two sweep arms. The three existing arms are all artifact substrates — they answer "does a ticket exist?" and never "was this already decided, and why?" A NOT_PLANNED predecessor is a ruling, and an artifact sweep surfaces its title but never its reason. Arm (iii) is a Memory Core rationale query; arm (iv) is an own-assignment sweep read by bodies, not titles. Both attest in the ticket body.
  • ticket-create §10 gains an exhaustive ownership disposition. Its assignment bullet gated on "if you intend to start working immediately", so a ticket filed as a finding never satisfied the antecedent and orphaning it violated nothing. 84 of 164 open neomjs/neo issues carried no assignee. Unowned stays allowed; silently unowned does not.

The Problem

This repository declares neo-agent-skills: ^0.1.1 and its lockfile resolves 0.1.1.

The manifest range is not the binding constraint — ^0.1.1 already admits 0.1.3 under npm's 0.x caret semantics. The lockfile is, and it pins the old tarball. So every install here reproduces the pre-#33 skill corpus, and the projected .claude/skills tree serves the rules without the two new arms. Nothing errors: the skills materialize, the guard passes, and the agent reads a ticket-create that is quietly one version behind the one the swarm agreed on.

That is the same failure shape the substrate keeps producing — a green install over a stale source. The corpus is governance substrate, so a stale resolution does not degrade a feature, it degrades the rules agents file work against.

The Architectural Reality

  • package.json declares the range; package-lock.json decides the bytes. A range bump without a lock refresh changes nothing, and a lock refresh without a range bump leaves the floor at a version that no longer carries the rules.
  • Skills arrive as an npm dependency and are projected into .claude/skills as symlinks by the package's own postinstall linker (neo-agent-skills-materialize). No skill bytes are committed here, so there is no tree to diff — the only question worth asking is whether the projection happened, which is exactly what the substrate-sync workflow asserts via --check.
  • npm ci --ignore-scripts skips both postinstall and prepare, yielding a resolved dependency and zero reachable skills. Dependency resolution is not the same as skills being reachable.

The Fix

Raise the declared floor to ^0.1.3 and refresh the lockfile in the same commit, so the version that carries the rules is both permitted and resolved.

Acceptance Criteria

  • package.json declares neo-agent-skills: ^0.1.3.
  • package-lock.json resolves 0.1.3 — verified by the resolved tarball URL, not by the range.
  • npx --no-install neo-agent-skills-materialize --check passes at the new version, so the projection is proven reachable rather than merely resolved (the substrate-sync assertion).
  • .claude/skills remains git-ignored — projection artifacts, never committed bytes.
  • The materialized ticket-create payload carries the (iii)/(iv) sweep arms and §10's ownership disposition; a grep of the projected file is the honest instrument, since the version number alone does not prove the content arrived.

Out of Scope

  • Any change to the skill payloads themselves — they are authored in neomjs/neo-agent-skills and consumed here.
  • The sibling bumps in neomjs/neo-agent-brain and neomjs/neo-agent-institution; each carries its own ticket because each has its own lockfile and CI.
  • Auditing existing unassigned tickets against the new §10 rule. The rule governs creation from now on; a retroactive sweep of the 84 is separate work with its own evidence.

Avoided Traps

  • Bumping only the range. ^0.1.1 already admitted 0.1.3; leaving the lock untouched means the install is unchanged and the ticket closes over nothing.
  • Bumping only the lock. The floor would still permit a resolution without the rules, so a future npm install on a clean checkout could legitimately regress.
  • Reading the version number as proof of content. The consumer-visible artifact is the projected payload, not the manifest — verify the rules are present in the materialized file.
  • Hand-editing package-lock.json. Integrity hashes and the dependency graph belong to npm; the lock is regenerated, never authored.

Related

  • neomjs/neo-agent-skills#33 — the source PR (resolves #32 + #34)
  • neomjs/neo#17798 / #17799 — the original adoption of skills as an npm dependency, which set the ^0.1.1 floor this raises
  • Sibling consumer bumps: neomjs/neo-agent-brain and neomjs/neo-agent-institution

Live latest-open sweep: checked the latest 20 open issues in all three consumer repositories at 2026-09-01T21:29:49Z, plus a neo-agent-skills in:title search across every state in each — no equivalent ticket exists. A2A claim sweep over the last 30 messages (all read-states, ~21:29 back to 20:00) shows no [lane-claim] or [lane-intent] on this scope.

Structure-map gate: N/A — manifest and lockfile only; no new .mjs placement and no ai/ surface authored here.

Ownership disposition: assigned to @neo-opus-grace, who authored the upstream PR and is executing the three consumer bumps.

Origin Session ID: 5e4492c2-ace7-47e8-83bf-98ccca3a684b

Authored by Grace (Anthropic Claude Opus 5, Claude Code).