@nimbus-dev/sdk
Advanced tools
| /** @moduleStability stable */ | ||
| /** The nine built-in read-only agents exposed over `agents.*` IPC. */ | ||
| /** | ||
| * The built-in agents whose brief SHAPES this SDK models — NOT the gateway's roster. | ||
| * | ||
| * These are the nine agents `brief-types` describes, `BRIEF_GUARDS` narrows and | ||
| * `BriefFor<A>` resolves. The gateway serves more: `ownership`, `premortem`, `glossary`, | ||
| * `decisions` and `negotiate` are all reachable over `agents.*` IPC and are deliberately | ||
| * absent here, because a name earns its place on this list only once its brief type, its | ||
| * guard and its guard fixture exist. Lagging the gateway is the intended state, not a bug | ||
| * to be closed by appending names. | ||
| * | ||
| * So do not read this as "the agents Nimbus has", and do not build a picker, a router or a | ||
| * capability list from it — each of those would silently omit five shipping agents. The | ||
| * gateway derives its own roster from its handler map and that is the authority. This SDK | ||
| * cannot import the gateway, so nothing here can detect the gap; this comment is the only | ||
| * protection against it. | ||
| * | ||
| * Its previous wording — "the nine built-in read-only agents exposed over `agents.*` IPC" | ||
| * — was true when written and went false across five agent additions without anything | ||
| * failing, which is what prompted the rewrite. | ||
| */ | ||
| export declare const AGENT_NAMES: readonly ["expert", "impact", "catchup", "ghost", "conflicts", "huddle", "janitor", "preflight", "why"]; | ||
@@ -4,0 +23,0 @@ export type AgentName = (typeof AGENT_NAMES)[number]; |
@@ -1,1 +0,1 @@ | ||
| {"version":3,"file":"agent-names.d.ts","sourceRoot":"","sources":["../../src/agents/agent-names.ts"],"names":[],"mappings":"AAAA,8BAA8B;AAE9B,sEAAsE;AACtE,eAAO,MAAM,WAAW,YACtB,QAAQ,EACR,QAAQ,EACR,SAAS,EACT,OAAO,EACP,WAAW,EACX,QAAQ,EACR,SAAS,EACT,WAAW,EACX,KAAK,CACG,CAAC;AAEX,MAAM,MAAM,SAAS,GAAG,CAAC,OAAO,WAAW,CAAC,CAAC,MAAM,CAAC,CAAC;AAErD;;;;;GAKG;AACH,eAAO,MAAM,UAAU;qBACb,QAAQ;qBACR,QAAQ;sBACP,SAAS;oBACX,OAAO;wBACH,UAAU;qBACb,QAAQ;sBACP,SAAS;wBACP,WAAW;kBACjB,KAAK;CACkC,CAAC"} | ||
| {"version":3,"file":"agent-names.d.ts","sourceRoot":"","sources":["../../src/agents/agent-names.ts"],"names":[],"mappings":"AAAA,8BAA8B;AAE9B;;;;;;;;;;;;;;;;;;;GAmBG;AACH,eAAO,MAAM,WAAW,YACtB,QAAQ,EACR,QAAQ,EACR,SAAS,EACT,OAAO,EACP,WAAW,EACX,QAAQ,EACR,SAAS,EACT,WAAW,EACX,KAAK,CACG,CAAC;AAEX,MAAM,MAAM,SAAS,GAAG,CAAC,OAAO,WAAW,CAAC,CAAC,MAAM,CAAC,CAAC;AAErD;;;;;GAKG;AACH,eAAO,MAAM,UAAU;qBACb,QAAQ;qBACR,QAAQ;sBACP,SAAS;oBACX,OAAO;wBACH,UAAU;qBACb,QAAQ;sBACP,SAAS;wBACP,WAAW;kBACjB,KAAK;CACkC,CAAC"} |
| /** @moduleStability stable */ | ||
| /** The nine built-in read-only agents exposed over `agents.*` IPC. */ | ||
| /** | ||
| * The built-in agents whose brief SHAPES this SDK models — NOT the gateway's roster. | ||
| * | ||
| * These are the nine agents `brief-types` describes, `BRIEF_GUARDS` narrows and | ||
| * `BriefFor<A>` resolves. The gateway serves more: `ownership`, `premortem`, `glossary`, | ||
| * `decisions` and `negotiate` are all reachable over `agents.*` IPC and are deliberately | ||
| * absent here, because a name earns its place on this list only once its brief type, its | ||
| * guard and its guard fixture exist. Lagging the gateway is the intended state, not a bug | ||
| * to be closed by appending names. | ||
| * | ||
| * So do not read this as "the agents Nimbus has", and do not build a picker, a router or a | ||
| * capability list from it — each of those would silently omit five shipping agents. The | ||
| * gateway derives its own roster from its handler map and that is the authority. This SDK | ||
| * cannot import the gateway, so nothing here can detect the gap; this comment is the only | ||
| * protection against it. | ||
| * | ||
| * Its previous wording — "the nine built-in read-only agents exposed over `agents.*` IPC" | ||
| * — was true when written and went false across five agent additions without anything | ||
| * failing, which is what prompted the rewrite. | ||
| */ | ||
| export const AGENT_NAMES = [ | ||
@@ -4,0 +23,0 @@ "expert", |
@@ -1,1 +0,1 @@ | ||
| {"version":3,"file":"agent-names.js","sourceRoot":"","sources":["../../src/agents/agent-names.ts"],"names":[],"mappings":"AAAA,8BAA8B;AAE9B,sEAAsE;AACtE,MAAM,CAAC,MAAM,WAAW,GAAG;IACzB,QAAQ;IACR,QAAQ;IACR,SAAS;IACT,OAAO;IACP,WAAW;IACX,QAAQ;IACR,SAAS;IACT,WAAW;IACX,KAAK;CACG,CAAC;AAIX;;;;;GAKG;AACH,MAAM,CAAC,MAAM,UAAU,GAAG;IACxB,MAAM,EAAE,QAAQ;IAChB,MAAM,EAAE,QAAQ;IAChB,OAAO,EAAE,SAAS;IAClB,KAAK,EAAE,OAAO;IACd,SAAS,EAAE,UAAU;IACrB,MAAM,EAAE,QAAQ;IAChB,OAAO,EAAE,SAAS;IAClB,SAAS,EAAE,WAAW;IACtB,GAAG,EAAE,KAAK;CACkC,CAAC"} | ||
| {"version":3,"file":"agent-names.js","sourceRoot":"","sources":["../../src/agents/agent-names.ts"],"names":[],"mappings":"AAAA,8BAA8B;AAE9B;;;;;;;;;;;;;;;;;;;GAmBG;AACH,MAAM,CAAC,MAAM,WAAW,GAAG;IACzB,QAAQ;IACR,QAAQ;IACR,SAAS;IACT,OAAO;IACP,WAAW;IACX,QAAQ;IACR,SAAS;IACT,WAAW;IACX,KAAK;CACG,CAAC;AAIX;;;;;GAKG;AACH,MAAM,CAAC,MAAM,UAAU,GAAG;IACxB,MAAM,EAAE,QAAQ;IAChB,MAAM,EAAE,QAAQ;IAChB,OAAO,EAAE,SAAS;IAClB,KAAK,EAAE,OAAO;IACd,SAAS,EAAE,UAAU;IACrB,MAAM,EAAE,QAAQ;IAChB,OAAO,EAAE,SAAS;IAClB,SAAS,EAAE,WAAW;IACtB,GAAG,EAAE,KAAK;CACkC,CAAC"} |
+1
-1
| { | ||
| "name": "@nimbus-dev/sdk", | ||
| "version": "1.30.0", | ||
| "version": "1.30.1", | ||
| "license": "MIT", | ||
@@ -5,0 +5,0 @@ "repository": { |
@@ -5,3 +5,8 @@ import { describe, expect, test } from "bun:test"; | ||
| describe("agent names", () => { | ||
| test("all nine agents are listed", () => { | ||
| // A golden over the MODELLED subset, not over the gateway's roster. It catches an | ||
| // unintended edit to the list; it cannot catch the list falling behind the gateway, | ||
| // because this package cannot import the gateway to ask. Its old name — "all nine agents | ||
| // are listed" — claimed the second thing while doing the first, and stayed green across | ||
| // the five agent additions that made the claim false. | ||
| test("the modelled subset is exactly these nine", () => { | ||
| expect([...AGENT_NAMES]).toEqual([ | ||
@@ -8,0 +13,0 @@ "expert", |
| /** @moduleStability stable */ | ||
| /** The nine built-in read-only agents exposed over `agents.*` IPC. */ | ||
| /** | ||
| * The built-in agents whose brief SHAPES this SDK models — NOT the gateway's roster. | ||
| * | ||
| * These are the nine agents `brief-types` describes, `BRIEF_GUARDS` narrows and | ||
| * `BriefFor<A>` resolves. The gateway serves more: `ownership`, `premortem`, `glossary`, | ||
| * `decisions` and `negotiate` are all reachable over `agents.*` IPC and are deliberately | ||
| * absent here, because a name earns its place on this list only once its brief type, its | ||
| * guard and its guard fixture exist. Lagging the gateway is the intended state, not a bug | ||
| * to be closed by appending names. | ||
| * | ||
| * So do not read this as "the agents Nimbus has", and do not build a picker, a router or a | ||
| * capability list from it — each of those would silently omit five shipping agents. The | ||
| * gateway derives its own roster from its handler map and that is the authority. This SDK | ||
| * cannot import the gateway, so nothing here can detect the gap; this comment is the only | ||
| * protection against it. | ||
| * | ||
| * Its previous wording — "the nine built-in read-only agents exposed over `agents.*` IPC" | ||
| * — was true when written and went false across five agent additions without anything | ||
| * failing, which is what prompted the rewrite. | ||
| */ | ||
| export const AGENT_NAMES = [ | ||
@@ -5,0 +24,0 @@ "expert", |
URL strings
Supply chain riskPackage contains fragments of external URLs or IP addresses, which the package may be accessing at runtime.
URL strings
Supply chain riskPackage contains fragments of external URLs or IP addresses, which the package may be accessing at runtime.
879698
0.44%16907
0.37%