Skip to content

feat(playbot-lane): onboard Playbot 0.93.1 compatibility + phase-1 mutation evidence - #8

Merged
jokim1 merged 1 commit into
lila-mainfrom
fm/fm-playbot-lane-093
Aug 19, 2026
Merged

feat(playbot-lane): onboard Playbot 0.93.1 compatibility + phase-1 mutation evidence#8
jokim1 merged 1 commit into
lila-mainfrom
fm/fm-playbot-lane-093

Conversation

@jokim1

@jokim1 jokim1 commented Aug 19, 2026

Copy link
Copy Markdown
Owner

Summary

Playbot auto-updated 0.92.0 -> 0.93.1, which dropped the native lane back to phase1-evidence-required / release_compatibility: fail because the compatibility seed and mutation evidence only covered 0.90.0 and 0.92.0.

This onboards 0.93.1:

  • Adds '0.93.1': releaseCompatibilityShape() to COMPATIBILITY_MANIFEST_SEED.releases. 0.93.1's application/codex DB schemas, IPC channel strings, and preload bridge strings are identical to the shared Phase-0 shape already used by 0.90.0 and 0.92.0, so it reuses that shape rather than introducing a new one.
  • Records the Phase 1 disposable-smoke mutation evidence for 0.93.1 (the signed overlay pointer plus per-operation records for create / openThread / send / stop / archiveThread / delete and the gate-8 confinement write-denial proof).

Verification

Against the live 0.93.1 app (CDP reachable):

  • doctor --json reports operatingState: native-enabled, mutationsEnabled: true, ready: true.
  • ready --json --capability native reports ready: true.
  • The smoke created a disposable non-MAIN workspace/thread on the registered disposable project only, exercised all mutation ops plus the confinement probe (readAllowed: true, writeDenied: true), cleaned up, and verified absence.

Notes

The evidence overlay is written solely by the smoke and binds a signed receipt to the lanes-script digest; it was generated with the seed change in place and is not hand-edited.

@jokim1
jokim1 merged commit 66edbb5 into lila-main Aug 19, 2026
11 of 12 checks passed
jokim1 added a commit that referenced this pull request Aug 25, 2026
jokim1 added a commit that referenced this pull request Aug 25, 2026
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