feat: Fleet management scripts, retry logic, morning report (#910, #896, #897, #898) #914

Closed
Rockachopa wants to merge 0 commits from timmy/issue-fix-896-897-898-910 into main
Owner

Changes

  • fleet/fleet.sh (#910): Cross-VPS health, status, restart, deploy for Ezra/Allegro/Bezalel
  • nexus/retry_helper.py (#896): Retry decorator with exponential backoff, dead letter queue, cycle state checkpoints
  • nexus/morning_report.py (#897): Automated 0600 report generator — gathers closed issues, merged PRs, stuck workers
  • fleet/allegro/archived-scripts/README.md (#898): Burn script audit and archived patterns

Acceptance Criteria

  • fleet.sh passes syntax check
  • retry_helper.py passes syntax check
  • morning_report.py passes syntax check
  • Archive placeholder created for burn scripts

Fixes #910, #896, #897, #898

## Changes - `fleet/fleet.sh` (#910): Cross-VPS health, status, restart, deploy for Ezra/Allegro/Bezalel - `nexus/retry_helper.py` (#896): Retry decorator with exponential backoff, dead letter queue, cycle state checkpoints - `nexus/morning_report.py` (#897): Automated 0600 report generator — gathers closed issues, merged PRs, stuck workers - `fleet/allegro/archived-scripts/README.md` (#898): Burn script audit and archived patterns ## Acceptance Criteria - [x] fleet.sh passes syntax check - [x] retry_helper.py passes syntax check - [x] morning_report.py passes syntax check - [x] Archive placeholder created for burn scripts Fixes #910, #896, #897, #898
Member

QA Review — @perplexity

Status: EMPTY BRANCH — nothing to merge

Gitea reports: "This branch is already included in the target branch. There is nothing to merge."

The PR description is well-structured (fleet.sh, retry_helper.py, morning_report.py, archived-scripts/README.md) and covers 4 issues (#910, #896, #897, #898), but the branch timmy/issue-fix-896-897-898-910 has 0 commits ahead of main.

Action Needed

  • Push the actual implementation commits to the branch
  • Or close this and reopen when code is ready

CI is stuck in "Waiting to run" because there's nothing to build.

cc @Rockachopa

## QA Review — @perplexity **Status: EMPTY BRANCH — nothing to merge** Gitea reports: "This branch is already included in the target branch. There is nothing to merge." The PR description is well-structured (fleet.sh, retry_helper.py, morning_report.py, archived-scripts/README.md) and covers 4 issues (#910, #896, #897, #898), but the branch `timmy/issue-fix-896-897-898-910` has 0 commits ahead of main. ### Action Needed - Push the actual implementation commits to the branch - Or close this and reopen when code is ready CI is stuck in "Waiting to run" because there's nothing to build. cc @Rockachopa
claude closed this pull request 2026-04-07 06:18:30 +00:00
Member

Closing: head branch (timmy/issue-fix-896-897-898-910) is at the same SHA as main (37b006d). Zero commits ahead, zero files changed. The work from #910/#896/#897/#898 was already merged in the prior commit. Nothing to merge here.

See #916 for full PR hygiene audit.

Closing: head branch (`timmy/issue-fix-896-897-898-910`) is at the same SHA as `main` (37b006d). Zero commits ahead, zero files changed. The work from #910/#896/#897/#898 was already merged in the prior commit. Nothing to merge here. See #916 for full PR hygiene audit.
Some checks failed
CI / validate (pull_request) Waiting to run
Deploy Nexus / deploy (push) Has been cancelled

Pull request closed

Sign in to join this conversation.
No Reviewers
3 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Timmy_Foundation/the-nexus#914