Updates: widening detection, approval, auto policy, rollback #248
Notifications
Due Date
No due date set.
Reference: sam/archie#248
Reference in new issue
Block a user
Widening updates always wait as pending. See docs/prds/store.md.
Close reason
2874b4ae: widening detection (Covers), pending, approve, rollback, RPCs, endpoints, Extensions page. Update policy control and auto trigger moved to archie-core-em7s.13.
Imported from beads
archie-core-em7s.5· GitHub #1191 · type task · priority P1 · created 2026-09-25 · closed 2026-10-10sam wrote (originally 2026-10-10):
Not built: the plan exceeds the 300-line limit (est. 500-600 hand-written lines plus generated pb/sqlc). Plan: migration 0043 adds pending_reference/pending_digest and previous_reference/previous_digest/previous_accepted_authority to installed_packages. Service.UpdatePackage(org,name): resolve the catalogue digest, fetch+validate, widening = !(accepted or empty).Covers(new.Authority); widening => SetPending, else apply (withdraw old projections, project new, swap pin, saving previous). ApprovePackageUpdate (admin 'approve' action; applies pending and records accepted authority = new declared). RollbackPackage re-fetches previous digest, swaps projections, restores previous accepted authority. SetPackageUpdatePolicy(manual|auto). Auto trigger: UpdatePackage run for auto packages whenever the dashboard lists the catalogue (no scheduler exists). New State RPCs: UpdatePackage, ApprovePackageUpdate, RollbackPackage, SetPackageUpdatePolicy (+ Installations/Manager/staterpc client+server). Dashboard: /api/extensions/{name}/update|approve-update|rollback|policy, pending diff (added grants only) and policy select in the Extensions page, rebuild ui/dist. One table test for the widening decision, one for the SQL pending/apply guard.