@moreih29/nexus-core 0.1.2 → 0.2.0

package/skills/nx-setup/body.md

@@ -1,10 +1,10 @@
 ## Role
 
-Interactive project setup wizard — configure Nexus for a new project with minimal token cost. Every step is a concrete choice via `AskUserQuestion`, with no open-ended exploration.
+Interactive project setup wizard — configure Nexus for a new project with minimal token cost. Every step is a concrete choice via `prompt_user`, with no open-ended exploration.
 
 ## Constraints
 
-- NEVER accept free-text input — every step must use `AskUserQuestion` with explicit options.
+- NEVER accept free-text input — every step must use `prompt_user` with explicit options.
 - NEVER skip the "Skip" option — all steps are optional.
 - NEVER modify files outside the selected scope without explicit user confirmation.
 - NEVER overwrite an existing `statusLine` field in settings.json without explicit user confirmation.
@@ -21,7 +21,7 @@ Interactive project setup wizard — configure Nexus for a new project with mini
 ### Step 1: Scope Selection
 
 ```
-AskUserQuestion({
+prompt_user({
   questions: [{
     question: "Where should the Nexus configuration be applied?",
     header: "Scope",
@@ -41,7 +41,7 @@ All file write paths for subsequent steps are determined by this selection:
 ### Step 2: Statusline
 
 ```
-AskUserQuestion({
+prompt_user({
   questions: [{
     question: "Enable the Nexus statusline? (model, branch, context usage, rate limits)",
     header: "Statusline",
@@ -97,7 +97,7 @@ Specifically, treat an existing statusline setting as detected if any of the fol
 If detected:
 
 ```
-AskUserQuestion({
+prompt_user({
   questions: [{
     question: "An existing statusline configuration was detected. Replace it with the Nexus statusline?",
     header: "Statusline",
@@ -129,7 +129,7 @@ Notify and skip:
 **Not installed:**
 
 ```
-AskUserQuestion({
+prompt_user({
   questions: [{
     question: "Install the context7 plugin? It enables agents to look up library docs in real time.",
     header: "Plugin",
@@ -158,7 +158,7 @@ Note: Once added to `enabledPlugins`, Claude Code automatically installs the plu
 ### Step 4: Knowledge Init
 
 ```
-AskUserQuestion({
+prompt_user({
   questions: [{
     question: "Auto-generate project core knowledge?",
     header: "Init",
@@ -185,12 +185,12 @@ Output a setup completion message:
 
 ## Key Principles
 
-1. **Every step uses AskUserQuestion** — no free-text input
+1. **Every step uses prompt_user** — no free-text input
 2. **Minimize tokens** — limit each step to concrete choices to prevent unnecessary exploration
 3. **Always provide a Skip option** — nothing is forced
 4. **Extensible structure** — includes recommended plugin step, expandable to additional categories in the future
 
 ## State Management
 
-Setup operates via sequential AskUserQuestion calls with no state file.
+Setup operates via sequential prompt_user calls with no state file.
 Configuration results are written to the scope-appropriate settings file at each step.

package/skills/nx-setup/meta.yml

@@ -1,4 +1,5 @@
 name: nx-setup
 description: Interactive project setup wizard for Nexus configuration.
+summary: "Interactive Nexus configuration wizard"
 manual_only: true
 id: nx-setup

package/skills/nx-sync/meta.yml

@@ -1,6 +1,7 @@
 name: nx-sync
 description: Context knowledge synchronization — scans project state and updates
   .nexus/context/ design documents
+summary: "Context knowledge synchronization"
 triggers:
   - sync
 id: nx-sync

package/vocabulary/capabilities.yml

@@ -1,32 +1,65 @@
-# Capabilities restrict an agent's access to harness-provided tools.
-# NOT constraints on nexus-core's own scripts/ or tooling.
+# Harness-neutral capability definitions.
+# Each entry describes WHAT is denied in semantic terms.
+# Consumers (claude-nexus, opencode-nexus, nexus-code) maintain their own
+# local map from these ids/classes to concrete tool names in their own repo.
+# nexus-core does not and must not know those tool names.
 
 capabilities:
   - id: no_file_edit
-    description: "Agent cannot create or modify files in the user's workspace"
-    harness_mapping:
-      claude_code:
-        - Edit
-        - Write
-        - NotebookEdit
-      opencode:
-        - edit
-        - write
-        - patch
-        - multiedit
+    description: "Agent cannot create, modify, or delete files in the user's workspace."
+    intent: workspace_write_denial
+    blocks_semantic_classes:
+      - file_creation
+      - file_modification
+      - file_deletion
+      - partial_file_edit
+      - structured_document_edit
+    prose_guidance: |
+      Block any tool whose primary effect is to alter content at a workspace
+      file path. This includes: creating new files at arbitrary paths, rewriting
+      whole file contents, applying partial edits (diffs, patches, find-replace,
+      multi-edit batches), deleting or truncating files, and cell-level edits in
+      structured documents such as notebooks.
+      Read-only operations are NOT blocked: reading file contents, querying
+      metadata, listing directories, and running code-intelligence queries that
+      do not mutate files.
 
   - id: no_task_create
-    description: "Agent cannot create new tasks in the Nexus task pipeline"
-    harness_mapping:
-      claude_code:
-        - mcp__plugin_claude-nexus_nx__nx_task_add
-      opencode:
-        - nx_task_add
+    description: "Agent cannot create new tasks in the Nexus task pipeline."
+    intent: task_pipeline_append_denial
+    blocks_semantic_classes:
+      - nexus_task_creation
+    prose_guidance: |
+      Block any tool that appends a new task to the Nexus task pipeline (the
+      mechanism by which Lead-owned work is enqueued for execution). Tools that
+      read, list, or query existing tasks are NOT blocked. Tools that modify
+      existing task state belong to a separate capability (no_task_update) and
+      are not governed here.
 
   - id: no_task_update
-    description: "Agent cannot update the state of existing Nexus tasks"
-    harness_mapping:
-      claude_code:
-        - mcp__plugin_claude-nexus_nx__nx_task_update
-      opencode:
-        - nx_task_update
+    description: "Agent cannot update the state of existing Nexus tasks."
+    intent: task_pipeline_mutate_denial
+    blocks_semantic_classes:
+      - nexus_task_state_transition
+      - nexus_task_metadata_modification
+    prose_guidance: |
+      Block any tool that mutates an existing Nexus task: changing its status,
+      editing its description, reassigning ownership, closing it, or modifying
+      any field on its record. Tools that read, list, or query tasks are NOT
+      blocked. Creation of new tasks is governed by no_task_create, not here.
+
+  - id: no_shell_exec
+    description: "Agent cannot execute arbitrary shell commands or spawn subprocesses."
+    intent: shell_execution_denial
+    blocks_semantic_classes:
+      - shell_command_exec
+      - subprocess_spawn
+      - interactive_shell_session
+    prose_guidance: |
+      Block any tool whose primary effect is to run a command-line invocation,
+      shell script, or spawn a subprocess on the user's machine. This includes
+      general-purpose shell runners, background process managers, shell output
+      readers, and shell-session kill operations. Tools that read files, query
+      metadata, or call specialized non-shell APIs (HTTP, language-server
+      queries, sandboxed code evaluators that do not spawn user-machine
+      processes) are NOT blocked.