Design: docs/prds/self-update-transaction.md#artifact-install-804-item-1. scripts/archie-update-install currently clones+compiles on every update (lines 139-160); deploy.yml already publishes the per-platform archive + checksums as a GitHub Release asset (lines 265-316), so this points the installer at the existing asset instead of standing up new CI. Source build stays as an explicit --from-source / ARCHIE_UPDATE_SOURCE_BUILD=1 opt-in, never default.
Acceptance criteria
Default archie-update-install downloads and SHA256-verifies the release asset instead of cloning+compiling. Opt-in flag still performs the old clone+compile path. Checksum-verification logic has a fixture-based test.
Notes
Suggested council lens: lens-deletionist (must not leave clone+compile as silent default cruft).
Close reason
Closed
Imported from beads archie-core-hj1t.1 · GitHub #934 · type task · priority P2 · created 2026-09-19 · closed 2026-10-05
Design: docs/prds/self-update-transaction.md#artifact-install-804-item-1. scripts/archie-update-install currently clones+compiles on every update (lines 139-160); deploy.yml already publishes the per-platform archive + checksums as a GitHub Release asset (lines 265-316), so this points the installer at the existing asset instead of standing up new CI. Source build stays as an explicit --from-source / ARCHIE_UPDATE_SOURCE_BUILD=1 opt-in, never default.
### Acceptance criteria
Default archie-update-install downloads and SHA256-verifies the release asset instead of cloning+compiling. Opt-in flag still performs the old clone+compile path. Checksum-verification logic has a fixture-based test.
### Notes
Suggested council lens: lens-deletionist (must not leave clone+compile as silent default cruft).
### Close reason
Closed
---
_Imported from beads `archie-core-hj1t.1` · GitHub #934 · type task · priority P2 · created 2026-09-19 · closed 2026-10-05_
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Design: docs/prds/self-update-transaction.md#artifact-install-804-item-1. scripts/archie-update-install currently clones+compiles on every update (lines 139-160); deploy.yml already publishes the per-platform archive + checksums as a GitHub Release asset (lines 265-316), so this points the installer at the existing asset instead of standing up new CI. Source build stays as an explicit --from-source / ARCHIE_UPDATE_SOURCE_BUILD=1 opt-in, never default.
Acceptance criteria
Default archie-update-install downloads and SHA256-verifies the release asset instead of cloning+compiling. Opt-in flag still performs the old clone+compile path. Checksum-verification logic has a fixture-based test.
Notes
Suggested council lens: lens-deletionist (must not leave clone+compile as silent default cruft).
Close reason
Closed
Imported from beads
archie-core-hj1t.1· GitHub #934 · type task · priority P2 · created 2026-09-19 · closed 2026-10-05