[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7D901PJ7DVXMXNCWPTDVR8T":3,"skill-same:01M7D901PJ7DVXMXNCWPTDVR8T":44},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M7D901PJ7DVXMXNCWPTDVR8T","print",null,"Print a ScadBuddy output through Bambuddy - read the dialog's choices, pick a spool per slot, the nozzle size, quality and plate, options and project, run it with the user's approval, and follow its progress. Use when asked to print, send, queue or slice a generated model, or to explain why a print was refused or failed, and to link or dismiss the prints ScadBuddy did not start (Import print, the print watcher, Unsorted imports).","eh-homelab\u002FScadBuddy","eh-homelab","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F151211405?v=4","01M7D8YNX7WA95EFW6VTKN1A7N","01M7D8YNY6562P06GFHH5TQ37V",2,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Feh-homelab\u002FScadBuddy\u002Fblob\u002Fmain\u002Fplugins\u002Fscadbuddy\u002Fskills\u002Fprint\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: print\ndescription: Print a ScadBuddy output through Bambuddy - read the dialog's choices, pick a spool per slot, the nozzle size, quality and plate, options and project, run it with the user's approval, and follow its progress. Use when asked to print, send, queue or slice a generated model, or to explain why a print was refused or failed, and to link or dismiss the prints ScadBuddy did not start (Import print, the print watcher, Unsorted imports).\n---\n\n# Printing a ScadBuddy output through Bambuddy\n\nScadBuddy renders, and Bambuddy prints. Bambuddy owns printers, spools, presets,\nthe queue and projects. ScadBuddy \"stores no second copy of printer, spool,\npreset or project state\" and \"reimplements no decision Bambuddy already makes\"\n(`docs\u002Fsuperpowers\u002Fspecs\u002F2026-09-24-print-flow-design.md`, introduction). Follow\nthe same rule: report Bambuddy's answers, and don't second-guess them.\n\nSources, relative to the root of\n[eh-homelab\u002FScadBuddy](https:\u002F\u002Fgithub.com\u002Feh-homelab\u002FScadBuddy):\n\n- `docs\u002Fsuperpowers\u002Fspecs\u002F2026-09-27-spool-first-print-design.md` (\"spool-first\n  spec\"): §2 for the flow, §3 for what each step reads, §4 for how presets are\n  derived, §4.5 for errors versus warnings, §6 for what Bambuddy decides. It\n  supersedes the print-flow spec's §2 rule that a pipeline is never bypassed.\n- `docs\u002Fsuperpowers\u002Fspecs\u002F2026-09-24-print-flow-design.md` (\"print-flow spec\"):\n  §3 to §5 for filaments, §6 for progress, §7 for projects.\n- `docs\u002Fsuperpowers\u002Fspecs\u002F2026-09-27-ai-integration-design.md` (\"AI spec\"): §8 for\n  tiers and approvals, §11 for analyzers.\n- `docs\u002Fsuperpowers\u002Fspecs\u002F2026-09-22-scadbuddy-design.md` (\"main spec\"): §7 for\n  Bambuddy integration and extruder order.\n- `backend\u002Fopenapi.json` for every route named below (all under `\u002Fapi\u002Fv1`).\n\nThe ScadBuddy MCP tools arrive with issue #251. A print tool wraps the run\nbehind a single approval (AI spec §5.1): read the choices, then run with them.\nThe routes below are what it calls. Use the tool when you have it. There is no\npipeline or eligibility step in the print dialog any more (spool-first spec §0).\nA file already in Bambuddy's library (#313) prints the same way as an output; only\nthe 3MF it slices differs (#1749). The `\u002Fapi\u002Fv1\u002Fprint\u002Flibrary\u002F{file_id}\u002F…` routes\nmirror the output ones, and every print tool takes `library_file_id` (a file from\n`GET \u002Fapi\u002Fv1\u002Fprint\u002Flibrary`, the `list_library` tool) in place of `output_id`\n(#1756).\n\n## Approvals come first\n\nSending, printing and deleting are `outward`. **Outward actions always need a\nhuman approval in the ScadBuddy UI, in every auth mode**, including `disabled`\n(AI spec §8.1 and §8.2).\n\n- In the in-app harness, the session waits in `waiting_approval` while the UI\n  shows a confirmation card (AI spec §8.2).\n- Over `\u002Fmcp` (external clients such as Claude Code), an outward tool is two\n  steps. `prepare` returns a pending action id and a summary. `confirm` completes\n  only after the user approves in the UI (AI spec §8.2).\n\nSo before you prepare a print, tell the user what will happen: which printer, how\nmany copies, the spool for each slot, the nozzle size, quality and plate, and any\nwarnings (§3 below). Never\nsay a print started until progress (§6 below) says so. Don't retry a denied\naction with different wording.\n\n## 1. Start from an output\n\nYou print an **output**, which is a render kept with Generate\n(`POST \u002Fapi\u002Fv1\u002Fmodels\u002F{slug}\u002Foutputs`, main spec §8). If there isn't one yet, use\nthe `customize` skill first. `GET \u002Fapi\u002Fv1\u002Foutputs\u002F{output_id}\u002Fplates` lists its\nplates, and ScadBuddy's own renders always have one plate (`backend\u002Fopenapi.json`,\nthat route's description).\n\n### Printers and their paths\n\nScadBuddy keeps a printer registry, one row per physical printer keyed by its\nserial (`backend\u002Fscadbuddy\u002Fapi\u002Fprinters.py`; plan\n`docs\u002Fsuperpowers\u002Fplans\u002F2026-10-16-printer-identity-native-path.md`). A row links\nthe Bambuddy printer it is, a LAN connection, or both, and `preferred_path` says\nhow a print reaches it: `native` over the LAN, `bambuddy` through Bambuddy, `auto`\nthe LAN when it answers. `list_printers` and `discover_printers` read it. No tool\nlinks a printer over the LAN: its access code is a device credential, typed\nonly in Settings > Printers (`PUT \u002Fapi\u002Fv1\u002Fprinters\u002F{printer_id}\u002Flan` is listed as\nnot a tool in `agent\u002Fsrc\u002Ftools\u002Fcoverage.ts`). Send the user there, or open it with\n`browser_navigate` to `\u002Fsettings\u002Fprinting#printers`, and never ask for the code in chat.\n`print_output` takes a registry `printer` (its `id`) in place of\n`printer_id`: the run prints on the Bambuddy printer the row links and is\nrecorded with the row. Sent together, `printer_id` decides: a row merged away or\nunlinked since falls back to its row, and only a row that links another Bambuddy\nprinter now is refused (`backend\u002Fscadbuddy\u002Fbambuddy\u002Fprint_run.py` `_named_printer`). A row that\nlinks no Bambuddy printer prints over the LAN, as the browser's print dialog prints\nit (#4646, `agent\u002Fsrc\u002Ftools\u002Fprint.ts` `printerOf`): name it only by `printer`, with no\n`printer_id`. Whether a run goes over the LAN is the server's call\n(`backend\u002Fscadbuddy\u002Fprinters\u002Fhot_path.py` `hot_path_native`), which the choices report\nas `lan_printers` when read with `printer`. On such a run `get_print_choices` and\n`get_print_filaments` (with `printer`) offer the printer's loaded trays as the spools,\neach under a negative `spool_id` (`backend\u002Fscadbuddy\u002Fbambuddy\u002Ftrays.py`\n`tray_spool_id`) that `filament_plan` takes; there is no project (a `project_id` is\nrefused; `folder_id` names one of ScadBuddy's own folders, `list_print_projects` with\n`native`) and nothing is queued on Bambuddy. `get_printers_now` lists both\nids and says which link answered (`path`).\n\n## 2. Assemble the request\n\nThe print dialog reads everything it offers in one call,\n`GET \u002Fapi\u002Fv1\u002Fprint\u002Foutputs\u002F{output_id}\u002Fchoices?printer_id=` (`ChoicesView` in\n`backend\u002Fopenapi.json`; spool-first spec §3): the printers, the installed nozzles\nand the four nozzle sizes, the quality tiers and processes for the size, the\nplates with the one the printer's last print used, the model's remembered\nchoices, and the filament step (slots, spools and a suggestion).\n\nThe run body is `PrintRunRequest` in `backend\u002Fopenapi.json`: `printer_id`,\n`filament_plan`, `choices`, `plate_id` \u002F `all_plates`, `options`, `project_id`\nand `copies`. `choices` is `PrintChoices`: `nozzles` (one size for the job),\n`tier` (`fine` \u002F `standard` \u002F `draft`) or a `process_name`, `bed_type`, and any\nper-slot `filament_overrides` (spool-first spec §2).\n\n| Step | Read with | Notes |\n|---|---|---|\n| Everything above | `GET \u002Fapi\u002Fv1\u002Fprint\u002Foutputs\u002F{output_id}\u002Fchoices?printer_id=` | One read for the whole dialog (spool-first spec §3). |\n| Filaments | `GET \u002Fapi\u002Fv1\u002Fprint\u002Foutputs\u002F{output_id}\u002Ffilaments?printer_id=&plate_id=` | The plate's slots and the whole spool inventory, already joined (print-flow spec §3). `all_plates=true` answers for every plate at once. |\n| Plate | `choices.bed_type`, `plate_id` \u002F `all_plates` | Preselected from the printer's last print, then the plate remembered with `PUT \u002Fapi\u002Fv1\u002Fprint\u002Fprinters\u002F{printer_id}\u002Fbed-type` (spool-first spec §4.4). |\n| Remembered choices | `PUT \u002Fapi\u002Fv1\u002Fprint\u002Fmodels\u002F{slug}\u002Fchoices` | The printer and spools last chosen for this model (`backend\u002Fopenapi.json`). |\n| Options | `GET \u002Fapi\u002Fv1\u002Fsettings\u002Fprint-options` | The sparse `PrintOptions` overlay (#88; `backend\u002Fopenapi.json`, `PrintOptions`). |\n| Project | `GET \u002Fapi\u002Fv1\u002Fprint\u002Fprojects` | Bambuddy's projects, with their library folders (print-flow spec §7). |\n\n### The filament plan\n\nA `FilamentPlan` is one chosen spool per plate slot (print-flow spec §1). Slot\norder is extruder order, which is the order of the model's colour parameters\n(main spec §7).\n\n- The route's opening selection matches the same material first, then the\n  nearest colour, preferring loaded spools and never offering one spool twice\n  (print-flow spec §5). Present it as a suggestion. Every slot stays the user's\n  choice.\n- **Traps in the data** (print-flow spec §3):\n  - `used_grams: 0` means *unknown*, not zero.\n  - `remain: -1` means *unknown*, not empty.\n  - `\u002Finventory\u002Fassignments` covers every printer, but `inventory-remain` covers\n    one. The route does this join for you, so don't redo it.\n- **The only warnings** (print-flow spec §4). None of them blocks a run:\n  1. The spool isn't loaded: name where it is (`storage_location`, or the other\n     printer).\n  2. Not enough filament: `remaining_g \u003C used_grams × copies`, and only when the\n     grams are known.\n  3. A slot has nothing chosen.\n- ScadBuddy sends **no `ams_mapping`**. Bambuddy's scheduler computes it against\n  the printer it actually dispatches to (print-flow spec §4). Don't invent one.\n\n## 3. The run: slice, then queue\n\nThere is one submit, `POST \u002Fapi\u002Fv1\u002Fprint\u002Foutputs\u002F{output_id}\u002Frun`. ScadBuddy\nderives the printer, process and per-slot filament presets from `choices` and the\nchosen spools (spool-first spec §4), slices through Bambuddy, waits for the slice\njob, then `POST \u002Fqueue\u002F` on the one printer the dialog is scoped to. No pipeline\nruns on this path.\n\nThe route answers **202** with a `PrintRun` (`status: \"running\"`) and slices and\nqueues in the background, because the slices outlast the proxies in front.\nFollow `GET \u002Fapi\u002Fv1\u002Fprint\u002Fruns\u002F{run_id}` until `status` is `succeeded` (its\n`result` is the `PrintRunResult` below) or `failed` (its `error` carries the\n`type`, `status` and `detail` of the refusal). The body's optional `request_id`\nnames one deliberate print: send a new one per print and the same one on a\nretry of it. The same request (same `request_id`) for the same output again\nanswers **200** with that run (`repeated: true`) while it is in flight, or for\nten minutes after it succeeded or failed with `may_have_queued: true`, and queues\nnothing more; a failed run that never tried to queue holds nothing, so repeating\nit tries again. A new `request_id` with\nthe same choices is a new print (`backend\u002Fopenapi.json`; #470). `print_output`\nmakes a new one per call, and re-sends that call's POST with the same id when no\nanswer from ScadBuddy arrived. If it still reports no answer, or names a run it\nstarted but could not read, follow that run or check Bambuddy's queue rather\nthan calling `print_output` again. A `failed` run with `may_have_queued: true` had already\ntried to queue (a queue call that timed out, or a later plate failing after an\nearlier one was queued): tell the user to check Bambuddy's queue, and do not\nprint again until they have, since another print would be a second one.\n\n- **Errors** are a 422 before anything is sliced, and name the slot or setting:\n  mixed nozzle sizes, or a slot with no filament preset for the nozzle\n  (spool-first spec §4.5). A slot error needs the uploaded file, so it arrives\n  as the run's `failed` `error` with that 422, not as the POST's answer.\n- **Warnings** come back in the result and never block: spool not loaded, nozzle\n  not installed, a nozzle of the chosen size mounted in the other flow on a\n  side the slice may use (`hf-mounted`, #797), a Generic filament preset\n  fallback, or a plate that differs from the last print (spool-first spec\n  §4.3, §4.5). An output's flow (Standard or High Flow) is sliced as chosen\n  for each side (#484), so choosing the mounted nozzle's flow for its side\n  avoids `hf-mounted`. When both sides could print their chosen flows and\n  those differ, the print goes to the High Flow side. A library file that\n  Bambuddy slices (an unsliced 3MF) is sliced as chosen too: with High Flow\n  chosen, the slicer gets a copy of it, uploaded to the library folder, that\n  states each side's flow; the file itself is never changed. A sliced file,\n  an STL or a 3MF from another slicer prints as it is, taken as Standard\n  whatever is chosen (#484).\n  Tell the user about the ones you can predict before they approve.\n\nWhich AMS tray and extruder each spool feeds, and which rack nozzle is used,\nstay Bambuddy's and the printer's decisions (spool-first spec §6). The run does\nnot check the chosen size against the mounted nozzles, so do not warn that a\nmulti-color print needs the size on both sides: a two-colour print sliced for\n0.2 mm printed through the one 0.2 mm nozzle (spool-first spec §4.3, #768).\n\nThe simpler **send** path, `POST \u002Fapi\u002Fv1\u002Foutputs\u002F{output_id}\u002Fsend` with\n`{mode: \"library\"}`, only uploads the 3MF to the library folder and attaches the\nedit link. It never slices or queues; `mode: \"queue\"` is refused with a 422\n(`backend\u002Fopenapi.json`, `SendRequest`; spool-first spec §0, the #312 note). To\nprint, use the run above. Sending is outward too.\n\n## 4. After the run: the result\n\nA `succeeded` run's `result`, a `PrintRunResult`, reports `route` (always `slice_queue`), `slice_job_id`,\n`queue_item_ids`, `library_file_id`, `copies`, `bambuddy_url` and `warnings`\n(`backend\u002Fopenapi.json`). Give the user the `bambuddy_url` and every warning.\nA run that went over the LAN has `path: \"native\"` and no queue item or Bambuddy URL\n(`PrintRunResult.path` and `lan` in `backend\u002Fscadbuddy\u002Fbambuddy\u002Fprint_run.py`):\n`print_output` and `get_print_run` answer with a `follow` handle instead, the\n`get_print_progress` call that follows it and each plate's `subtask_name`\n(`agent\u002Fsrc\u002Ftools\u002Fprint.ts` `followed`).\n\n## 5. Projects\n\nA project is Bambuddy's (print-flow spec §7). `POST \u002Fapi\u002Fv1\u002Fprint\u002Fprojects`\ncreates one, or links an existing one, together with its library folder. Attaching\nqueue entries and archives is a separate call,\n`POST \u002Fapi\u002Fv1\u002Fprint\u002Foutputs\u002F{output_id}\u002Fproject`. Call it once the ids exist:\nqueue entries appear once a plate is queued, and archives only\nafter the print finishes. Calling it again later is how archives land on the\nproject (print-flow spec §7). The project routes need Bambuddy's **Manage\nProjects** scope, which the key may not have (print-flow spec §7).\n\n## 6. Follow progress\n\n`GET \u002Fapi\u002Fv1\u002Fprint\u002Foutputs\u002F{output_id}\u002Fprogress` follows whichever route ran\n(print-flow spec §6; `backend\u002Fopenapi.json`, `PrintProgress`):\n\n- `null` means the output was never printed. That is an answer, not an error.\n- `settled` says when to stop. An all-plates print reads \"Slicing…\" until one of\n  its plates has a queue entry, and a plate can fail before it is ever queued.\n- Show Bambuddy's `error_message` **word for word**, next to the `fix` the route\n  suggests (change the mapping, retry). Don't paraphrase it\n  (print-flow spec §6).\n\n## 7. Errors that name a scope\n\nEvery Bambuddy call declares the API-key scope it needs, so a 401 or 403 names\nthe missing scope (`CLAUDE.md`, section \"Bambuddy iframe facts\";\n`backend\u002Fscadbuddy\u002Fbambuddy\u002Ferrors.py`). Sending needs **Manage Library**,\nprinting also needs **Manage Queue**, and listing printers needs **Read Status**\n(main spec §7).\nTell the user which scope to add to the key in Bambuddy. The key itself never\nleaves the server (`CLAUDE.md`, section \"Bambuddy iframe facts\").\n\n## 8. Print analyzers (coming with #284)\n\nAnalyzers inspect a print before it runs and propose **diffs against the base\nrequest** that this flow already builds. They never propose a profile of their\nown (AI spec §11; issue #284). The run already slices then queues, so an\naccepted diff lands on that same request:\n\n1. Filament-level settings go in `filament_overrides` on the queue item.\n2. Process-level settings become a derived local preset.\n3. The 3MF's `project_settings.config` is used only if it is shown to beat the\n   resolved process preset. Main spec §3 measured the preset winning.\n\nEach of these is on AI spec §3.2's \"to verify\" list, so don't rely on any of them\nuntil a PR verifies it. Analyzer sessions can read and propose, but they can't\nsend or print (issue #284, \"Agent-mode analyzers\"). Every proposed value needs a\nsource. A value without one is the analyzer's judgement, and is never applied\nautomatically (AI spec §2, D10).\n\n## 9. Prints ScadBuddy did not start\n\nImport print (#4698) links such a print to a model by hand, and the print watcher\n(#4699) does it with no user step (`README.md`, section \"The print watcher (#4699)\").\nThe tools are in `agent\u002Fsrc\u002Ftools\u002Fprints.ts`.\n\n- The watcher is off by default. Only a person switches it on or changes it, in\n  Settings → Printing; the API refuses an agent with 403 `person_only`\n  (`backend\u002Fscadbuddy\u002Fapi\u002Fsettings.py` `PRINT_WATCH`). `get_settings` reads it.\n- It links a print to a model only when earlier imports of the same file name one\n  model, or the job's name has exactly one model's words. Every other print goes to\n  Unsorted imports, with a `reason` and suggested models\n  (`backend\u002Fscadbuddy\u002Fprint_watch\u002Fsweep.py`, module docstring step 3).\n- For a print Bambuddy archived: `list_auto_imports` (`state: inbox` is Unsorted\n  imports). To link one, show the user the suggestions, let them choose, then\n  `get_print_sources` and `import_print`. To take one out of the inbox,\n  `dismiss_auto_import`, only when the user says it is not worth keeping.\n- For a print on a LAN-only printer (no Bambuddy link, so no archive):\n  `list_lan_auto_imports`, `link_lan_auto_import` (never `import_print`) and\n  `dismiss_lan_auto_import`. A linked LAN-only print is not in `list_prints` or on the\n  model's Prints tab; it is in Activity (`backend\u002FCLAUDE.md`, the print watcher's\n  phase 4 paragraph).\n","# Printing a ScadBuddy output through Bambuddy\n\nScadBuddy renders, and Bambuddy prints. Bambuddy owns printers, spools, presets,\nthe queue and projects. ScadBuddy \"stores no second copy of printer, spool,\npreset or project state\" and \"reimplements no decision Bambuddy already makes\"\n(`docs\u002Fsuperpowers\u002Fspecs\u002F2026-09-24-print-flow-design.md`, introduction). Follow\nthe same rule: report Bambuddy's answers, and don't second-guess them.\n\nSources, relative to the root of\n[eh-homelab\u002FScadBuddy](https:\u002F\u002Fgithub.com\u002Feh-homelab\u002FScadBuddy):\n\n- `docs\u002Fsuperpowers\u002Fspecs\u002F2026-09-27-spool-first-print-design.md` (\"spool-first\n  spec\"): §2 for the flow, §3 for what each step reads, §4 for how presets are\n  derived, §4.5 for errors versus warnings, §6 for what Bambuddy decides. It\n  supersedes the print-flow spec's §2 rule that a pipeline is never bypassed.\n- `docs\u002Fsuperpowers\u002Fspecs\u002F2026-09-24-print-flow-design.md` (\"print-flow spec\"):\n  §3 to §5 for filaments, §6 for progress, §7 for projects.\n- `docs\u002Fsuperpowers\u002Fspecs\u002F2026-09-27-ai-integration-design.md` (\"AI spec\"): §8 for\n  tiers and approvals, §11 for analyzers.\n- `docs\u002Fsuperpowers\u002Fspecs\u002F2026-09-22-scadbuddy-design.md` (\"main spec\"): §7 for\n  Bambuddy integration and extruder order.\n- `backend\u002Fopenapi.json` for every route named below (all under `\u002Fapi\u002Fv1`).\n\nThe ScadBuddy MCP tools arrive with issue #251. A print tool wraps the run\nbehind a single approval (AI spec §5.1): read the choices, then run with them.\nThe routes below are what it calls. Use the tool when you have it. There is no\npipeline or eligibility step in the print dialog any more (spool-first spec §0).\nA file already in Bambuddy's library (#313) prints the same way as an output; only\nthe 3MF it slices differs (#1749). The `\u002Fapi\u002Fv1\u002Fprint\u002Flibrary\u002F{file_id}\u002F…` routes\nmirror the output ones, and every print tool takes `library_file_id` (a file from\n`GET \u002Fapi\u002Fv1\u002Fprint\u002Flibrary`, the `list_library` tool) in place of `output_id`\n(#1756).\n\n## Approvals come first\n\nSending, printing and deleting are `outward`. **Outward actions always need a\nhuman approval in the ScadBuddy UI, in every auth mode**, including `disabled`\n(AI spec §8.1 and §8.2).\n\n- In the in-app harness, the session waits in `waiting_approval` while the UI\n  shows a confirmation card (AI spec §8.2).\n- Over `\u002Fmcp` (external clients such as Claude Code), an outward tool is two\n  steps. `prepare` returns a pending action id and a summary. `confirm` completes\n  only after the user approves in the UI (AI spec §8.2).\n\nSo before you prepare a print, tell the user what will happen: which printer, how\nmany copies, the spool for each slot, the nozzle size, quality and plate, and any\nwarnings (§3 below). Never\nsay a print started until progress (§6 below) says so. Don't retry a denied\naction with different wording.\n\n## 1. Start from an output\n\nYou print an **output**, which is a render kept with Generate\n(`POST \u002Fapi\u002Fv1\u002Fmodels\u002F{slug}\u002Foutputs`, main spec §8). If there isn't one yet, use\nthe `customize` skill first. `GET \u002Fapi\u002Fv1\u002Foutputs\u002F{output_id}\u002Fplates` lists its\nplates, and ScadBuddy's own renders always have one plate (`backend\u002Fopenapi.json`,\nthat route's description).\n\n### Printers and their paths\n\nScadBuddy keeps a printer registry, one row per physical printer keyed by its\nserial (`backend\u002Fscadbuddy\u002Fapi\u002Fprinters.py`; plan\n`docs\u002Fsuperpowers\u002Fplans\u002F2026-10-16-printer-identity-native-path.md`). A row links\nthe Bambuddy printer it is, a LAN connection, or both, and `preferred_path` says\nhow a print reaches it: `native` over the LAN, `bambuddy` through Bambuddy, `auto`\nthe LAN when it answers. `list_printers` and `discover_printers` read it. No tool\nlinks a printer over the LAN: its access code is a device credential, typed\nonly in Settings > Printers (`PUT \u002Fapi\u002Fv1\u002Fprinters\u002F{printer_id}\u002Flan` is listed as\nnot a tool in `agent\u002Fsrc\u002Ftools\u002Fcoverage.ts`). Send the user there, or open it with\n`browser_navigate` to `\u002Fsettings\u002Fprinting#printers`, and never ask for the code in chat.\n`print_output` takes a registry `printer` (its `id`) in place of\n`printer_id`: the run prints on the Bambuddy printer the row links and is\nrecorded with the row. Sent together, `printer_id` decides: a row merged away or\nunlinked since falls back to its row, and only a row that links another Bambuddy\nprinter now is refused (`backend\u002Fscadbuddy\u002Fbambuddy\u002Fprint_run.py` `_named_printer`). A row that\nlinks no Bambuddy printer prints over the LAN, as the browser's print dialog prints\nit (#4646, `agent\u002Fsrc\u002Ftools\u002Fprint.ts` `printerOf`): name it only by `printer`, with no\n`printer_id`. Whether a run goes over the LAN is the server's call\n(`backend\u002Fscadbuddy\u002Fprinters\u002Fhot_path.py` `hot_path_native`), which the choices report\nas `lan_printers` when read with `printer`. On such a run `get_print_choices` and\n`get_print_filaments` (with `printer`) offer the printer's loaded trays as the spools,\neach under a negative `spool_id` (`backend\u002Fscadbuddy\u002Fbambuddy\u002Ftrays.py`\n`tray_spool_id`) that `filament_plan` takes; there is no project (a `project_id` is\nrefused; `folder_id` names one of ScadBuddy's own folders, `list_print_projects` with\n`native`) and nothing is queued on Bambuddy. `get_printers_now` lists both\nids and says which link answered (`path`).\n\n## 2. Assemble the request\n\nThe print dialog reads everything it offers in one call,\n`GET \u002Fapi\u002Fv1\u002Fprint\u002Foutputs\u002F{output_id}\u002Fchoices?printer_id=` (`ChoicesView` in\n`backend\u002Fopenapi.json`; spool-first spec §3): the printers, the installed nozzles\nand the four nozzle sizes, the quality tiers and processes for the size, the\nplates with the one the printer's last print used, the model's remembered\nchoices, and the filament step (slots, spools and a suggestion).\n\nThe run body is `PrintRunRequest` in `backend\u002Fopenapi.json`: `printer_id`,\n`filament_plan`, `choices`, `plate_id` \u002F `all_plates`, `options`, `project_id`\nand `copies`. `choices` is `PrintChoices`: `nozzles` (one size for the job),\n`tier` (`fine` \u002F `standard` \u002F `draft`) or a `process_name`, `bed_type`, and any\nper-slot `filament_overrides` (spool-first spec §2).\n\n| Step | Read with | Notes |\n|---|---|---|\n| Everything above | `GET \u002Fapi\u002Fv1\u002Fprint\u002Foutputs\u002F{output_id}\u002Fchoices?printer_id=` | One read for the whole dialog (spool-first spec §3). |\n| Filaments | `GET \u002Fapi\u002Fv1\u002Fprint\u002Foutputs\u002F{output_id}\u002Ffilaments?printer_id=&plate_id=` | The plate's slots and the whole spool inventory, already joined (print-flow spec §3). `all_plates=true` answers for every plate at once. |\n| Plate | `choices.bed_type`, `plate_id` \u002F `all_plates` | Preselected from the printer's last print, then the plate remembered with `PUT \u002Fapi\u002Fv1\u002Fprint\u002Fprinters\u002F{printer_id}\u002Fbed-type` (spool-first spec §4.4). |\n| Remembered choices | `PUT \u002Fapi\u002Fv1\u002Fprint\u002Fmodels\u002F{slug}\u002Fchoices` | The printer and spools last chosen for this model (`backend\u002Fopenapi.json`). |\n| Options | `GET \u002Fapi\u002Fv1\u002Fsettings\u002Fprint-options` | The sparse `PrintOptions` overlay (#88; `backend\u002Fopenapi.json`, `PrintOptions`). |\n| Project | `GET \u002Fapi\u002Fv1\u002Fprint\u002Fprojects` | Bambuddy's projects, with their library folders (print-flow spec §7). |\n\n### The filament plan\n\nA `FilamentPlan` is one chosen spool per plate slot (print-flow spec §1). Slot\norder is extruder order, which is the order of the model's colour parameters\n(main spec §7).\n\n- The route's opening selection matches the same material first, then the\n  nearest colour, preferring loaded spools and never offering one spool twice\n  (print-flow spec §5). Present it as a suggestion. Every slot stays the user's\n  choice.\n- **Traps in the data** (print-flow spec §3):\n  - `used_grams: 0` means *unknown*, not zero.\n  - `remain: -1` means *unknown*, not empty.\n  - `\u002Finventory\u002Fassignments` covers every printer, but `inventory-remain` covers\n    one. The route does this join for you, so don't redo it.\n- **The only warnings** (print-flow spec §4). None of them blocks a run:\n  1. The spool isn't loaded: name where it is (`storage_location`, or the other\n     printer).\n  2. Not enough filament: `remaining_g \u003C used_grams × copies`, and only when the\n     grams are known.\n  3. A slot has nothing chosen.\n- ScadBuddy sends **no `ams_mapping`**. Bambuddy's scheduler computes it against\n  the printer it actually dispatches to (print-flow spec §4). Don't invent one.\n\n## 3. The run: slice, then queue\n\nThere is one submit, `POST \u002Fapi\u002Fv1\u002Fprint\u002Foutputs\u002F{output_id}\u002Frun`. ScadBuddy\nderives the printer, process and per-slot filament presets from `choices` and the\nchosen spools (spool-first spec §4), slices through Bambuddy, waits for the slice\njob, then `POST \u002Fqueue\u002F` on the one printer the dialog is scoped to. No pipeline\nruns on this path.\n\nThe route answers **202** with a `PrintRun` (`status: \"running\"`) and slices and\nqueues in the background, because the slices outlast the proxies in front.\nFollow `GET \u002Fapi\u002Fv1\u002Fprint\u002Fruns\u002F{run_id}` until `status` is `succeeded` (its\n`result` is the `PrintRunResult` below) or `failed` (its `error` carries the\n`type`, `status` and `detail` of the refusal). The body's optional `request_id`\nnames one deliberate print: send a new one per print and the same one on a\nretry of it. The same request (same `request_id`) for the same output again\nanswers **200** with that run (`repeated: true`) while it is in flight, or for\nten minutes after it succeeded or failed with `may_have_queued: true`, and queues\nnothing more; a failed run that never tried to queue holds nothing, so repeating\nit tries again. A new `request_id` with\nthe same choices is a new print (`backend\u002Fopenapi.json`; #470). `print_output`\nmakes a new one per call, and re-sends that call's POST with the same id when no\nanswer from ScadBuddy arrived. If it still reports no answer, or names a run it\nstarted but could not read, follow that run or check Bambuddy's queue rather\nthan calling `print_output` again. A `failed` run with `may_have_queued: true` had already\ntried to queue (a queue call that timed out, or a later plate failing after an\nearlier one was queued): tell the user to check Bambuddy's queue, and do not\nprint again until they have, since another print would be a second one.\n\n- **Errors** are a 422 before anything is sliced, and name the slot or setting:\n  mixed nozzle sizes, or a slot with no filament preset for the nozzle\n  (spool-first spec §4.5). A slot error needs the uploaded file, so it arrives\n  as the run's `failed` `error` with that 422, not as the POST's answer.\n- **Warnings** come back in the result and never block: spool not loaded, nozzle\n  not installed, a nozzle of the chosen size mounted in the other flow on a\n  side the slice may use (`hf-mounted`, #797), a Generic filament preset\n  fallback, or a plate that differs from the last print (spool-first spec\n  §4.3, §4.5). An output's flow (Standard or High Flow) is sliced as chosen\n  for each side (#484), so choosing the mounted nozzle's flow for its side\n  avoids `hf-mounted`. When both sides could print their chosen flows and\n  those differ, the print goes to the High Flow side. A library file that\n  Bambuddy slices (an unsliced 3MF) is sliced as chosen too: with High Flow\n  chosen, the slicer gets a copy of it, uploaded to the library folder, that\n  states each side's flow; the file itself is never changed. A sliced file,\n  an STL or a 3MF from another slicer prints as it is, taken as Standard\n  whatever is chosen (#484).\n  Tell the user about the ones you can predict before they approve.\n\nWhich AMS tray and extruder each spool feeds, and which rack nozzle is used,\nstay Bambuddy's and the printer's decisions (spool-first spec §6). The run does\nnot check the chosen size against the mounted nozzles, so do not warn that a\nmulti-color print needs the size on both sides: a two-colour print sliced for\n0.2 mm printed through the one 0.2 mm nozzle (spool-first spec §4.3, #768).\n\nThe simpler **send** path, `POST \u002Fapi\u002Fv1\u002Foutputs\u002F{output_id}\u002Fsend` with\n`{mode: \"library\"}`, only uploads the 3MF to the library folder and attaches the\nedit link. It never slices or queues; `mode: \"queue\"` is refused with a 422\n(`backend\u002Fopenapi.json`, `SendRequest`; spool-first spec §0, the #312 note). To\nprint, use the run above. Sending is outward too.\n\n## 4. After the run: the result\n\nA `succeeded` run's `result`, a `PrintRunResult`, reports `route` (always `slice_queue`), `slice_job_id`,\n`queue_item_ids`, `library_file_id`, `copies`, `bambuddy_url` and `warnings`\n(`backend\u002Fopenapi.json`). Give the user the `bambuddy_url` and every warning.\nA run that went over the LAN has `path: \"native\"` and no queue item or Bambuddy URL\n(`PrintRunResult.path` and `lan` in `backend\u002Fscadbuddy\u002Fbambuddy\u002Fprint_run.py`):\n`print_output` and `get_print_run` answer with a `follow` handle instead, the\n`get_print_progress` call that follows it and each plate's `subtask_name`\n(`agent\u002Fsrc\u002Ftools\u002Fprint.ts` `followed`).\n\n## 5. Projects\n\nA project is Bambuddy's (print-flow spec §7). `POST \u002Fapi\u002Fv1\u002Fprint\u002Fprojects`\ncreates one, or links an existing one, together with its library folder. Attaching\nqueue entries and archives is a separate call,\n`POST \u002Fapi\u002Fv1\u002Fprint\u002Foutputs\u002F{output_id}\u002Fproject`. Call it once the ids exist:\nqueue entries appear once a plate is queued, and archives only\nafter the print finishes. Calling it again later is how archives land on the\nproject (print-flow spec §7). The project routes need Bambuddy's **Manage\nProjects** scope, which the key may not have (print-flow spec §7).\n\n## 6. Follow progress\n\n`GET \u002Fapi\u002Fv1\u002Fprint\u002Foutputs\u002F{output_id}\u002Fprogress` follows whichever route ran\n(print-flow spec §6; `backend\u002Fopenapi.json`, `PrintProgress`):\n\n- `null` means the output was never printed. That is an answer, not an error.\n- `settled` says when to stop. An all-plates print reads \"Slicing…\" until one of\n  its plates has a queue entry, and a plate can fail before it is ever queued.\n- Show Bambuddy's `error_message` **word for word**, next to the `fix` the route\n  suggests (change the mapping, retry). Don't paraphrase it\n  (print-flow spec §6).\n\n## 7. Errors that name a scope\n\nEvery Bambuddy call declares the API-key scope it needs, so a 401 or 403 names\nthe missing scope (`CLAUDE.md`, section \"Bambuddy iframe facts\";\n`backend\u002Fscadbuddy\u002Fbambuddy\u002Ferrors.py`). Sending needs **Manage Library**,\nprinting also needs **Manage Queue**, and listing printers needs **Read Status**\n(main spec §7).\nTell the user which scope to add to the key in Bambuddy. The key itself never\nleaves the server (`CLAUDE.md`, section \"Bambuddy iframe facts\").\n\n## 8. Print analyzers (coming with #284)\n\nAnalyzers inspect a print before it runs and propose **diffs against the base\nrequest** that this flow already builds. They never propose a profile of their\nown (AI spec §11; issue #284). The run already slices then queues, so an\naccepted diff lands on that same request:\n\n1. Filament-level settings go in `filament_overrides` on the queue item.\n2. Process-level settings become a derived local preset.\n3. The 3MF's `project_settings.config` is used only if it is shown to beat the\n   resolved process preset. Main spec §3 measured the preset winning.\n\nEach of these is on AI spec §3.2's \"to verify\" list, so don't rely on any of them\nuntil a PR verifies it. Analyzer sessions can read and propose, but they can't\nsend or print (issue #284, \"Agent-mode analyzers\"). Every proposed value needs a\nsource. A value without one is the analyzer's judgement, and is never applied\nautomatically (AI spec §2, D10).\n\n## 9. Prints ScadBuddy did not start\n\nImport print (#4698) links such a print to a model by hand, and the print watcher\n(#4699) does it with no user step (`README.md`, section \"The print watcher (#4699)\").\nThe tools are in `agent\u002Fsrc\u002Ftools\u002Fprints.ts`.\n\n- The watcher is off by default. Only a person switches it on or changes it, in\n  Settings → Printing; the API refuses an agent with 403 `person_only`\n  (`backend\u002Fscadbuddy\u002Fapi\u002Fsettings.py` `PRINT_WATCH`). `get_settings` reads it.\n- It links a print to a model only when earlier imports of the same file name one\n  model, or the job's name has exactly one model's words. Every other print goes to\n  Unsorted imports, with a `reason` and suggested models\n  (`backend\u002Fscadbuddy\u002Fprint_watch\u002Fsweep.py`, module docstring step 3).\n- For a print Bambuddy archived: `list_auto_imports` (`state: inbox` is Unsorted\n  imports). To link one, show the user the suggestions, let them choose, then\n  `get_print_sources` and `import_print`. To take one out of the inbox,\n  `dismiss_auto_import`, only when the user says it is not worth keeping.\n- For a print on a LAN-only printer (no Bambuddy link, so no archive):\n  `list_lan_auto_imports`, `link_lan_auto_import` (never `import_print`) and\n  `dismiss_lan_auto_import`. A linked LAN-only print is not in `list_prints` or on the\n  model's Prints tab; it is in Activity (`backend\u002FCLAUDE.md`, the print watcher's\n  phase 4 paragraph).\n",{"name":5,"description":7},"main","255462a55f2ea83cfdaf8e90e7e856e2ea4e01e6","plugins\u002Fscadbuddy\u002Fskills\u002Fprint",0,"https:\u002F\u002Fgithub.com\u002Feh-homelab\u002FScadBuddy","https:\u002F\u002Fgithub.com\u002Feh-homelab","2026-11-15 06:30:12",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add eh-homelab\u002FScadBuddy --skill print",{"tool":36,"command":37},"bunx","bunx skills add eh-homelab\u002FScadBuddy --skill print",{"tool":39,"command":40},"pnpm","pnpm dlx skills add eh-homelab\u002FScadBuddy --skill print","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Feh-homelab\u002FScadBuddy\u002Fblob\u002Fmain\u002Fplugins\u002Fscadbuddy\u002Fskills\u002Fprint\u002FSKILL.md",true,[],[45,52,59,66,73,80],{"skillNo":46,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":49,"categories":50,"keywords":51,"publishedAt":18},"01M7E2YQKQGGZVCN7PK2RV8HPV","filament-intake","Use when adding purchased filament to the spool inventory from receipts or invoices (Bambu Lab, Best Buy, Micro Center, Amazon), when spool cost should include sales tax, when ScadBuddy's price book or job cost needs the new spool prices, when downloading or importing 3dfilamentprofiles.com slicer profiles, or when a spool needs per-nozzle presets for the H2C. Also when 3dfilamentprofiles answers 429 \"Vercel Security Checkpoint\", Micro Center answers 403, or a Bambu RFID spool duplicates a manually added one.","https:\u002F\u002Fgithub.com\u002Feh-homelab\u002FScadBuddy\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Ffilament-intake\u002FSKILL.md",[],[],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":18},"01M7D8ZX598J5NWYFJDDD453GR","customize","Drive the ScadBuddy customizer for a template - read its parameter schema and presets, choose values, render and inspect the preview, check the plate fit, and keep the result as an output. Use when asked to make, tweak or preview a customized model (a keychain with a name, a box of a given size) on a ScadBuddy instance.","https:\u002F\u002Fgithub.com\u002Feh-homelab\u002FScadBuddy\u002Fblob\u002Fmain\u002Fplugins\u002Fscadbuddy\u002Fskills\u002Fcustomize\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":18},"01M7D8ZMFA168DVQ1A7DSYAFF1","authoring","How to write and edit ScadBuddy OpenSCAD templates (model.scad) so the customizer, the per-colour print parts and the fonts come out right. Use when creating, editing, reviewing or debugging a .scad template for ScadBuddy, or when a render shows the wrong font, the wrong colours, open parts or unexpected parameters. Also covers FDM design rules (hole and fit clearance, wall thickness, overhangs, bridges) and OpenSCAD pitfalls (coincident faces, use vs include, leftover modifiers).","https:\u002F\u002Fgithub.com\u002Feh-homelab\u002FScadBuddy\u002Fblob\u002Fmain\u002Fplugins\u002Fscadbuddy\u002Fskills\u002Fauthoring\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":18},"01M7D8ZH2MFMCE60S9MD8XKFCZ","hello","Fixture skill for the plugin vetting tests.","https:\u002F\u002Fgithub.com\u002Feh-homelab\u002FScadBuddy\u002Fblob\u002Fmain\u002Fagent\u002Ftest\u002Ffixtures\u002Fplugins\u002Fclean\u002Fskills\u002Fhello\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":18},"01M7D8Z9GM7Y3XECZTJ9H9Y1A0","scadbuddy-run-forensics","Find out what a ScadBuddy print, slice or order operation actually did by reading its Temporal workflow history, instead of trusting the HTTP reply or the run record. Answers whether a run whose reply was lost reached the printer, which sliced library file it produced, why an activity failed (ERROR STATE refusal, heartbeat timeout on the sliced upload, workflow task timeouts, \"no spool chosen\"), and which spools and trays a LAN send used. Use it whenever a ScadBuddy MCP call times out or its transport drops, the API answers HTTP 500 \"Workflow Task in failed state\" or \"did not answer\", get_print_progress reads null while the printer is clearly busy, or before resending any print, and for any \"did it actually go\", \"what happened to my run\", \"which file did it make\" question.","https:\u002F\u002Fgithub.com\u002Feh-homelab\u002FScadBuddy\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fscadbuddy-run-forensics\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":18},"01M7D8YZWP4KS7TGTKSXK5XTMA","h2c-print-from-scadbuddy","Print a ScadBuddy output or library file on the Bambu H2C (Bambuddy printer 1, \"3DP-31B-598\") and see it through to a cleared bed. Covers the LAN print_output recipe with negative tray ids, the Bambuddy-queue route for when bed levelling, flow dynamics, nozzle offset or vibration calibration must be forced on, verifying the AMS mapping over MQTT, watching progress, plate-clear holds between plates, stopping and restarting, and what to do when the reply is lost, the printer answers ERROR STATE, or progress reads null. Use this whenever the user says print, send it, reprint, queue it in Bambuddy, stop it, \"is it done\", \"is it mapped\", \"turn on flow calibration\", or asks why a ScadBuddy print did not start, even when they do not name the H2C or ScadBuddy.","https:\u002F\u002Fgithub.com\u002Feh-homelab\u002FScadBuddy\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fh2c-print-from-scadbuddy\u002FSKILL.md",[],[]]