[Proxicon]

Completes durable RatelDesk incident delivery for Monitoring Flows through the shared M2M connection and exact organization/customer mapping. Configuration, validation and preview are read only. Published runs retain their action identity and prepared payload across restart; retries reuse the same key/body and reconcile possible commits through authenticated receipt lookup, preserving one incident per occurrence with current tenant/owner authorization.

Targets NetRatel v0.1.1-beta.1 with the public RatelDesk beta.16, source a428d84b228213a3b1036b896610a19e51e19fa6. Both companion pin files retain its verified immutable API/Web images. Refs #141, #146 and #164.

• Normally integrates CI Main e3897c3d9c8362de23c006aa6cb259c07db7f50e into the existing feature history. Preserves Services, Monitoring, the native Velox Flow editor and stable client/gateway work.
• Adopts CI PR #168 and the owner's 7 October amendment: source checks, one Release build, three fast regression assemblies and a real aggregate. Full pairs, physical/native runtime, rotation/recovery, browsers and deployment/upgrades run only through the selected manual workflow.
• Resolves workflow conflicts using the accepted fast policy. Preserves all 81 static test identities, including all 17 publication-journal tests, authenticated artifact receipts, immutable image/asset guards and recovery journals. Publication completion records distribution integrity separately from pending owner functional acceptance.
• Keeps production connector/protocol authorization, tenant/owner checks, credential handling, incident identity and prepared-payload behavior unchanged during this CI integration. The original expensive test bodies, assertions, waits and timeouts remain intact.
• Updates active documentation and the developer fast-test command. The physical wrapper changes only obsolete cadence comments.

Final reviewed feature head: 979e832fb0b07fafe6ce922f48442bbb64a05e5a, tree d9f2b0d2a31f8ada9c2d523acd5afef0e13b0eec; normal merge parents are original feature head 0cd3ae56980c118a0f45ef5f9daa3c2665981f70 and CI Main. The merged preview passed all 81 existing Python checks and shell/Python/YAML syntax checks. Production source and companion pins were preserved. Natural PR validation passed in 13m41s (821s), with 3156 Core + 35 API + 400 Components passes, zero failed/skipped cases and strict nonzero TRXs. Restore 21s, Release build 136s, fast regressions 602s; queue 0s and summed runner-job duration 829s. Actual tested merge SHA: 7b99fcb221ab71d1438c3b35bf4559f92590545a. Normally merged to Main at 8cb37bcaf5f5a2e290327fb38efb185eabf44391, preserving tree d9f2b0d2a31f8ada9c2d523acd5afef0e13b0eec. Natural final Main validation passed in 13m32s (812s) with 3156 Core + 35 API + 400 Components passes, all adverse/skip counters zero. Restore 29s, Release build 121s, fast regressions 595s; queue 0s and summed runner duration 822s. The annotated v0.1.1-beta.1 tag (4d2ed4e8cafdfc5b8c0a088475b026f4cae5eb89) identifies this exact Main commit. Natural hosted Release build passed all six jobs in 17m40s, with 3,591 tests passing. Natural publication passed all seven jobs in 5m28s through the final job (5m29s to terminal metadata). The same public beta.1 prerelease now contains 13 verified downloads and the digest-pinned Compose bundle for all five public containers. Ten unchanged public build artifacts passed strict provenance verification; derived Compose source/final hashes and all five live OCI identities were checked. Stable/latest remains v0.1.0. The release notes contain the owner deployment and OTEL guide; functional acceptance remains pending owner testing. The focused CI change’s own natural Main run passed in 9m03s, following its 13m04s PR run; issue #167 is completed on verified acceptance.

Preserved functional observations remain unresolved: earlier setup-to-login browser ceremonies failed before M2M; an earlier Clear-button timeout has no established cause despite a later pass; the latest complete physical incident timed out at its original 300-second bound. Earlier fixture URL/identity and rotation-observer source repairs remain preserved, while these historical receipts do not establish final deployed-beta acceptance. Removing mandatory cadence does not mark those failures fixed.

Owner deployment testing with OTEL/log inspection is the functional acceptance path. Epic #141, connector #146, NetRatel #164 and RatelDesk #119 remain open for those results. Optional suites have not run as part of this CI integration. Beta.2 client resilience is outside this release.

