Mentra Update Live Firmware

Fetch, verify, prepare

Use curl --fail --silent --show-error --location for the feeds and artifacts. Python's default urllib user agent has received 403 from this CDN when curl succeeded; that is not evidence of missing firmware. Save feed snapshots and validation output outside the checkout.

Before pinning the selected artifacts:

1. Correlate the feed source commit/tag with the intended merged upstream BES or MTK revision. Avoid selecting an unrelated PR build from a newer timestamp.
2. Download and hash each changed artifact; require the declared SHA-256 and byte count. For combined updates this is BES, MTK full OTA, and MTK patch.
3. Inspect MTK ZIP META-INF/com/android/metadata and payload_properties.txt: require A/B OTA for Mentra Live, incremental source constraints on the patch, no source constraint on the full OTA, no wipe/downgrade request, matching post-build metadata, and the payload's declared size and FILE_HASH. The Android metadata may use generic MentraLive/mp1k61v164bspP6 values; it does not independently prove the dated firmware version. Use release provenance for that mapping; never invent a version-field assertion.
4. For BES, preserve a direct firmware BIN URL from its feed. Do not substitute the raw factory image for the compressed OTA payload. If comparing against a GitHub release ZIP, compare with its update_ota.bin.

Use the local helper after verifying inputs. It only transforms local JSON; it does not establish release provenance, fetch artifacts, commit, or publish:

python3 <skill-dir>/scripts/prepare_manifest.py \
  --current <worktree>/asg_client/ota_manifests/firmware_live.json \
  --production <evidence>/production-firmware.json \
  --mtk-latest <evidence>/mtk-latest.json \
  --bes-latest <evidence>/bes-latest.json \
  --output <evidence>/candidate-firmware.json

Omit --bes-latest for MTK-only updates. For BES-only updates omit --production and --mtk-latest. Review the candidate, then copy it over the manifest in the isolated worktree. A helper rejection should be investigated; do not weaken its checks simply to produce a diff.

Validate and deliver

• Confirm only the requested fields changed, historical production entries are unchanged, source versions are unique, all upgrade paths reach the target, and the full OTA target agrees with the development bridge.
• Run git diff --check and the repository's .github/scripts/collect-ota-release-inputs.mjs on the candidate manifest. The validate-asg-ota-manifest.sh script validates an assembled manifest with an apps section; do not apply it directly to this firmware-only file.
• Run the relevant existing coordinated OTA/release-family tests. They read .github/release-family.json, its package manifests, and the current family changelog; include those files if using a sparse checkout.
• Re-fetch the latest feeds before publishing. If a selected release changed, reselect and verify its artifacts before updating the PR. Avoid empty PRs when the pins already match.
• Commit only asg_client/ota_manifests/firmware_live.json. The PR should state BES/MTK targets, production baseline, patch replacement/addition, preserved historical paths, and validation. Report CI status separately from local checks and do not imply that manifest validation proves device behavior.
• Return the PR URL. Leave it open when user approval was requested; continue merge/release work only within the user's authorization.

Approved example: MentraOS PR #4071. Use it for diff shape, never as authority for current version numbers.

Helper regression checks: python3 -m unittest discover -s <skill-dir>/scripts -p 'test_*.py'.