Update to Stratta

{
  "description": "Draft the project basis (base du projet, Projektbasis) required by SIA 260 clause 2.5 from a Stratta dossier and its site sheet, chapter by chapter, every statement traced to a decision, a site fact or a clause, every gap written as a gap. Trigger phrases: \"redige la base du projet\", \"base du projet\", \"Projektbasis\", \"project basis\".",
  "included_files": [],
  "name": "project-basis",
  "skill_md_contents": "---\nname: project-basis\ndescription: Draft the project basis (base du projet, Projektbasis) required by SIA 260 clause 2.5 from a Stratta dossier and its site sheet, chapter by chapter, every statement traced to a decision, a site fact or a clause, every gap written as a gap. Trigger phrases: \"redige la base du projet\", \"base du projet\", \"Projektbasis\", \"project basis\".\n---\n\n# Project basis (SIA 260 clause 2.5)\n\nUse this skill when the user asks for the project basis of a structure, in any of its\nnames: base du projet, Projektbasis, project basis. The document states the conditions the\ndesign rests on: the site, the actions, the retained values and the norms. Stratta holds\nmost of that matter already; the skill assembles it and shows what is missing.\n\nDo not use it for the use agreement (convention d'utilisation, clause 2.2): that is the\n`use-agreement` skill. Do not use it to decide anything: a gap stays a gap.\n\n## Before writing\n\n1. `list_skills`: if the office wrote its own `project-basis`, that version replaces this\n   one entirely. Read it with `get_skill` and follow it.\n2. `list_dossiers` then `load_dossier` on the project. Read its decisions and its open\n   questions; `get_question` on any decision whose clause you need in full.\n3. `get_site_context` on the dossier's site when it has one (`siteId` in `load_dossier`),\n   then `get_boreholes` when the terrain chapter needs them.\n4. `get_toc(\"SIA 260\", maxDepth: 2)` and read the clause on the project basis with\n   `get_section` when the corpus holds SIA 260. If it does not, say so once at the top of\n   the document and keep the chapter plan below.\n\n## How to write it\n\nThe document lives in Stratta, not in the conversation:\n\n1. `draft_deliverable` with the dossier id and `kind: \"project_basis\"`. It returns the\n   plan (the office template when one was validated, otherwise the plan below), the\n   decisions of the dossier with their entry ids, the open questions and the site id.\n   Calling it twice returns the same document.\n2. For each section of the plan, `write_section` with the text and its sources. Every\n   sentence of substance rests on one of:\n   - a decision or piece of evidence: `{kind: \"entry\", ref: \"<entryId>\"}`;\n   - a site fact: `{kind: \"fact\", ref: \"groundwater.level\"}`;\n   - a clause you read in this conversation: `{kind: \"clause\", ref: \"SIA 261 s. 16.2.1\"}`;\n   - a page of an attachment: `{kind: \"attachment\", ref: \"<id>#p12\"}`.\n     A section with no source is refused. When the dossier holds nothing for a section,\n     call `write_section` with `gap: true` and a body that says what is missing and who\n     can supply it.\n3. Tell the user the document is on the dossier page, under Livrables, where they read\n   it section by section, correct, and export it to Word. Do not paste the whole\n   document in the conversation; summarise what was written and list the gaps.\n\n## The plan\n\nUnless the office's own skill says otherwise:\n\n1. **Objet et situation**: the structure, the address, the parcel, the mandate.\n2. **Terrain de fondation**: one paragraph per site topic (geology, groundwater, hazards,\n   contamination, protection sectors, boreholes), built with the `site-chapter` skill's\n   rules: an `established` fact is a statement with its source and date; an `indicative`\n   fact is written as `[A confirmer : ...]`; an `uncovered` topic is `[A etablir : ...]`.\n3. **Actions**: seismic zone and ground class, snow, wind, from the site facts that carry\n   a SIA 261 clause; each value with its clause and page.\n4. **Hypotheses et valeurs retenues**: one line per decision of the dossier: the value,\n   its confidence (established, judgement, to confirm), the clause it rests on.\n5. **Bases normatives**: the norms and editions cited in the dossier, one line each.\n6. **Points ouverts**: the open questions, with their due date and assignee when set.\n\nThe text of a section is plain prose: the sources go in the `sources` argument, not in\nthe text. Stratta prints them under each section.\n\n## Rules\n\n- Write nothing the dossier, the site sheet or a clause you read does not carry. A\n  plausible sentence with no source is the one mistake this document cannot afford.\n- A value retained by judgement stays a judgement in the text; do not upgrade it.\n- A site fact is a register's answer, not a design value: it goes in chapter 2 or 3 with\n  its source, and the retained value goes in chapter 4 only if the dossier decided it.\n- Do not conclude that the structure complies, and do not write a decision the user has\n  not confirmed.\n- Stratta prints the closing sentence (\"Document prepare par un agent...\") and the\n  signature belongs to the engineer, on the dossier page. Do not sign anything.\n\n## After drafting\n\nList the gaps in one short table (chapter, what is missing, which tool or which person can\nfill it), and ask which one to settle first. A gap settled later is written with\n`write_section` on the same path; the document keeps its version history.\n\nWhen the user comes back and `draft_deliverable` returns sections in state `stale`, start\nwith those: `staleReason` says which source moved (a decision retaken, a fact changed by a\nrescan, a clause changed by a new edition). Reread the source, rewrite the section or tell\nthe user it still holds.\n"
}