Update to Yoro Manufacturing Tracker

{
  "description": "Explore what a maker can produce using Yoro stock and saved recipes or bills of materials, compare hypothetical batch sizes, and calculate material needs, shortages or receipt-based material-cost estimates without saving. Check whether the user's current Yoro plan permits recording another batch or recipe. Generic recipes or manufacturing advice do not require Yoro.",
  "included_files": [],
  "name": "yoro-planning",
  "skill_md_contents": "---\nname: yoro-planning\ndescription: Explore what a maker can produce using Yoro stock and saved recipes or bills of materials, compare hypothetical batch sizes, and calculate material needs, shortages or receipt-based material-cost estimates without saving. Check whether the user's current Yoro plan permits recording another batch or recipe. Generic recipes or manufacturing advice do not require Yoro.\n---\n\nUse Yoro as a source of recorded production facts while helping the user explore ideas. Read relevant stock and saved versions when needed. `check_production` checks a saved version; `simulate_production` can use a saved version or an inline proposed definition containing known items. Both leave stock unchanged and reserve nothing. New item ideas can remain drafts in conversation without creating records.\n\nChatGPT may brainstorm, calculate, compare, and combine Yoro information with other authorized data sources. Keep external demand, accounting, supplier information, and assumptions attributed to their sources. Reconcile mismatched units or timestamps before treating figures as comparable. A conversational calculation may answer a question even when there is no dedicated Yoro tool; label estimates and explain material assumptions.\n\nYoro simulation returns material requirements, shortages, expected products, projected stock and receipt-based material-cost estimates. Its method is latest_costed_receipt: for each required input, use the latest non-reversed costed receipt by business date, then recording time and ID. Costs use normalized base quantities and the requested scale. Explain the source receipt, date, quantity and explicit currency. Evidence older than 90 days, a newer uncosted receipt and missing evidence are flagged. Stale evidence remains included; missing evidence is not zero. Partial subtotals are not a complete batch cost. Mixed currencies have separate subtotals and no single money total or FX conversion. These estimates exclude labour and overhead and are not inventory valuation, COGS or finished-product unit costs. For desired quantities, use `plan_production` with a saved version, selected output and target quantity/unit. Exact is the default; select round_down or round_up only when authorized. max_stock returns the largest run supported by gross input stock, including all coproduct increments. Preserve returned fractional scales unchanged. The nested simulation includes required inputs, shortages, projected balances and cost evidence. Impossible exact targets return adjacent alternatives, not a silently rounded plan. No positive capacity is reported explicitly. Combined schedules remain outside this primitive. External-cost calculations remain separately attributed conversational estimates.\n\n“What if”, “draft”, “try 200”, and substitution ideas authorize exploration. They do not authorize saved recipe versions or production events. When the user asks to preserve a definition or record real work, use the recording workflow. Known conversions and actual stock remain constraints on Yoro operations, not on discussing alternatives.\n\nFor questions about the user's current Yoro plan or whether it permits another batch or recipe, `get_usage` provides the effective plan, usage, remaining capacity, and batch reset time. Describe only the relevant returned facts. A positive remaining count means capacity was available at that snapshot; saving rechecks it. Recipe and item caps do not reset each month. `enforced:false` with a null plan means limits are disabled, not a known paid subscription.\n\nFree's batch period is a UTC calendar month; Maker and Maker Plus use their native Clerk paid periods. Active items and recipes count toward capacity. Archiving frees a slot; after a downgrade the owner may need to choose an active set before new production. New production uses the latest recipe version; all saved versions remain available for simulations and history. Exact reset instants may be displayed in the returned `profileTimezone`, which is a read-only display preference.\n\nProduction write limits do not prevent ordinary simulation, access to history, or conversational analysis. A preview of proposed writes can encounter the same write quotas as saving; disclose that rejection without promoting subscriptions or sending the user to checkout.\n\nRead [operation details](../yoro-production/references/operations.md) if precise conversion, version, lot, or preview semantics are needed.\n"
}