@haaaiawd/second-nature 0.1.29 → 0.1.30

package/index.js

@@ -58,23 +58,11 @@ import { fileURLToPath } from "node:url";
 import { startRuntimeService, } from "./runtime/core/second-nature/runtime/service-entry.js";
 import { getLifecycleState, recordRegistration, } from "./runtime/core/second-nature/runtime/lifecycle-service.js";
 import { openWorkspaceOpsBridge } from "./workspace-ops-bridge.js";
-// definePluginEntry is OpenClaw's canonical factory for non-channel plugins
-// (provider/tool/command/service/memory/context-engine). At runtime it returns
-// a plain options object; it does NOT add a brand symbol — earlier debugging
-// rounds wrongly assumed the factory was the "plain-capability" marker. The
-// real classification happens via manifest fields (see file header). We still
-// use the factory because it is the documented, supported entry shape, and
-// keeping it future-proof against SDK option-processing changes.
-//
-// IMPORTANT — keep this a STATIC import. The packaged runtime is loaded inside
-// OpenClaw's vm sandbox, which rejects top-level await (manifests as
-// "SyntaxError: Unexpected identifier 'Promise'" at host load time). The same
-// constraint applies to the sql.js async bootstrap noted in the file header.
-// In production the host always provides `openclaw` as a sibling module under
-// ~/.openclaw/npm/node_modules/, so this resolves synchronously. Locally,
-// `openclaw` is declared as a devDependency so build and tests resolve via
-// the same import path.
-import { definePluginEntry } from "openclaw/plugin-sdk/plugin-entry";
+// Keep the entry as a plain object instead of importing OpenClaw's
+// SDK entry helper. Upload/package validators may import this module
+// before the host SDK is installed; a static SDK import turns a valid package
+// into ERR_MODULE_NOT_FOUND. OpenClaw classifies this plugin from the manifest
+// fields, and the helper returns this same object shape at runtime.
 // Stderr sentinels make daemon load-path observable in `gateway.log`. Three
 // lines should appear at startup: "module evaluated", "register() entered ...",
 // "register() completed". Their absence after `openclaw gateway run` proves
@@ -1189,7 +1177,7 @@ const SECOND_NATURE_TOOL_SCHEMA = {
     },
     required: ["command"],
 };
-export default definePluginEntry({
+export default {
     id: "second-nature",
     name: "Second Nature",
     description: "Registers command/tool/service surface with load-reload lifecycle semantics.",
@@ -1264,4 +1252,4 @@ export default definePluginEntry({
         });
         process.stderr.write("[second-nature] register() completed\n");
     },
-});
+};

package/openclaw.plugin.json

@@ -1,7 +1,7 @@
 {
   "id": "second-nature",
   "name": "Second Nature",
-  "version": "0.1.29",
+  "version": "0.1.30",
   "description": "OpenClaw native plugin with synchronous surface registration and bundled runtime spine. Set SECOND_NATURE_WORKSPACE_ROOT or tool workspaceRoot to the same path as the agent workspace. Agent inner guide is packaged as agent-inner-guide.md. v7 ops surface: self_health, tool_affordance, heartbeat_digest, narrative:diff, timeline, restore, runtime_secret_bootstrap.",
   "activation": {
     "onStartup": true,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@haaaiawd/second-nature",
-  "version": "0.1.29",
+  "version": "0.1.30",
   "description": "OpenClaw native plugin with synchronous registration, a packaged runtime artifact, and operator-facing status/explain flows.",
   "keywords": [
     "openclaw",