…gelog backfill (B/8) (#574) * chore(packaging): manifest+peerdep drift guards, Windows install, #510 changelog backfill Five separate sub-fixes that all touch packaging/process surface and review together cleanly: * test/manifest.test.ts: guard against contracts.tools / registerTool name drift. PR #555 hand-listed 4 tool names in openclaw.plugin.json; nothing prevented the next added/renamed tool from re-introducing the silent-compaction-disabled failure mode. * package.json peerDependencies: tighten @mariozechner/pi-* from "*" to ">=0.66 <1" so the next major silently mismatches at install time rather than runtime. * package.json openclaw.compat.pluginApi: add upper bound (>=2026.2.17 <2026.6.0) and a `tested:` array so `openclaw plugins doctor` can flag known-incompatible host versions instead of leaving users with the silent-load behavior #555 fixed. * .github/workflows/ci.yml: add a smoke-install job against the latest published openclaw, asserting plugin registers and lcm_* tools wire up. Catches host-side breaks like #555 before users hit them. * openclaw.plugin.json: declare kind: "context-engine" to disambiguate the Windows installer's hook-pack detector (#451). * .changeset: retroactive entry crediting jalehman for #510, which was in the v0.9.2…v0.9.3 commit delta but absent from the release notes. Closes #570, closes #571. Refs #497, #501, #527, #555, #483, #451, #384, #447, #492, #510, #511, #521. * ci: scope smoke-latest-openclaw to bundle loadability only The initial smoke job called plugin.register() against a stub api that omitted the modelAuth surface (and others) the real register path reaches into. The throw was caught, but registeredTools stayed empty and the assertion `registeredTools.length >= 4` then exit 1'd — a self-inflicted failure that doesn't map to any real host-side regression. Pivot the smoke to what we can verify without a richer fixture: - bundle imports cleanly (catches esbuild externals / ESM resolution changes) - `mod.default.register` is a callable function (catches missing default export + register-shape changes) A "register against the real openclaw plugin loader" check would be the right way to catch #555-class regressions on host-version bumps, but that needs a richer fixture than CI can stub up cheaply. Note in the comment block. Refs: #570, #555. * fix(packaging): manifest test resilience + smoke prune + changeset wording Address review on #574: * test/manifest.test.ts: discover `src/tools/lcm-*-tool.ts` files dynamically via directory scan (was a hard-coded TOOL_FACTORY_FILES list). Adding a new tool no longer requires updating this test. Loosen the registerTool factory matcher to accept arrow-block bodies (`(ctx) => { return createXTool(...) }`), arrow-expression bodies, and async arrows — so a refactor to a different arrow shape doesn't fail the drift guard spuriously. * .github/workflows/ci.yml: add `npm prune --omit=dev` between build and openclaw install, so the smoke import resolves `@mariozechner/pi-*` from `openclaw@latest`'s transitive deps rather than from the pinned 0.66.1 devDependency we ship for local builds. Catches install-time mismatches that would otherwise hide behind the pinned versions. * .changeset/manifest-peerdep-windows-guards.md: the workflow's smoke job no longer claims to call `plugin.register(...)` and assert registerTool wiring (that path requires more host-runtime fixture than is reasonable to maintain — see #555 for the regression class). The changeset now describes the actual scope: bundle import, latest `openclaw` co-installed, callable `register` export. Manifest drift is covered by the dedicated unit test. * .changeset/retroactive-510-bootstrap-ingest-protections.md: explicit "@jalehman" credit in the body so the next changesets-rendered release note attributes #510 to its real author rather than to the PR introducing the retroactive entry. Test count unchanged at 836. * test(manifest): drop duplicate kind=context-engine assertion `test/config.test.ts > "declares context-engine kind so OpenClaw core binds the contextEngine slot on install"` already covers the `manifest.kind === "context-engine"` invariant — and that single assertion also satisfies the Windows-installer hook-pack-detector concern from #451 since the `kind` field is the same discriminator in both cases. Replaced the duplicate manifest.test.ts assertion with a comment pointing readers to the canonical location to avoid the maintenance burden of updating two tests if the kind ever changes again. Addresses review on #574. --------- Co-authored-by: Eva <eva@100yen.org>

Can the plugin dependencies be streamlined? #447

Description

Metadata

Metadata

Assignees

Labels

Type

Fields

Projects

Milestone

Relationships

Development

Issue actions