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.7 origin/main packages/unlocked-core/force-app/main/default (monorepo)
ClientVerse Modules 0.4.0 origin/main packages/modules/force-app (monorepo)

Both packages track cv-crm main — the branch package versions are cut from, and therefore the only ref that describes what a customer can actually install. Versions mirror each package's versionName in sfdx-project.json (1.1.7 / 0.4.0); the corresponding package versions are ClientVerse Core Unlocked@1.1.7-6 and ClientVerse Modules@0.4.0-2.

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.7 — inventory

new objects 148 (+13 extended) · fields 2457 · permission sets 66 · permission-set groups 8 · apps 6 · tabs 60 · apex classes 708 · triggers 110 · LWC 78 · flexipages 131 · flows 30 · record types 35

Modules 0.4.0 — inventory

new objects 21 (+3 extended) · fields 269 · permission sets 11 · apps 1 · tabs 11 · apex classes 184 · LWC 25

By module: dispatch 11 obj (shipped), whitespace 4 obj (shipped), general 0 obj (shipped), ai 5 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.7 136/148 (92%) 886/2457 (36%) 86/2457 (4%)
Modules 0.4.0 19/21 (90%) 30/269 (11%) 10/269 (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.4.0 declares ClientVerse Core Unlocked@1.1.7-6 (04tfj000000TYCnAAO), so Core 1.1.7 is the floor. An org on an older Core must upgrade Core before installing Modules 0.4.0.
  • Package versions documented: ClientVerse Core Unlocked@1.1.7-6 and ClientVerse Modules@0.4.0-2.
  • dispatch module — shipped: user-reachable in the released package. 11 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), 82 Apex classes, 13 LWC, 10 tabs.
  • whitespace module — shipped: user-reachable in the released package. 4 object(s) (WhiteSpace_Opportunity__c, Whitespace_Score_Weight__mdt, Whitespace_Scoring_Config__mdt, Whitespace_Threshold__mdt), 17 Apex classes, 3 LWC, 0 tabs.
  • general module — shipped: user-reachable in the released package. 0 object(s) (no objects), 7 Apex classes, 0 LWC, 0 tabs.
  • ai module — shipped: user-reachable in the released package. 5 object(s) (AI_Adapter_Limit__mdt, CV_AI_Action_Template__mdt, CV_AI_Session_Item__c, CV_AI_Session__c, System_Prompt_Config__mdt), 72 Apex classes, 3 LWC, 1 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 110 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.

⚠ Package versions not on the documented ref

These tags exist but are not reachable from origin/main, so the facts above do not describe them. Most often that means a release branch is still in flight and its versions were tagged before it merged — expected, and no action beyond knowing. The case that matters is a version that reached a customer from a branch that never landed. Check which before treating this report as a complete picture of what is installable.

Tag Dated
v0.5.0-1-modules 2026-08-27