Skip to content

docs(operations): mark the dedicated-account migration untested on hardware - #293

Open
CrazyWillBear wants to merge 1 commit into
mainfrom
docs/migration-untested
Open

docs(operations): mark the dedicated-account migration untested on hardware#293
CrazyWillBear wants to merge 1 commit into
mainfrom
docs/migration-untested

Conversation

@CrazyWillBear

Copy link
Copy Markdown
Collaborator

Why

docs/OPERATIONS.md → "Migrating a live box to the dedicated account" reads as a validated procedure. It isn't. It was written from the code, and its one trial run stopped at step 4: Apple declined to issue the second Apple ID, and the dedicated posture rests on one iMessage account per user session, so there was nothing to migrate to.

Nobody following that checklist today can tell it's untrodden. The failure mode it hides isn't cosmetic — the account plan makes real, privileged system changes partway through, which is exactly what #289 and #291 describe.

What

Two edits, docs only.

It also records what is verified on real macOS 26.5.2, so the next person doesn't re-derive it: sysadminctl -addUser … -password - does read the password from piped stdin (#292), and the No clear text password or interactive option was specified line it prints appears on success too. That line reads exactly like a parse-time refusal and cost this session a wrong conclusion before dscl -authonly settled it.

The notice is self-deleting: first person to complete a migration removes it.

Check

uv run pytest 785 passed · uv run ruff check . clean · uv run mypy . clean

🤖 Generated with Claude Code

…rdware

The checklist reads as validated; it is not. It was written from the code and
its one trial run stopped at step 4, because Apple declined to issue the second
Apple ID and the dedicated posture rests on one iMessage account per user
session.

Say so at the top, name the known-open holes (#289, #290, #291), and point at
the reason the interactive path is the risky part: installer-e2e runs
--non-interactive and skips the whole dedicated branch, which is where all three
high findings in the #288 review lived.

Also record what IS verified on real macOS 26.5.2 — sysadminctl reads the piped
password, and the "No clear text password" line it prints is noise, not a
failure — so the next person does not re-derive it, and move the Apple ID
warning onto step 4 where they will actually hit it.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.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.

1 participant