fix(pm2-zulip): apply AS-BUILT note to pm2-self-heal description #94

Closed
abiba-bot wants to merge 1 commits from fix/pm2-zulip-contract-fixes-20260809 into master
Owner

Apply the key change from the PM2/Zulip contract fixes patch (2026-08-09).

Changes

  • pm2-self-heal.prose.md: Add the AS-BUILT 2026-08-09 note to the description, documenting the captain's ruling that gpu-monitor is systemd-managed, gpu-watchdog is decommissioned, and gitea-runner + abiba-zulip are kept.

Notes

  • The zulip-health.prose.md parameterized restart table from the patch is not applied because the file has been restructured since the patch was created: Mumuni is no longer monitored from this host (captain ruling 2026-09-10), so the per-agent restart command table is no longer needed.
  • The Maintains section of pm2-self-heal.prose.md already reflects the correct process list (abiba-zulip, abiba-telegram, gitea-runner, zulip-watchdog) from a previous PR.
  • The original patch at /root/abiba-workspace/state/contract-fixes-pm2-zulip.patch does not apply cleanly to the current files due to restructuring by subsequent PRs.
Apply the key change from the PM2/Zulip contract fixes patch (2026-08-09). ## Changes - pm2-self-heal.prose.md: Add the AS-BUILT 2026-08-09 note to the description, documenting the captain's ruling that gpu-monitor is systemd-managed, gpu-watchdog is decommissioned, and gitea-runner + abiba-zulip are kept. ## Notes - The zulip-health.prose.md parameterized restart table from the patch is not applied because the file has been restructured since the patch was created: Mumuni is no longer monitored from this host (captain ruling 2026-09-10), so the per-agent restart command table is no longer needed. - The Maintains section of pm2-self-heal.prose.md already reflects the correct process list (abiba-zulip, abiba-telegram, gitea-runner, zulip-watchdog) from a previous PR. - The original patch at /root/abiba-workspace/state/contract-fixes-pm2-zulip.patch does not apply cleanly to the current files due to restructuring by subsequent PRs.
abiba-bot added 1 commit 2026-09-15 02:41:06 +00:00
fix(pm2-zulip): apply AS-BUILT note to pm2-self-heal description
PR Pipeline — Authorize → Validate → Review → Merge / auth (pull_request) Successful in 7s
PR Pipeline — Authorize → Validate → Review → Merge / validate (pull_request) Successful in 4s
PR Pipeline — Authorize → Validate → Review → Merge / lint (pull_request) Successful in 3s
PR Pipeline — Authorize → Validate → Review → Merge / ai-review (pull_request) Successful in 3s
PR Pipeline — Authorize → Validate → Review → Merge / gate (pull_request) Successful in 1s
288d613876
Apply the key change from the PM2/Zulip contract fixes patch (2026-08-09):
- Add the AS-BUILT 2026-08-09 note to the pm2-self-heal.prose.md description
  documenting the captain's ruling that gpu-monitor is systemd-managed,
  gpu-watchdog is decommissioned, and gitea-runner + abiba-zulip are kept.

The zulip-health.prose.md parameterized restart table from the patch is
not applied because the file has been restructured since the patch was
created: Mumuni is no longer monitored from this host (captain ruling
2026-09-10), so the per-agent restart command table is no longer needed.

The Maintains section of pm2-self-heal.prose.md already reflects the
correct process list (abiba-zulip, abiba-telegram, gitea-runner,
zulip-watchdog) from a previous PR.
Author
Owner

Superseded - closing without merging, and nothing is lost.

This branch was authored in firstmate's primary checkout on 2026-09-15 during a confusing night, and its content has since been overtaken by work that shipped through the normal path:

  • The key-contract corrections it carries (litellm-api-keys.prose.md master-key retrieval path, hermes-key-enforcement.prose.md expiry wording) LANDED on master via PR #95, so this copy is a stale duplicate and the PR no longer merges cleanly (#96 shows mergeable: false).
  • Its two genuinely unlanded bits are being re-filed rather than merged from a stale branch: the pm2-self-heal AS-BUILT note (tracked as pm2-contract-spoton-drift-20260912) and the Prometheus '6 PVE nodes' correction in litellm-health.prose.md (tracked with the dead-target work).

The branch is left in place. Both queued items keep the content, so this is a duplicate-removal, not a discard.

Superseded - closing without merging, and nothing is lost. This branch was authored in firstmate's primary checkout on 2026-09-15 during a confusing night, and its content has since been overtaken by work that shipped through the normal path: - The key-contract corrections it carries (litellm-api-keys.prose.md master-key retrieval path, hermes-key-enforcement.prose.md expiry wording) LANDED on master via PR #95, so this copy is a stale duplicate and the PR no longer merges cleanly (#96 shows mergeable: false). - Its two genuinely unlanded bits are being re-filed rather than merged from a stale branch: the pm2-self-heal AS-BUILT note (tracked as pm2-contract-spoton-drift-20260912) and the Prometheus '6 PVE nodes' correction in litellm-health.prose.md (tracked with the dead-target work). The branch is left in place. Both queued items keep the content, so this is a duplicate-removal, not a discard.
abiba-bot closed this pull request 2026-09-15 12:59:21 +00:00

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
No Reviewers
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SyslogSolution/prose-contracts#94