Update to BOLDR MAX

{
  "description": "Produce a jobsite status report for a BOLDR project — per-job progress, out-of-tolerance measurements, and recent activity — ready to paste into a standup or email.",
  "included_files": [],
  "name": "jobsite-status",
  "skill_md_contents": "---\nname: jobsite-status\ndescription: Produce a jobsite status report for a BOLDR project — per-job progress, out-of-tolerance measurements, and recent activity — ready to paste into a standup or email.\n---\n\n# Jobsite status report\n\nUse this when the user asks how a project or job is going, what's left, or\nwhat's out of spec.\n\n1. If the user didn't name a project, call `list_projects` and ask which one\n   (or pick the obvious match from their words).\n2. Call `get_project_progress` for the roll-up, then `list_jobs` for per-job\n   completion fractions.\n3. For each active job the user cares about (or the 2–3 least complete),\n   call `find_out_of_tolerance` and `get_job_progress`.\n4. Report, in this order: overall project completion, per-job completion,\n   then out-of-tolerance items as \"group → column: measured X vs target Y\n   (band min–max)\" using the values exactly as the tools format them —\n   never convert units yourself; pass the user's preferred `unit` to the\n   tools instead.\n5. If the user wants the full table, call `export_job_csv` and provide the\n   CSV rather than re-typing values.\n\nKeep the report short: lead with the one number they asked for, then the\nexceptions. Offer the CSV export instead of pasting large tables.\n"
}