Skip to content

test: assert the stale tenant-guard claim stays removed (#1355 follow-up) #1359

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
alfredo1996 merged 1 commit into from
Jul 29, 2026
Merged

test: assert the stale tenant-guard claim stays removed (#1355 follow-up) #1359

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions app/src/lib/__tests__/docs-accuracy.test.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -121,6 +121,13 @@ describe("documentation accuracy", () => {
// that believes the ORM scopes queries will write an unscoped one.
expect(doc).toMatch(/per query, in the route/);
expect(doc).toMatch(/not runtime enforcement/);

// And the stale claim must stay gone. Asserting only that the NEW text is
// present would pass if someone reintroduced "nothing catches it /
// tracked in #1226" alongside it — leaving the document contradicting
// itself, which is worse for a reader than either version alone.
expect(doc).not.toMatch(/tracked in #1226/i);
expect(doc).not.toMatch(/leak that nothing catches/i);
});

it("the deploy skill does not send auditors looking for a flag that does not exist", () => {
Expand Down
Loading