/procurement-offer-review — review supplier offers, keep the pack consistent

One job: the receiving side of procurement. A supplier's technical and financial offer arrives against an IPPF ToR; this skill checks it, comments on it, keeps the internal pack (ToR, waiver justification, best-value note, acquisition checklist) internally consistent when a decision changes, and compares scores in multi-bidder evaluations. The drafting side (writing the ToR) is tor-procurement, upstream.

Mode routing

• OFFER-REVIEW — an offer or revised offer arrived; Ane wants alignment checked against the ToR and, when one exists, against her prior comment round. Read-only on the vendor file; optionally writes a _COMMENTS copy.
• PACK-PROPAGATE — one procurement decision changed (contracting entity, budget figure, structure, dates); apply it consistently across every pack document.
• SCORE-COMPARE — a multi-bidder evaluation with a scoring workbook; build or link the evaluator-vs-AI comparison.

If the mode is ambiguous, ask in one line before working.

Shared rules — all modes

• Never edit the vendor's file. The offer is the supplier's document. Comments go on a copy named <original>_COMMENTS.docx; analysis goes in chat or internal notes. If the offer is a PDF, comments go in the chat report (a PDF is the vendor's frozen record — that is a feature, not a problem: it also freezes out any stale margin comments).
• Factual reliability. Never invent or approximate a figure, entity name, SIREN/VAT number, date, or approval. Every figure in the report traces to a named document or a named confirmation. A gap is reported as a gap.
• ⚠ Finance-to-confirm convention. This skill never asserts CERV, VAT, subcontracting, or procurement-manual compliance. It states what the documents say, names the tension, and flags ⚠ Finance to confirm: [question]. Compliance calls belong to Finance and the waiver signatory.
• Preserve originals. Before touching any internal pack document, note its timestamp; write versioned or suffixed copies where the pack convention uses them. Ane hand-edits and renames pack files mid-session — re-list the folder and re-read each file immediately before editing it, never from an earlier read.
• OneDrive revert hazard. In non-git OneDrive folders, sync can silently revert a fresh write within seconds. After any file write, verify the content landed (re-read a changed line). In git folders, write and commit in one block.
• Extraction mechanics (docx text, tracked changes, comments XML, PDF text, openpyxl formulas) live in references/docx-xlsx-mechanics.md. Read it before writing any comment, in-place docx edit, or workbook formula.