What problem does it solve? Maintainers of the Senzing Bootcamp plugin receive raw feedback files from bootcampers and must manually turn each entry into actionable, deduplicated GitHub issues while confirming every Senzing fact still holds against the live MCP server. ## Core Features & Use Cases - Per-entry duplicate detection: A bundled Python ledger script content-addresses each feedback entry (sha256 of normalized text) so overlapping feedback files are never re-processed. - Live fact re-verification: Every Senzing claim is re-checked against the current MCP server before filing, catching defects already fixed upstream or guidance the server now contradicts. - Structured issue filing: Generates GitHub issues from a strict template with root cause, acceptance criteria, provenance, and invariant references, plus optional upstream defect reports via submit_feedback. - Use Case: A maintainer drops SENZING_BOOTCAMP_PLUGIN_FEEDBACK.md into the repo and asks to process it; the skill classifies entries, skips known ones, files new issues, archives the file, and reports a triage table. ## Quick Start Process the feedback file SENZING_BOOTCAMP_PLUGIN_FEEDBACK.md at the repo root and file GitHub issues for any new entries.