Found during 0.25.0 release testing. Pre-existing — byte-identical on published 0.24.0.
hackmyagent secure ./fixture/myagent (agent lives in myagent, wrapper dir fixture contains only it):
── Next Steps ─────────────────────────────────────────────────
Protect credentials: opena2a protect ./fixture
AI analysis: hackmyagent check ./fixture/myagent --nanomind
protect (and harden-soul when governance items are present) point at ./fixture — the PARENT of the scanned directory — while check on the same block correctly cites ./fixture/myagent. Following the suggestion acts on the wrong directory (confirmed: harden-soul ./fixture --dry-run targets the empty wrapper). Looks like a dirname()/path-truncation bug in the Next Steps builder, applied to some entries but not others.
Dead-end class (CISO Rule 11): the cited command runs but acts on the wrong target. P2.
Found during 0.25.0 release testing. Pre-existing — byte-identical on published 0.24.0.
hackmyagent secure ./fixture/myagent(agent lives inmyagent, wrapper dirfixturecontains only it):protect(andharden-soulwhen governance items are present) point at./fixture— the PARENT of the scanned directory — whilecheckon the same block correctly cites./fixture/myagent. Following the suggestion acts on the wrong directory (confirmed:harden-soul ./fixture --dry-runtargets the empty wrapper). Looks like a dirname()/path-truncation bug in the Next Steps builder, applied to some entries but not others.Dead-end class (CISO Rule 11): the cited command runs but acts on the wrong target. P2.