Attached are domains.csv, schema-fields.csv and domains.json from the Inspired
focus-domain dataset.

I am adding Inspired to a product catalogue tool. Our internal product record
has these fields: name, description, category, colour, material, shape,
condition_notes, and hardware_notes.

Using the dataset, not guesswork:

1. Build me a mapping table from each Inspired item field to one of our fields,
   per domain. I care about fashion, furniture and devices. Where a domain has
   no equivalent for one of ours, say so explicitly rather than picking the
   nearest field — I would rather leave it empty than fill it with the wrong
   thing.
2. Point out every field that exists in one of those three domains and not in
   the others, and tell me which of our fields would be empty as a result. I
   know front_opening is fashion-only; find the rest from the data.
3. Tell me which fields are lists rather than strings, and what their ceilings
   are, so I size our columns correctly.
4. For the fields with a closed vocabulary, give me the allowed values so I can
   make them an enum on our side instead of free text.
5. Write me a check that fails our build if Inspired's reading prompt changes
   for any of those three domains, using analysis_prompt_sha256. Pin today's
   values from the CSV.

One thing to be careful about: every field in this schema is required, so a
missing value in a response is not "the reader skipped it" — it means something
else went wrong. Do not design around optional fields that do not exist.