Skip to content

Package-facts sync report

Generated by sync.py from the cv-crm active package line. Do not hand-edit the JSON files — re-run the sync instead (see sync.md).

Sources (the released line on main, per ADR-0009)

Package Version Ref Layout
ClientVerse Core 1.1.10 6077cbd29749aa14506c36a9cab49b294862b318 packages/unlocked-core/force-app/main/default (monorepo)
ClientVerse Modules 0.8.0 v0.8.0-1-modules packages/modules/force-app (monorepo)

Both packages are pinned to their release tags, not to a branch. main equals the documented release only until the next release merges — on 2026-09-14 it moved to 1.1.8 while these docs describe 1.1.7, which would have produced 1.1.8 structure under a 1.1.7 label. A tag cannot drift, and assert_ref_version in sync.py fails the run if a pin and its version label ever disagree. Versions mirror each package's versionName in sfdx-project.json (1.1.10 / 0.8.0); the corresponding package versions are ClientVerse Core Unlocked@1.1.10-2 and ClientVerse Modules@0.8.0-1.

On the Core package name. Per ADR-0010 the product called ClientVerse Core is the ClientVerse Core Unlocked package in the Dev Hub, and it is the only Core line anyone can install. main also declares packages/core (managed, schema only) and packages/core-plus, but neither is developed against yet and neither ships to a customer — so neither is counted here.

Why not develop. ADR-0008 sourced facts from develop; ADR-0009 supersedes that. Customer-facing guides sourced from develop describe features that exist in no installable package. main is "always releasable" and still carries in-flight corrections, so it keeps ADR-0008's benefit without the overstatement.

Core 1.1.10 — inventory

new objects 166 (+13 extended) · fields 2711 · permission sets 74 · permission-set groups 9 · apps 6 · tabs 69 · apex classes 881 · triggers 111 · LWC 99 · flexipages 139 · flows 33 · record types 35

Modules 0.8.0 — inventory

new objects 31 (+4 extended) · fields 384 · permission sets 20 · apps 1 · tabs 13 · apex classes 310 · LWC 32

By module: dispatch 12 obj (shipped), whitespace 5 obj (shipped), general 0 obj (shipped), ai 13 obj (shipped), analytics 1 obj (shipped)

Annotation coverage (the gap the catalog fills)

objects w/ description fields w/ description fields w/ inline help
Core 1.1.10 166/166 (100%) 1162/2711 (43%) 134/2711 (5%)
Modules 0.8.0 31/31 (100%) 139/384 (36%) 17/384 (4%)

Low coverage is expected and is exactly why the docs-side annotation catalog (objects/*.yaml) exists. Un-annotated objects/fields are tracked in annotation-backlog.md for backfill into the Salesforce metadata.

Flags

  • Modules→Core dependency: Modules 0.8.0 declares ClientVerse Core Unlocked@1.1.10-2 (04tfj000000aKJZAA2), so Core 1.1.10 is the floor. An org on an older Core must upgrade Core before installing Modules 0.8.0.
  • Package versions documented: ClientVerse Core Unlocked@1.1.10-2 and ClientVerse Modules@0.8.0-1.
  • dispatch module — shipped: user-reachable in the released package. 12 object(s) (Dispatch_Action__c, Dispatch_Config__mdt, Dispatch_DataTable_Column__c, Dispatch_DataTable_Config__c, Dispatch_Definition__c, Dispatch_Role_Mapping__mdt, Dispatch_Run_Item__c, Dispatch_Run__c, Dispatch_Section__c, Dispatch_Settings__c, Dispatch_Subscription__c, ERM_Privacy_Preference__c), 103 Apex classes, 16 LWC, 10 tabs.
  • whitespace module — shipped: user-reachable in the released package. 5 object(s) (WhiteSpace_Opportunity__c, Whitespace_Score_Weight__mdt, Whitespace_Scoring_Config__mdt, Whitespace_Threshold__mdt, Whitespace_Tier_Score__mdt), 18 Apex classes, 3 LWC, 0 tabs.
  • general module — shipped: user-reachable in the released package. 0 object(s) (no objects), 10 Apex classes, 0 LWC, 0 tabs.
  • ai module — shipped: user-reachable in the released package. 13 object(s) (AI_Adapter_Limit__mdt, AI_Cleansing_Action__mdt, AI_Cleansing_Proposal__c, AI_Cleansing_Setting__mdt, AI_Cleansing_Threshold__mdt, CV_AI_Action_Template__mdt, CV_AI_Session_Item__c, CV_AI_Session__c, CV_Semantic_Field__mdt, Email_Intake_Proposal__c, Email_Intake_Setting__mdt, Email_Intake__c, System_Prompt_Config__mdt), 155 Apex classes, 4 LWC, 3 tabs.
  • analytics module — shipped: user-reachable in the released package. 1 object(s) (CV_BI_Connection__mdt), 6 Apex classes, 6 LWC, 0 tabs.
  • Trigger-framework rollout: Core carries 111 triggers, up from 17 at v1.1.3-4-core — a systematic one-trigger-per-object fflib rollout, not a counting change. Every custom object now routes through the domain layer.

⚠ Releases these docs do not describe

These package versions are not reachable from 6077cbd29749aa14506c36a9cab49b294862b318, the tag these facts are generated from. Versions newer than the pin are expected here, and this list is the drift signal: it is how you find out the product has moved on while the docs have not. Read it as "has a newer release shipped than the one customers are being pointed at?" — and if so, whether this doc set should be re-cut against it.

A tag that is neither the pin nor newer than it is the case worth investigating: a version that reached a customer from a branch that never landed.

Tag Dated
v0.6.0-3-modules 2026-09-09
v1.1.8-7-core 2026-09-11
v1.1.9-1-core 2026-09-21
v0.7.0-1-modules 2026-09-25
v0.8.0-1-modules 2026-09-25
v1.1.10-2-core 2026-09-25
v1.2.0-10-core 2026-10-06
v0.9.0-3-modules 2026-10-07