[Upd4ting]

Summary

Moves every @antelopejs/* dependency to its npm latest from the 2026-11-12 release pass (ANT-2140). Lockfiles were refreshed with pnpm 10.6.5, and no other package moved.

 package.json
-  "@antelopejs/core": "^1.21.1",
-  "@antelopejs/tooling-configs": "^0.5.1",
+  "@antelopejs/core": "^1.21.3",
+  "@antelopejs/tooling-configs": "^0.5.4",
   "@antelopejs/interface-core": ">=0.4.0 <1.0.0"   # unchanged on purpose (AGENTS.md Versioning)

 pnpm-lock.yaml, playground/pnpm-lock.yaml
-  @antelopejs/core 1.21.1, tooling-configs 0.5.1, interface-core 0.4.0
+  @antelopejs/core 1.21.3, tooling-configs 0.5.4, interface-core 0.4.1

pnpm run sync writes nothing for 0.5.4, so AGENTS.md and the verify skill stay as they are. The README names no versions.

Evidence

• Before: main locks core 1.21.1, tooling-configs 0.5.1 and interface-core 0.4.0. npm view <pkg> dist-tags.latest gives 1.21.3, 0.5.4 and 0.4.1.
  After: the lockfiles resolve exactly those latest versions.

Checks on this branch:

$ pnpm run checks
Checks: 12 passed, 0 failed.
$ pnpm test
  template-module beta
    ✔ logs a message through the module implementation
  1 passing
$ pnpm exec antelopejs-check-interface-ranges   # exit 0
$ pnpm build && pnpm --dir playground build     # exit 0
$ pnpm install --frozen-lockfile && pnpm --dir playground install --frozen-lockfile   # exit 0

antelopejs-verify journey <run> --plan ran at e05f62a. Every feature ran because package.json and pnpm-lock.yaml are shared files:

PASS smoke/module-build (9.7 s)
PASS docs/scaffold-docs (6.8 s)
PASS git/scaffold-gitignore (9.8 s)
PASS module/scaffold-shape (0.4 s)
PASS module/module-build (reuses smoke/module-build, not run again)
PASS playground/playground-dev (17.4 s)
PASS tests/module-test (3.3 s)
PASS tests/module-test-fails (2.7 s)
PASS tooling/scaffold-lint-rejects (4.3 s)
PASS tooling/scaffold-checks (6.3 s)

From the evidence:

• The scaffolded module installs core 1.21.3, tooling-configs 0.5.4 and interface-core 0.4.1 from the frozen lockfile.
• Its pnpm run checks prints Checks: 10 passed, 0 failed.
• The playground logs [INFO] Hello world and exits 130 on Ctrl+C.

A separate subagent judged the run with antelopejs-verify verdict.

Manual end-to-end check, done the way a user would:

1. ajs module init my-module --template 'Module Typescript' --pm pnpm --git-init from the offline manifest, then pnpm install --frozen-lockfile and pnpm run build.
2. ajs project init blank --template blank-typescript --pm pnpm.
3. ajs project modules add --mode local ../my-module, with the blank project's start calling the module's Log.

$ ajs project dev --watch
✔ Installed dependencies for my-module
✔ Installed dependencies for antelopejs-module
✔ Loaded 2 modules
✔ Constructed modules
[INFO] Hello from the blank project

This is not caused by this change: a fresh module and a fresh blank project both use the package name antelopejs-module. With that clash, modules add prints Skipped antelopejs-module: already in the project until the module's placeholder name is renamed.

Merge Danger

Door: two-way

Only devDependency ranges and lockfiles changed. Reverting the commit restores the previous resolution.

Blast Radius: scaffolds

Modules created from the template after merge start on core 1.21.3 and tooling-configs 0.5.4. Existing modules are unaffected.