sixfold-space/madtea
sixfold-space/madtea
SHA256
2
0
Fork 0
Code Issues 221 Pull requests Projects Releases 13 Packages Wiki Activity Actions 9

test(parity): #669 fail the gate when a forge write skips the guard #801

Merged
hexajon merged 1 commit from issue-669-guard-parity-test into main 2026-10-18 02:07:38 +00:00
Conversation 0 Commits 1 Files changed 4 +5129
hexajon commented 2026-10-18 02:07:36 +00:00
Owner
Copy link

Summary

A new parity detector and test fail the gate when production code builds a forge client or a git writer with no write guard, or sends a write around the guarded functions, as ADR 0046 requires. It passes on the current tree, after the git and forge write seams route through the guard (#659, #660).

Refs #669

## Summary A new parity detector and test fail the gate when production code builds a forge client or a git writer with no write guard, or sends a write around the guarded functions, as ADR 0046 requires. It passes on the current tree, after the git and forge write seams route through the guard (#659, #660). Refs #669
test(parity): #669 fail the gate when a forge write skips the guard
Some checks failed
ci / mcp-conformance (pull_request) Successful in 1m38s
Details
drift / govulncheck (pull_request) Has been skipped
Details
drift / surface-diff (pull_request) Successful in 34s
Details
drift / forgejo-smoke (pull_request) Has been skipped
Details
ci / mcp-conformance (push) Successful in -31s
Details
drift / govulncheck (push) Has been skipped
Details
drift / surface-diff (push) Successful in -38s
Details
drift / forgejo-smoke (push) Has been skipped
Details
ci / gate (push) Failing after 4m3s
Details
ci / gate (pull_request) Failing after 16m58s
Details
7655873968
 
Add a parity detector and test, as ADR 0046 requires: the gate fails when
production code builds a forge client or a git writer with no write guard, or
sends a write around the guarded functions. It passes on the current tree,
after the git and forge write seams route through the guard (#659, #660).

Refs #669
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
breaking
Breaking change - flag for release notes

  
bug
Something is not working

  
documentation
Documentation only

  
enhancement
New feature

  
epic
Tracking epic with dependency children

  
good first issue
Interested in contributing? Get started here.

  
help wanted
Maintainer would welcome outside help

  
refactoring
Code restructuring without behavior changes

  
resolution/duplicate
Closed as duplicate of another issue

  
resolution/invalid
Closed as invalid or not reproducible

  
resolution/wontfix
Closed as won't fix

  
security
Security issue or hardening

  
severity/critical
Security severity: critical

  
severity/high
Security severity: high

  
severity/low
Security severity: low

  
severity/medium
Security severity: medium

  
status/abandoned
Someone started, then walked away - up for grabs

  
status/blocked
Blocked by another issue or an external dependency

  
status/needs-decision
Waiting on a maintainer decision; workable once decided

  
status/needs-info
Waiting on reporter / more information before work can start

  
status/needs-verification
Done except verification in a live interactive session

  
testing
Test suite / CI infrastructure work

  
upstream
Related to an upstream repository, already reported there

No labels
breaking
bug
documentation
enhancement
epic
good first issue
help wanted
refactoring
resolution/duplicate
resolution/invalid
resolution/wontfix
security
severity/critical
severity/high
severity/low
severity/medium
status/abandoned
status/blocked
status/needs-decision
status/needs-info
status/needs-verification
testing
upstream
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
sixfold-space/madtea!801
No description provided.