Disclosure check: this description contains no credentials, private deployment URLs or customer/employee data.

[Proxicon]

Tracking: RatelDesk #119, building on receiver #116.

RatelDesk PR #120 is merged at 006381c6f78ac1d37965f52ddc28bff002753055. The handoff release is RatelDesk-0.1.1-beta.9: dedicated service credentials, both reciprocal-link consent roles, protected provider integration and the existing idempotent incident receiver.

Final reviewed PR head: 2aef71262467d90b4ba1e498c208d43ff6ca5fe4; independent review and exact-head addendum identify no remaining concrete code blocker in their reviewed scope. All 17 PR checks passed: validation, deployment-managed PostgreSQL. Results: 1,857 .NET passes, 6 existing skips; 164 required actual-provider passes, 0 skips across SQLite/PostgreSQL; 73 browser passes, 0 skips; 8 mailbox passes, 0 skips. Lifecycle peer fixtures are synthetic.

Completed release evidence:

• Merged-main validation: 17/17 checks passed on the exact merged SHA: main validation, managed PostgreSQL. Actual merged-main TRX/log totals independently match the counts above, including exactly six unchanged baseline skips.
• Release workflow: 9/9 jobs passed, including full Release tests, clean SQLite Compose install, executable runtime checks on Linux x64/arm64 and Windows x64, multiarchitecture image publication and anonymous pulls.
• Public prerelease: published, non-draft. Independently verified all ten asset sizes/digests, seven archive identities, SHA256SUMS, manifest and its detached checksum. Manifest SHA256: f7286fad48cd015ddbc024fca0a157ce2c46cbc17039cad59ce4824312b81aac. All three images pull with an empty Docker configuration; both amd64/arm64 configuration digests carry the exact source/version labels and indexed provenance/SBOM attestations. Beta.8 still points to its original source; publication used latest=false.

Image (ghcr.io/bostontechnologies/)	Immutable index digest
rateldesk-api:0.1.1-beta.9	sha256:eec06b11de2f348469130c45ecd7ab89375bcf28a8691a268d4fb6cda8473fe0
rateldesk-mcp-http:0.1.1-beta.9	sha256:c2355af06f77571a6ebe3a55ab20eeed594839a8bc1cb128e3b07341a95dbc6b
rateldesk-web:0.1.1-beta.9	sha256:732130de06c8229ac1d5fc3e14a9ca423468924a51e3f143aded6d3bd05f4ede

Immutable handoff at the merged SHA:

• Shared protocol prose, schema and permission profiles, golden fixtures, SHA256 manifest. Prose SHA256: ab3a33e61a33cf86744a9cb1b58c24513ca5bb193bbc1566a2e16362866c7f77.
• Preserved incident receiver contract, with unchanged schema/fixture digests.
• Issuer/deployment configuration and full later two-product acceptance sequence.

Read-only exact-title and broader-title searches found no NetRatel companion issue on 2026-10-04. Helpdesk M2M credentials and reciprocal RatelDesk linking remains a planned issue title. Context: NetRatel #141, #146, draft PR #152. Its current delivery guard requires actual compatible receiver verification before automatic delivery is enabled.

Later real acceptance must:

1. Pin this published release and the updated NetRatel candidate's SHA/build identities, artifacts, origins and persistent keys; use disposable explicitly mapped test tenants/customers.
2. Complete both initiating roles with final grants approved by both administrators, real directional OAuth probes, durable commit and both active acknowledgements; verify tenant/source isolation and pre-commit business denial.
3. Run approved catalogs, request invocation and an actual recorded-task callback. Create an incident, lose its committed response, restart, reconcile its receipt and replay the identical source/key/body; prove one incident/effect and conflicting-body rejection.
4. Exercise both directional rotations and response-loss/restart recovery, including late commit after setup expiry, cached-token grant disable, source identity continuity and unlink during peer outage with later reconciliation.
5. Record actual HTTP/database outcomes, immutable build identities, counts/skips and redacted evidence in the NetRatel continuation.

Actual production NetRatel interoperability has not been run. RatelDesk publication and synthetic peer conformance supply the forward-compatible handoff; they do not certify the real two-product deployment.