Skip to content

beta.4: Integration hub, scoped credentials, NetRatel orchestration and Netclaw #83

Closed

Description

@boston-ai-agent

Current M2M scope — owner decision, 9 October 2026

Replacement implementation: BostonTechnologies/netratel#180 ↔ #143.

The owner has retired the old NetRatel ↔ RatelDesk approval/redirect/recovery system and requested pairing codes: Generate a Pairing Code; address + code → Pair & connect; final tenant mapping/name/incident-or-automation capabilities → Save; View/Test/Delete. The replacement owns removal of old runtime/setup records, reviewed source changes, CI, normal merges and next compatible beta artifacts. Do not continue the earlier frozen-protocol, double-consent or manual/fallback setup criteria in this historical tracker.

This programme stays open. Its NetRatel interoperability child #89 now uses the replacement pairing-code foundation. Independent Netclaw child #90 and unrelated account credentials/MCP functionality remain in scope.

The old M2M-only issues are closed as superseded, not as evidence that their failed deployed journeys passed. Historical implementation and test receipts below retain their original meaning. Source/disposable acceptance and the owner’s deployed-beta acceptance must still be reported separately.


Programme for the beta.4 release: deliver the administrator Integration hub with separate NetRatel orchestrator, Netclaw AI harness, and account integration-credential destinations. Includes secure persisted provider configuration with canonical Orchestrator__ and Netclaw__ aliases, legacy compatibility, runtime application, protected secrets, scoped credential and local MCP verification, diagnostics, migrations, docs, and release rehearsal. Preserve existing account credential, CLI/stdio, HTTP MCP, callback, and reverse-auth boundaries. Do not modify NetRatel or Netclaw upstream, merge, tag, publish, promote, deploy, or change protection. Child phases: B4-00 baseline; B4-01 provider configuration; B4-02 credential lifecycle; B4-03 CLI/stdio; B4-04 HTTP MCP; B4-05 NetRatel; B4-06 Netclaw; B4-07 hub UX; B4-08 docs/release notes; B4-09 validation/readiness.

Current reconciliation — 6 October 2026

The historical programme/authority text above is retained. Its old draft/no-merge wording describes the original beta.4 task; the current reconciliation goal separately authorized reviewed in-scope RatelDesk merges through unchanged required gates. Implementation is already merged through PR #94 and later follow-ups. Current receipt: #132, merge abd5eaa49cfed28b79c91a31f130559b74220bf9; normal main validation https://github.com/BostonTechnologies/rateldesk/actions/runs/37437602554 and managed PostgreSQL https://github.com/BostonTechnologies/rateldesk/actions/runs/37437602528.

Post-merge verification is complete: all 17 normal jobs passed on abd5eaa49cfed28b79c91a31f130559b74220bf9; both linked final-main workflows completed successfully.

Eight children complete, two provider-acceptance children open. #93's original disposable-check scope was “where available”; closing that tracker does not establish unavailable real-provider acceptance. Keep #83 open and close it last when #89/#90 meet their accepted functionality. The historical beta.4 milestone does not request a revert or another beta.4 release.

RatelDesk beta.13 is now normally published from af71b9f9ae47bf75ea44f9fb486bd5c812d34910 (release run 37428393499), containing #131 but predating the current worker correction and dependency #122. Source availability/publication/actual acceptance remain separate.

The existing NetRatel #166 owner tested integration merge c1272be6f1aed7925a239bd1effbb49d4bf66a95, reviewed head d5bfa08550bd303e2d5d1388ed71336404c45fbc, in run 37433948570 against published RatelDesk beta.13. It finished cancelled at 08:45:33 UTC with 20 execution jobs (16 successful, three failed, one cancelled), a failed aggregate gate and skipped final guards. Its complete API Integration TRX is 42 passed / 10 failed / 0 skipped; both precommit-cancellation roles passed, both unlink roles failed with HTTP 429, only NetRatel-initiated native completion passed, and one manual RatelDesk-issuer rotation passed. These partial criteria are mapped in #89; they are not accepted final functionality. Keep the epic and its provider children open, preserve the existing owner and exact published-artifact boundary.

At 08:47 UTC / 10:47 SAST on 6 October, the latest observed open NetRatel #166 head is ef2e1467623e8d9ce7035e9025ce794967188732, owned by Proxicon. The d5bfa085/c1272be6 identities above belong to the completed cancelled run and are not the current head. Remaining accepted results are pending with that existing continuation.

Final repository checkpoint: the existing owner's newer NetRatel run 37438102230 is still in progress on ef2e1467623e8d9ce7035e9025ce794967188732, with no accepted conclusion. Reuse that owner's results; the completed d5/c127 receipts above are historical.

Activity

  1. Proxicon commented on Sep 26, 2026

    @Proxicon
    Contributor

    Implementation is on feat/beta4-integration-hub; review handoff is PR #94. Repository-scoped beta.4 work and non-publishing release rehearsal are complete. Live unchanged-target NetRatel M2M and Netclaw paired-device interoperability remain explicit acceptance steps for an authorized integration environment. No upstream changes, merge, tag, publish, promotion, deployment, or protection changes were made.

  2. boston-ai-agent commented on Sep 26, 2026

    @boston-ai-agent
    ContributorAuthor

    Beta.4 integration status update (2026-09-26):

    • Implementation commit 0f73da7 is pushed on feat/beta4-integration-hub; evidence ledger commit 945fd5d records the final review state.
    • Local final-head validation is green: 1,474 passed, 6 skipped, 0 failed; focused reliability set 73/73; Release build 0 errors; Slopwatch 0 findings; UX setup 1/1 and browser suite 31/31; non-publishing CLI/stdio/deployment archive rehearsal passed.
    • Hosted validation is green in PR run 36263572804 and managed PostgreSQL run 36263572778, including .NET, UX, mailbox lifecycle, Docker, Compose/PostgreSQL, disclosure/layout, release rehearsal, and all archive-runtime jobs.
    • Read-only NetRatel Dev M2M token acquisition and protected health are green. Full deployed RatelDesk ingest/ticket acceptance, paired unchanged Netclaw SignalR acceptance, and deployed CLI/stdio/HTTP MCP journeys remain external gates because no exact authorized target was identified.

    The implementation ledger is here, and PR #94 remains draft. No merge, release, deployment, registry publication, or upstream change was performed.

  3. Proxicon commented on Oct 6, 2026

    @Proxicon
    Contributor

    Current reconciliation merged in corrective PR, merge abd5eaa49cfed28b79c91a31f130559b74220bf9; ledger, normal final-main validation and managed PostgreSQL validation.

    Post-merge verification is complete: all 17 normal jobs passed on abd5eaa49cfed28b79c91a31f130559b74220bf9; both linked final-main workflows completed successfully.

    Eight repository-scoped children are complete: #84–#88 and #91–#93. The implementation is already merged through #94 and subsequent Netclaw/service-link follow-ups. PR #94 became non-draft and merged on 27 September 2026; its retained branch is not unmerged work. The #93 closure covers its original repository-validation/handoff and available disposable-check scope, not unavailable real-provider acceptance.

    The existing owner's NetRatel run 37433948570, reviewed head d5bfa08550bd303e2d5d1388ed71336404c45fbc and tested integration merge c1272be6f1aed7925a239bd1effbb49d4bf66a95, finished cancelled at 08:45:33 UTC / 10:45:33 SAST on 6 October against published beta.13 af71b9f. Its 21 checks comprise 20 execution jobs (16 successful, three failed, one cancelled .NET job) plus a failed aggregate gate; final general/native guards were skipped. Artifact 11400136247 contains a completed API Integration TRX (52 executed, 42 passed, 10 failed, 0 skipped; service-link subset 32 executed, 22 passed, 10 failed, 0 skipped). This is completed per-project evidence, not an accepted overall reciprocal suite. The #89 receipt records the exact peer identities/results. Keep the original unproven acceptance criteria pending and reuse the existing owner's continuation.

    A fresh read at 08:47 UTC / 10:47 SAST on 6 October found the open NetRatel #166 continuation at newer head ef2e1467623e8d9ce7035e9025ce794967188732, owned by Proxicon. The d5bfa085 reviewed head and c1272be6 integration merge identify the completed cancelled run above, not the latest continuation head. At the 08:50:32 UTC checkpoint the existing owner's run 37438102230 was in progress at that ef2 head, without a conclusion. Its PR body describes fixture pacing within unchanged rate-limit windows and explicit bootstrap tenant selection; that author report is not a completed CI receipt. Reuse the owner's current run and immutable results rather than starting another programme.

    Keep this epic open. #89 still needs accepted exact-peer M2M/catalog/payload/ingest/execution/callback/replay/uncertain-outcome evidence, including the supported legacy contract. #90 still needs the authorized real paired-daemon/device journey with its exact version/endpoint/operator and message/approval/reconnect/restart/runtime/provider-ownership proof. Their original acceptance boundaries remain unchanged.

    The existing release continuation published RatelDesk-0.1.1-beta.13 from af71b9f9ae47bf75ea44f9fb486bd5c812d34910 at 08:05 UTC / 10:05 SAST on 6 October (release run 37428393499). It includes #131, and predates both the new worker correction and dependency PR #122; it does not establish their publication or real-peer acceptance.

    The rollup checklist reflects these dispositions; close the epic only after #89 and #90 satisfy their outstanding accepted functionality.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions