kj-aiml/heli-harness/impact

impact

Trigger: before editing shared or high-use surfaces.

Scope:

• Identify callers, consumers, siblings, generated files, tests, data flows, and operational paths.
• Check recent history when useful.
• State expected blast radius before editing.

Destructive-operation call-chain checklist (S2+)

When the change touches cleanup, delete, revoke, janitor, reset, or fail-closed staging paths, inventory every delete-capable caller — not only the named preflight function:

• [ ] Preflight / gate path
• [ ] Post-run / teardown path
• [ ] Janitor / cron / scheduled path
• [ ] Fallback / error-recovery path
• [ ] Label/prefix synthesis that could widen blast radius
• [ ] Tests cover each path (or explicitly mark untested gaps)

Rules:

• Do not assume a symbol is local because only one file was mentioned.
• For S2/S3 impact, include rollback or mitigation notes.
• If impact is broader than the task, stop and surface the scope change.
• Fail-closed: prefer "missing attestation → no delete" over "prefix match → delete".
• If the responsible subsystem changes, create the lightweight diagnosis checkpoint before selecting a broader fix.

Output:

Surface:
Callers/consumers:
Destructive paths inventoried:
Files likely affected:
Generated files:
Tests/checks:
Rollback: