Wallezy/mgu-setup-skills / skills/mgu-setup
mgu-setup
VerifiedSet up and maintain an owner-authorized BMW MGU over ENET using SSH and Store tools. Use for environment checks, backup preparation, initial root, Store setup, supported distribution migration, map/HUD setup, live read-only log collection and diagnostic bundles, updates, and supported rollback or removal. Supports Chinese and English.
| File | Kind | Size |
|---|---|---|
| LICENSE | other | 34.3 KB |
| NOTICE.md | markdown | 958 B |
| SKILL.md | skill md | 7.7 KB |
| agents/openai.yaml | config | 358 B |
| assets/wechat-code.png | binary | 613.2 KB |
| references/contact.md | markdown | 437 B |
| references/diagnostics.md | markdown | 15.3 KB |
| references/evidence.md | markdown | 14.3 KB |
| references/maintenance-update.md | markdown | 7.9 KB |
| references/network-mirrors.md | markdown | 16.1 KB |
| references/network-sources.json | config | 976 B |
| references/recovery.md | markdown | 23.4 KB |
| references/release-channels.md | markdown | 11.0 KB |
| references/root-tool.json | config | 568 B |
| references/root-tool.md | markdown | 9.8 KB |
| references/session-record.md | markdown | 7.3 KB |
| references/store-distributions.md | markdown | 11.7 KB |
| references/workflow.en.md | markdown | 13.6 KB |
| references/workflow.zh-CN.md | markdown | 12.2 KB |
| scripts/check_environment.py | script | 6.5 KB |
| scripts/collect_diagnostics.py | script | 21.7 KB |
| scripts/diagnose.py | script | 18.8 KB |
| scripts/mirror_resources.py | script | 18.8 KB |
references/release-channels.md
View on GitHub# Internal release workflow / 内部发布与明确请求的测试版流程
Read this reference only for an explicitly requested Beta installation/trial,
maintenance of a previously explicitly selected Beta installation, or maintainer
release work. It is not a user-facing menu. Ordinary installation and updates use
the production release; call it 正式版, not Stable. Do not proactively mention or
recommend Beta, ask users to choose a channel, or offer Beta when production is
unavailable. “Latest” alone is not an explicit Beta request. A maintainer's request
to publish both channels does not authorize installing Beta on a user's vehicle.
Use one Skill and one set of component IDs. `stable` remains the internal
production identifier. Beta requires the user's explicit request; reuse that
request during the session. Preserve a previously explicitly selected Beta
installation during routine maintenance rather than silently switching it.
Root 工具仍按自己的审阅版本选择,不随商店通道切换。下表仅用于操作者核对路径,
不得作为普通用户安装前的二选一问题。
| Channel | Root | Admission |
| --- | --- | --- |
| Stable | `https://mgu.walle.pw/mgu/cn/` | Reviewed upstream, expressly owner-reviewed or vehicle-validated candidate; exact bytes and public acceptance |
| Beta | `https://mgu.walle.pw/mgu/cn/beta/` | Explicit owner trial, exact candidate/plan, successful offline checks and public package/channel acceptance |
These roots identify channels, not proof that a usable release is published.
Read current publication records and verify the selected snapshot. The official
raw-package mirror under `/mgu/mgu-store/` and `/mgu/idrive-apps/` is neither CN channel.
For an existing Beta installation, retain its recorded explicit channel during
routine maintenance; the Stable default does not silently switch that vehicle.
Official `mirror_resources.py` snapshots and CN `cn-manifest.json` snapshots
use different schemas. Validate CN resources with the matched CN tooling.
For maintainer-authorized upstream adaptation, the owner's 2026-11-20 policy
defaults to identical Beta and Stable payloads after source review, dependency
and update-order checks, reproducible builds and exact-commit CI. Feature size
or missing per-app vehicle trials alone does not require a Beta-only stage.
Resolve concrete defects and failed checks; isolate unresolved components and
their dependants while independent passing updates can ship. Record unperformed
vehicle validation explicitly. This does not authorize automatic CN releases
from monitoring tasks or any vehicle operation.
## Owner Beta trial / 车主 Beta 实车试验
1. Establish the requested scope and current vehicle architecture, versions,
access and health using saved records plus fresh observations. Existing
healthy SSH needs no Root reflash. Reuse confirmed power and backup conditions.
2. Freeze one complete Beta snapshot: installer, both catalogs, component
dependencies, versions and hashes. Check its source/installer CI and public
Beta acceptance. Keep original payloads, application settings and source/channel
state recoverable. A BimmerCode coding backup does not replace those bytes.
3. Use the selected installer's documented trial route. The first implementation
supports existing-store ID7 migration: `migrate-cn --channel beta --plan-only`
with the local `--from` snapshot. Planning stages temporary files and compiles
candidates; it is not a strictly read-only inventory.
4. Execution requires `--channel beta`, `--expect-snapshot` and `--expect-plan`
for that exact reviewed snapshot/plan. These are operator interfaces; do not
hand owners shell edits or ask them to set readiness flags. Stable's
`installReady` and successful integration records stay unchanged during a trial.
5. Observe any normal restart, actual active channel, one row per component,
Chinese menus/status/log page, settings and boot stability. Verify domestic
catalogs and downloads. A genuine later component/self-update and recovery
remain separate tests; never fake higher versions to create an update.
The owner's explicit choice of real-vehicle validation can replace the emulator
step. Keep offline checks, vehicle results and formal release approval separate.
Stop the affected write for an incompatible version, missing old payload,
unexpected identity, failed integrity check or incomplete recovery. Do not
relax downgrade/unknown-source/ID8 refusals to make a trial run.
车主可以选择“跳过不可用模拟器,直接实车试验”,这项选择不是实车通过记录。
默认正式安装和明确 Beta 试验使用不同准入条件,不能要求先实车成功才能首次试验,
也不能因允许试验就给普通用户开放正式安装。
The initial map candidate (app 0.6.7, service 0.9.10, renderer 0.5.4) is not a
permanent target. An installed official service 0.9.11/0.9.12 cannot be silently
downgraded into it. Review the target's map-URL patch/deactivate compatibility
and prepare a compatible newer CN candidate when needed.
### Resume a prepared trial / 继续已准备的试验
Use the private trial handoff's exact **migration snapshot** and **online-update
snapshot**, with their recorded publication and CI results. Recheck their local
hashes; download or rebuild only a missing/mismatched item. Do not replace a
reviewed snapshot with a newer catalog midway through the vehicle session.
The migration snapshot's archived manifest and local files remain pinned when
the online-update snapshot replaces the public catalog. Do not compare the
older snapshot's mutable catalog paths against the newer live catalog; validate
the current public catalog against the online-update snapshot instead.
The November 12 owner trial uses deploy 0.8.17 with Store 0.9.38 for migration and
deploy 0.8.18 with Store 0.9.39 for the subsequent real online update. Its initial
snapshot requires the complete Store and map-app recovery packages verified
against the saved vehicle files; recheck their hashes on reconnection. Other
starting states use a reviewed snapshot with deploy 0.8.18 or later, whose
preflight also rejects a runtime-only recovery package for an installed UI.
These version numbers are a
recorded test pair, not permanent minimums or proof of vehicle acceptance.
Deploy 0.8.16's migration is a known failed candidate: its check rejects RHMI
files consumed by MainApp, and its runtime-only recovery omits the UI. Do not
reuse that candidate for a new trial.
Before the update, finish the migration verifier and confirm the actual Store
tile opens. Its recovery package must include both the installed runtime bytes
and the complete matching RHMI resources. A registered tile is insufficient.
Once a subsequent update changes payloads, the migration journal is historical:
use that update's supported component rollback, not a blind old-transaction
rollback or a forced migration verification.
Read the updater's own network/source state or use its supported fetch path.
MGU uplink may deny root UID Internet access while the Store's allowed UID is
online; a root `https.get` failure does not establish that the hotspot is down.
上车前把资源、校验、两个固定快照与恢复材料准备完。上车后只做当前身份与版本检查、
执行切换、确认商店入口、在商店里在线更新、正常重启与结果记录。
网络验收走更新器实际使用的访问路径,不用 root 直连探测反复要求用户改热点。
## Promotion and maintenance / 晋升与维护
Maintainer builds prefer the exact main commit's successful GitHub Actions
artifact. Use the selected repository's `release/online_build.py fetch` to verify
the workflow run, attempt, archive digest, catalog and package hashes; use that
output as the candidate's build input. Reuse unchanged published packages.
If authenticated `gh` is unavailable, a connected GitHub app can download the
selected run's artifact; pass that ZIP with `--archive` for the same verification.
Do not repeat a passed online build locally or start Lima/Docker automatically.
Expired/unavailable artifacts or failed builds remain explicit blockers; rerun
online or obtain authenticated artifact access. A local debugging build requires
an explicit need. Source/installer CI and public acceptance still apply.
App compilation against the vehicle's SDK donor remains on the vehicle.
Use the CN Store's selected release tooling and policy:
[CN-RELEASE-CHANNELS.md at 60585be](https://github.com/Wallezy/mgu-store-cn/blob/60585be972822d0a59dfd9931bd3070f857e2d8a/docs/CN-RELEASE-CHANNELS.md).
Do not reintroduce the old blanket vehicle-test gate:
| Work | Publication and evidence |
| --- | --- |
| Reviewed upstream synchronization and CN compatibility changes | Publish Beta then Stable from the same payloads in one release task; `reviewed-upstream` evidence. Vehicle tests are recorded honestly, not a required gate. |
| Small improvement explicitly authorized for both channels without a car trial | `owner-reviewed` evidence; complete source checks, review and reproducible builds. |
| Separate development feature/trial | Beta only until wider release is requested; preserve it when publishing an unrelated shared change. |
| Claimed vehicle-validated release | Evidence must bind actual installation, migration, update order, restart, settings, download/self-update and rollback results to the exact snapshot. |
All routes bind fixed commits, successful applicable CI, complete dependencies,
immutable versioned payloads, a real review/evidence report and public download
verification. `prepare_cn.py`, `promote_cn.py` and `publish_cn.py` are maintainer
tools; source pushes, public publication and vehicle operations are separate.
Review-only releases must retain `fully_vehicle_validated: false`.
When Beta has a separate trial, compare both channel inventories before building.
Use the supported `owner-reviewed` route for explicitly authorized dual-channel
updates with `channel_variants`: pin each full catalog entry for both channels,
the exact `--stable-base`, and the prepared Stable candidate. Shared components
must match Beta; unchanged Stable-only components use `retained_components`.
Retain a whole repository only when none of its components should change.
Keep the Beta trial in Beta, and publish only the reviewed Stable variant.
Changed Stable baselines require replanning. All source, dependency, reproducibility,
CI and public-download checks still apply; this route does not claim vehicle validation.
Keep three-part numeric versions, with upstream version/CN revision in release
records. Changed published bytes require a new component version, even within
Beta. Promotion preserves payloads; it does not rebuild or force downgrades.
Release notes should be short, user-facing Chinese: what changed and why it
matters, with no invented improvements or internal build details.
For a trial with two snapshots, retain both and record the tested path to the
final snapshot. Pending tests stay pending. Keep private vehicle data out of
public evidence. Daily monitoring and official backup-source synchronization
do not themselves authorize new merges, CN publication or vehicle writes.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |