Skip to content

device/bluejay: document the persistent desktop and review dependencies - #561

Merged
derekross merged 2 commits into
derekross:mainfrom
latentoperator:revision/bluejay-docs-20261109
Nov 11, 2026
Merged

derekross merged 2 commits into
derekross:mainfrom
latentoperator:revision/bluejay-docs-20261109

Conversation

@latentoperator

@latentoperator latentoperator commented Nov 9, 2026 •

Copy link
Copy Markdown
Contributor

Record the Pixel 6a persistent desktop demonstrated on the exact development kernel, its reproduction gaps, the earlier slot-success write, and the remaining review/runtime gates.

The historical combined #543 is closed unmerged in favour of this documentation PR, root policy #562, installer #563 and bring-up #565. The status guide now records Trusty #231 as merged and the remaining work on kernel #225–#230. Development-kernel results stay explicitly labelled, with no claim that the revised kernel stack has run.

The slot-success audit retains the recorded before/after bytes, verified 8 KiB readback and binary-provenance limitation. Further gs101 marking stays on hold; a fresh read-only protected-data backup remains required before another hardware trial.

Validation: policy gate passes against current main; documentation-only follow-up was reviewed. No package, descriptor, executable, phone operation or revised-stack runtime qualification is added.

Local package validation: the full tests/packages run passed every package except omamobile-modem under the assistant shell's PYTHONUNBUFFERED=1. That failure is the known test-only #457: grep -q closes the NV-overlay status pipe early. It reproduces on clean main 3a4f582. The unchanged modem suite passes with PYTHONUNBUFFERED unset, matching CI's normal environment, on both the current-main and documentation baselines. A scratch-only assertion correction also passes the complete modem suite; no modem or fixture change is included here. Fresh published-head CI remains the merge gate.

Published-head validation: the fresh Policy and Tests (tests/all, every package) CI jobs both passed on this PR's current head.

Record the tested development result separately from executable integration.
Document the one devinfo write with its saved eight-byte before/after table,
the earlier backup, and the limits of the tool provenance. No phone operation
or new hardware qualification is claimed.

Co-Authored-By: OpenAI Codex <noreply@openai.com>
@derekross

Copy link
Copy Markdown
Owner

Thanks, Chris. The slot-success audit is exactly the record I was after, and the devinfo bytes before and after settle what happened. The Devices row reads right now too. Please do take the fresh read-only backup before the next hardware step, as your note says. Happy to merge this once it's out of draft.

Record the closed historical PR, published mobile splits and merged Trusty fix. Replace completed kernel revision tasks with the remaining review and runtime gates while preserving the exact tested-kernel scope and slot-success hold.

Co-Authored-By: OpenAI Codex <noreply@openai.com>
@latentoperator
latentoperator marked this pull request as ready for review November 10, 2026 18:31
@derekross

Copy link
Copy Markdown
Owner

Thanks, Chris. The refresh matches what I see: #543 closed, kernel #231 merged, and the table of what's left on #225 to #230 is right as of today. Nothing else changed since I last read it, so this is ready and I'll merge it.

@derekross
derekross merged commit fda8e35 into derekross:main Nov 11, 2026
2 checks passed
robertzas pushed a commit to robertzas/omarchy-mobile that referenced this pull request Nov 14, 2026
…encies (derekross#561)

Records the Pixel 6a's persistent desktop on its development kernel, what can and can't be reproduced from published sources, the one slot-success write with its before and after bytes, and the hold on further marking. Lists the split pull requests (derekross#562, derekross#563, derekross#565) and the kernel pull requests the port still waits on. Documentation only.

Co-Authored-By: OpenAI Codex <noreply@openai.com>
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.

2 participants