@gyoungwe/research-suite 0.1.0 → 0.1.1

package/README.md

@@ -6,6 +6,6 @@ packages, so the manifest points at each bundled dependency's `dist` and
 `skills` paths and `bundleDependencies` keeps all three packages inside the
 tarball. The Pi host remains a peer dependency and is never duplicated.
 
-The `0.1.0` package is published under the `@gyoungwe` scope. The repository
+The `0.1.1` package is published under the `@gyoungwe` scope. The repository
 keeps the manifest, bundle declarations and offline unpacked fixture as release
 gates; install the published package with `pi install npm:@gyoungwe/research-suite`.

package/node_modules/@gyoungwe/pi-core/README.md

@@ -0,0 +1,10 @@
+# @gyoungwe/pi-core
+
+Portable Pi extension for Drone's task ledger and user-facing core tools:
+`ask_user`, `set_status`, `todo`, `deliver_files`, and `memory_save`.
+
+The package also registers the `@drone/tasks` runtime. Native Pi uses the
+extension context's `ctx.ui`; Drone Desktop can inject its existing ask gate
+through `registerPiCore(pi, { ask })`. The package has no Electron, backend, or
+renderer dependency and keeps all task and memory data in the existing `.pi`
+locations.

package/node_modules/@gyoungwe/pi-core/build-manifest.json

@@ -0,0 +1,8 @@
+{
+	"version": 1,
+	"generator": "scripts/build-pi-core.mjs",
+	"inputsSha256": "0a7a9931d9c82a304460a498ea8611a741c5eb9cd74c865831058f357f031f73",
+	"outputs": {
+		"dist/index.mjs": "34036b70dd1f62e9ec23d3f4f6c9f2ba1a0e085cac6975860bbb587f91ec3a84"
+	}
+}