mosaicstack/stack
1
0
Fork 0
Code Issues 79 Pull Requests 1 Actions Packages Projects Releases 15 Wiki Activity

test(#832): define receipt challenge replay contracts

Browse Source
This commit is contained in:
ms-lead-reviewer
2026-07-19 16:26:47 -05:00
parent e522b22fa4
commit 5f967a4dc2
4 changed files with 354 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
docs/scratchpads/832-receipt-challenge-protocol.md Normal file
View File

@@ -0,0 +1,13 @@
# #832 Receipt-challenge protocol — build scratchpad
- **Objective:** Deliver WI-5 receipt-challenge protocol ACs T25, T26, T28, and T29 only.
- **Authority:** BUILD-BRIEF, SPEC-v5, ratification, and red-team hashes verified in STEP-0.
- **Base:** `e522b22fa4492861b0fcd4a956a8795c54eb9bfe` (`origin/main`).
- **Constraints:** Byte-build only: no live broker/socket/systemd/tmux mutation. No PR, self-review, or probe fire. T27/T30 are out of scope.
- **Plan:**
1. Add red-first deterministic T26/T29 in-build tests that call shipped normative construction and broker path.
2. Add an unexecuted, isolated P5 out-of-process replay harness that drives the shipped daemon and asserts consume-before-promote for T25/T28.
3. Implement the broker-minted receipt challenge and exact receipt observation/consume/promote path.
4. Run unit, framework-shell, compile, lint, and type checks; push after the required queue guard; report to `mosaic-100`.
- **Risks:** The standalone harness must drive the real daemon without a divergent fixture. If that is impossible, stop and flag Mos.
- **Evidence:** Pending red run, green checks, and push.