BEAR-119 Remove neutral bear titles and restore uninstall cleanup - #126
Merged
Merged
Conversation
![openswebot[bot]](https://avatars.githubusercontent.com/in/4340220?s=60&v=4){kind=small}
Owner
Author
|
@Mergifyio queue |
Contributor
Merge Queue Status
This pull request spent 26 seconds in the queue, including 3 seconds running CI. Required conditions to merge
|
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
1 participant
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
🐻remains only as a recognized legacy prefix so ordinary status updates and uninstall can remove titles created by the regression. The five semantic status icons are unchanged. There is no final scan, retry, queue, controller, marker, pacing, migration, general compatibility layer, or title-writer coordination fence.Review boundary
The installed Codex skill is the trusted lifecycle orchestrator;
--commitis its explicit internal phase attestation, not a security boundary against a local user deliberately bypassing the supported flow. Adding process handshakes, tokens, or persisted proof would violate BEAR-119's no-marker/no-resume boundary without protecting against a local caller that can already delete the same files.The uninstall guarantee covers the one fresh prepared snapshot: each prepared row receives an immediate exact reread and at most one acknowledged removal before the skill invokes commit. It does not freeze user-owned Codex titles against later concurrent writes. Cross-task writer coordination is explicitly outside this ticket and would expand the product beyond the requested regression fix.
Verification
go test ./...go test -race ./...go vet ./...python3 scripts/validate-experiments.pygit diff --check, shell checks, and guide/site byte parityv3.0.2release smokeLive Desktop canaries
The first full-catalog canary exposed the real regression footprint: 307 of 362 unarchived rows carried removable ThreadBear prefixes. One fresh serial pass confirmed 307/307 exact removals with zero drift and zero unconfirmed results, initiating task last, followed by artifact teardown.
After review corrections, exact final arm64 candidate SHA-256
5f05b9f872ca101f545feaca8df399d8752342fe0c7f7365e3b25da16ad0f864refused bare confirmed uninstall while remaining healthy. A fresh 362-row preview then found only the two reseeded controls; the final cell removed both exactly in historical-then-initiator order and ran explicit artifact commit. All owned artifacts were absent, and unrelated hooks/config remained byte-identical. No final task scan or post-commit title call ran.The cleanup canaries are recorded as seam evidence only; repaint and restart-persistence claims remain grounded in the existing rendered capability experiments.
Linear: BEAR-119