Skip to content

CLI contract 1.0: no linger line when loginctl can't answer; reference headers name 1.0 - #998

Merged
edspencer merged 1 commit into
mainfrom
g3-contract-1.0
Nov 5, 2026
Merged

edspencer merged 1 commit into
mainfrom
g3-contract-1.0

Conversation

@edspencer

Copy link
Copy Markdown
Owner

From G3, the CLI-contract rollout's final sweep. It goes with cli-contract#9 (SPEC 1.0).

  • Linger (SPEC 1.0 §7): when loginctl can't answer, paddock service install used to print "If you log out (this check could not reach loginctl), a user service…" and the sudo line. It now prints nothing, as Hallway, Local Review and BragDoc already did and as the reference's lingerAdvice now does. The line still prints when linger is off. doctor still reports the unknown case as skipped, and status already warned only when it's off.
    • lingerNote is exported and unit-tested for off, unknown, on, and macOS.
    • "still prints everything install always printed" relied on the unknown case printing enable-linger, so its fake loginctl now says Linger=no. A new test checks that install says nothing about linger when loginctl doesn't answer.
  • Reference headers: every copied reference/ file now says @ 1.0. Each was diffed against cli-contract's current reference/ first.
  • Changeset: a patch on @paddock/server.

Checks: typecheck is clean, and vitest run test/unit/cli- passes (414 tests). This box has no systemd, so the real-systemd job in CI is the live check.

🤖 Generated with Claude Code

…e headers name 1.0

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@cloudflare-workers-and-pages

Copy link
Copy Markdown

Deploying paddock with  Cloudflare Pages  Cloudflare Pages

Latest commit: 5572b5c
Status: ✅  Deploy successful!
Preview URL: https://c0a3993e.paddock-7u2.pages.dev
Branch Preview URL: https://g3-contract-1-0.paddock-7u2.pages.dev

View logs

@edspencer
edspencer merged commit 6ac6e6c into main Nov 5, 2026
10 checks passed
@edspencer
edspencer deleted the g3-contract-1.0 branch November 5, 2026 10:03
@github-actions github-actions Bot mentioned this pull request Nov 5, 2026
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