Sign-up can now hand off its saved full name, normalized email and customer reference to Sendico’s public individual registry and immutable Facts intake when api.sendico is configured. The BFF persists the customer binding and intake receipt before activation email or sign-up success, and activation/resend cannot bypass the handoff.
Retries reuse the subject, saved assertions and source reference. A durable registration claim prevents automatic duplicate subjects after uncertain outcomes; typed EN/RU feedback directs those cases to support during sign-up and verification recovery. Initial activation tokens are replayable after intake outages without breaking atomic customer/token creation. The adapter keeps platform scope and credentials server-side, validates receipts, supports same-account credential rotation and emits bounded handoff metrics.
Validation: make lint-backend, GOFLAGS=-p=2 make test (all backend race tests and frontend suites), Dart formatting for all changed files, and flutter analyze in frontend/app and frontend/packages/sxchnge_auth. Initial validation exposed a Testcontainers reaper startup timeout and a new locale fixture that double-disposed app-owned state. The fixture was corrected and the final reduced-concurrency full run passed. Focused tests cover HTTP contracts, failures, privacy, concurrent durable claims, replay, activation rollback and localized mobile error state/analytics.
Enable with the real Sendico API URL, provisioned organization/source account IDs and a Vault-rendered access token. No live provider resources, live email, deployment or merge performed. Individual registration has no upstream idempotency contract, so ambiguous outcomes require documented operational reconciliation. See docs/signup-facts.md for configuration, rollout, measurement and recovery.
Sign-up can now hand off its saved full name, normalized email and customer reference to Sendico’s public individual registry and immutable Facts intake when `api.sendico` is configured. The BFF persists the customer binding and intake receipt before activation email or sign-up success, and activation/resend cannot bypass the handoff.
Retries reuse the subject, saved assertions and source reference. A durable registration claim prevents automatic duplicate subjects after uncertain outcomes; typed EN/RU feedback directs those cases to support during sign-up and verification recovery. Initial activation tokens are replayable after intake outages without breaking atomic customer/token creation. The adapter keeps platform scope and credentials server-side, validates receipts, supports same-account credential rotation and emits bounded handoff metrics.
Validation: `make lint-backend`, `GOFLAGS=-p=2 make test` (all backend race tests and frontend suites), Dart formatting for all changed files, and `flutter analyze` in `frontend/app` and `frontend/packages/sxchnge_auth`. Initial validation exposed a Testcontainers reaper startup timeout and a new locale fixture that double-disposed app-owned state. The fixture was corrected and the final reduced-concurrency full run passed. Focused tests cover HTTP contracts, failures, privacy, concurrent durable claims, replay, activation rollback and localized mobile error state/analytics.
Enable with the real Sendico API URL, provisioned organization/source account IDs and a Vault-rendered access token. No live provider resources, live email, deployment or merge performed. Individual registration has no upstream idempotency contract, so ambiguous outcomes require documented operational reconciliation. See `docs/signup-facts.md` for configuration, rollout, measurement and recovery.
Closes #46.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Sign-up can now hand off its saved full name, normalized email and customer reference to Sendico’s public individual registry and immutable Facts intake when
api.sendicois configured. The BFF persists the customer binding and intake receipt before activation email or sign-up success, and activation/resend cannot bypass the handoff.Retries reuse the subject, saved assertions and source reference. A durable registration claim prevents automatic duplicate subjects after uncertain outcomes; typed EN/RU feedback directs those cases to support during sign-up and verification recovery. Initial activation tokens are replayable after intake outages without breaking atomic customer/token creation. The adapter keeps platform scope and credentials server-side, validates receipts, supports same-account credential rotation and emits bounded handoff metrics.
Validation:
make lint-backend,GOFLAGS=-p=2 make test(all backend race tests and frontend suites), Dart formatting for all changed files, andflutter analyzeinfrontend/appandfrontend/packages/sxchnge_auth. Initial validation exposed a Testcontainers reaper startup timeout and a new locale fixture that double-disposed app-owned state. The fixture was corrected and the final reduced-concurrency full run passed. Focused tests cover HTTP contracts, failures, privacy, concurrent durable claims, replay, activation rollback and localized mobile error state/analytics.Enable with the real Sendico API URL, provisioned organization/source account IDs and a Vault-rendered access token. No live provider resources, live email, deployment or merge performed. Individual registration has no upstream idempotency contract, so ambiguous outcomes require documented operational reconciliation. See
docs/signup-facts.mdfor configuration, rollout, measurement and recovery.Closes #46.
tech referenced this pull request2026-10-17 05:18:02 +00:00