@agenttrail/guardrails 0.0.2 → 0.1.0

package/dist/guardrails.d.cts

@@ -3,7 +3,7 @@ export { Action, FixtureInput, Fixtures, Match, RuleInput, Severity } from './sc
 import 'zod';
 
 /**
- * The eight packs, and the order they are presented in.
+ * The eleven packs, and the order they are presented in.
  *
  * These ids are authoritative and shared with the rules authored against them,
  * and with the guard's `config.json` `enabledPacks`. Renaming one of these is a
@@ -16,10 +16,10 @@ import 'zod';
  * Per-pack rule counts are deliberately NOT encoded here: a rule count asserted in
  * code becomes a reason to write a weak rule to hit a number.
  */
-declare const PACKS: readonly ["working-tree", "destructive-data", "prod-infra", "secret-exposure", "rce-supply-chain", "safety-bypass", "privilege-supply-chain", "file-scope"];
-/** One of the eight pack ids. A rule's `category` is always one of these. */
+declare const PACKS: readonly ["working-tree", "destructive-data", "prod-infra", "secret-exposure", "rce-supply-chain", "safety-bypass", "privilege-supply-chain", "file-scope", "agent-context", "test-integrity", "exfiltration"];
+/** One of the eleven pack ids. A rule's `category` is always one of these. */
 type Pack = (typeof PACKS)[number];
-/** Is this string one of the eight pack ids? */
+/** Is this string one of the eleven pack ids? */
 declare function isPack(value: string): value is Pack;
 
 /**
@@ -38,7 +38,7 @@ declare function isPack(value: string): value is Pack;
  *     curl --data "we ran rm -rf /tmp/x" https://…    -> DENY  dd.rm-rf-absolute
  *
  * Without an exemption, a person documenting this tool is blocked by this tool.
- * That applies to every command-channel rule — 48 of the 56. The eight `file_glob`
+ * That applies to every command-channel rule — 62 of the 74. The twelve `file_glob`
  * rules never see a command.
  *
  * ── Why exemption by CARRIER VERB, and not by "the payload is quoted" ────────
@@ -276,7 +276,7 @@ declare function mentions(text: string): Fixture[];
  * Pinned to `package.json`'s `version` by `__tests__/stamp.test.ts` — this is a copy
  * of that value, not an independent one, and the test is what makes the copy safe.
  */
-declare const CATALOG_VERSION = "0.0.2";
+declare const CATALOG_VERSION = "0.1.0";
 /**
  * When the rules in this catalog reached their current state, as an ISO-8601
  * instant. The question it answers is not "when did this reach a registry" but "how
@@ -286,7 +286,7 @@ declare const CATALOG_VERSION = "0.0.2";
  * the guard handles a missing date, and a wrong date that looks right is worse than
  * a missing one.
  */
-declare const CATALOG_PUBLISHED_AT = "2026-09-07T12:44:09Z";
+declare const CATALOG_PUBLISHED_AT = "2026-09-15T07:13:18Z";
 
 /**
  * The corpus itself — rules only, and **deliberately free of zod**.

package/dist/guardrails.d.ts

@@ -3,7 +3,7 @@ export { Action, FixtureInput, Fixtures, Match, RuleInput, Severity } from './sc
 import 'zod';
 
 /**
- * The eight packs, and the order they are presented in.
+ * The eleven packs, and the order they are presented in.
  *
  * These ids are authoritative and shared with the rules authored against them,
  * and with the guard's `config.json` `enabledPacks`. Renaming one of these is a
@@ -16,10 +16,10 @@ import 'zod';
  * Per-pack rule counts are deliberately NOT encoded here: a rule count asserted in
  * code becomes a reason to write a weak rule to hit a number.
  */
-declare const PACKS: readonly ["working-tree", "destructive-data", "prod-infra", "secret-exposure", "rce-supply-chain", "safety-bypass", "privilege-supply-chain", "file-scope"];
-/** One of the eight pack ids. A rule's `category` is always one of these. */
+declare const PACKS: readonly ["working-tree", "destructive-data", "prod-infra", "secret-exposure", "rce-supply-chain", "safety-bypass", "privilege-supply-chain", "file-scope", "agent-context", "test-integrity", "exfiltration"];
+/** One of the eleven pack ids. A rule's `category` is always one of these. */
 type Pack = (typeof PACKS)[number];
-/** Is this string one of the eight pack ids? */
+/** Is this string one of the eleven pack ids? */
 declare function isPack(value: string): value is Pack;
 
 /**
@@ -38,7 +38,7 @@ declare function isPack(value: string): value is Pack;
  *     curl --data "we ran rm -rf /tmp/x" https://…    -> DENY  dd.rm-rf-absolute
  *
  * Without an exemption, a person documenting this tool is blocked by this tool.
- * That applies to every command-channel rule — 48 of the 56. The eight `file_glob`
+ * That applies to every command-channel rule — 62 of the 74. The twelve `file_glob`
  * rules never see a command.
  *
  * ── Why exemption by CARRIER VERB, and not by "the payload is quoted" ────────
@@ -276,7 +276,7 @@ declare function mentions(text: string): Fixture[];
  * Pinned to `package.json`'s `version` by `__tests__/stamp.test.ts` — this is a copy
  * of that value, not an independent one, and the test is what makes the copy safe.
  */
-declare const CATALOG_VERSION = "0.0.2";
+declare const CATALOG_VERSION = "0.1.0";
 /**
  * When the rules in this catalog reached their current state, as an ISO-8601
  * instant. The question it answers is not "when did this reach a registry" but "how
@@ -286,7 +286,7 @@ declare const CATALOG_VERSION = "0.0.2";
  * the guard handles a missing date, and a wrong date that looks right is worse than
  * a missing one.
  */
-declare const CATALOG_PUBLISHED_AT = "2026-09-07T12:44:09Z";
+declare const CATALOG_PUBLISHED_AT = "2026-09-15T07:13:18Z";
 
 /**
  * The corpus itself — rules only, and **deliberately free of zod**.

package/dist/guardrails.js

@@ -20,7 +20,7 @@ import {
   mentions,
   pwsh,
   rulesForPack
-} from "./chunk-IQBU26ZF.js";
+} from "./chunk-DBB7HO4T.js";
 export {
   CATALOG_PUBLISHED_AT,
   CATALOG_VERSION,