@webship.co/workspace-sandboxes 1.0.0-alpha1 → 1.0.0-beta1

package/README.md

@@ -37,10 +37,7 @@ The settings file and the docs are placed once and never overwritten: they hold
 | `cmd-tools-cancel-users.sh` |
 | `cmd-tools-checks.sh` |
 | `cmd-tools-clone.sh` |
-| `cmd-tools-graphify.sh` |
 | `cmd-tools-hostnames.sh` |
-| `cmd-tools-obsidian.sh` |
-| `cmd-tools-ragify.sh` |
 | `cmd-tools-reclaim.sh` |
 | `cmd-tools-remove.sh` |
 | `cmd-tools-screen.sh` |

package/features/sandboxes.feature

@@ -4,7 +4,8 @@ Feature: The Sandboxes workspace plugin
 
   Scenario: The workspace page is there
     Given I am on "/sandboxes"
-     Then I should see "Sandboxes"
+     Then the element "h1" should be displayed
+      And the element "#webship-workspace-projects, .items-list, .workspace-page" should be attached
 
   Scenario: The plugin is listed on the Plugins page
     Given I am on "/settings/plugins"

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@webship.co/workspace-sandboxes",
-  "version": "1.0.0-alpha1",
-  "description": "The Sandboxes workspace for Webship Workspace: the `sandboxes/` folder (type sites), its settings file, its 33 commands and its docs, activated as a plugin.",
+  "version": "1.0.0-beta1",
+  "description": "The Sandboxes workspace for Webship Workspace: the `sandboxes/` folder (type sites), its settings file, its 30 commands and its docs, activated as a plugin.",
   "main": "dist/src/index.js",
   "types": "dist/src/index.d.ts",
   "license": "ISC",
@@ -47,10 +47,7 @@
         "commands/cmd-tools-cancel-users.sh",
         "commands/cmd-tools-checks.sh",
         "commands/cmd-tools-clone.sh",
-        "commands/cmd-tools-graphify.sh",
         "commands/cmd-tools-hostnames.sh",
-        "commands/cmd-tools-obsidian.sh",
-        "commands/cmd-tools-ragify.sh",
         "commands/cmd-tools-reclaim.sh",
         "commands/cmd-tools-remove.sh",
         "commands/cmd-tools-screen.sh",
@@ -76,7 +73,7 @@
   },
   "devDependencies": {
     "@types/node": "^24.0.0",
-    "@webship.co/workspace-plugin-api": "^1.0.0-alpha1",
+    "@webship.co/workspace-plugin-api": "^1.0.0-beta1",
     "typescript": "^5.9.0"
   },
   "publishConfig": {

package/commands/cmd-tools-graphify.sh

@@ -1,27 +0,0 @@
-#!/usr/bin/env bash
-
-# Map a project in this workspace into a queryable knowledge graph with
-# graphify (https://github.com/Graphify-Labs/graphify), or ask an existing
-# graph a question.
-
-# Bootstrap.
-# Find the workspace tooling from this script, so a fresh clone needs no setup.
-WORKSPACE_SCRIPTS="${WORKSPACE_SCRIPTS:-$(cd "$(dirname "${BASH_SOURCE[0]}")/../core/scripts" && pwd)}";
-source ${WORKSPACE_SCRIPTS}/bootstrap.sh || exit 1 ;
-
-# Load workspace settings and extra lists.
-eval $(parse_yaml ${WORKSPACE_CONFIG}/workspace.sandboxes.settings.yml);
-
-ARGPARSE_DESCRIPTION="Build or query the knowledge graph of a project in the sandboxes workspace"
-source ${WORKSPACE_SCRIPTS}/args/arg-graphify.sh || exit 1 ;
-
-shift $#;
-
-if [ ! "${STORE}" == '_none_' ] ; then
-  ensure_graphify || exit 1 ;
-  graphify_store_url "${WORKSPACE_ROOT}/${doc_name}/${PROJECT_NAME}" "${STORE}" ;
-elif [ -n "${QUERY}" ] ; then
-  graphify_query_project ;
-else
-  graphify_project ;
-fi

package/commands/cmd-tools-obsidian.sh

@@ -1,31 +0,0 @@
-#!/usr/bin/env bash
-
-# Turn a project's knowledge graph into an Obsidian vault — one note per entity,
-# a [[wikilink]] per relation, and a JSON Canvas of the map. Written next to the
-# graph in graphs/sandboxes/<project>/obsidian/.
-#
-# Build the graph first with cmd-tools-graphify.sh: this reads what that wrote
-# rather than parsing the project a second time.
-
-# Bootstrap.
-# Find the workspace tooling from this script, so a fresh clone needs no setup.
-WORKSPACE_SCRIPTS="${WORKSPACE_SCRIPTS:-$(cd "$(dirname "${BASH_SOURCE[0]}")/../core/scripts" && pwd)}";
-source ${WORKSPACE_SCRIPTS}/bootstrap.sh || exit 1 ;
-
-# Load workspace settings and extra lists.
-eval $(parse_yaml ${WORKSPACE_CONFIG}/workspace.sandboxes.settings.yml);
-
-ARGPARSE_DESCRIPTION="Build an Obsidian vault from the knowledge graph of a project in the sandboxes workspace"
-source ${WORKSPACE_SCRIPTS}/args/arg-obsidian.sh || exit 1 ;
-
-shift $#;
-
-export MAX_CANVAS_NODES="${MAX_CANVAS_NODES}";
-
-if [ "${REMOVE}" == 'yes' ] ; then
-  obsidian_remove ;
-elif [ "${STATUS}" == 'yes' ] ; then
-  obsidian_status ;
-else
-  obsidian_project ;
-fi

package/commands/cmd-tools-ragify.sh

@@ -1,28 +0,0 @@
-#!/usr/bin/env bash
-
-# Index a project in this workspace into the Milvus vector database
-# (https://github.com/milvus-io/milvus) held in ~/workspace/rag, or ask an
-# existing index a question.
-#
-# The RAG counterpart of cmd-tools-graphify.sh: graphify parses the CODE into a
-# graph and reads no Markdown, Twig, *.module hooks or Drupal wiring YAML — this
-# indexes the text of exactly those and retrieves passages from them.
-
-# Bootstrap.
-# Find the workspace tooling from this script, so a fresh clone needs no setup.
-WORKSPACE_SCRIPTS="${WORKSPACE_SCRIPTS:-$(cd "$(dirname "${BASH_SOURCE[0]}")/../core/scripts" && pwd)}";
-source ${WORKSPACE_SCRIPTS}/bootstrap.sh || exit 1 ;
-
-# Load workspace settings and extra lists.
-eval $(parse_yaml ${WORKSPACE_CONFIG}/workspace.sandboxes.settings.yml);
-
-ARGPARSE_DESCRIPTION="Build or query the Milvus RAG index of a project in the sandboxes workspace"
-source ${WORKSPACE_SCRIPTS}/args/arg-ragify.sh || exit 1 ;
-
-shift $#;
-
-if [ -n "${QUERY}" ] ; then
-  ragify_query_project ;
-else
-  ragify_project ;
-fi