gamealgo-cli 0.4.1 → 0.4.2

package/README.md

@@ -47,7 +47,7 @@ gamealgo report advanced run --query-id battle_analysis --from 2026-09-04 --to 2
 gamealgo report advanced list
 ```
 
-The current CLI reads legacy v1 Packs during migration, but all Report Pack write commands require `schemaVersion: 2`. Advanced query runs are explicit, are never preloaded, and remain available as immutable reports for 30 days.
+All Report Packs use `schemaVersion: 2`, with custom `groups[].views` or platform-owned `groups[].standard`. Advanced query runs are explicit, are never preloaded, and remain available as immutable reports for 30 days.
 
 Help and documentation are fetched from the configured Server on every invocation. The CLI intentionally does not keep a documentation cache.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "gamealgo-cli",
-  "version": "0.4.1",
+  "version": "0.4.2",
   "description": "GameAlgo command-line client for AI agents and game developers",
   "repository": {
     "type": "git",

package/skills/gamealgo/SKILL.md

@@ -49,9 +49,9 @@ When changing an existing Report Pack, run `gamealgo report pull --out <working-
 
 Validate with the compact default output, then use `report preview` to inspect v2 validation and generated Dataset SQL without running a warehouse query. After publishing, verify only the affected tab, group, or View with `report result`; do not query unrelated tabs. A report result request must explicitly select a tab, group, or chart/View. A globally unique bare id is accepted; if the Server returns an ambiguity error, use its candidate ids and the local Pack structure to retry without asking the developer to choose an internal id. Before applying event metadata or publishing the Pack, show the exact changes and impact unless the developer already authorized them. After publishing, pull the effective Pack again and verify the expected manifest and materialized result state.
 
-### Use Report Pack v2 For New Work
+### Use Report Pack v2
 
-New, validated, previewed, or published Report Packs must declare `schemaVersion: 2`. Unversioned v1 Packs may still be pulled and queried during migration, but they are read-only; do not edit them in place, pass them to a write command, or add v2 branches to their Report/Chart model. v2 uses independent `datasets`, inline `groups[].views`, `tabs`, and optional `advancedQueries`; it has no top-level `reports` or `charts`, no `groups[].standard`, and no author-managed Pack version.
+Every Report Pack must declare `schemaVersion: 2`. v2 uses independent `datasets`, inline `groups[].views`, platform-owned `groups[].standard`, `tabs`, and optional `experimentViews` and `advancedQueries`. It has no top-level `reports` or `charts` and no author-managed Pack version. Generate, explain, validate, preview, and publish only this structure; do not expose migration-era formats to the developer.
 
 An ordinary v2 Dataset must read only `adn.dwd_gamealgo_events_enriched_di`, include `dt` in its output grain, and be independently computable for each natural day. Before selector filtering, each `datasetFingerprint × platform × dt` must remain at or below 100 rows and 128 KiB. Estimate the output cardinality from every `groupBy` dimension before publishing. If it may exceed either limit, reduce or bucket dimensions, split the business question, or move it into `advancedQueries`; a table View, front-end selector, or `dataset.limit` does not bypass the ordinary limit.