Semi-automated package updating mechanism via pacman for dependencies which want or need bleeding edge updates from repo/source.

Austin Schaefer 6361e9eb5e Design for scale: many tracked packages, not multi-user ... Corrects the earlier non-goal framing: per-user scale (tracking dozens of packages) is explicitly in scope, distinct from multi-user/adversarial config trust, which stays out. Adds a Scaling section covering review-queue fatigue at volume, per-package check cadence, packages.d/ config layout, audit-as-core, local repo retention, and GitHub rate limits/staggering. Also settles the GitHub push-notification question: no true webhook push for repos we don't own, and a relay-based alternative would need a public inbound receiver this box's WireGuard-only posture deliberately avoids. Settles on outbound-only github-atom/conditional github-api polling instead, added to the config schema as check_method/check_interval. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01A2FEut5tVMNjeVjqhgVZbr		2026-09-11 09:24:13 +02:00
SPEC.md	Design for scale: many tracked packages, not multi-user	2026-09-11 09:24:13 +02:00