Files
seanbetts--steam-hardware-w…/status/runs/2026-05-12.md
T

65 lines
3.6 KiB
Markdown

# Run Note: 2026-05-12
## Summary
- Fresh run completed under `/Users/sean/Coding/steam-hardware-watch/runs/2026-05-12`.
- Material update: SteamKit/PICS shows all four watched Steam Machine package IDs moved since `2026-05-11`.
- Manual package-history context makes this more interesting: the Machine packages reportedly changed in an uneven `1 / 3 / 3 / 4` pattern across about three minutes, while the earlier Steam Controller package `1558609` had a `3`-change cluster plus one later follow-up roughly two days before public purchase timing appeared.
- No equivalent Steam Frame package movement was observed.
- Public Valve APIs still show Steam Machine and Steam Frame as `Coming soon` with no public packages, package groups, prices, or exact dates.
- Komodo Controller modified timestamp moved, but the product JSON diff is timestamp-only.
## Source Checks
### Komodo
- API access worked.
- Product modified timestamps: Controller `2026-05-12T09:15:51`, Machine `2026-04-24T14:32:54`, Frame `2026-04-24T14:33:36`.
- Controller JSON diff versus `2026-05-11` only changed `modified` / `modified_gmt`.
- Visual assets: `141` discovered, `141` retrieved, `0` blocked.
### SteamDB
- Automated fetches remained blocked by challenge pages for watched app/package pages.
### SteamTracking / GameTracking
- Known Triton/Ibex controller pairing surfaces remain present.
- No new price, exact availability, or public package readiness signal found in the standard grep pass.
### SteamVR Depots
- SteamVR news metadata was saved.
- SteamDB depot page fetch remained blocked by challenge page; no fresh depot manifest/build comparison collected.
### SteamOS Package Mirror
- Mirror reachable.
- Notable unchanged/default hits include `fremont-hw-support 20260506.1-1` in `holo-3.8` and `holo-main`.
- No direct Steam Frame, Steam Machine, Deckard, Roy, ARM/Snapdragon, or new product-specific top-level repo signal found in the default pass.
### Valve Support / CDN
- Valve `appdetails` / `packagedetails` remain unchanged in public-readiness terms.
- Controller app `4165870` remains public with package `1558609`, package group, and `$99.00`.
- Controller package-history precedent is now useful as a heuristic only: package `1558609` showed clustered changes before Valve publicly exposed purchase timing, but one precedent is not enough to treat Machine package movement as confirmation.
- Frame app `4165890` and Machine app `4165910` remain public app metadata only: `Coming soon`, no packages, no package groups, no price.
- Machine packages `1629446`, `1629447`, `1629458`, `1629460` and Frame packages `1629484`, `1629486` still return `packagedetails success:false`.
### Customs / Regulatory
- ImportInfo automated searches were blocked.
## Effect On Key Questions
- Price: unchanged. Steam Controller remains `$99.00`; Machine and Frame have no public price.
- Release date: unchanged. Steam Controller remains May 4, 2026; Machine and Frame still have only broad `Coming soon` / `2026` timing.
- Same-time launch: unchanged. Same-day full-trio launch is ruled out; Machine package movement is backend metadata activity, not public launch readiness. The lack of Frame package movement increases the Machine-first hypothesis, but it remains unconfirmed.
## Next Checks
- Re-run SteamKit/PICS to see whether Machine package changenumber movement continues.
- Watch specifically for a Controller-like follow-up Machine package change after the initial cluster.
- Watch Valve `appdetails` / `packagedetails` for any Machine package-group, price, purchase, reservation, or timing exposure.
- Continue Steam Frame package monitoring; no Frame package movement was observed in this run.