Skip to content

Fix service-link consent recovery and bounded protocol token reuse - #131

Merged
Proxicon merged 1 commit into
mainfrom
correction/service-link-human-consent-worker
Oct 6, 2026
Merged

Proxicon merged 1 commit into
mainfrom
correction/service-link-human-consent-worker

Conversation

@Proxicon

@Proxicon Proxicon commented Oct 6, 2026

Copy link
Copy Markdown
Contributor

Background workers were writing scheduling updates to attempts still awaiting administrator consent, creating avoidable approval conflicts. Protocol recovery also acquired a new token for each retry. Keep live consent waits unchanged and reuse verification/control tokens for the exact current peer, tenant, scope and credential revision.

Every use rechecks durable authority and current endpoint policy. Expiry, terminal recovery permissions, rotation journals, rate limits and timeouts retain their existing bounds. Prepare RatelDesk 0.1.1-beta.13 through the central version properties and record the corrections in the release notes.

Validation:

  • Complete Release solution build passed: 14 projects, zero errors, 21 unchanged existing warnings.
  • Whole unfiltered solution tests passed: 2,077 distinct cases, 2,071 passed, zero failed, six unchanged existing skips. All 70 new token-cache cases and six new real PostgreSQL consent/expiry cases passed without skips. All 2,001 prior cases retain their original identities and outcomes.
  • The six existing skips retain their original reasons: three incident endpoint cases, two presence endpoint cases and the invalid-request problem-details case. They do not count as acceptance for the new behavior.
  • Independent review verified the exact 11-file change and all unchanged contracts, migrations, dependencies and workflows.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant