v1.0.2

Added

versionTracking profiles — consumers can now declare "profile": "component" | "library" | "package-wrapper" in cwm-build.config.json instead of hand-authoring the entire versionTracking block.

• Profile defaults live in templates/profiles/<name>.json and resolve through CWM\BuildTools\Config\ProfileResolver at every read site (cwm-bump, cwm-release, substitute-tokens, and release.sh's gate check).
• The consumer's versionTracking key is still honored as an override layer: maps deep-merge, lists replace wholesale.
• cwm-init detects the right profile from extension.type and pre-fills the prompt.
• cwm-sync-configs prints a migration hint when an inline block exists without a profile, and a "safe to delete" hint when an inline block exactly matches the profile defaults. Never auto-rewrites JSON.

Migration

Existing consumers can keep their inline versionTracking block (no breaking change) or migrate to the profile pattern:

{
  "extension": { "type": "library", "name": "lib_x" },
  "profile":   "library"
  // Optional: add "versionTracking": { ... } to override per-repo bits.
}