@follenfang/wowdata 0.0.6 → 0.0.8

package/dist/SHA256SUMS

@@ -1,5 +1,5 @@
-9f128ef734763ff9e70240ea224fc7e7ab76364341a9b2a589a004824118eb51  dist/wowdata-darwin-amd64
-e195c0461a854d9e2f29476c3924d33978ef1c7248af14d841fdef7892ada6b0  dist/wowdata-darwin-arm64
-494a58ac1f04b7464c019dad2e2e28f977b6f02e26ca4068c18f00c2decefcbd  dist/wowdata-linux-amd64
-34002378fc1eaaa3e306ea2ed07a1983669914a3143dfa91dc4921d2ee8d6b55  dist/wowdata-linux-arm64
-2a1039729991bb92324d7d610f3625ba3239a5d3a3978779705c96a93026656e  dist/wowdata-windows-amd64.exe
+79ea350a8115f35944fcd2cc9f05f433c43fecc778d0e024c3ef02861e3af356  dist/wowdata-darwin-amd64
+6b54c81e8bedce67bc381331d9d73f121ece7a3111214740d8c89a1b5778f1fa  dist/wowdata-darwin-arm64
+d2ad6f118efd32642f6269417a6eb181e3f4e58cead16a2761c091664fab9c2b  dist/wowdata-linux-amd64
+9325a5353ae88a49453d67dab816c335a66fde38d46f585b0f458631bf943f45  dist/wowdata-linux-arm64
+17d96b435171e9922937fd18f64d421a40d366b04af78eaf024bf84dbb27bfe9  dist/wowdata-windows-amd64.exe

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@follenfang/wowdata",
-  "version": "0.0.6",
+  "version": "0.0.8",
   "description": "Auditable CLI for querying World of Warcraft CASC and DB2 data",
   "license": "AGPL-3.0-or-later",
   "type": "commonjs",

package/skill/wowdata/SKILL.md

@@ -18,10 +18,11 @@ Use the `wowdata` executable from `PATH`. This Skill is CLI-only: do not search
 Resolve the target before reading CASC or DB2 data.
 
 1. If the user gives a Profile, pass only `--profile <name>`; do not combine it with target flags.
-2. Resolve product from the user's words or conversation context. Read [clients.yaml](references/clients.yaml) for aliases. Product has no default; if it remains ambiguous, ask one short product question before running a data command. Treat “硬核服” as a server rule and resolve its actual product from context.
-3. Preserve every explicit source, path, region, product, Build, and locale. Read [locales.yaml](references/locales.yaml) for locale aliases.
-4. If no source or local path is stated, use remote CDN. For an otherwise unspecified remote target, pass `--source remote --region cn --build latest --locale zhCN` plus the resolved product.
-5. For `--source local`, require `--path <client>` and complete the remaining target fields explicitly; never guess missing local-client facts.
+2. Resolve product from the user's words or conversation context. Read [clients.yaml](references/clients.yaml) for the friendly names and the CDN product each one means. The CLI accepts CDN product IDs only and does not resolve those names, so translate the user's wording yourself before calling `--product`. Product has no default; if it remains ambiguous, ask one short product question before running a data command. Treat “硬核服” as a server rule and resolve its actual product from context.
+3. A product ID names a reusable slot, not a fixed game: `wow_classic_beta` held the MoP Classic beta (5.5.x) and holds WoW Forever (1.60.x) now, and a region may not list it at all. Never infer content from the product ID alone — read the label and version from `casc products --source remote --region <region>`, confirm they match what the user asked for, and state the product and version you used. Pin the Build when the result must stay reproducible.
+4. Preserve every explicit source, path, region, product, Build, and locale. Read [locales.yaml](references/locales.yaml) for locale aliases.
+5. If no source or local path is stated, use remote CDN. For an otherwise unspecified remote target, pass `--source remote --region cn --build latest --locale zhCN` plus the resolved product.
+6. For `--source local`, require `--path <client>` and complete the remaining target fields explicitly; never guess missing local-client facts.
 
 Never rely on CLI target defaults; the CLI intentionally has none. `--build latest` resolves at execution time and must not be hard-coded in this Skill.
 

package/skill/wowdata/VERSION

@@ -1 +1 @@
-0.0.6
+0.0.8

package/skill/wowdata/references/clients.yaml

@@ -1,4 +1,15 @@
 schema: wowdata.clients.v1
+# Friendly names a user may say, and the CDN product to pass to --product.
+#
+# The CLI accepts CDN product IDs only: it does not resolve these names, and a name
+# passed to --product fails as an unknown product. Translate the user's wording to the
+# product on the right yourself, pass that value, and state which product and version
+# you actually used.
+#
+# A product ID names a reusable slot, not a fixed game. wow_classic_beta carried the
+# Mists of Pandaria Classic beta (5.5.x) and carries WoW Forever (1.60.x) now, so never
+# infer content from the ID alone: read the label and version from
+# `casc products --source remote --region <region>` and confirm before reporting.
 clients:
   retail: wow
   ptr: wowt
@@ -11,9 +22,10 @@ clients:
   classic-ptr: wow_classic_ptr
   "怀旧服 PTR": wow_classic_ptr
   怀旧服测试服: wow_classic_ptr
-  classic-beta: wow_classic_beta
+  # WoW Forever runs on the classic beta slot as of 1.60.x.
   forever: wow_classic_beta
   classic-plus: wow_classic_beta
+  classic-beta: wow_classic_beta
   classic-era: wow_classic_era
   怀中怀: wow_classic_era
   "60级": wow_classic_era
@@ -24,6 +36,14 @@ clients:
   泰坦服: wow_classic_titan
   泰坦重铸: wow_classic_titan
   时光服: wow_classic_titan
+regionalNotes:
+  # Not naming rules, but they explain failures that otherwise look like bad data.
+  wow_classic_titan:
+    regions: [cn]
+    instruction: Listed for cn only. WoWDBDefs has no structure for its Build either, so a DB2 read fails with "no DBD structure for table <table>"; report that as missing definitions, not as missing data.
+  wow_classic_beta:
+    regions: [us]
+    instruction: Not listed for cn. Use --region us, or report that the region does not carry the slot.
 contextualAliases:
   硬核服:
     type: realm-rule

package/skill/wowdata/references/commands.md

@@ -16,6 +16,10 @@ or a complete target:
 
 Use `--source local --path <client>` plus explicit region, product, Build, and locale for a local client.
 
+`--product` takes the CDN product ID (for example `wow_classic_beta`). The CLI does not resolve friendly names, so translate the user's wording with [clients.yaml](clients.yaml) first. Because a product ID names a slot rather than a fixed game, confirm what the slot currently carries from `casc products` before reporting data.
+
+A remote target is only valid for the region that lists it. Confirm with `casc products --source remote --region <region>` before concluding that data is missing.
+
 ## Discovery And Preparation
 
 | Intent | Command |