add the write-guard parity test: no write around the guard #785

New issue

Closed

opened 2026-10-16 01:00:36 +00:00 by hexajon · 0 comments

hexajon commented

2026-10-16 01:00:36 +00:00

Owner

Fix:

Add a test that asserts every forge-client send function that can write routes through the guard.
It must fail on the current passthrough send path and pass once that path is guarded.

Acceptance:

The test fails if any write send, new or existing, skips the guard.

Part of the write-guard work (#670). Locks the fix for #784.

The write-guard design (ADR 0046) requires a parity test that fails when production code builds a forge client or a git writer with no guard, or sends a write around the guarded functions. That test is missing, which is why the passthrough gap in #784 passed a green gate. Fix: - Add a test that asserts every forge-client send function that can write routes through the guard. - It must fail on the current passthrough send path and pass once that path is guarded. Acceptance: - The test fails if any write send, new or existing, skips the guard. Part of the write-guard work (#670). Locks the fix for #784.

hexajon added a new dependency

2026-10-16 01:01:42 +00:00

#670 epic: one guard enforces the recorded limits on every surface

hexajon referenced this issue

2026-10-16 02:09:28 +00:00

widen the write-guard parity test to the full-URL mode and the normalized path #789

hexajon referenced this issue from a pull request that will close it,

2026-10-16 02:41:35 +00:00

feat(guard): enforce the ADR 0046 write guard on every forge write surface #790

hexajon referenced this issue from a commit

2026-10-16 02:41:35 +00:00

feat(guard): #660 enforce the ADR 0046 forge write guard on the first-class CLI and MCP surfaces