Skip to content

docktermj/senzing-bootcamp-maintainer

v1.1.0Apache-2.0

Maintainer tooling for the Senzing Bootcamp Kiro Power. Use when creating the Senzing bootcamp power from a template release, when updating it to a newer template release, when checking it for parity with the parent release, when escalating a curriculum problem to the parent, when auditing it for production readiness before the manual checklist, when dry-running it against the live Senzing MCP server and the Kiro host, when releasing a tested version with its changelog entry and git tag, when propagating it into a working tree of the public Senzing/senzing-bootcamp-kiro-power repository for review, or when retrofitting edits made in that public repository back as triaged issues.

create-bootcamp-power

Build the Senzing Bootcamp Kiro Power at powers/senzing-bootcamp/ from the latest Senzing bootcamp Claude plugin release, by running the shared transformation engine and publishing its output only after validation passes. Use when the maintainer says 'create the senzing bootcamp power'.

dry-run

Dry-run the Senzing Bootcamp Kiro Power to find what only shows up when it runs, in three phases that get more expensive in order: phase 1 checks every Senzing MCP call the Power makes against the live server, phase 2 installs the hooks with the Power's own installer into a realistic scratch project and executes every one in Kiro's payload shape, and phase 3 walks the bootcamp with the maintainer answering as the bootcamper — in this workspace, and installed on the Kiro host. A phase that cannot run on Kiro is recorded as an advisory degradation, never as a pass. Findings are recorded as they appear, routed local or parent-bound with a reason, and filed as issues only with approval. Use when the maintainer says 'dry-run the senzing bootcamp power'.

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'.

parity-check

Compare the committed Senzing Bootcamp Kiro Power against a tagged release of the parent Senzing bootcamp Claude plugin and file GitHub issues in this repository describing the delta needed to reach parity — without running the transform and without writing to the parent. Use when the maintainer says 'check the senzing bootcamp power for parity'.

production-readiness-audit

Audit the shipped Senzing Bootcamp Kiro Power at powers/senzing-bootcamp/ for production readiness: a static review of the Power as one body of instructions for consistency, coherence, completeness and concision, checked against both invariant records — the inherited INV-NNN through the disposition register, and the Kiro-native KINV-NNN ledger — in both directions. Shows a parent-bound or local verdict for every finding with its reason, hands parent-bound findings to escalate-to-parent, and files local findings as deduplicated GitHub issues in this repository. The static gate between the mechanical checks and the recorded host-behavior checklist; it fixes nothing unasked. Use when the maintainer says 'audit the senzing bootcamp power for production readiness'.

propagate-to-public

Propagate the built Senzing Bootcamp Kiro Power at powers/senzing-bootcamp/ into an existing working tree of the public repository Senzing/senzing-bootcamp-kiro-power, through the Publication_Contract: mirror only what a bootcamper installs, rewrite development self-references, and stop at the working tree — no commit, no push, no branch, no pull request, no release, no issue. The Maintainer reviews the diff and publishes by hand. Use when the maintainer says 'propagate the senzing bootcamp power to public'.

release

Release a version of the Senzing Bootcamp Kiro Power in this development repository: verify that every place asserting the version agrees, enforce the tagging gate (a passing ValidationReport and a fully recorded Test_Checklist for exactly that version), write the CHANGELOG.md entry, commit it, and create the annotated git tag — as one operation, with no path that moves one without the others. Touches this repository only; never pushes, and never writes to the public repository. Use when the maintainer says 'release the senzing bootcamp power'.

retrofit-from-public

Report how the public repository Senzing/senzing-bootcamp-kiro-power diverged from the Senzing Bootcamp Kiro Power that was last propagated to it, triage every divergence as parent-bound or local and show the verdict with its reason, hand parent-bound items to escalate-to-parent, and file local items as GitHub issues in this repository after checking the tracker for duplicates. Writes nothing into this repository or the public one; filing is the deliverable, and implementing is implement-github-issue's job. The inverse direction of propagate-to-public. Use when the maintainer says 'retrofit the senzing bootcamp power from public'.

update-bootcamp-power

Move the existing Senzing Bootcamp Kiro Power at powers/senzing-bootcamp/ to a newer Senzing bootcamp Claude plugin release, by re-running the shared transformation engine, reconciling the result against the Power so every Kiro-specific adaptation is preserved, and publishing only after validation passes. Use when the maintainer says 'update the senzing bootcamp power'.