Skip to content

Question seal via SUBMIT text_sha256; restore ledger-form rescore tamper tests - #108

Merged
AzielEliab merged 1 commit into
mainfrom
fix/challenge-seal
Oct 11, 2026
Merged

AzielEliab merged 1 commit into
mainfrom
fix/challenge-seal

Conversation

@AzielEliab

Copy link
Copy Markdown
Owner

Off main 892cfcb (#107 follow-up).

  1. Tamper tests restored in ledger form: an edited rescore factor_detail with its RESCORE row kept comes out not covered. An unsealed previous (SUBMIT) detail comes out not covered even when the line's own detail is sealed. A control test checks that both sealed is covered.
  2. Question seal: challengeSealed is true only when the SUBMIT row is in the verified chain (hash_ok, in range, matches_checkpoint) and sha256(challenge_text) === text_sha256 from that row. The drop-down gets a 'Question seal' line reading covered or 'stored data, not covered'. The JSON returns challenge_sealed. I checked live receipt e8be822c: sha256 of its stored challenge_text equals its SUBMIT text_sha256.

No new D1 queries. Hash-linked and sealed, not signed. Tests: 313/313. Not merged, not deployed.

@AzielEliab
AzielEliab merged commit a719c02 into main Oct 11, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant