Repository navigation
Attach external PDFs to partner and account records - #143
Merged
Merged
Conversation
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
added 4 commits
October 22, 2026 12:38
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Staff can now attach an externally signed MNDA or another PDF directly to a saved partner, organization, or account. The Documents section captures a title, document type and optional signing date, shows who uploaded it and when, and provides private view/download links. Organization and account pages share the account's attachments; standalone partner records retain their own files.
The existing PDF store enforces the 25 MB limit and verifies file hashes. Migration 001482 adds append-only attachment metadata with an explicit account or partner foreign key, content deduplication, and protection against deleting referenced bytes. Every request requires the record's staff read permission and MFA; uploads also require
contract:write. Uploads and downloads are audited. Retries preserve the same attachment, and attaching an external document does not advance signing or approval workflows.Release compatibility: route handlers use the repository’s explicit guard pattern. The release audit also required patching the existing MCP SDK to 1.32.0 and Vite to 8.2.4, removing the resolved SDK advisory waiver, and enabling the SDK’s input-element limit with an audited-refusal regression test.
CI database startup now preserves the pinned CLI’s ECR → GHCR → Docker Hub fallback instead of forcing a single mirror, and authenticates GHCR with the job’s read-only token. Repeated registry throttling had prevented integration/proof jobs from starting, including an authenticated GHCR attempt.
Approved registration seeds now keep their protection windows relative to reset time, matching the existing referral seed. Fixed October expiries had started failing existing RLS quote and registration-ownership tests. No production policy is changed.
Validation: