integration-doc-maintainerlisted

## What It Does Maintains cross-module integration docs by documenting events, jobs, contracts, and fallback behavior for any change that crosses module or service boundaries. ## Use This When Use this when a request affects published events, consumed events, background jobs, external service contracts, or any cross-module dependency. ## Inputs - Read the current integration docs first: `integration/events.md` and `integration/contracts.md` for the affected module. - Read the changed code and any generated event inventory or contract references. - Read `references/integration-contract-fields.md` before updating entries. ## Procedure 1. Run `scripts/find-integration-docs.sh` to enumerate canonical events/contracts/jobs/integration docs. 2. Run `scripts/extract-events.sh <changed-files...>` to surface candidate event names; LLM confirms each before writing. 3. Update each event entry using `assets/event.template.md` (publisher, subscribers, payload, async behavior, failure expectations, versioning). 4. Update contracts with owner, versioning, and fallback/degradation behavior. Document both sides of every cross-module coupling. 5. Format report per `assets/output.template.md` and validate with `scripts/lint-output.sh`. Missing fallback / undocumented coupling → `## Consistency Warnings`, never silent. ## Output Contract - Match `assets/output.template.md`: `## Updated Integration Docs` and `## Consistency Warnings`. - Every updated item must name the event, contract, j