Skip to content

feat(connections): shadow write policy and the shadow close receipt - #243

Merged
jfrench9 merged 1 commit into
mainfrom
feature/shadow-write-policy
Oct 8, 2026
Merged

jfrench9 merged 1 commit into
mainfrom
feature/shadow-write-policy

Conversation

@jfrench9

@jfrench9 jfrench9 commented Oct 8, 2026

Copy link
Copy Markdown
Member

Summary

Regenerated from the server after robosystems #1733 (shadow close) and #1738 (write-policy ladder). These fields reach the hosted API with the next server release after v1.16.5; until then the server rejects shadow and omits the new receipt fields.

Changes

  • SetWritePolicyRequestWritePolicy — now qb_authoritative or shadow. native is removed: it is what disconnecting or severing a connection leaves, and the server refuses it for a live connection.
  • ClosePeriodResponse — shadow, entries_shadowed, gate_findings, and gate_finding_counts (new model ClosePeriodResponseGateFindingCounts).
  • GraphQL schema — the close receipt's shadow fields (receipt v2), and on the period-drafts read shadow, shadowedCount, and each draft's closeDisposition.
  • Docstrings — connection creation and the Mercury config describe the per-entity bank-feed rule; LinkBankAccountResponse.changed.

Breaking Changes

None in the stable tier. Removing native from SetWritePolicyRequestWritePolicy is a generated-tier change and rides a client minor; it belongs in the release notes. No facade, the integration template, or the three apps send it.

Testing

  • just test-all: 667 passed, 17 skipped; ruff, format, and basedpyright clean.

🤖 Generated with Claude Code

Regenerated from robosystems #1733 and #1738. The write-policy request
takes 'qb_authoritative' or 'shadow'; 'native' is no longer accepted,
since it is what disconnecting or severing leaves. The close receipt and
the period-drafts read carry the shadow fields.
@jfrench9
jfrench9 merged commit 6174ab6 into main Oct 8, 2026
4 checks passed
@jfrench9
jfrench9 deleted the feature/shadow-write-policy branch October 8, 2026 18:57
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