ARTICLE REVIEW FIXTURES — NOT A FILEMAKER APPLICATION

All people, IDs and records are fictional. Work in a disposable review file.
These CSVs do not create tables, relationships, scripts or transaction guards.
These fixture files alone do not establish native execution. Each article describes the scope of its separate native laboratory checks.

Import identifiers as Text. Import date components as Number; create Timestamp
values with Timestamp(Date(Month;Day;Year);Time(Hour;Minute;Second)).
For DueDateISO, parse the known YYYY-MM-DD components explicitly into Date;
do not assume the CSV import locale. Leave the empty due date empty.

Exact find: use the supplied Contacts fields and inspect returned ContactIDs.
Timestamp: expected membership is T02,T03,T04 for 21 October 2026.
Dashboard: expected-results.json names exact IDs, not merely totals.
Bulk update: import bulk-tasks and bulk-update-plan separately. Create a real
receipt/transaction worker before testing writes; the article is pseudocode.
Merge: import contacts and notes separately. Do not run in a customer file.
Review dependency coverage and concurrency before implementing the merge.

Attachment: the tiny text file tests metadata only. Create an oversized file
in your temporary review folder by saving more than 5,242,880 bytes. Insert it
as a candidate; the policy should reject it. Do not rename it to imply safety.

Record exact FileMaker/client/server versions, account role, actual IDs,
error outcomes and date. A Python fixture consistency check is not a native
FileMaker find, transaction, container or hosting test.