sensorium-mcp 3.0.59 → 3.0.61

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "sensorium-mcp",
-  "version": "3.0.59",
+  "version": "3.0.61",
   "description": "MCP server for remote control of AI assistants via Telegram",
   "main": "dist/index.js",
   "bin": {

package/templates/azure-devops-securevault.default.md

@@ -10,30 +10,37 @@ replaces_orchestrator: false
 
 # Azure DevOps via SecureVault
 
-Wrap all `az` CLI calls with `securevault run --profile azure-devops -- <command>`. PAT is injected from OS keychain as `AZURE_DEVOPS_EXT_PAT`. Agent never sees credentials.
+Wrap all `az` CLI calls with `securevault run --profile Azure_DevOps <command>`. PAT is injected from OS keychain as `AZURE_DEVOPS_EXT_PAT`. Agent never sees credentials.
+
+- Profile name is **`Azure_DevOps`** (case-sensitive — not `azure-devops`).
+- On Windows do **not** add the `--` separator between `securevault run --profile Azure_DevOps` and the command — it breaks under cmd. Just append the command directly.
+
+## Org and project
+The org and project the vault PATs are scoped to are persisted in `~/.azure/azuredevops/config` (set once via `az devops configure --defaults`). A 401 on every call almost always means the wrong org is configured — verify with `az devops configure --list` before assuming the token is expired.
 
 ## Before first use
 ```bash
 securevault health   # start backend if fails: securevault &
+securevault run --profile Azure_DevOps az devops configure --list   # confirm org/project defaults
 ```
 
 ## Examples
 ```bash
 # Create PR
-securevault run --profile azure-devops -- az repos pr create --repository <repo> --source-branch <branch> --target-branch main --title "title" --org <org> --project <project>
+securevault run --profile Azure_DevOps az repos pr create --repository <repo> --source-branch <branch> --target-branch main --title "title" --org <org> --project <project>
 
 # PR threads
-securevault run --profile azure-devops -- az devops invoke --area git --resource pullRequestThreads --route-parameters project=<p> repositoryId=<r> pullRequestId=<id> --org <org>
+securevault run --profile Azure_DevOps az devops invoke --area git --resource pullRequestThreads --route-parameters project=<p> repositoryId=<r> pullRequestId=<id> --org <org>
 
 # Clone
-securevault run --profile azure-devops -- git clone https://<org>@dev.azure.com/<org>/<project>/_git/<repo>
+securevault run --profile Azure_DevOps git clone https://<org>@dev.azure.com/<org>/<project>/_git/<repo>
 
 # Push
-securevault run --profile azure-devops -- git push origin <branch>
+securevault run --profile Azure_DevOps git push origin <branch>
 ```
 
 ## Rules
-- ALWAYS use `securevault run --profile azure-devops --` for authenticated ops
+- ALWAYS use `securevault run --profile Azure_DevOps` for authenticated ops
 - NEVER use `az` directly, NEVER ask for PAT values
 - `#<number>` in Azure DevOps PR comments/descriptions auto-links to a **work item**, not a PR. To reference a PR, use the full URL: `[PR 12345](https://dev.azure.com/ORG/PROJECT/_git/REPO/pullrequest/12345)`
 

package/templates/delegate-and-wait.default.md

@@ -65,6 +65,7 @@ Results arrive as a message in `wait_for_instructions`. Review, approve, or requ
 
 ### Rules
 
+- **PREFER** breaking down your main task into atomic, small steps. A worker should never recieve a huge task to work on.
 - **NEVER** duplicate work after delegating. If you sent it to a worker, wait for the response.
 - **ALWAYS** include the orchestrator thread ID in the task message so the worker can report back.
 - **ALWAYS** include clear acceptance criteria in the task message.