borgmcp-shared 0.12.0 → 0.12.3

package/src/conformance/adapter.ts

@@ -209,6 +209,11 @@ export interface ConformanceAdmin {
     readonly isMandatory?: boolean;
   }): Promise<ConformanceRole>;
   referenceRoleFromTaxonomy(cube: ConformanceCube, role: ConformanceRole): Promise<void>;
+  configureMessageClassRouting(
+    cube: ConformanceCube,
+    className: string,
+    recipientDroneIds: readonly string[],
+  ): Promise<void>;
   createDrone(
     principal: ConformancePrincipal,
     cube: ConformanceCube,
@@ -1457,6 +1462,8 @@ export async function runAdapterConformance(
     });
     const firstRecipient = await environment.admin.createDrone(principal, cube, role);
     const secondRecipient = await environment.admin.createDrone(principal, cube, role);
+    await environment.admin.configureMessageClassRouting(cube, 'conformance-review', [firstRecipient.id]);
+    await environment.admin.configureMessageClassRouting(cube, 'conformance-security', [firstRecipient.id]);
     const postId = '00000000-0000-4000-8000-000000000313';
     const initialPayload = {
       post_id: postId,
@@ -1475,12 +1482,32 @@ export async function runAdapterConformance(
     const firstResult = decodeAppendLogResultEnvelope(first.body).payload;
     invariant(!firstResult.deduplicated, 'Initial append was reported as deduplicated.');
     for (const [index, vector] of APPEND_LOG_IDEMPOTENCY_CONFORMANCE.entries()) {
-      const payload = {
+      const classRouting = vector.mutation === 'resolved_class_routing';
+      const vectorPostId = classRouting
+        ? '00000000-0000-4000-8000-000000000314'
+        : postId;
+      if (classRouting) {
+        const baseline = await environment.operations.append(
+          credential,
+          cube,
+          createProtocolEnvelope('append-idempotency-class-baseline', {
+            post_id: vectorPostId,
+            message: 'once',
+            class: 'conformance-review',
+          }),
+        );
+        expectStatus(baseline, 201, 'Resolved class-routing baseline');
+      }
+      const payload = classRouting ? {
+        post_id: vectorPostId,
+        message: 'once',
+        class: 'conformance-security',
+      } : {
         ...initialPayload,
         ...(vector.mutation === 'message' ? { message: 'changed' } : {}),
         ...(vector.mutation === 'visibility' ? { visibility: 'broadcast' as const } : {}),
         ...(vector.mutation === 'recipient_set' ? { recipientDroneIds: [secondRecipient.id] } : {}),
-        ...(vector.mutation === 'resolved_class_routing' ? { class: 'security', to: ['Security Auditor'] } : {}),
+        ...(vector.mutation === 'ignored_request_shape' ? { class: 'security', to: ['Security Auditor'] } : {}),
       };
       const response = await environment.operations.append(
         vector.actor === 'same' ? credential : otherCredential,
@@ -1508,10 +1535,10 @@ export async function runAdapterConformance(
     );
     expectStatus(read, 200, 'Idempotent append read');
     invariant(
-      decodeReadLogResultEnvelope(read.body).payload.entries.length === 2,
+      decodeReadLogResultEnvelope(read.body).payload.entries.length === 3,
       'Append collision controls persisted the wrong number of entries.',
     );
-    return { persisted_entries: 2, stable_entry: true, deduplicated: true, conflicts: 4, cross_author_created: true };
+    return { persisted_entries: 3, stable_entry: true, deduplicated: true, conflicts: 4, cross_author_created: true };
   });
 
   const entries: Array<{ id: string; created_at: string; message: string }> = [];

package/src/conformance/index.ts

@@ -108,7 +108,7 @@ export interface AppendLogRequestConformanceVector {
 export interface AppendLogIdempotencyConformanceVector {
   name: string;
   actor: 'same' | 'different';
-  mutation: 'none' | 'message' | 'visibility' | 'recipient_set' | 'resolved_class_routing';
+  mutation: 'none' | 'message' | 'visibility' | 'recipient_set' | 'ignored_request_shape' | 'resolved_class_routing';
   expected: 'deduplicated' | 'POST_ID_CONFLICT' | 'created';
 }
 
@@ -118,6 +118,7 @@ export const APPEND_LOG_IDEMPOTENCY_CONFORMANCE: readonly AppendLogIdempotencyCo
   { name: 'rejects a same-author message collision', actor: 'same', mutation: 'message', expected: 'POST_ID_CONFLICT' },
   { name: 'rejects a same-author visibility collision', actor: 'same', mutation: 'visibility', expected: 'POST_ID_CONFLICT' },
   { name: 'rejects a same-author recipient-set collision', actor: 'same', mutation: 'recipient_set', expected: 'POST_ID_CONFLICT' },
+  { name: 'deduplicates ignored class selectors with identical resolved delivery', actor: 'same', mutation: 'ignored_request_shape', expected: 'deduplicated' },
   { name: 'rejects a same-author resolved class-routing collision', actor: 'same', mutation: 'resolved_class_routing', expected: 'POST_ID_CONFLICT' },
   { name: 'creates an independent cross-author post', actor: 'different', mutation: 'none', expected: 'created' },
 ];

package/src/protocol/contract.ts

@@ -13,7 +13,7 @@ import type {
 } from './types.js';
 
 export const SHARED_PACKAGE_NAME = 'borgmcp-shared' as const;
-export const SHARED_PACKAGE_VERSION = '0.12.0' as const;
+export const SHARED_PACKAGE_VERSION = '0.12.3' as const;
 /** Maximum UTF-8 payload for each newly recorded decision text field. */
 export const DECISION_TEXT_MAX_BYTES = 512 as const;
 /** Maximum UTF-8 size of role detailed-description text and any returned section slice. */

package/src/templates.ts

@@ -103,7 +103,8 @@ Integration and release:
 - Review approval does not itself authorize merge, deployment, publication, tagging, or release.
 - Perform those actions only when the user request or a standing delegation explicitly includes them.
 - Use the repository's protected workflow and bind every gate to the exact revision being integrated.
-- Never substitute, move, overwrite, or rerun an immutable release artifact without explicit recovery authority.`;
+- A release tag starts the tag-restricted staging workflow automatically; npm stage approval is the sole human publication boundary.
+- Before npm accepts a stage, correct a failed workflow and retry the same immutable tag. Never move, replace, or force-update the tag.`;
 
 export const GIT_OPERATIONAL_DISCIPLINE_BUILDER = `
 
@@ -200,7 +201,7 @@ const SOFTWARE_DEV_DIRECTIVE = `## Scope and coordination
 - When an outcome includes a separately published external surface, the Coordinator names one owning role or seat for its implementation. Other seats report findings or perform routed review; they do not mutate that surface.
 - Waiting is valid when no authorized action is available.
 - Merge, deploy, publish, tag, release, credential, and live-operator actions require explicit authority.
-- Keep cube-log signals concise. Put durable reasoning in the relevant issue, change, or existing maintained documentation only when it has an operational consumer.${SAME_REPOSITORY_WORKFLOW_DISCIPLINE}`;
+- Keep cube-log signals concise. Put durable reasoning in the relevant issue, change, or existing maintained documentation only when it has an operational consumer.${SAME_REPOSITORY_WORKFLOW_DISCIPLINE}${RELEASE_CYCLE_SHAPES}`;
 
 const SOFTWARE_DEV_TAXONOMY: MessageTaxonomy = [
   {
@@ -308,6 +309,8 @@ Review:
 - Classify findings as in-scope blocker, touched-surface safety blocker, or out-of-scope finding.
 - Drop an observation when it changes no decision; do not create work merely to preserve it.
 - Reviewers provide evidence; they do not redefine the work unit. Route one due gate at a time, proportionate to the changed surface. Never pre-route a later gate.
+- Require one proof per property. Mechanical, version, lock, and generated changes require exact-revision CI plus one Code Review only.
+- Give a successor revision delta review. Carry unchanged green evidence without rerunning it.
 - Bind every verdict to the exact revision. Before claiming gate completion, reread the source log and verify every required verdict.
 - After two blocked rounds, stop and ask the human for the smallest next choice.
 
@@ -340,10 +343,11 @@ Implementation discipline:
 - Mark a deliberate corner-cut with a comment naming the known ceiling and the upgrade path.
 
 While working:
-- Post STARTING with the branch and first concrete action, then substantive PROGRESS during active work.
+- Post STARTING with the branch and first concrete action. Omit PROGRESS for work expected to finish within 10 minutes; otherwise post only substantive PROGRESS during active work.
 - Do not add cleanup, broad refactors, speculative hardening, documentation programs, or follow-up issues unless assigned.
 - A discovered issue outside the slice is a finding, not permission to fix it.
-- Add proportionate tests for behavior you change. Run the repository checks required by the touched surface.
+- Add proportionate tests for behavior you change. Run focused verification required by the touched surface, and do not rerun green CI checks merely to duplicate exact-revision evidence.
+- Check documentation or a separately published site only when the changed behavior, public API, package metadata, or named user claim belongs to that surface.
 
 Handoff:
 - Verify the final diff contains only the authorized slice.