From e7b2dea5526f2a8eb26477179f473597cadd6050 Mon Sep 17 00:00:00 2001 From: seanbetts Date: Sun, 10 May 2026 21:38:18 +0100 Subject: [PATCH] Prioritize SteamDB package monitoring --- SKILL.md | 18 ++++++++++++++++-- references/sources.md | 25 ++++++++++++++++++++++++- 2 files changed, 40 insertions(+), 3 deletions(-) diff --git a/SKILL.md b/SKILL.md index 6b27294..1ccbb3b 100644 --- a/SKILL.md +++ b/SKILL.md @@ -129,6 +129,13 @@ Preferred human-in-the-loop fallback: Check the controller app, packages, depots, and history. Prefer primary records. +Primary reservation-package check: + +- for Machine and Frame launch readiness, start with the SteamDB package pages for the known reservation package IDs +- record `Last Record Update`, `Last Changenumber`, inferred app association, and whether the page still says SteamDB has no information beyond package existence +- compare those fields against the previous run before interpreting any noisier store-page timestamp +- treat SteamDB package-page movement as the earliest update signal; use Valve `packagedetails` and app `appdetails` to determine whether that movement has become public purchase or reservation readiness + Watch for: - new apps or packages @@ -143,11 +150,11 @@ Known IDs and starting points are in [references/sources.md](references/sources. Reservation package monitoring: -- check Machine app `4165910`, Frame app `4165890`, and Controller app `4165870` through `appdetails` -- check reservation-package IDs from SteamTracking/SteamDB: +- check reservation-package IDs from SteamTracking/SteamDB on SteamDB first: - Machine: `1629446`, `1629447`, `1629458`, `1629460` - Frame: `1629484`, `1629486` - Controller baseline: `1558609` +- then check Machine app `4165910`, Frame app `4165890`, and Controller app `4165870` through Valve `appdetails` - treat private packages returning `packagedetails success:false` as meaningful existence evidence but not launch-ready by itself - treat any transition to public `packagedetails`, new `appdetails.packages`, `package_groups`, price, reservation text, purchase eligibility, or exact release timing as high-signal @@ -173,6 +180,12 @@ Look for: - reservation flow allowlists and package IDs - support or OOBE changes +Known reservation-package code baseline: + +- Machine package IDs `1629446`, `1629447`, `1629458`, `1629460` and Frame package IDs `1629484`, `1629486` first appear in SteamTracking bundle snapshots at commit `334bd31a28a0` on `2026-04-28T23:46:34Z` +- the parent `4a2195407fde` does not contain those IDs +- later reservation-code commits such as `cb7ae45d7bb1` are not the first appearance; inspect diffs for behavioral changes rather than treating repeated IDs as new + Only summarize findings that materially affect launch-readiness or architecture inference. ### 4. SteamVR Depots @@ -243,6 +256,7 @@ Strong examples: - new controller-only Komodo section rollout - new SteamDB unboxing or store media +- SteamDB package-page `Last Record Update` / changenumber movement for Machine or Frame reservation packages - published price or release date - private Machine/Frame reservation packages becoming public or gaining price/package-group/reservation metadata - controller-specific support or legal docs diff --git a/references/sources.md b/references/sources.md index 7ce5ac0..60015f4 100644 --- a/references/sources.md +++ b/references/sources.md @@ -41,13 +41,36 @@ Reservation/package IDs seen in SteamTracking reservation-system code and SteamD - `Steam Machine`: `1629446`, `1629447`, `1629458`, `1629460` - `Steam Frame`: `1629484`, `1629486` -For each run, check both SteamDB package pages and Valve Store APIs: +Primary update check: for each package ID, check the SteamDB package page first and record: + +- `Last Record Update` +- `Last Changenumber` +- possible app association or inferred app association +- whether SteamDB still has no package information beyond existence + +SteamDB package pages: + +- `Steam Controller package`: `https://steamdb.info/sub/1558609/` +- `Steam Machine package`: `https://steamdb.info/sub/1629446/` +- `Steam Machine package`: `https://steamdb.info/sub/1629447/` +- `Steam Machine package`: `https://steamdb.info/sub/1629458/` +- `Steam Machine package`: `https://steamdb.info/sub/1629460/` +- `Steam Frame package`: `https://steamdb.info/sub/1629484/` +- `Steam Frame package`: `https://steamdb.info/sub/1629486/` + +Corroborating Valve Store APIs: - `https://store.steampowered.com/api/appdetails?appids=4165910,4165890,4165870&cc=us&l=english` - `https://store.steampowered.com/api/packagedetails?packageids=&cc=us&l=english` Known baseline: the Machine and Frame package IDs may exist on SteamDB while `packagedetails` still returns `success:false`. Treat that as private-package existence, not public launch readiness. +SteamTracking origin baseline: + +- package IDs first appear in SteamTracking bundle snapshots at commit `334bd31a28a0` (`2026-04-28T23:46:34Z`) +- parent commit `4a2195407fde` does not contain the IDs +- later commit `cb7ae45d7bb1` (`2026-05-07T20:10:35Z`) changes reservation behavior but is not first package-ID exposure + ## SteamTracking / GameTracking Primary local paths if already cloned: