CONTRACT CHECK (law and compliance)
Everything here is invented: the vendors, the contracts, the playbook.

our-playbook.md            A one-page playbook: what we insist on as the customer, and what we'll accept.
contract-A-meridian.md     A vendor's software agreement. Jay runs this one in the demo.
contract-B-harbor.md       A consultant's statement of work. Your second input.

Level 5 move: turn a review you'd do by hand into a skill you can run again.

Try this:
  Make me a skill called contract-check that reviews a contract against
  our-playbook.md and builds an interactive one-page HTML issues list.
  On top, a three-line bottom line for the business owner. One row per
  playbook topic: red / yellow / green, section, exact quote, and
  replacement language we could paste into a redline. Clicking a row
  shows the clause beside our Must and Fallback. Below, risky terms the
  playbook doesn't cover. Tick rows to draft the vendor email. Style it
  like a law-firm memo. Open it when done. Ask me questions first.

Then run it:  /contract-check contract-A-meridian.md
Then again:   /contract-check contract-B-harbor.md

Check: open the contract and find two of the sections it quoted. Are the quotes exact?
Look for anything the contract mentions that isn't actually in the folder.
