[testing] Add property-based test for freeze/unfreeze toggling"

[nagasatish007]

Summary

Add a fast-check property test proving that freeze(agentId) followed by unfreeze(agentId) restores the agent to operational state.

What to do

• Create src/observe/__tests__/freeze-registry.property.test.ts
• Use fast-check (already a dev dependency)
• Test properties:
  1. For any agentId: freeze(id) → isFrozen(id) === true
  2. For any agentId: freeze(id) → unfreeze(id) → isFrozen(id) === false
  3. Freezing one agent doesn't affect another agent's state
• Run 100 iterations per property

Example structure

import fc from 'fast-check';
import { freeze, unfreeze, isFrozen } from '../freeze-registry';

describe('FreezeRegistry (property-based)', () => {
  it('freeze then unfreeze restores operational state', () => {
    fc.assert(
      fc.property(fc.string({ minLength: 1 }), (agentId) => {
        freeze(agentId);
        expect(isFrozen(agentId)).toBe(true);
        unfreeze(agentId);
        expect(isFrozen(agentId)).toBe(false);
      }),
      { numRuns: 100 }
    );
  });
});

Acceptance criteria

• Property test file created
• All 3 properties pass with 100 iterations
• Tests run with npx vitest run src/observe/__tests__/freeze-registry.property.test.ts
• No flaky failures

Helpful links

• Freeze registry: src/observe/freeze-registry.ts
• fast-check docs: https://github.com/dubzzz/fast-check
• Existing property tests: dashboard/web/src/utils/formatters.test.ts (for pattern)

[Ehtasham-Yasin]

Hi, I started checking this issue before working on it and noticed that packages/tealtiger-ai-sdk/src/observe/tests/FreezeRegistry.properties.test.ts already covers the requested property-based tests, including freeze/unfreeze round-trip and independence between agent IDs.

Should this issue be closed, or is there any additional behavior you want tested?

[nagasatish007]

@Ehtasham-Yasin good catch — you're right, that file covers the base cases. Let me redirect this:

The existing test is in packages/tealtiger-ai-sdk/ (the Vercel AI SDK adapter). What we actually need is the same coverage in the core SDK at packages/tealtiger-sdk/src/observe/tests/. The core observe module's freeze registry should have its own property tests independent of the adapter package.

If you'd like to take this on: port/adapt the existing test from tealtiger-ai-sdk to the core SDK location (
freeze-registry.property.test.ts
), using vitest + fast-check (the core SDK uses vitest, not jest).

If the core already has equivalent coverage there too, then yes we can close this. Let me know what you find.

[Ehtasham-Yasin]

Thanks for the clarification. I checked the current repo structure and found that `packages/tealtiger-sdk` exists, but I don’t see `packages/tealtiger-sdk/src/observe/` or a core `freeze-registry.ts` implementation there. The only `observe` folder and FreezeRegistry implementation I found is still under `packages/tealtiger-ai-sdk/src/observe/`. Should I create the core `observe/freeze-registry.ts` implementation plus the property test, or should the test target a different existing core SDK path?

…

