Repository navigation
Add reliability signals, notifications and recovery coverage - #150
Merged
Merged
Conversation
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
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.
Operators can monitor control readiness, scrape project-filtered metrics, receive signed best-effort notifications and check external application reachability without adding required services.
Validation: 1,176 local tests passed; typecheck, build, lint and documentation checks passed (three pre-existing lint warnings). Code commit fa1a609 passed the complete CI matrix, including the damaged-repository Docker drill, fake-VPS convergence and all Node versions. Latest commit 9bbf18d only records verified runtime evidence; its CI rerun is pending.
The source-built linux/arm64 agent ran in a disposable Ubuntu 24.04.5 guest, emitted JSON startup logs, remained online using its existing state volume, and passed debug-cause checks against synthetic bearer/basic/cookie/token/URL secrets. The verified logger hash matches the pushed source. Guest/control processes and temporary credentials/build artifacts were cleaned up. Canonical evidence is in docs/real-host-evaluation.md.
CI investigation: the repository-permission fixture was corrected; the subsequent fake-VPS inspect gap was narrowed to discovery convergence and now retries only the exact transient missing-container response within the existing deadline. The intervening commit changed only the backup integration fixture, not product runtime. Restore assertions now include response bodies if the intermittent 400 recurs; all checks passed on the review code.
Limits: notification queues/cursors are in memory and can lose events across outages or shutdown; retain external availability and scheduled backup checks. Real endpoint changes still recreate clients to update hosts entries. Debug sanitization covers common patterns, not arbitrary application-secret recognition. Injected faults do not establish behavior on a physically full production host.