chore(ops): version the fleet ops scripts — fleet-status, fleet-alert, papers-digest - #453
Merged
Merged
Conversation
…, papers-digest (#427) Three production launchd scripts lived only on the mini's disk, hand-maintained, outside any repo: a mini disk failure loses them, and scripts that page humans had no review trail. Now versioned in ops/ alongside scripts/: - fleet-status.sh (5 min) — fleet health JSON for the dashboard + server guard - fleet-alert.sh (15 min) — device transitions -> Slack #fleet (noise-gated) - papers-digest/daily.sh (daily ~09:00) — frozen-bundle digest -> Slack #papers - launchd/ — reference copies of the three plists - install.sh — deploy scripts to ~/.amico/ops/ (idempotent, state-safe) - README.md — what runs where, on what cadence, posting where; the frozen-bundle upgrade pattern (copy dist + refresh sha sidecar) ~/.amico/ops/ becomes a deploy target, not the source of truth. Closes #427
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (8)
📝 WalkthroughWalkthroughThe PR adds versioned fleet monitoring and alerting scripts, launchd schedules, an installer, operational documentation, and a daily papers digest runner that executes the frozen bundle. ChangesFleet operations automation
Estimated code review effort: 4 (Complex) | ~45 minutes Sequence Diagram(s)sequenceDiagram
participant launchd
participant fleet-status.sh
participant fleet-alert.sh
participant Slack
launchd->>fleet-status.sh: run every five minutes
fleet-status.sh->>fleet-status.sh: collect and write fleet-status.json
launchd->>fleet-alert.sh: run every fifteen minutes
fleet-alert.sh->>fleet-status.sh: read fleet status
fleet-alert.sh->>Slack: post transition or outage messages
Possibly related PRs
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
aarontrowbridge
marked this pull request as ready for review
August 20, 2026 10:14
This was referenced Aug 20, 2026
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.
Closes #427.
Problem — three production launchd scripts lived only on the mini's disk, hand-maintained, outside any repo. A disk failure loses them; scripts that page humans had no review trail.
What's here — the three scripts verbatim from the mini (
fleet-status.sh5-min,fleet-alert.sh15-min → #fleet,papers-digest/daily.shdaily → #papers), reference copies of their launchd plists,install.sh(idempotent deploy to~/.amico/ops/; touches no state, no plists, no bundle), and a README documenting cadences, posting targets, and the frozen-bundle upgrade pattern (copy dist + refresh sha sidecar).~/.amico/ops/becomes a deploy target; this repo is the source of truth.Summary by CodeRabbit
New Features
Documentation