Repository navigation
Conversation
…s off Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Merged
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.
Summary
cli-contract SPEC §7 ("Linger", a must): on Linux,
service installmust checkloginctl show-user $USER -p Linger, and only when it's off printsudo loginctl enable-linger <user>and why; never run sudo. Until nowinstallprintedloginctl enable-linger $USER(withoutsudo) to everybody, as part of the systemd lifetime line, without checking.server/service/linger.ts:lingerOf(moved fromdoctor.ts, unchanged),lingerUser, andlingerAdvice(the reference'slingerAdvicewording, but an unreadable answer gives nothing, per the task).service install(Linux, not--dry-run, not--refresh) asks after the service answers. Off: a blank line, why, andsudo loginctl enable-linger <user>. On, orloginctlcan't answer (no logind, a container): nothing.--json: the advice leads the document'swarnings(merged with the status report's), and the prose goes to stderr like the rest.installanddoctorcheck" (G-WORDING item 2), with sample output.Testing
npm test(512 pass),npm run typecheck, docs siteastro build.--dry-run/--refresh;--jsonputs it inwarnings(and not on stdout). Control: with the oldservice/index.tsthe three new positive tests fail.HOME, with a stand-insystemctl(runs the unit'sExecStart) and a stand-inloginctlonPATH:service installwith Linger=no prints the advice, Linger=yes and a failing loginctl print nothing;--jsonstdout is one document whosewarningshold the advice;doctorstill warns withfix: sudo loginctl enable-linger alex; uninstalled and cleaned up afterwards.Checklist
🤖 Generated with Claude Code