v0.6.0 — Workflow v3, Claude Code plugin, MCP Registry

Install

npx graphyloop                 # all 7 harnesses it detects

Claude Code plugin:

/plugin marketplace add chadixearth/graphyloop
/plugin install graphyloop@graphyloop

MCP Registry: io.github.chadixearth/graphyloop (npx -y graphyloop mcp)

0.5.0 was tagged but never reached npm: npm trusted publishing was not set up
for the package, so the tag's publish run failed with E404 PUT. 0.6.0
contains everything from 0.5.0 (CHANGELOG).

Changed

• Workflow v3: 12 rules updated to October 2026 practice. The rules now
  start from measured costs (a dispatch costs the driver about 12 minutes of
  waiting; an inline edit costs seconds) and from what current field reports
  find works:
  • Goal and proof up front: state the end state, the check that proves
    it and the invariant it must not break; never meet a target by weakening
    a test.
  • Inline first: up to 8 known files in any mix of layers (was 3).
    Fan out only when the work splits into 2+ independent slices of about
    5 minutes each. Use 1-3 lanes, and the driver keeps the largest or most
    coupled slice and builds it while the lanes run. The driver writes the
    context pack itself when one read pass maps the code.
  • Isolate what collides: a lane that runs servers, databases or
    browsers gets its own worktree, port and database name.
  • No polling; schedule follow-ups: later checks go to the harness
    scheduler (/loop, /schedule) instead of sleep loops.
  • Proof, not claims: failing-before/passing-after, a real-browser
    screenshot, before/after numbers from the same machine, the live URL. The
    rules also list what is NOT evidence ("tests pass" alone, a typecheck
    alone, "should work", a mocked run).
  • Review by blast radius: review and security lanes run for migrations,
    auth, payments, secrets, tenant boundaries, public APIs and the project's
    named central files; everything else is covered by proof.
  • Keep the rules honest: short always-loaded rules with procedures in
    on-demand skills, guidance checked with with/without runs, and anything
    that must survive compaction written to files.
  • Memory entries record the why and the commit or PR it landed in.
• plan_feature reports inlineThreshold: 8, and its notes say the driver
  writes wave 0 itself when it can map the code and keeps one wave-1 lane.
  The builder, contract and verifier footers are unchanged.
• agent-chadi, graphyloop-workflow, /chadi-fast, /chadi-go, the Codex
  prompts, the dsh graphyloop-squad skill and swarm-memory follow Workflow
  v3.

Added

• Claude Code plugin. Run /plugin marketplace add chadixearth/graphyloop,
  then /plugin install graphyloop@graphyloop. You get the 15
  /graphyloop:chadi-* commands, 26 agents, the 3 core skills and the MCP
  server (npx -y graphyloop@0.6.0 mcp). The plugin lives in
  integrations/claude-code/ and is generated from the canonical sources by
  npm run build:integrations (CI runs --check). For Claude Code, use either
  the plugin or npx graphyloop --harness claude, not both.
• MCP Registry. The server is listed as io.github.chadixearth/graphyloop:
  mcpName in package.json plus a root server.json. publish.yml
  publishes it with GitHub OIDC after the npm release and skips a version that
  is already listed.
• Agent Skills standard. --harness codex and --harness cursor now
  install the bundled skills into ~/.agents/skills, the cross-tool user
  skills directory that Codex and Cursor read (before this, neither harness
  received any skills). The ownership rules match the other harnesses.
  Uninstall removes untouched copies only after the last harness that uses the
  directory is gone.
• npm version regenerates the plugin and server.json, so their versions
  never drift from package.json.

Fixed

• Releases: the one-time trusted-publishing setup is now one command,
  npm trust github graphyloop --file publish.yml --repository chadixearth/graphyloop
  (see CONTRIBUTING). The E404 PUT failure mode is documented.

Full changelog: v0.5.0...v0.6.0