Goal
Add a small synthetic export fixture set that can be used for tests, documentation examples, validation work, SQLite/schema work, and contributor development.
The fixture data must be fake, public-safe, and clearly marked as synthetic.
Why this matters
PluralBridge should not rely on private Simply Plural exports, real System data, real member/avatar data, real notes, real messages, real friends, real fronting history, real tokens, or real database files for public development.
Synthetic fixtures give contributors a safe way to build and test without handling private user data.
Suggested scope
Create a fixture area for synthetic export-like data, likely under one of these paths:
examples/synthetic-export/tests/fixtures/synthetic-export/
The fixture set should include small representative examples for data shapes PluralBridge already works with, such as:
- user/me data
- members
- groups
- custom fields
- front history
- privacy buckets
- notes shape
- avatar manifest shape
The first version does not need to cover every edge case. It should be small, readable, and safe to inspect in public.
Safety requirements
Do not use real Simply Plural exports.
Do not include real System data.
Do not include real member names, avatars, notes, messages, friend data, fronting history, API tokens, authorization headers, screenshots, logs, or database files.
Do not derive examples by lightly editing private data.
Use deliberately fictional data only.
Possible follow-up work
After the first fixture set exists, later Issues can use it for:
- export validation tests
- SQLite schema work
- documentation examples
- non-technical success/failure reporting
- regression tests
- sample reports
Acceptance criteria
- A small synthetic fixture set exists in a clear repo path.
- The fixture README or nearby documentation states that all fixture data is synthetic.
- The fixture data is suitable for public tests and examples.
- No private export data, real System data, tokens, avatars, notes, messages, logs, or database files are included.
Goal
Add a small synthetic export fixture set that can be used for tests, documentation examples, validation work, SQLite/schema work, and contributor development.
The fixture data must be fake, public-safe, and clearly marked as synthetic.
Why this matters
PluralBridge should not rely on private Simply Plural exports, real System data, real member/avatar data, real notes, real messages, real friends, real fronting history, real tokens, or real database files for public development.
Synthetic fixtures give contributors a safe way to build and test without handling private user data.
Suggested scope
Create a fixture area for synthetic export-like data, likely under one of these paths:
examples/synthetic-export/tests/fixtures/synthetic-export/The fixture set should include small representative examples for data shapes PluralBridge already works with, such as:
The first version does not need to cover every edge case. It should be small, readable, and safe to inspect in public.
Safety requirements
Do not use real Simply Plural exports.
Do not include real System data.
Do not include real member names, avatars, notes, messages, friend data, fronting history, API tokens, authorization headers, screenshots, logs, or database files.
Do not derive examples by lightly editing private data.
Use deliberately fictional data only.
Possible follow-up work
After the first fixture set exists, later Issues can use it for:
Acceptance criteria