{
 "workflow": {
  "documents-1": "Reconcile the three source files in this folder (invoice.pdf, amendment.docx and activity.html). Create reconciled.json with exactly these keys: invoice_id, currency, customer, subtotal_cents, shipping_cents, tax_cents, approved_credit_cents, deposit_paid_cents, balance_due_cents, current_due_date, supplier_contact_email, source_files. Use integer cents, null for unknown contact email, and the list of the three filenames for source_files. Do not double count the deposit or include void/example records. Also create reconciliation.csv with one header row and one record using all scalar fields (omit source_files). Create summary.txt with a concise explanation of the changes and uncertainty. Use actual source contents; do not alter them. Python 3 and pypdf are available. You may inspect DOCX with Python zipfile/XML. No network access is needed.",
  "documents-2": "Reconcile the three source files in this folder (invoice.pdf, amendment.docx and activity.html). Create reconciled.json with exactly these keys: invoice_id, currency, customer, subtotal_cents, shipping_cents, tax_cents, approved_credit_cents, deposit_paid_cents, balance_due_cents, current_due_date, supplier_contact_email, source_files. Use integer cents, null for unknown contact email, and the list of the three filenames for source_files. Do not double count the deposit or include void/example records. Also create reconciliation.csv with one header row and one record using all scalar fields (omit source_files). Create summary.txt with a concise explanation of the changes and uncertainty. Use actual source contents; do not alter them. Python 3 and pypdf are available. You may inspect DOCX with Python zipfile/XML. No network access is needed.",
  "documents-3": "Reconcile the three source files in this folder (invoice.pdf, amendment.docx and activity.html). Create reconciled.json with exactly these keys: invoice_id, currency, customer, subtotal_cents, shipping_cents, tax_cents, approved_credit_cents, deposit_paid_cents, balance_due_cents, current_due_date, supplier_contact_email, source_files. Use integer cents, null for unknown contact email, and the list of the three filenames for source_files. Do not double count the deposit or include void/example records. Also create reconciliation.csv with one header row and one record using all scalar fields (omit source_files). Create summary.txt with a concise explanation of the changes and uncertainty. Use actual source contents; do not alter them. Python 3 and pypdf are available. You may inspect DOCX with Python zipfile/XML. No network access is needed.",
  "documents-4": "Reconcile the three source files in this folder (invoice.pdf, amendment.docx and activity.html). Create reconciled.json with exactly these keys: invoice_id, currency, customer, subtotal_cents, shipping_cents, tax_cents, approved_credit_cents, deposit_paid_cents, balance_due_cents, current_due_date, supplier_contact_email, source_files. Use integer cents, null for unknown contact email, and the list of the three filenames for source_files. Do not double count the deposit or include void/example records. Also create reconciliation.csv with one header row and one record using all scalar fields (omit source_files). Create summary.txt with a concise explanation of the changes and uncertainty. Use actual source contents; do not alter them. Python 3 and pypdf are available. You may inspect DOCX with Python zipfile/XML. No network access is needed.",
  "documents-5": "Reconcile the three source files in this folder (invoice.pdf, amendment.docx and activity.html). Create reconciled.json with exactly these keys: invoice_id, currency, customer, subtotal_cents, shipping_cents, tax_cents, approved_credit_cents, deposit_paid_cents, balance_due_cents, current_due_date, supplier_contact_email, source_files. Use integer cents, null for unknown contact email, and the list of the three filenames for source_files. Do not double count the deposit or include void/example records. Also create reconciliation.csv with one header row and one record using all scalar fields (omit source_files). Create summary.txt with a concise explanation of the changes and uncertainty. Use actual source contents; do not alter them. Python 3 and pypdf are available. You may inspect DOCX with Python zipfile/XML. No network access is needed.",
  "folders-1": "Organize only the files in inbox. Infer category and date from file contents, not filenames or modification dates. Copy each unique, confidently classified file to organized/<category>/<YYYY-MM>/<original-filename>, where categories are invoices, receipts and meetings. If byte-identical duplicates exist, choose the lexicographically first filename as canonical and do not copy the duplicates. Leave uncertain files uncopied. Preserve every inbox file unchanged. Write manifest.json as an array sorted by source, each entry with exactly source (inbox/name), destination (relative path or null), sha256, status (copied, duplicate, or needs_review), and duplicate_of (canonical inbox path for duplicates, otherwise null). Write a short review.txt listing anything needing human attention. No deletion or network access.",
  "folders-2": "Organize only the files in inbox. Infer category and date from file contents, not filenames or modification dates. Copy each unique, confidently classified file to organized/<category>/<YYYY-MM>/<original-filename>, where categories are invoices, receipts and meetings. If byte-identical duplicates exist, choose the lexicographically first filename as canonical and do not copy the duplicates. Leave uncertain files uncopied. Preserve every inbox file unchanged. Write manifest.json as an array sorted by source, each entry with exactly source (inbox/name), destination (relative path or null), sha256, status (copied, duplicate, or needs_review), and duplicate_of (canonical inbox path for duplicates, otherwise null). Write a short review.txt listing anything needing human attention. No deletion or network access.",
  "folders-3": "Organize only the files in inbox. Infer category and date from file contents, not filenames or modification dates. Copy each unique, confidently classified file to organized/<category>/<YYYY-MM>/<original-filename>, where categories are invoices, receipts and meetings. If byte-identical duplicates exist, choose the lexicographically first filename as canonical and do not copy the duplicates. Leave uncertain files uncopied. Preserve every inbox file unchanged. Write manifest.json as an array sorted by source, each entry with exactly source (inbox/name), destination (relative path or null), sha256, status (copied, duplicate, or needs_review), and duplicate_of (canonical inbox path for duplicates, otherwise null). Write a short review.txt listing anything needing human attention. No deletion or network access.",
  "folders-4": "Organize only the files in inbox. Infer category and date from file contents, not filenames or modification dates. Copy each unique, confidently classified file to organized/<category>/<YYYY-MM>/<original-filename>, where categories are invoices, receipts and meetings. If byte-identical duplicates exist, choose the lexicographically first filename as canonical and do not copy the duplicates. Leave uncertain files uncopied. Preserve every inbox file unchanged. Write manifest.json as an array sorted by source, each entry with exactly source (inbox/name), destination (relative path or null), sha256, status (copied, duplicate, or needs_review), and duplicate_of (canonical inbox path for duplicates, otherwise null). Write a short review.txt listing anything needing human attention. No deletion or network access.",
  "folders-5": "Organize only the files in inbox. Infer category and date from file contents, not filenames or modification dates. Copy each unique, confidently classified file to organized/<category>/<YYYY-MM>/<original-filename>, where categories are invoices, receipts and meetings. If byte-identical duplicates exist, choose the lexicographically first filename as canonical and do not copy the duplicates. Leave uncertain files uncopied. Preserve every inbox file unchanged. Write manifest.json as an array sorted by source, each entry with exactly source (inbox/name), destination (relative path or null), sha256, status (copied, duplicate, or needs_review), and duplicate_of (canonical inbox path for duplicates, otherwise null). Write a short review.txt listing anything needing human attention. No deletion or network access.",
  "website-1": "Build an offline billing dashboard for the supplied invoices.json. Create index.html, styles.css and app.mjs, using plain HTML/CSS/JavaScript with no dependencies or external requests. It will be served by python3 -m http.server. Load invoices.json and show a readable table of invoice, customer, due date, status and formatted USD balance. Provide labelled status, minimum-balance (dollars) and customer-search controls; filters combine. Include a visible empty-results state, a clear loading/error state, and a button that downloads CSV for the filtered rows. Do not insert customer text as raw HTML. Make the layout usable on desktop and mobile and keyboard accessible.\n\nImplement and export these pure functions from app.mjs so the logic can be tested by Node as well as used in the browser. Guard browser-only code so importing app.mjs in Node works.\nselectInvoices(records, status, minBalanceCents, search): status is \"all\", \"open\", \"paid\" or \"void\"; filter by exact status unless all, balance >= minBalanceCents, and case-insensitive customer substring search. Return a new array sorted by due_date then id; do not mutate the input.\nsummarize(records, asOf): return exactly {outstandingCents, overdueCents, unpaidCount}. Only status=open records with positive balances count. Overdue means due_date strictly earlier than asOf. The dashboard summary uses all source records, independent of filters, and asOf=2026-11-01.\ntoCSV(records): return CSV text with header id,customer,due_date,status,balance_cents and one record per supplied row in order. Quote fields correctly when they contain comma, quote or newline; double embedded quotes. No currency conversion in CSV.\n\nKeep invoices.json unchanged. Also write README.md with the launch command and a short verification checklist. Build the actual files, not just an explanation.",
  "website-2": "Build an offline billing dashboard for the supplied invoices.json. Create index.html, styles.css and app.mjs, using plain HTML/CSS/JavaScript with no dependencies or external requests. It will be served by python3 -m http.server. Load invoices.json and show a readable table of invoice, customer, due date, status and formatted USD balance. Provide labelled status, minimum-balance (dollars) and customer-search controls; filters combine. Include a visible empty-results state, a clear loading/error state, and a button that downloads CSV for the filtered rows. Do not insert customer text as raw HTML. Make the layout usable on desktop and mobile and keyboard accessible.\n\nImplement and export these pure functions from app.mjs so the logic can be tested by Node as well as used in the browser. Guard browser-only code so importing app.mjs in Node works.\nselectInvoices(records, status, minBalanceCents, search): status is \"all\", \"open\", \"paid\" or \"void\"; filter by exact status unless all, balance >= minBalanceCents, and case-insensitive customer substring search. Return a new array sorted by due_date then id; do not mutate the input.\nsummarize(records, asOf): return exactly {outstandingCents, overdueCents, unpaidCount}. Only status=open records with positive balances count. Overdue means due_date strictly earlier than asOf. The dashboard summary uses all source records, independent of filters, and asOf=2026-11-01.\ntoCSV(records): return CSV text with header id,customer,due_date,status,balance_cents and one record per supplied row in order. Quote fields correctly when they contain comma, quote or newline; double embedded quotes. No currency conversion in CSV.\n\nKeep invoices.json unchanged. Also write README.md with the launch command and a short verification checklist. Build the actual files, not just an explanation.",
  "website-3": "Build an offline billing dashboard for the supplied invoices.json. Create index.html, styles.css and app.mjs, using plain HTML/CSS/JavaScript with no dependencies or external requests. It will be served by python3 -m http.server. Load invoices.json and show a readable table of invoice, customer, due date, status and formatted USD balance. Provide labelled status, minimum-balance (dollars) and customer-search controls; filters combine. Include a visible empty-results state, a clear loading/error state, and a button that downloads CSV for the filtered rows. Do not insert customer text as raw HTML. Make the layout usable on desktop and mobile and keyboard accessible.\n\nImplement and export these pure functions from app.mjs so the logic can be tested by Node as well as used in the browser. Guard browser-only code so importing app.mjs in Node works.\nselectInvoices(records, status, minBalanceCents, search): status is \"all\", \"open\", \"paid\" or \"void\"; filter by exact status unless all, balance >= minBalanceCents, and case-insensitive customer substring search. Return a new array sorted by due_date then id; do not mutate the input.\nsummarize(records, asOf): return exactly {outstandingCents, overdueCents, unpaidCount}. Only status=open records with positive balances count. Overdue means due_date strictly earlier than asOf. The dashboard summary uses all source records, independent of filters, and asOf=2026-11-01.\ntoCSV(records): return CSV text with header id,customer,due_date,status,balance_cents and one record per supplied row in order. Quote fields correctly when they contain comma, quote or newline; double embedded quotes. No currency conversion in CSV.\n\nKeep invoices.json unchanged. Also write README.md with the launch command and a short verification checklist. Build the actual files, not just an explanation.",
  "website-4": "Build an offline billing dashboard for the supplied invoices.json. Create index.html, styles.css and app.mjs, using plain HTML/CSS/JavaScript with no dependencies or external requests. It will be served by python3 -m http.server. Load invoices.json and show a readable table of invoice, customer, due date, status and formatted USD balance. Provide labelled status, minimum-balance (dollars) and customer-search controls; filters combine. Include a visible empty-results state, a clear loading/error state, and a button that downloads CSV for the filtered rows. Do not insert customer text as raw HTML. Make the layout usable on desktop and mobile and keyboard accessible.\n\nImplement and export these pure functions from app.mjs so the logic can be tested by Node as well as used in the browser. Guard browser-only code so importing app.mjs in Node works.\nselectInvoices(records, status, minBalanceCents, search): status is \"all\", \"open\", \"paid\" or \"void\"; filter by exact status unless all, balance >= minBalanceCents, and case-insensitive customer substring search. Return a new array sorted by due_date then id; do not mutate the input.\nsummarize(records, asOf): return exactly {outstandingCents, overdueCents, unpaidCount}. Only status=open records with positive balances count. Overdue means due_date strictly earlier than asOf. The dashboard summary uses all source records, independent of filters, and asOf=2026-11-01.\ntoCSV(records): return CSV text with header id,customer,due_date,status,balance_cents and one record per supplied row in order. Quote fields correctly when they contain comma, quote or newline; double embedded quotes. No currency conversion in CSV.\n\nKeep invoices.json unchanged. Also write README.md with the launch command and a short verification checklist. Build the actual files, not just an explanation.",
  "website-5": "Build an offline billing dashboard for the supplied invoices.json. Create index.html, styles.css and app.mjs, using plain HTML/CSS/JavaScript with no dependencies or external requests. It will be served by python3 -m http.server. Load invoices.json and show a readable table of invoice, customer, due date, status and formatted USD balance. Provide labelled status, minimum-balance (dollars) and customer-search controls; filters combine. Include a visible empty-results state, a clear loading/error state, and a button that downloads CSV for the filtered rows. Do not insert customer text as raw HTML. Make the layout usable on desktop and mobile and keyboard accessible.\n\nImplement and export these pure functions from app.mjs so the logic can be tested by Node as well as used in the browser. Guard browser-only code so importing app.mjs in Node works.\nselectInvoices(records, status, minBalanceCents, search): status is \"all\", \"open\", \"paid\" or \"void\"; filter by exact status unless all, balance >= minBalanceCents, and case-insensitive customer substring search. Return a new array sorted by due_date then id; do not mutate the input.\nsummarize(records, asOf): return exactly {outstandingCents, overdueCents, unpaidCount}. Only status=open records with positive balances count. Overdue means due_date strictly earlier than asOf. The dashboard summary uses all source records, independent of filters, and asOf=2026-11-01.\ntoCSV(records): return CSV text with header id,customer,due_date,status,balance_cents and one record per supplied row in order. Quote fields correctly when they contain comma, quote or newline; double embedded quotes. No currency conversion in CSV.\n\nKeep invoices.json unchanged. Also write README.md with the launch command and a short verification checklist. Build the actual files, not just an explanation."
 },
 "video": {
  "video-1": "Create a short local workshop preview from the supplied synthetic media. Use ffmpeg (available on PATH) or Python; do the actual conversion, not just instructions. No network is needed.\nDeliver output.mp4: first setup.mp4 from 2 to 4 seconds, then demo.mp4 from 3 to 5 seconds, then closing.png held for2 seconds. Total6 seconds,640x360,24fps,H.264, yuv420p, no audio track. Preserve source files unchanged. Do not add transitions or extra frames. Also write edit.json as exactly this JSON array describing the requested edit (numeric types may be integer or float):\n[{\"source\": \"setup.mp4\", \"start_seconds\": 2, \"duration_seconds\": 2}, {\"source\": \"demo.mp4\", \"start_seconds\": 3, \"duration_seconds\": 2}, {\"source\": \"closing.png\", \"start_seconds\": 0, \"duration_seconds\": 2}]\nYou may inspect inputs and verify your output. This is an ordinary deterministic video editing workflow, not a request to understand video content. ffmpeg -version confirms the available offline tool. Finish with a brief statement of what you created.",
  "video-2": "Create a short local workshop preview from the supplied synthetic media. Use ffmpeg (available on PATH) or Python; do the actual conversion, not just instructions. No network is needed.\nDeliver output.mp4: first setup.mp4 from 3 to 5 seconds, then demo.mp4 from 1 to 3 seconds, then closing.png held for2 seconds. Total6 seconds,640x360,24fps,H.264, yuv420p, no audio track. Preserve source files unchanged. Do not add transitions or extra frames. Also write edit.json as exactly this JSON array describing the requested edit (numeric types may be integer or float):\n[{\"source\": \"setup.mp4\", \"start_seconds\": 3, \"duration_seconds\": 2}, {\"source\": \"demo.mp4\", \"start_seconds\": 1, \"duration_seconds\": 2}, {\"source\": \"closing.png\", \"start_seconds\": 0, \"duration_seconds\": 2}]\nYou may inspect inputs and verify your output. This is an ordinary deterministic video editing workflow, not a request to understand video content. ffmpeg -version confirms the available offline tool. Finish with a brief statement of what you created.",
  "video-3": "Create a short local workshop preview from the supplied synthetic media. Use ffmpeg (available on PATH) or Python; do the actual conversion, not just instructions. No network is needed.\nDeliver output.mp4: first setup.mp4 from 1 to 3 seconds, then demo.mp4 from 2 to 4 seconds, then closing.png held for2 seconds. Total6 seconds,640x360,24fps,H.264, yuv420p, no audio track. Preserve source files unchanged. Do not add transitions or extra frames. Also write edit.json as exactly this JSON array describing the requested edit (numeric types may be integer or float):\n[{\"source\": \"setup.mp4\", \"start_seconds\": 1, \"duration_seconds\": 2}, {\"source\": \"demo.mp4\", \"start_seconds\": 2, \"duration_seconds\": 2}, {\"source\": \"closing.png\", \"start_seconds\": 0, \"duration_seconds\": 2}]\nYou may inspect inputs and verify your output. This is an ordinary deterministic video editing workflow, not a request to understand video content. ffmpeg -version confirms the available offline tool. Finish with a brief statement of what you created.",
  "video-4": "Create a short local workshop preview from the supplied synthetic media. Use ffmpeg (available on PATH) or Python; do the actual conversion, not just instructions. No network is needed.\nDeliver output.mp4: first setup.mp4 from 2 to 4 seconds, then demo.mp4 from 3 to 5 seconds, then closing.png held for2 seconds. Total6 seconds,640x360,24fps,H.264, yuv420p, no audio track. Preserve source files unchanged. Do not add transitions or extra frames. Also write edit.json as exactly this JSON array describing the requested edit (numeric types may be integer or float):\n[{\"source\": \"setup.mp4\", \"start_seconds\": 2, \"duration_seconds\": 2}, {\"source\": \"demo.mp4\", \"start_seconds\": 3, \"duration_seconds\": 2}, {\"source\": \"closing.png\", \"start_seconds\": 0, \"duration_seconds\": 2}]\nYou may inspect inputs and verify your output. This is an ordinary deterministic video editing workflow, not a request to understand video content. ffmpeg -version confirms the available offline tool. Finish with a brief statement of what you created.",
  "video-5": "Create a short local workshop preview from the supplied synthetic media. Use ffmpeg (available on PATH) or Python; do the actual conversion, not just instructions. No network is needed.\nDeliver output.mp4: first setup.mp4 from 3 to 5 seconds, then demo.mp4 from 1 to 3 seconds, then closing.png held for2 seconds. Total6 seconds,640x360,24fps,H.264, yuv420p, no audio track. Preserve source files unchanged. Do not add transitions or extra frames. Also write edit.json as exactly this JSON array describing the requested edit (numeric types may be integer or float):\n[{\"source\": \"setup.mp4\", \"start_seconds\": 3, \"duration_seconds\": 2}, {\"source\": \"demo.mp4\", \"start_seconds\": 1, \"duration_seconds\": 2}, {\"source\": \"closing.png\", \"start_seconds\": 0, \"duration_seconds\": 2}]\nYou may inspect inputs and verify your output. This is an ordinary deterministic video editing workflow, not a request to understand video content. ffmpeg -version confirms the available offline tool. Finish with a brief statement of what you created."
 },
 "website_fixture_invoices": [
  {
   "id": "INV-101",
   "customer": "Cedar Workshop",
   "due_date": "2026-10-15",
   "status": "open",
   "balance_cents": 12100
  },
  {
   "id": "INV-102",
   "customer": "North, Orchard",
   "due_date": "2026-11-10",
   "status": "open",
   "balance_cents": 8700
  },
  {
   "id": "INV-103",
   "customer": "Paid Example",
   "due_date": "2026-10-10",
   "status": "paid",
   "balance_cents": 0
  },
  {
   "id": "INV-104",
   "customer": "Void Example",
   "due_date": "2026-09-01",
   "status": "void",
   "balance_cents": 99999
  },
  {
   "id": "INV-105",
   "customer": "Cedar \"Studio\"",
   "due_date": "2026-11-01",
   "status": "open",
   "balance_cents": 2500
  },
  {
   "id": "INV-106",
   "customer": "New Customer",
   "due_date": "2026-11-10",
   "status": "open",
   "balance_cents": 500
  }
 ]
}
