@gyoungwe/research-suite 0.1.0 → 0.1.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (27) hide show
  1. package/README.md +6 -9
  2. package/build-manifest.json +11 -0
  3. package/node_modules/@gyoungwe/pi-core/README.md +10 -0
  4. package/node_modules/@gyoungwe/pi-core/build-manifest.json +8 -0
  5. package/node_modules/@gyoungwe/pi-core/dist/index.mjs +17412 -0
  6. package/node_modules/@gyoungwe/pi-core/package.json +62 -0
  7. package/node_modules/@gyoungwe/pi-knowledge/README.md +27 -0
  8. package/node_modules/@gyoungwe/pi-knowledge/build-manifest.json +13 -0
  9. package/node_modules/@gyoungwe/pi-knowledge/dist/index.mjs +13103 -0
  10. package/node_modules/@gyoungwe/pi-knowledge/lib/knowledge/runtime/worker.mjs +1680 -0
  11. package/node_modules/@gyoungwe/pi-knowledge/package.json +48 -0
  12. package/node_modules/@gyoungwe/pi-knowledge/plugin.manifest.json +27 -0
  13. package/node_modules/@gyoungwe/pi-knowledge/skills/research-show-me/SKILL.md +18 -0
  14. package/node_modules/@gyoungwe/pi-knowledge/skills/research-vault/SKILL.md +143 -0
  15. package/node_modules/@gyoungwe/pi-research/README.md +16 -0
  16. package/node_modules/@gyoungwe/pi-research/build-manifest.json +8 -0
  17. package/node_modules/@gyoungwe/pi-research/dist/index.mjs +16404 -0
  18. package/node_modules/@gyoungwe/pi-research/package.json +58 -0
  19. package/node_modules/@gyoungwe/pi-research/skills/research-workflow/SKILL.md +15 -0
  20. package/node_modules/@gyoungwe/plugin-api/README.md +15 -0
  21. package/node_modules/@gyoungwe/plugin-api/dist/index.d.ts +146 -0
  22. package/node_modules/@gyoungwe/plugin-api/dist/index.d.ts.map +1 -0
  23. package/node_modules/@gyoungwe/plugin-api/dist/index.js +86 -0
  24. package/node_modules/@gyoungwe/plugin-api/dist/index.js.map +1 -0
  25. package/node_modules/@gyoungwe/plugin-api/package.json +35 -0
  26. package/package.json +44 -55
  27. package/plugin.manifest.json +34 -0
package/README.md CHANGED
@@ -1,11 +1,8 @@
1
1
  # @gyoungwe/research-suite
2
2
 
3
- The suite package aggregates `@gyoungwe/pi-core`, `@gyoungwe/pi-knowledge` and
4
- `@gyoungwe/pi-research`. Pi does not automatically load resources from dependency
5
- packages, so the manifest points at each bundled dependency's `dist` and
6
- `skills` paths and `bundleDependencies` keeps all three packages inside the
7
- tarball. The Pi host remains a peer dependency and is never duplicated.
8
-
9
- The `0.1.0` package is published under the `@gyoungwe` scope. The repository
10
- keeps the manifest, bundle declarations and offline unpacked fixture as release
11
- gates; install the published package with `pi install npm:@gyoungwe/research-suite`.
3
+ The suite aggregates the published `@gyoungwe/pi-core`,
4
+ `@gyoungwe/pi-knowledge`, and `@gyoungwe/pi-research` packages. The release
5
+ tarball bundles those dependencies so a Pi host can discover the extensions and
6
+ skills without a second network resolution step. `research-workflow` comes
7
+ from `@gyoungwe/pi-research`; `@gyoungwe/pi-knowledge` supplies the Vault and
8
+ Show Me skills, so the suite exposes one copy of each skill.
@@ -0,0 +1,11 @@
1
+ {
2
+ "version": 1,
3
+ "generator": "packages/research-suite/scripts/build.mjs",
4
+ "packageVersion": "0.1.2",
5
+ "bundled": [
6
+ "@gyoungwe/pi-core",
7
+ "@gyoungwe/pi-knowledge",
8
+ "@gyoungwe/pi-research"
9
+ ],
10
+ "dependenciesSha256": "226c3c4a28a71df1f571ff6a977d3798d9ccc0914297292772a636f45abf5716"
11
+ }
@@ -0,0 +1,10 @@
1
+ # @gyoungwe/pi-core
2
+
3
+ Portable Pi extension for Drone's task ledger and user-facing core tools:
4
+ `ask_user`, `set_status`, `todo`, `deliver_files`, and `memory_save`.
5
+
6
+ The package also registers the `@drone/tasks` runtime. Native Pi uses the
7
+ extension context's `ctx.ui`; Drone Desktop can inject its existing ask gate
8
+ through `registerPiCore(pi, { ask })`. The package has no Electron, backend, or
9
+ renderer dependency and keeps all task and memory data in the existing `.pi`
10
+ locations.
@@ -0,0 +1,8 @@
1
+ {
2
+ "version": 1,
3
+ "generator": "scripts/build-pi-core.mjs",
4
+ "inputsSha256": "0a7a9931d9c82a304460a498ea8611a741c5eb9cd74c865831058f357f031f73",
5
+ "outputs": {
6
+ "dist/index.mjs": "34036b70dd1f62e9ec23d3f4f6c9f2ba1a0e085cac6975860bbb587f91ec3a84"
7
+ }
8
+ }