@company-semantics/contracts 51.1.0 → 51.3.0

package/src/index.ts

@@ -329,16 +329,89 @@ export type {
 // contracts drift on it has NO server-side tripwire and mis-places comments
 // silently. Response vocabulary only — request bodies stay backend-side.
 // See src/comments/README.md.
+//
+// The anchor SIZE BOUNDS are published alongside the shape, because the client
+// that composes an anchor and the schema that accepts it are the two halves of
+// that same driftable agreement: a constructor capturing more context than the
+// boundary accepts loses a comment after it was written. Note ANCHOR_CONTEXT_CHARS
+// (capture) and ANCHOR_AFFIX_MAX_CHARS (accept) differ ON PURPOSE.
 // @see ADR-CONTRACTS-116, ADR-CONT-029
 export {
+  ANCHOR_AFFIX_MAX_CHARS,
+  ANCHOR_CONTEXT_CHARS,
   COMMENT_ANCHOR_TYPES,
   COMMENT_SUBJECT_TYPES,
   COMMENT_THREAD_KINDS,
   COMMENT_THREAD_STATUSES,
+  QUOTE_MAX_CHARS,
+  RELATIVE_POSITION_MAX_CHARS,
   SUGGESTION_OPS,
   SUGGESTION_STATUSES,
 } from "./comments/index";
 
+// The anchor's INTERPRETATION, published beside its shape (ADR-CONTRACTS-127).
+// The schema said what an anchor looks like; these say what it MEANS. Both
+// halves have to be published for the same reason: the writing client and the
+// resolving client agree with no server-side arbiter between them, so a second
+// description of "where does this anchor land" mis-places comments with nothing
+// anywhere throwing. `resolveAnchorFromText` is total, pure and text-only — the
+// Yjs relative-position rung stays in consumers, which compose it on top.
+export {
+  contextAfter,
+  contextBefore,
+  contextsMatchAt,
+  findSoleOccurrence,
+  resolveAnchorFromText,
+} from "./comments/index";
+
+export type { AnchorResolution, Occurrence } from "./comments/index";
+
+// The two questions asked BEFORE the body is written (ADR-CONTRACTS-127).
+// `anchorStillReads` is a SECOND assertion, independent of the ladder — the
+// applier must not trust the finder — and `plannedEdit` derives the mutation
+// from the canonical payload rather than a caller's restatement of it. Both are
+// total functions of their arguments, which is exactly what makes them liftable
+// out of a browser applier: no Y.Text, no clock, no lease.
+export { anchorStillReads, plannedEdit } from "./comments/index";
+
+export type { PlannedEdit } from "./comments/index";
+
+// The CONSTRUCTION half of the same contract (ADR-CONTRACTS-127). Publishing
+// anchor → text while leaving text → anchor browser-only would be half an
+// extraction: the side that COMPOSES an anchor decides how much context to
+// capture and what counts as a quote, and a second description of that is the
+// same silent-drift hazard the resolver was published to end. Both constructors
+// validate through `CommentAnchorSchema` before returning and refuse — `null` —
+// rather than truncate, because an anchor the route boundary rejects is a
+// comment lost after it was composed. The relative-position pair is NOT
+// produced here; a consumer holding a `Y.Text` merges it onto the result.
+export {
+  createTextAnchorFromRange,
+  createTextInsertionAnchorAt,
+} from "./comments/index";
+
+export type { TextRange } from "./comments/index";
+
+// The application receipt — the durable proof that an accepted suggestion's
+// edit ALREADY LANDED IN THE BODY (ADR-CONTRACTS-127). It travels in the same
+// CRDT transaction as the edit, so either both survived or neither did, which
+// is what closes the window between the write and the acknowledgement. The MAP
+// KEY is the load-bearing part: a receipt written under any other name lands in
+// a map nobody reads while the reader watches a map nobody writes, and nothing
+// anywhere throws — the same no-arbiter hazard as the anchor, now that a second
+// implementation is about to write receipts too. Published with a PARSER,
+// because these values arrive from a peer through a CRDT that has no schema of
+// its own: a row that is not three well-typed fields is dropped, never
+// surfaced. The receipt lives BESIDE the body and must never reach the markdown
+// source, an export, or the content hash.
+export {
+  SUGGESTION_RECEIPTS_MAP,
+  SuggestionReceiptSchema,
+  readSuggestionReceipt,
+} from "./comments/index";
+
+export type { SuggestionReceipt } from "./comments/index";
+
 export {
   CommentAnchorSchema,
   CommentAnchorTypeSchema,

package/src/message-parts/__tests__/confirmation.test.ts

@@ -121,6 +121,9 @@ describe("CONFIRMATION_LABELS", () => {
       "system.cleanup": "Cleanup Connections",
       "member.changeManager": "Change Reporting Manager",
       "companyMd.ingest": "Ingest Company Knowledge",
+      "companyMd.commentPass": "Apply Comment Pass",
+      "semantic.transform": "Apply Reporting Transformation",
+      "companyMd.importContextDoc": "Import Context Document",
     });
   });
 });

package/src/message-parts/confirmation.ts

@@ -46,6 +46,9 @@ export const CONFIRMATION_LABELS: Record<ExecutionKind, string> = {
   "system.cleanup": "Cleanup Connections",
   "member.changeManager": "Change Reporting Manager",
   "companyMd.ingest": "Ingest Company Knowledge",
+  "companyMd.commentPass": "Apply Comment Pass",
+  "semantic.transform": "Apply Reporting Transformation",
+  "companyMd.importContextDoc": "Import Context Document",
 };
 
 /**