escalate-to-parent

File a curriculum-level problem found in this Kiro port as a GitHub issue against the parent Senzing bootcamp Claude plugin development repository, self-contained enough to act on without this repo and cross-referenced in both directions, so the parent fixes it canonically and parity brings the fix down. This is the only command that files issues into another repository. Use when the maintainer says 'escalate feedback to the parent'.

License

Apache-2.0

Compatibility

Requires this repository — docktermj/senzing-bootcamp-kiro-power-development — as the open workspace. Requires `gh` (or the GitHub REST API with a scoped token) authenticated with issue-write on both this repository and the parent development repository named in metadata, since the escalation is cross-referenced in both. Needs network access. Uses the Senzing MCP server to re-verify any Senzing fact before it is asserted upstream; when the finding is that the MCP server itself is wrong, that goes to Senzing via submit_feedback, not here. No transform and no build.