Repository navigation
Clarify the post-install fresh-session step - #71
Merged
Merged
Conversation
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
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.
Review on ArchCode
Problem and author intent
The public machine installer updates global harness instructions, but coding-agent sessions that were already open keep the instructions they started with. Without an explicit fresh-session step, a pilot engineer can complete installation successfully and still conclude that Room participation is not working.
This documentation-only change adds that step immediately after the canonical install sequence and names the harnesses the installer detects.
What changed
room-post doctor.Scope
Documentation-only developer-tooling change.
Risk assessment
Low. No runtime behavior changes.
User impact
Pilot engineers get the missing final activation step and avoid diagnosing a successful install as broken.
Testing
npm pack --dry-runsucceeds and includes the updated README in the same 28-file package.git diff --checkpasses.The runtime journey remains covered by
tests/installer_battery.sh, Case 0, which installs and invokes the real machine command. This PR documents the process-lifecycle boundary that a local installer cannot restart on the user's behalf.Follow-ups and known issues
None.