sc-summary

# Steering Committee Meeting Summaries Use the notes folder or files the user supplies in the request or current conversation. If no source location is available, ask for it. Write to the repository's `GOVERNANCE.md`, under **Meeting Notes**. 1. Read the existing Meeting Notes entries and list the files at the supplied location. Summarize the requested dates or files. If the user gives no date or quantity, choose the earliest meeting without an entry and do one meeting for review. Do not duplicate an existing entry unless asked to revise it. 2. Read each entire source note, especially the details. Resolve repeated or inconsistent points before writing. Treat proposed ideas, decisions, and suggested next steps distinctly; do not present an unconfirmed proposal as an agreed decision. 3. Write a public-facing, high-level summary of React Router discussion only. Omit unrelated conversation and banter. Refer to participants by first name. Follow the existing `<details>` format and prose in `GOVERNANCE.md`; use short topical headings when useful. Match the depth of existing entries, adjusted to how much substantive discussion occurred. 4. Insert each entry near the other meeting dates, preserve unrelated content, then review the diff against the source and run `git diff --check`. Show the new or revised entries to the user. Do not post them to GitHub, commit, or publish unless requested.