Customer commitment audits need request-tail and coverage-gap accounting

Classify a commitment at the granularity of the customer's full request, not the broad feature label. A base feature can be active while a customer-specific tail such as filtering, history, writeback, or labeling remains partial or absent. Independently enumerate feedback sources, inspect contradiction or frustration language, and verify mapped merge commits against the active deployment. Report connector failures and missing recordings as coverage gaps; zero records in one source is not evidence of zero feedback.