fix: accept nullable message publishers and scoped dev SPB trust
Some checks failed
Mostovik Backend CI/CD / Tests and lint (push) Successful in 3m3s
Mostovik Backend CI/CD / Deploy dev (push) Has been cancelled
Mostovik Backend CI/CD / Deploy and verify internal main (push) Has been cancelled
Mostovik Backend CI/CD / Build linux/amd64 release images (push) Has been cancelled

This commit is contained in:
Aleksandr Meshchryakov
2026-10-05 19:23:03 +02:00
parent 0dd763109b
commit 1a82345ab3
13 changed files with 131 additions and 15 deletions

View File

@@ -98,3 +98,24 @@ readiness remains separate from enablement.
already-applied and fresh databases — cost if wrong: 0048 must apply to activate.
- Ruling: retain daily FSSP/exchange and 30-day Checko intervals/monthly claims —
minimal requested change — cost if wrong: 30-day cadence is not a calendar month.
## Live acceptance continuation
- Ruling: accept nullable Checko publisher only when the canonical subject still
matches the publisher or an exact participant — observed real upstream null,
no invented identifier — cost if wrong: messages without confirmed subject
remain rejected; generated clients must accept null.
- Ruling: preserve specific SnapshotValidationError before its ValueError base
handler — real diagnostics otherwise conceal the rejected field — cost if
wrong: safe error codes become more specific for existing rejected inputs.
- Ruling: stop the broken messages run cooperatively, keep all monthly claims,
and rerun only eligible unclaimed scopes after release — avoids repeated costs
for known adapter failures — cost if wrong: first-month coverage stays partial.
- Ruling: use the two already verified official FSSP daily files for separate
manual import acceptance when dev receives HTTP 474 — no network bypass or
invented freshness — cost if wrong: manual publication does not prove the
automatic upstream download is operational.
- Ruling: enable the existing Russian CA only in SPB's dedicated allowlisted
session behind a default-off setting and a dev-only host compose flag after
explicit user consent — cost if wrong: only SPB gains this extra trust;
MOEX/system/main trust remains unchanged, certificate verification stays on.