Skip to content

Coherence 1.11.0 from npm; Swift plugin on plugin API 4 - #42

Open
daniloc wants to merge 1 commit into
mainfrom
claude/project-thread-4ojq2s
Open

daniloc wants to merge 1 commit into
mainfrom
claude/project-thread-4ojq2s

Conversation

@daniloc

@daniloc daniloc commented Oct 27, 2026

Copy link
Copy Markdown
Owner

Requested by Danilo · project thread

What changed

  • mnemion-js and mnemion-swift now pin @posthog/coherence ^1.11.0 from npm, replacing the 1.11.0-beta.3 GitHub tarball, which has since been deleted. Both lockfiles now resolve to registry.npmjs.org/.../coherence-1.11.0.tgz.
  • Swift plugin: pluginApi 3 → 4. API 4 refuses an interfaces table that answers anything besides serverBounds, so isDefaultExport is removed from swift-scope.js. The parser now handles that reading.

Verification (Linux container)

  • coherence:spec, worker: 0 problems. Swift: 0 problems.
  • coherence:plugin-check, Swift: the parser duties pass (file rule, declarations, answers agree, reference reading, mass, imports, entrances, one answer each). Before the plugin change, "one answer each" failed on isDefaultExport. The sourcekit-lsp duties (references, server agrees, chokepoint, interfaces) did not run, because the container has no Swift toolchain.
  • npm test / coherence:run, worker: could not run here. The vitest pool needs CLOUDFLARE_API_TOKEN for the remote AI and Vectorize bindings, and the container doesn't have one, so every test file failed to start. This comes from the environment and not from the upgrade, but it means the oracles still need a run on a machine with Cloudflare credentials.
  • coherence:hooks-check: mnemion-js/.claude/settings.json matches. The root .claude/settings.json reports all 7 events as drifted. That drift comes from f6a77e5, which hand-widened the root hooks so the Swift project joins the hook roots, and it doesn't come from 1.11. I left it untouched, because running hooks install would revert that change.

Generated by Claude Code

Both projects move off the deleted 1.11.0-beta.3 GitHub tarball to the
npm release. Plugin API 4 reads interface facts other than serverBounds
through the parser alone, so the Swift plugin drops isDefaultExport.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014qe3NbTU15Nern3rj4gjAW
@daniloc daniloc self-assigned this Oct 27, 2026
@cloudflare-workers-and-pages

Copy link
Copy Markdown

Deploying with  Cloudflare Workers  Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status Name Latest Commit Updated (UTC)
✅ Deployment successful!
View logs
mnemion 2a72491 Oct 27 2026, 10:28 PM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants