@brainmcp/brainmcp 0.1.15 → 0.1.16

package/README.md

@@ -71,7 +71,7 @@ No API keys or OAuth secrets are written to config files.
 
 ## Guidance included in the next release
 
-Local source version `0.1.15` bundles guidance `2026.09.14`: clear knowledge classes,
+Local source version `0.1.16` bundles guidance `2026.09.19`: clear knowledge classes,
 proactive proposals during authorized work, explicit Rule/account-library write limits, and
 customer-agent processing responsibility. It also retains sector discovery/filtering,
 Neuron `brain_remember` / `brain_amend` selection, advanced `brain_change_propose` operations,

package/dist/agent-config.js

@@ -60,8 +60,9 @@ export const BRAIN_MCP_INITIAL_SCOPES = [
     'workflows:read',
 ];
 /** Bump when always-on guidance text changes in a way clients should refresh. */
-export const GUIDANCE_VERSION = '2026.09.14';
+export const GUIDANCE_VERSION = '2026.09.19';
 export const BRAIN_HANDLE_CATALOG = [
+    { idParameter: 'activityId', kind: 'activity', scope: 'workspace', template: 'brain://workspace/{workspaceId}/activity/{activityId}', resolver: 'the Activity historical-read resource (explicit graph:read and changes:read consent; follow continuation.resourceUri for complete evidence; the reference does not authorize a revert)' },
     { idParameter: 'nodeId', kind: 'node', scope: 'workspace', template: 'brain://workspace/{workspaceId}/ref/live/node/{nodeId}', resolver: 'brain_node_read or the live-node MCP resource' },
     { idParameter: 'commentId', kind: 'comment', scope: 'workspace', template: 'brain://workspace/{workspaceId}/comment/{commentId}', resolver: 'brain_comment_list(commentId) or the comment MCP resource' },
     { idParameter: 'ruleId', kind: 'rule', scope: 'workspace', template: 'brain://workspace/{workspaceId}/rule/{ruleId}', resolver: 'the workspace-rule MCP resource' },
@@ -124,7 +125,7 @@ export const BRAIN_REPORTING_GUIDE_MARKDOWN = [
     'References: use `references` for cited nodes that should deep-link from the report without changing where the report is bound.',
 ].join('\n');
 export const EMPTY_WORKSPACE_RESPONSE_REQUIREMENT = 'Empty-workspace response requirement: when brain_workspace_overview reports no applied Cores or Neurons, do not finish the response until you either bootstrap after explicit user authorization or explicitly tell the user the workspace is empty and offer to bootstrap it with comprehensive, durable project context. A status/overview request does not authorize graph writes. If the resolved policy is auto_apply, warn that an authorized bootstrap will become live immediately. Always report the proposal id/status, and never call the workspace populated until the proposal is applied.';
-export const AUTHORIZED_BOOTSTRAP_DETAIL_REQUIREMENT = 'Authorized bootstrap detail requirement: study the repository comprehensively and maximize supported durable detail within one valid proposal and its operation limits. Model Cores as stable concepts. Parent a focused Neuron under exactly one Core when that broader concept genuinely owns it; allow a legitimate standalone Neuron to remain flat rather than inventing a misleading parent. Use standalone descriptions, detailed content with exact paths/commands/status/caveats/rationale, and useful described cross-Core links. Exclude secrets, personal data, raw transcripts, temporary output, speculation, and large file dumps.';
+export const AUTHORIZED_BOOTSTRAP_DETAIL_REQUIREMENT = 'Authorized bootstrap detail requirement: study the repository comprehensively and maximize supported durable detail within one valid proposal and its operation limits. Model Cores as stable concepts. Parent a focused Neuron under exactly one Core when that broader concept genuinely owns it; allow a legitimate standalone Neuron to remain flat rather than inventing a misleading parent. Use standalone descriptions, detailed content with exact paths/commands/status/caveats/rationale, and useful described cross-Core links. Exclude secrets, personal data, raw transcripts, temporary output, speculation, and large file dumps. If the workspace description is missing and update_workspace_description is advertised, also submit a separate single-operation live proposal describing the workspace purpose and when to use it, using beforeJson.description from overview. Never mix workspace metadata and graph operations. Report both proposal IDs/statuses; an existing description should be preserved unless the user asks to change it.';
 /** Canonical copy-paste prompt used after connection/overview to populate an empty workspace. */
 export function buildBrainBootstrapPrompt(options = {}) {
     const starterCores = options.starterCores ?? [];
@@ -155,7 +156,8 @@ ${coreLines}
 4. Do not store secrets, credentials, personal data, raw transcripts, temporary logs/output, speculative claims, or large file dumps.
 5. When nodes created in this proposal must reference each other, pre-assign UUID targetIds and reuse them in later operations.
 6. Before submitting, check coverage across every major project area, verify that parent relationships reflect real conceptual ownership, and use the proposal budget efficiently. Prefer dense, focused durable knowledge over superficial node count; identify any material coverage gap that could not fit.
-7. Stop after brain_change_propose. Report the proposal ID, returned status, affected scope, any remaining coverage gaps, and whether it was auto-applied or awaits Review. Do not claim the workspace is populated unless the proposal was applied.`;
+7. If the workspace description is absent and update_workspace_description is advertised, submit a separate brain_change_propose with targetRef.type="live", targetType="workspace", targetId=workspaceId, beforeJson.description=null, and afterJson.description explaining the project purpose and when this workspace should be used (up to 1000 characters). This requires workspace:manage and changes:write and follows workspace/connection review policy. Do not mix it into the graph proposal. Preserve an existing description unless the user asks to change it.
+8. Stop after these proposals. Report each proposal ID, returned status, affected scope, any remaining coverage gaps, and whether it was auto-applied or awaits Review. Do not claim the workspace is populated unless the proposal was applied.`;
 }
 export const BRAIN_BOOTSTRAP_PROMPT = buildBrainBootstrapPrompt();
 export const MCP_OAUTH_CLIENT_IDS = {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@brainmcp/brainmcp",
-  "version": "0.1.15",
+  "version": "0.1.16",
   "description": "Safely configure BrainMCP guidance and MCP connections across agent projects",
   "type": "module",
   "bin": {