Skip to content

feat(install): add explicit recovery for modified clients - #25

Merged
vriesd merged 6 commits into
mainfrom
feat/install-recovery
Oct 24, 2026
Merged

vriesd merged 6 commits into
mainfrom
feat/install-recovery

Conversation

@vriesd

@vriesd vriesd commented Oct 24, 2026 •

Copy link
Copy Markdown
Collaborator

Why

A locally modified Tailmux client blocks both update and uninstall. Add an explicit recovery path that preserves the original bytes and requires approval of the current executable digest.

What changed

  • Add local recovery preview, approved replacement, and guarded transaction resume, rollback, and abandoned-lock release.
  • Reuse the existing replacement writer and verify private backups. Candidate configuration never executes the installed wrapper.
  • Prepare v0.3.0 and separate candidate tests from the source pinned by the public installer.

Scope

  • Covers reviewed local setup and recovery of modified clients with valid path-bound receipts.
  • Public installer actions and README distribution pins follow after authenticated release assets exist. They still select v0.2.3.
  • The new release selector remains inactive and requires a fresh source-bound owner decision. Real SSH acceptance remains unverified.

Blast Radius

This changes local lifecycle parsing and replacement authorization. Foreign files, unsafe metadata, changed observations, and unknown locks still refuse replacement. Explicit abandoned-lock release requires the operator to confirm that no writer remains active.

Verification

  • bash scripts/tests/run.sh full passed before the guard and fixture corrections. After them, all 22 recovery tests and lint passed. Five native-Linux cases were skipped on macOS.
  • Independent source reviews and comment review passed. Both follow-up corrections passed independent review. Hosted checks are pending.
  • Twenty alternating preview pairs passed the local overhead budget with unchanged inventories and no forbidden calls. Documentation links and shell snippets passed.

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review 🔄 Running since 2026-10-24T02:09:03.344799Z 811e946 PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@vriesd
vriesd merged commit 877f8ff into main Oct 24, 2026
7 checks passed
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.

2 participants