docs(computers): document Force Reboot - #36
Merged
Merged
Conversation
Put self-service recovery guidance alongside computer monitoring and daemon updates. Explain both entry points, confirmation and reconnection states, eligibility, and the difference between persisted files and in-memory work. Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
Contributor
|
Droid finished @factory-qingchen's task —— View job LGTM — no high-confidence, actionable issues were found in this documentation-only change. 0 inline comments posted |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
What: Users need to know where to find Force Reboot and what work it can interrupt.
How: Add a section to the Droid Computers overview, beside monitoring and daemon updates. Cover the session and Settings menus, confirmation, recovery progress, supported computers, and the warning that processes stop while persisted files remain.
Related Issue
Closes SBX-1062
Documentation follow-up for SBX-944. Behavior checked against Factory-AI/factory-mono#21140 and the supplied recording.
Reviewer Guide
Skim: One file, 17 added lines in
docs/cli/features/droid-computers.mdx. Check the steps, eligibility, and data-loss warning. No navigation changes; Japanese translation uses the existing sync workflow.Risk & Impact
Documentation only. No runtime changes or computer reboot. The warning distinguishes persisted files from in-memory work and unflushed writes.
Verification
Content verified @
88e08cdc: Menu labels, confirmation wording, and success message match the recording and merged implementation.Standard validators:
mintlify validate --disable-openapi --telemetry falseandgit diff --checkpassed.Not tested: No live reboot, because this PR changes documentation only.