sync: catalog variants expose their bit width; 0.2.2 version macro

`basert pull basecompute/Muse-Glimmer-30B` failed with

  no pre-converted .base for quant "q4" in this repo; it offers: 17gb, dynamic

A bare pull requests "q4", and the catalog row is only served when the
requested bits match. `quant_bits` scans for `q` followed by a digit, so
`kquant-dynamic` yielded None — the `q` there is followed by `u` — and
resolution fell through to matching by filename tag. These files are named
after the upstream GGUFs, whose tags are "dynamic" and "17gb".

Renamed the variants to `default-q4k-dynamic` / `q4k-17gb`, which scan to
"q4". Only the catalog's variant ids change; the published artifacts are
untouched. A test now asserts every catalog quant exposes its bit width.

Also carries BASERT_VERSION_PATCH 2. Still no header or binding mirrors —
those must follow the 0.2.2 engine release, not lead it.

Author: prabod

base-convert/Cargo.lock

@@ -12,7 +12,7 @@ members = [
 ]
 
 [workspace.package]
-version = "0.2.1"
+version = "0.2.2"
 edition = "2021"
 license = "Apache-2.0"
 repository = "https://github.com/basecompute/baseRT"

base-convert/Cargo.toml

@@ -674,7 +674,7 @@
       "file": "muse-glimmer-30B-kquant-dynamic.base",
       "source_repo": "meta-models/Muse-Glimmer-30B-GGUF",
       "arch": "muse_glimmer",
-      "quant": "default-kquant-dynamic",
+      "quant": "default-q4k-dynamic",
       "size": 20952383488,
       "sha256": "1eb639041f638099f6b1f7415c808cd6762b52be672d4ff5ef97829cc7669876"
     },
@@ -684,7 +684,7 @@
       "file": "muse-glimmer-30B-kquant-17gb.base",
       "source_repo": "meta-models/Muse-Glimmer-30B-GGUF",
       "arch": "muse_glimmer",
-      "quant": "kquant-17gb",
+      "quant": "q4k-17gb",
       "size": 18054873088,
       "sha256": "9c323d37c192e45375a936828427f50c7a303d5772465f672df478b1f8cfc1d2"
     }

base-convert/crates/base-hub/catalog.json

@@ -307,6 +307,31 @@ mod tests {
         assert_eq!(e.arch.as_deref(), Some("llama"));
     }
 
+    /// Every catalog `quant` must expose its bit-width to `quant_bits`, because
+    /// `basert pull <id>` with no `--target` asks for "q4" and the Catalog arm
+    /// only serves the cataloged file when the bits match. A variant whose name
+    /// hides them — `kquant-dynamic`, where the `q` is followed by `u` — silently
+    /// falls through to picking a file by filename tag instead, which for a repo
+    /// named after its upstream GGUFs fails outright:
+    ///
+    ///   no pre-converted .base for quant "q4" in this repo; it offers: 17gb, dynamic
+    ///
+    /// Hence `q4k`, not `kquant`.
+    #[test]
+    fn every_catalog_quant_exposes_its_bit_width() {
+        let cat = Catalog::bundled().unwrap();
+        for e in &cat.models {
+            assert!(
+                crate::registry::quant_bits(&e.quant).is_some(),
+                "catalog quant {:?} (id {}) hides its bit width from quant_bits — a bare \
+                 `basert pull {}` cannot match it",
+                e.quant,
+                e.id,
+                e.id
+            );
+        }
+    }
+
     #[test]
     fn find_matches_exact_and_ci() {
         let cat = Catalog::from_json(

base-convert/crates/base-hub/src/catalog.rs

@@ -64,7 +64,7 @@ extern "C" {
 
 #define BASERT_VERSION_MAJOR 0
 #define BASERT_VERSION_MINOR 2
-#define BASERT_VERSION_PATCH 1
+#define BASERT_VERSION_PATCH 2
 
 /// Compile-time version, packed as `(MAJOR<<16) | (MINOR<<8) | PATCH`.
 /// Useful for `#if BASERT_VERSION >= 0x000200` feature checks.