watching-ai-format-evolutionlisted

# Watching AI Format Evolution ## Overview Run a manual format-watch pass that prioritizes official evidence, extracts only parser-relevant structural signals, and produces a bounded maintenance report. Core principle: separate confirmed upstream evidence from local inference. ## Required Output Contract Unless the user explicitly asks for a different structure, the response MUST be organized as a separate section for each assistant checked or considered. This applies to general monthly watch passes, monthly summaries, watch updates, exploratory checks, and triage requests. For each assistant section, use these exact headings in this exact order: 1. `Sources checked` 2. `Confirmed deltas` 3. `Likely deltas` 4. `Unknowns` 5. `Confidence` 6. `Risk` 7. `Inspect next` 8. `Recommended action` Do not rename, merge, reorder, omit, or replace these headings. If a heading has no content, write an explicit placeholder such as `None confirmed`, `Unknown`, or `Not checked`. The exact heading contract is mandatory. Treat it like a schema, not a stylistic preference. Use `## <Assistant name>` for the assistant section heading, then the exact eight `###` headings below it. Do not answer this skill as freeform prose. ## Format Violations The following are violations of this skill: - Combining multiple assistants into one shared report - Using only some of the required headings - Replacing headings with close variants such as `Evidence`, `Findings`, `Next steps`, or `Action` - Writi