bluejay/bluejay-infra
1
0
Fork 0
Code Issues Pull Requests 14 Actions Packages Projects Releases Wiki Activity

Sprint 40 Cx-5: mirror printer alert routing #18

Open
bluejay wants to merge 1 commits from sprint40/cx-5-alert-classification-offline-vs-depleted into main
pull from: sprint40/cx-5-alert-classification-offline-vs-depleted
merge into: bluejay:main
Conversation 0 Commits 1 Files Changed 2 +205 -11
bluejay commented 2026-05-19 20:18:27 +00:00
Owner
Copy Link

Agent Report

  • Lane: Cx-5
  • Scope: bluejay-infra monitoring mirror for Print.Web offline/depleted/jam/head-error/cover-open routing.
  • Files created: []
  • Files modified: D:\git\FlowerCore\bluejay-infra.sprint40-cx-5\apps\monitoring\noc-monitoring.yaml; D:\git\FlowerCore\bluejay-infra.sprint40-cx-5\tests\bluejay-infra-lint\FleetManifestLintTests.cs
  • Tests before: 1,255 | Tests after: 1,270 | Delta: +15 (from Print.Web companion PR)
  • Validation: dotnet.exe test tests\bluejay-infra-lint\BluejayInfraLint.Tests.csproj -c Release --no-build --filter FullyQualifiedName~Monitoring_MustIncludeRequiredAlertRoutingGuards; full FleetManifestLintTests currently has unrelated pre-existing failures in updater ingress and GitHub runner container assumptions.
  • Build status: Focused routing guard passes; full infra lint class has unrelated existing failures.
  • Decisions made (defaults): offline/jam/cover are IRC-only; paper depleted requires print_printer_state == 3 and print_printer_online == 1; head-error critical keeps thermal digest eligibility under existing critical policy.
  • Notes/blockers: Live Grafana/Prometheus/thermal routing was not mutated per guard. Merge/apply should wait for coordinated deploy and unrelated infra lint cleanup.
## Agent Report - **Lane:** Cx-5 - **Scope:** bluejay-infra monitoring mirror for Print.Web offline/depleted/jam/head-error/cover-open routing. - **Files created:** [] - **Files modified:** D:\git\FlowerCore\bluejay-infra.sprint40-cx-5\apps\monitoring\noc-monitoring.yaml; D:\git\FlowerCore\bluejay-infra.sprint40-cx-5\tests\bluejay-infra-lint\FleetManifestLintTests.cs - **Tests before:** 1,255 | **Tests after:** 1,270 | **Delta:** +15 (from Print.Web companion PR) - **Validation:** `dotnet.exe test tests\bluejay-infra-lint\BluejayInfraLint.Tests.csproj -c Release --no-build --filter FullyQualifiedName~Monitoring_MustIncludeRequiredAlertRoutingGuards`; full `FleetManifestLintTests` currently has unrelated pre-existing failures in updater ingress and GitHub runner container assumptions. - **Build status:** Focused routing guard passes; full infra lint class has unrelated existing failures. - **Decisions made (defaults):** offline/jam/cover are IRC-only; paper depleted requires `print_printer_state == 3` and `print_printer_online == 1`; head-error critical keeps thermal digest eligibility under existing critical policy. - **Notes/blockers:** Live Grafana/Prometheus/thermal routing was not mutated per guard. Merge/apply should wait for coordinated deploy and unrelated infra lint cleanup.
bluejay added 1 commit 2026-05-19 20:18:28 +00:00
Mirror printer state alert routing 40b5027ee3
This pull request has changes conflicting with the target branch.
  • tests/bluejay-infra-lint/FleetManifestLintTests.cs
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin sprint40/cx-5-alert-classification-offline-vs-depleted:sprint40/cx-5-alert-classification-offline-vs-depleted
git checkout sprint40/cx-5-alert-classification-offline-vs-depleted
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
bluejay
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: bluejay/bluejay-infra#18
Delete Branch "sprint40/cx-5-alert-classification-offline-vs-depleted"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?