kiro-powers: mirror the skill changes from #197

[shravan-lambdatest]

Problem

The Kiro power under integrations/kiro-powers is a translation of the Kane CLI skill, and the skill changed in #197: the pre-run variable check is a warning with a fill-before-any-run recipe, every testrun run line ends in < /dev/null, test-case authoring goes through the assurance commands only, and directory examples select with --match. The power still described none of that, still routed test-case requests to kane-cli generate with its own generate steering file, and its command lines showed an --agent flag that testrun run does not have.

Change

• POWER.md: the third way Kiro uses Kane CLI is test-case authoring through the assurance commands; the --agent sentence carries the testrun stdin rule with its cmd.exe and PowerShell forms and the first-line stream_start check; the command reference and the quick example drop the --agent flag on testrun run and end in < /dev/null; the steering-file mapping sends every "write test cases" ask to the assurance steering.
• steering/kane-cli-run.md: the unresolved-variables contract (0.8.15+) and the fill-before-any-run recipe under Variables and secrets; a warning row in the typed-events table; a Variables row rule for the result card; missing variable values are no longer an exit-2 cause; the decision tree routes test-case asks to the assurance steering.
• steering/kane-cli-testrun.md: preflight checks variables but never fails a member for them; testrun_plan members carry unresolved? and a warning follows the plan; every command line ends in < /dev/null; the --match note says the path is as the OS writes it; directory examples use --match '^tests/…/'.
• steering/kane-cli-mobile.md: the same redirect and --match examples.
• steering/kane-cli-testmd.md: authoring from a description goes through assurance; the non-TTY note no longer describes ask_user.
• steering/kane-cli-assurance.md: a chat description becomes a requirements file and follows the same path; design's declared variables are surfaced as a to-do and filled before any run.
• steering/kane-cli-generate.md removed; integrations/docs/kiro-powers.md mapping table updated to match.

Tests

None: steering text only. The guide's verification checklist was run: frontmatter keys present, no inclusion: frontmatter, the "wait for run_end" rule and the License and support section untouched, the tour block untouched, the hook still parses as JSON.

Verification

• Every fact added here traces to a line in skill-installer/skills/SKILL.md or its references as merged in docs, skill: an unresolved variable warns and the run goes ahead (kane-cli 0.8.15+) #197.
• No kane-cli generate, generate_* or generate-steering reference remains under integrations/.

🤖 Generated with Claude Code