Skip to content

Restore safe Android and image identities - #395

Merged
rldyourmnd merged 2 commits into
mainfrom
fix/host-oom-and-image-lineage
Sep 4, 2026
Merged

Restore safe Android and image identities#395
rldyourmnd merged 2 commits into
mainfrom
fix/host-oom-and-image-lineage

Conversation

@rldyourmnd

Copy link
Copy Markdown
Contributor

Summary

  • publish the already-applied 8192 MiB release and priority-integration scale-set shape
  • advance all four image aliases after the SQLite manifest change
  • reject future manifest/provisioning changes that retain an immutable image alias

Why

The estate raised the Android lanes to 8192 MiB, but public GARM reconciliation still declared 6144 MiB. Separately, #392 changed image bytes while keeping b25/b19, so the live images correctly fail the new manifest identity check and the estate validator cannot pass.

This PR makes the public source match the intended runtime contract. Host-global OOM safety remains private estate policy: the estate rollout restores 12 GiB worker memory plus a 3 GiB host reserve and charges every worker at its hard memory limit.

Verification

rldyourmnd and others added 2 commits September 4, 2026 04:46
Keep public scale-set contracts aligned with the applied 8192 MiB release and priority-integration limits so reconciliation cannot restore the failed 6144 MiB ceiling.

Co-authored-by: Cursor <cursoragent@cursor.com>
Move every SQLite-capable image to a new immutable alias and make pull-request CI reject future manifest or provisioning changes that retain an existing identity.

Co-authored-by: Cursor <cursoragent@cursor.com>
@rldyourmnd
rldyourmnd merged commit 7dbbed2 into main Sep 4, 2026
10 checks passed
@rldyourmnd
rldyourmnd deleted the fix/host-oom-and-image-lineage branch September 4, 2026 00:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant