-
Notifications
You must be signed in to change notification settings - Fork 91
Define safe uninstall and retained-model cleanup for Wally #101
Copy link
Copy link
Open
Labels
P2Follow-up priority: important improvement or deferred scope.Follow-up priority: important improvement or deferred scope.enhancementNew feature or requestNew feature or requestpost-mvpDeferred performance, portability, or out-of-scope work; not a Monday release gate.Deferred performance, portability, or out-of-scope work; not a Monday release gate.status:all-clearFixed and verifiedFixed and verified
Description
Activity
Metadata
Metadata
Assignees
Labels
P2Follow-up priority: important improvement or deferred scope.Follow-up priority: important improvement or deferred scope.enhancementNew feature or requestNew feature or requestpost-mvpDeferred performance, portability, or out-of-scope work; not a Monday release gate.Deferred performance, portability, or out-of-scope work; not a Monday release gate.status:all-clearFixed and verifiedFixed and verified
Overview
Model remove/lifecycle commands exist but no first-class uninstall command/script; sources explicitly asked to manage stale packages and recognize previous downloads.
Priority: P2 / post-mvp. Impact: roadmap improvement. Initial planning estimate: Medium; refine after inventory. This issue does not add a release blocker.
Current evidence
Model remove/lifecycle commands exist but no first-class uninstall command/script; sources explicitly asked to manage stale packages and recognize previous downloads.
Design and implementation plan
Separate binary removal, credential revocation/local deletion and optional shared-model cleanup; preserve user data by default and show exact scope.
Acceptance criteria
Related work and deduplication
No existing issue has this acceptance scope; existing release defects remain separate.
No exact existing issue found in the all-state inventory.
Requirement provenance
Reconciled September 13, 2026 against
WALLY_CLOUD_PRODUCT_SOURCES.md(SHA-256e601b7b154b750965fa8d25d4533d3542621bd00b3bb30038c1fae553a549e7b) and the consolidated requirements report. Historical proposals are not evidence of current delivery, customer agreement or approved pricing.Source records and physical line references
Records: C01-042.
Lines: 948–961.