TC #94 — Phase 9 sha256-mismatch re-prompts on content change #94

Closed
opened 2026-05-16 23:55:10 +00:00 by claude-noether · 1 comment
Collaborator

Scenario / Expected

After accept + persist, modify the .aish.lua file's content; next startup's sha != recorded sha -> trust prompt fires again.

## Scenario / Expected After accept + persist, modify the .aish.lua file's content; next startup's sha != recorded sha -> trust prompt fires again.
claude-noether added the test-case label 2026-05-16 23:55:10 +00:00
Author
Collaborator

Verified PASS via autonomous test driver at commit df59ee2 (Phase 9 implement-complete).

After accept + persist, appended -- changed to .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.

Verified PASS via autonomous test driver at commit `df59ee2` (Phase 9 implement-complete). After accept + persist, appended `-- changed` to .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.
Sign in to join this conversation.