artworklady-digitizingArtwork Lady embroidery-digitizing intake adapter — post a digitizing job into the Art work Lady portal (https://www.artworklady.com), which has no API. A Playwright driver logs in, opens the "Embroidery Digitizing" tab on the /placeorder form, fills the fields (job reference, turnaround, file type, color scheme, message), attaches 1–3 files, and — only when told to — clicks Send and confirms the job posted by watching the real order_form_submit response. Use when a decoration needs to be sent out for digitizing: "send this decoration to Artwork Lady", "post the digitizing job", "submit to the digitizer". It is a THIN PORTAL ADAPTER and touches no ERP: give it a job reference, the field values, and local file paths, and it returns a structured result. Pair it with a routine that polls Odoo `digitize.demand` (or `decoration`), downloads the attachments to disk, calls this skill, and updates the record on success. Submitting is gated behind `confirm: true`; the default is a dry run that fills and validates the form but posts nothing. A `fetch` command also downloads the FINISHED files back from `/orders` by job reference (the return leg), returning the DST path — by scraping our own order row so a job-number collision can't fetch the wrong file.
drivethru-digitize-outsourcingOutsource embroidery digitizing end to end for BaconCo (Odoo). On a routine, read the `digitize.demand` records that are Ready to send out, pull the decoration's embroidery artwork + specs (production PNG, AI source file, height/width, thread-colour names, ship date), download the two files, decide rush from the ship date, submit the job to the outside digitizer via the `artworklady-digitizing` skill with a brief that states the size and colours, and — only on a confirmed submission — transition the demand to Outsource in Odoo. Talks to Odoo through the `drivethru_mcp` MCP server (digitize_demand_* + decoration_* tools) and hands the actual portal submission to the `artworklady-digitizing` skill. Idempotent: it only ever works Ready demands and marks them outsourced after a confirmed send, so a retry can't double-post. Use whenever the user asks to outsource digitizing, send embroidery jobs to the digitizer / Artwork Lady, receive digitized files back, or run the digitizing-outsourcing routine. It also runs the RETURN leg: for demands already Outsourced, fetch the finished stitch file (DST) from the digitizer by job number and upload it to Odoo via `digitize_demand_upload`, advancing the demand Outsource → Sew Out, then parse the job's Production Worksheet PDF and push its stitch count, sewn size, and Stop-Sequence thread colours onto the decoration via `digitize_demand_apply_worksheet`, and file the vendor's returned files (worksheet PDF, DST, native design) away on the agent's own persistent storage — organized by job, retrievable on request, not in Odoo.