LocalSetup 4.56.0

LocalSetup 4.56.0

LocalSetup 4.56.0 opens a managed operations pane below your agent and automates sudo authentication while preserving command input and handling uncertain outcomes safely.

Highlights

• Run operations below your agent: managed commands use a lower pane without taking focus. Herdr and tmux share the same ownership and safety checks, and sudo authentication preserves the command input.
• Keep compatibility evidence accurate: standalone compatibility records identify the release that shipped each integration while retaining the original standalone candidate evidence.
• Update security-sensitive dependencies: runtime certificate data uses certifi 2026.10.19, and development image tooling uses Pillow 13.0.0.
• Report sudo readiness safely: the managed workflow distinguishes cached readiness, credential-variable outcomes, and required manual authentication. Results expose variable names and statuses, never credential values; readiness does not authorize a privileged command.
• Find skills and workflows by task: all 20 workflows use the compact ls-wf- prefix. The naming review renamed 84 of 113 skills and retained 29 names. Published selectors remain aliases, recorded refresh migrates renamed selections, and authoring guidance starts with natural activation phrases.
• Catch installed-wheel preset regressions: a focused test builds and installs the wheel in isolation, runs the normal personal preset without a source-root override, checks that bootstrap references are present, and confirms private local-context files stay out of the install.

Compatibility

The ordered targets from the verified live v4.53.3 baseline are 4.53.4 for the compatibility-record correction, 4.53.5 for dependency maintenance, 4.54.0 for managed sudo credentials, 4.55.0 for activation-based package naming, and 4.55.1 for installed-wheel regression coverage. This terminal-pane feature targets 4.56.0 under corrected 4.x arithmetic; previously published tags and artifacts remain unchanged.

By default, pick and run use the caller-owned lower pane. Callers that need the former standalone ops* session behavior must explicitly pass --legacy-session; the legacy session path is retained for compatibility.

Published skill and workflow selectors remain accepted as aliases. Recorded package refresh, CLI package paths and package tokens resolve renamed selections to current locations while preserving custom adapter content.

The default managed-pane route selects <exact-host-alias.upper()>_SUDO_KEY for a bound host, or <repository.upper()>_SUDO_KEY locally, then GENERIC_SUDO_KEY when the first candidate is absent or invalid. Trying a second candidate after a rejected password requires an explicitly qualified single-password conversation; uncertain authentication stops fallback. The legacy route retains hostname-based lookup. Results expose variable names and statuses, never credential values; authentication does not expand command authorization.

Runtime certifi changes to 2026.10.19 and development Pillow changes to 13.0.0. Re-sync the supported environment to receive the pinned versions.

Qualification of detached app-server live panes is unavailable. tmux and PTY fixture results cover adapter behavior only and do not qualify detached app-server panes or every live client integration.

Local installed-wheel and source-distribution checks do not qualify optional live services or establish that every platform has been exercised.

Update

Use the supported LocalSetup install or recorded package-refresh workflow with the updated source. Existing selected package names continue to resolve; refresh installs the current canonical package directories and preserves custom adapter content.

Re-sync the project environment through the supported dependency workflow to install the updated certifi and Pillow pins.

For default managed sudo use, run pick and run from a verified caller context so LocalSetup can bind its owned lower pane. Use --legacy-session only when explicitly retaining the standalone ops* session lifecycle.

Verification

Focused authentication, alias and refresh, package-path, resource provenance, branding, installed-wheel and source-distribution checks passed locally. The wheel case applied the normal personal preset without a source-root override, verified all eight bootstrap reference documents and confirmed private local-context files were excluded.

The terminal changes passed focused authentication, pane lifecycle, workflow, release-preflight and PTY checks after review fixes. Release acceptance still requires successful hosted validation of the exact final candidate.

Caller-pane, shared Herdr/tmux, sudo, unknown-input and PTY fixtures exercise the adapters and operation safeguards. They are fixture evidence only; detached app-server live pane qualification remains unavailable.

Release acceptance requires the exact final signed candidate to pass required hosted validation jobs. Before publication, verify the required-key signed commit and tag, downloaded archive and its .sha256 and .cdx.json sidecars, build provenance and an isolated installation.

Optional live capabilities remain unqualified; release inclusion and local fixture results are not evidence of live-service support.

Download the archive with its .sha256 checksum and .cdx.json SBOM sidecars, then follow the release guide.