On Thu, Jul 9, 2026 at 4:21 PM Naga Satish Chilakamarti < ***@***.***> wrote: *nagasatish007* left a comment (agentguard-ai/tealtiger#372) <#372 (comment)> @Ehtasham-Yasin <https://github.com/Ehtasham-Yasin> good catch — you're right, that file covers the base cases. Let me redirect this: The existing test is in packages/tealtiger-ai-sdk/ (the Vercel AI SDK adapter). What we actually need is the same coverage in the core SDK at packages/tealtiger-sdk/src/observe/*tests*/. The core observe module's freeze registry should have its own property tests independent of the adapter package. If you'd like to take this on: port/adapt the existing test from tealtiger-ai-sdk to the core SDK location ( freeze-registry.property.test.ts ), using vitest + fast-check (the core SDK uses vitest, not jest). If the core already has equivalent coverage there too, then yes we can close this. Let me know what you find. — Reply to this email directly, view it on GitHub <#372?email_source=notifications&email_token=CCOMGCHLLWEDSQHGEDKFSXL5D6S5VA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIOJSGYYDEMJZHA4KM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-4926021988>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/CCOMGCHG6MAWTDJN4IFDW5D5D6S5VAVCNFSNUABGKJSXA33TNF2G64TZHMYTCNJQGY3TIMRZHA5US43TOVSTWNBYGQ3DINBUGE4DDILWAI> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/CCOMGCAXWOXPN62RFZTG56T5D6S5VA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIOJSGYYDEMJZHA4KM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJKTGN5XXIZLSL5UW64Y> and Android <https://github.com/notifications/mobile/android/CCOMGCAXOEBA3RNSLDUKFWD5D6S5VA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIOJSGYYDEMJZHA4KM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLTGN5XXIZLSL5QW4ZDSN5UWI>. Download it today! You are receiving this because you were mentioned.Message ID: ***@***.***>

[nagasatish007]

@Ehtasham-Yasin — The core SDK source is at packages/tealtiger-sdk (it's a git submodule pointing to tealtiger-typescript-prod). The observe module and freeze-registry.ts are at:

packages/tealtiger-sdk/src/observe/freeze-registry.ts
The tests folder there only has observe-governance.test.ts — no property test for freeze/unfreeze yet. So the task is:

Clone tealtiger-typescript-prod
Create
freeze-registry.property.test.ts
Import from ../freeze-registry
Use vitest + fast-check (both are already dev dependencies in that repo)
Submit a PR to tealtiger-typescript-prod
The implementation already exists — you just need to write the property tests against it. Assigning you.

[Ehtasham-Yasin]

I checked `tealtiger-typescript-prod`. The freeze registry implementation exists at `src/observe/freeze-registry.ts`, but I noticed two things before writing the test: 1. The repo currently has Jest scripts (`"test": "jest --runInBand"`), and I don’t see `vitest` in `package.json` or `package-lock.json`. 2. `freeze-registry.ts` exports `freeze` and `unfreeze`, but not a top-level `isFrozen`; `isFrozen` is currently available via `FreezeRegistry.getInstance().isFrozen(agentId)`. Should I add the property test using the existing Jest setup, or should I add Vitest as a dev dependency and use Vitest for this test?

…

On Thu, Jul 9, 2026 at 5:45 PM Naga Satish Chilakamarti < ***@***.***> wrote: Assigned #372 <#372> to @Ehtasham-Yasin <https://github.com/Ehtasham-Yasin>. — Reply to this email directly, view it on GitHub <#372?email_source=notifications&email_token=CCOMGCERPOYPYO2UCSNCBRD5D642FA5CNFSNUABQM5UWIORPF5TWS5BNNB2WEL2JONZXKZKFOZSW45CON52GSZTJMNQXI2LPNYXTENZXG4ZTGNZRHAYDFJTSMVQXG33OUZQXG43JM5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#event-27773371802>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/CCOMGCFX3ZYTANLUGQFCCGD5D642FAVCNFSNUABGKJSXA33TNF2G64TZHMYTCNJQGY3TIMRZHA5US43TOVSTWNBYGQ3DINBUGE4DDILWAI> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/CCOMGCHPAFWCLCSVFO4FEQL5D642FA5CNFSNUABQM5UWIORPF5TWS5BNNB2WEL2JONZXKZKFOZSW45CON52GSZTJMNQXI2LPNYXTENZXG4ZTGNZRHAYDFJTSMVQXG33OUZQXG43JM5XKKZLWMVXHJKTGN5XXIZLSL5UW64Y> and Android <https://github.com/notifications/mobile/android/CCOMGCEZEJB3ZER57MI56J35D642FA5CNFSNUABQM5UWIORPF5TWS5BNNB2WEL2JONZXKZKFOZSW45CON52GSZTJMNQXI2LPNYXTENZXG4ZTGNZRHAYDFJTSMVQXG33OUZQXG43JM5XKKZLWMVXHJLTGN5XXIZLSL5QW4ZDSN5UWI>. Download it today! You are receiving this because you were assigned.Message ID: ***@***.***>

[nagasatish007]

@Ehtasham-Yasin — good investigation.

Use Jest — stick with the existing test setup. Don't add vitest as a separate dep for one test file. fast-check works with Jest just fine (npm install --save-dev fast-check if it's not already there).

For isFrozen — use the singleton directly:

import { freeze, unfreeze } from '../freeze-registry';
import { FreezeRegistry } from '../freeze-registry';

const registry = FreezeRegistry.getInstance();
// then: registry.isFrozen(agentId)
Or, if you'd prefer, you can also add a top-level isFrozen export as part of this PR — it's a one-liner convenience wrapper and makes the API more ergonomic:

export function isFrozen(agentId: string): boolean {
return FreezeRegistry.getInstance().isFrozen(agentId);
}
Either approach works for the PR. Adding the export is a nice bonus if you want the extra contribution credit.

Also if you can give a github star, that would help :)