Keep new Chore assignees in the current family

[NewWorldVenture]

A new Chore assignment now verifies that the referenced member belongs to the current family after the existing chore lookup succeeds and before writing the assignment. Missing, foreign, malformed, or failed member reads return the existing refusal result. UUID casing, chore error precedence, due dates, assignment keys, and settled createChore retries retain their behavior.

The change inserts only the member preflight in assignChore and adds its finite SDK regression suite. All original 19 case bodies and the existing service-tasks test remain unchanged.

Validation:

• Same frozen 25 cases: candidate25 PASS, parent10 desired FAIL/15 controls, canonical default25 PASS; zero skipped cases.
• Root, author, and independent reviewer agree on all50 pair request/raw-response/SDK-reply/result vectors. Transport is synthetic and bounded to at most3 requests per case.
• Full native sealed8192MB nonincremental TypeScript and scoped two-file lint pass.

The proof covers the service contract with the installed SDK and inert transport. Migration0311 already guards authenticated database references; its trusted-role exemption is unchanged. Actual database/RLS, Auth, provider, audit, AI tool, createChore workflow, browser, and production behavior remain outside this proof. The parent does not issue member reads, so configured member403/500 cases only become physical SDK error coverage in the candidate.

Stacked on #858. Ownership and preserved chronology: #771 (comment). Final root acceptance71e7f443 and independent33484223 accepted source1574ab20/testc92db2e1 before commit. Historical unit-status reconciliation and private fixture/header/lint diagnostics are retained in the evidence packet; there is no closure credit.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated
bubaly	Ignored		Oct 3, 2026 5:54am UTC