zeekayandHanzo Dev eaab7eeda3 token: compare the mac, not the label, when checking domain separation ...

The test asserted that two domains mint different tokens, which the domain prefix
guarantees on its own — so it passed with the per-domain key derivation removed
and one key minting every domain. It now compares the mac behind the prefix,
which is the thing the key schedule is responsible for.

Found by mutating the HKDF info to a constant: the mutant survived, which is the
only way to learn that a test passes for the wrong reason.

Co-authored-by: Hanzo Dev <[email protected]>

2026-07-29 11:14:53 -07:00

..

anomaly.go

token: compare the mac, not the label, when checking domain separation

2026-07-29 11:14:53 -07:00

identity_test.go

api: derive the tenant from a credential, not from a request header

2026-07-29 11:03:54 -07:00

readiness.go

sanctions: make screening readiness answerable per list, and show it

2026-07-29 11:13:09 -07:00

records_test.go

aml: check the record plane join, and put the replay report on the surface

2026-07-29 11:09:43 -07:00

records.go

aml: anomaly scoring, retention, tokenisation, replay, reference data

2026-07-29 11:04:33 -07:00

routes_test.go

aml: anomaly scoring, retention, tokenisation, replay, reference data

2026-07-29 11:04:33 -07:00

routes.go

sanctions: make screening readiness answerable per list, and show it

2026-07-29 11:13:09 -07:00