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
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).
Context
neo-agent-skills@0.1.3published 2026-09-01, carryingneomjs/neo-agent-skills#33(resolves#32+#34). Two governance rules land with it, and both change what an agent does beforecreate_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?" ANOT_PLANNEDpredecessor 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 openneomjs/neoissues carried no assignee. Unowned stays allowed; silently unowned does not.The Problem
This repository declares
neo-agent-skills: ^0.1.1and its lockfile resolves 0.1.1.The manifest range is not the binding constraint —
^0.1.1already admits0.1.3under npm's0.xcaret semantics. The lockfile is, and it pins the old tarball. So every install here reproduces the pre-#33skill corpus, and the projected.claude/skillstree serves the rules without the two new arms. Nothing errors: the skills materialize, the guard passes, and the agent reads aticket-createthat 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.jsondeclares the range;package-lock.jsondecides 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..claude/skillsas 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 thesubstrate-syncworkflow asserts via--check.npm ci --ignore-scriptsskips bothpostinstallandprepare, 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.3and refresh the lockfile in the same commit, so the version that carries the rules is both permitted and resolved.Acceptance Criteria
package.jsondeclaresneo-agent-skills: ^0.1.3.package-lock.jsonresolves0.1.3— verified by theresolvedtarball URL, not by the range.npx --no-install neo-agent-skills-materialize --checkpasses at the new version, so the projection is proven reachable rather than merely resolved (thesubstrate-syncassertion)..claude/skillsremains git-ignored — projection artifacts, never committed bytes.ticket-createpayload carries the(iii)/(iv)sweep arms and §10's ownership disposition; agrepof the projected file is the honest instrument, since the version number alone does not prove the content arrived.Out of Scope
neomjs/neo-agent-skillsand consumed here.neomjs/neo-agent-brainandneomjs/neo-agent-institution; each carries its own ticket because each has its own lockfile and CI.Avoided Traps
^0.1.1already admitted0.1.3; leaving the lock untouched means the install is unchanged and the ticket closes over nothing.npm installon a clean checkout could legitimately regress.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.1floor this raisesneomjs/neo-agent-brainandneomjs/neo-agent-institutionLive 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:titlesearch 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
.mjsplacement and noai/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).