TC #94 — Phase 9 sha256-mismatch re-prompts on content change #94
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Scenario / Expected
After accept + persist, modify the .aish.lua file's content; next startup's sha != recorded sha -> trust prompt fires again.
Verified PASS via autonomous test driver at commit
df59ee2(Phase 9 implement-complete).After accept + persist, appended
-- changedto .aish.lua content. Next startup: sha mismatch detected (current file's sha != recorded sha) -> trust prompt re-fires. User can re-evaluate before re-trusting.Closed by Phase 9 verify.