Skip to content

fix(installation): identify protected uninstall failure checkpoints - #884

Merged
antropos17 merged 1 commit into
masterfrom
codex/protected-uninstall-diagnostic-20261011
Oct 11, 2026
Merged

antropos17 merged 1 commit into
masterfrom
codex/protected-uninstall-diagnostic-20261011

Conversation

@antropos17

Copy link
Copy Markdown
Owner

Hosted qualification run 38127180297 confirmed native attempt process closure, then exact-owned uninstall reported only protected-operation-refused. The receipt could not identify which cleanup boundary failed.

Add finite uninstall checkpoints for validation, stop, service unregister, stage removal and ancillary/account cleanup, plus administrator and absence confirmation. Preserve original exception/native diagnostics, immediately stop on failure and project only allowlisted checkpoint/message identifiers. Partial control or receipt refusals now retain their finite existing codes.

Validation: protected-installation.test.js 21/21 passed; final checkpoint test passed after narrowing the message allowlist; Prettier and git diff --check passed. Synthetic callbacks only, with no personal-host account/service/ACL writes. This diagnostic change does not establish cleanup of the historical run or fix partial-control cleanup behavior.

@antropos17
antropos17 merged commit 3203124 into master Oct 11, 2026
5 checks passed
@antropos17
antropos17 deleted the codex/protected-uninstall-diagnostic-20261011 branch October 11, 2026 09:23
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