@pikku/inspector 0.12.103 → 0.12.106

package/dist/utils/post-process.d.ts

@@ -1,7 +1,7 @@
-import type { InspectorState, InspectorLogger, InspectorOptions } from "../types.js";
-import type { PermissionMetadata } from "@pikku/core/function";
-import type { MiddlewareMetadata } from "@pikku/core/middleware";
-import type ts from "typescript";
+import type { InspectorState, InspectorLogger, InspectorOptions } from '../types.js';
+import type { PermissionMetadata } from '@pikku/core/function';
+import type { MiddlewareMetadata } from '@pikku/core/middleware';
+import type ts from 'typescript';
 /**
  * Stamp the inspected authorize/callbacks service set onto the generated auth
  * handler's function meta.
@@ -15,7 +15,7 @@ import type ts from "typescript";
  * onto the handler meta. Re-derived every inspect and ordered BEFORE
  * `aggregateRequiredServices` so it flows into `requiredServices`.
  */
-export declare function stampAuthHandlerServices(state: InspectorState | Omit<InspectorState, "typesLookup">): void;
+export declare function stampAuthHandlerServices(state: InspectorState | Omit<InspectorState, 'typesLookup'>): void;
 /**
  * Helper to extract wire-level middleware/permission names from metadata.
  * Only extracts type:'wire' variants (individual middleware/permissions).
@@ -29,12 +29,12 @@ export declare function extractWireNames(list?: Array<MiddlewareMetadata | Permi
  * Note: usedFunctions, usedMiddleware, and usedPermissions are tracked directly
  * in the add-* methods during AST traversal for efficiency.
  */
-export declare function aggregateRequiredServices(state: InspectorState | Omit<InspectorState, "typesLookup">): void;
-export declare function validateSecretOverrides(logger: InspectorLogger, state: InspectorState | Omit<InspectorState, "typesLookup">): void;
-export declare function validateAddonUses(logger: InspectorLogger, state: InspectorState | Omit<InspectorState, "typesLookup">): void;
-export declare function validateAddonContentGrants(logger: InspectorLogger, state: InspectorState | Omit<InspectorState, "typesLookup">): void;
-export declare function validateCredentialOverrides(logger: InspectorLogger, state: InspectorState | Omit<InspectorState, "typesLookup">): void;
-export declare function validateVariableOverrides(logger: InspectorLogger, state: InspectorState | Omit<InspectorState, "typesLookup">): void;
+export declare function aggregateRequiredServices(state: InspectorState | Omit<InspectorState, 'typesLookup'>): void;
+export declare function validateSecretOverrides(logger: InspectorLogger, state: InspectorState | Omit<InspectorState, 'typesLookup'>): void;
+export declare function validateAddonUses(logger: InspectorLogger, state: InspectorState | Omit<InspectorState, 'typesLookup'>): void;
+export declare function validateAddonContentGrants(logger: InspectorLogger, state: InspectorState | Omit<InspectorState, 'typesLookup'>): void;
+export declare function validateCredentialOverrides(logger: InspectorLogger, state: InspectorState | Omit<InspectorState, 'typesLookup'>): void;
+export declare function validateVariableOverrides(logger: InspectorLogger, state: InspectorState | Omit<InspectorState, 'typesLookup'>): void;
 /**
  * Every wired addon must be installed, in the bucket matching how it is used.
  *
@@ -58,14 +58,14 @@ export declare function validateVariableOverrides(logger: InspectorLogger, state
  * up in `dependencies`. Asking the resolver is the only question that matches
  * what the loader will actually do.
  */
-export declare function validateRemoteAddonDependencies(logger: InspectorLogger, state: InspectorState | Omit<InspectorState, "typesLookup">): void;
+export declare function validateRemoteAddonDependencies(logger: InspectorLogger, state: InspectorState | Omit<InspectorState, 'typesLookup'>): void;
 /**
  * The auth a `wireRemoteAddon` consumer binds must reference a slot the consumer
  * actually declares: a `credentialId` must be a wired credential, a `secretId`
  * a wired secret. A custom `resolve()` and a public (omitted) surface are not
  * statically checkable and are left to runtime.
  */
-export declare function validateRemoteAddonAuth(logger: InspectorLogger, state: InspectorState | Omit<InspectorState, "typesLookup">): void;
+export declare function validateRemoteAddonAuth(logger: InspectorLogger, state: InspectorState | Omit<InspectorState, 'typesLookup'>): void;
 export declare function computeResolvedIOTypes(state: InspectorState): void;
 export declare function computeMiddlewareGroupsMeta(state: InspectorState): void;
 export declare function computePermissionsGroupsMeta(state: InspectorState): void;
@@ -90,11 +90,11 @@ export declare function validateSchemaReferences(logger: InspectorLogger, state:
  * A model is either concrete (`provider/model`) or an alias, which must appear
  * in the `models` table from pikku.config.json.
  */
-export declare function validateAgentModels(logger: InspectorLogger, state: InspectorState | Omit<InspectorState, "typesLookup">, modelAliases?: Record<string, string>): void;
+export declare function validateAgentModels(logger: InspectorLogger, state: InspectorState | Omit<InspectorState, 'typesLookup'>, modelAliases?: Record<string, string>): void;
 /**
  * Scenarios are pure stories of remote RPCs (same rule as client-side CLI
  * renderers): the func may only destructure logger/config — everything else
- * must go through actor steps so the flow runs against the TARGET
+ * must go through virtual user steps so the flow runs against the TARGET
  * environment, never local services.
  *
  * This runs in post-processing rather than in `addWorkflow` because
@@ -102,17 +102,17 @@ export declare function validateAgentModels(logger: InspectorLogger, state: Insp
  * `addFunctions` (`visitFunctions`) has populated `state.functions.meta` — so
  * the check read `undefined` there and never fired.
  */
-export declare function validateScenarioServices(logger: InspectorLogger, state: InspectorState | Omit<InspectorState, "typesLookup">): void;
+export declare function validateScenarioServices(logger: InspectorLogger, state: InspectorState | Omit<InspectorState, 'typesLookup'>): void;
 /**
- * Does this step's prose open by naming the actor who is already its subject?
+ * Does this step's prose open by naming the virtual user who is already its subject?
  *
- * `composeStepProse` renders the actor as the sentence's subject, so a step
+ * `composeStepProse` renders the virtual user as the sentence's subject, so a step
  * authored as `'sam' creates the client` reads "Given sam 'sam' creates the
- * client". Only the subject position counts: a persona keyed after a role noun
+ * client". Only the subject position counts: a virtual user keyed after a role noun
  * ("admin") must still be able to say "creates the admin client", and naming
  * someone mid-sentence — "sends sam an invite" — is ordinary prose.
  */
-export declare const proseOpensWithActor: (prose: string, actor: string) => boolean;
+export declare const proseOpensWithVirtualUser: (prose: string, virtualUser: string) => boolean;
 /**
  * Walk every scenario step, wherever it is nested, and validate the two things
  * that can only be known once both the workflow meta and the function meta
@@ -120,9 +120,9 @@ export declare const proseOpensWithActor: (prose: string, actor: string) => bool
  *
  * - the step target must be a static string literal (PKU678) — otherwise it
  *   can't be bundled, typed or drawn;
- * - a step that runs as a persona must be given one (PKU677) — declared by
- *   `actor: true`, or implied by a `browser` binding, since the browser context
- *   signs in as that persona. It is checked statically even though a browser
+ * - a step that runs as a virtual user must be given one (PKU677) — declared by
+ *   `virtualUser: true`, or implied by a `browser` binding, since the browser context
+ *   signs in as that virtual user. It is checked statically even though a browser
  *   binding only runs on a browser run: a step that can never be driven by a
  *   human is a latent failure, not a passing default run.
  * - a scenario written as a step ladder must assert something (PKU680).
@@ -130,7 +130,7 @@ export declare const proseOpensWithActor: (prose: string, actor: string) => bool
  * It also marks the step's function as used, so `scenario run` boots the
  * singletons the step actually needs.
  */
-export declare function validateScenarioSteps(logger: InspectorLogger, state: InspectorState | Omit<InspectorState, "typesLookup">): void;
+export declare function validateScenarioSteps(logger: InspectorLogger, state: InspectorState | Omit<InspectorState, 'typesLookup'>): void;
 /**
  * Reports scenarios that no `pikkuFeature` lists.
  *
@@ -155,7 +155,7 @@ export declare function validateScenarioSteps(logger: InspectorLogger, state: In
  * the check reports it then and downgrades to a warn naming both sides, rather
  * than accusing a scenario that may well be in that array.
  */
-export declare function validateScenarioFeatures(logger: InspectorLogger, state: InspectorState | Omit<InspectorState, "typesLookup">): void;
+export declare function validateScenarioFeatures(logger: InspectorLogger, state: InspectorState | Omit<InspectorState, 'typesLookup'>): void;
 /**
  * A `pikkuWorkflowGraph` node that references the `graph:` namespace (e.g.
  * `graph:editFields`) needs @pikku/addon-graph wired — otherwise the RPC never
@@ -180,7 +180,7 @@ export declare function validateSchemaWiringSeparation(logger: InspectorLogger,
  * a name the omit does not cover. A name-based rule misses this; the type does
  * not.
  */
-export declare function validateNoSecretAliasServices(logger: InspectorLogger, checker: ts.TypeChecker, state: InspectorState | Omit<InspectorState, "typesLookup">): void;
+export declare function validateNoSecretAliasServices(logger: InspectorLogger, checker: ts.TypeChecker, state: InspectorState | Omit<InspectorState, 'typesLookup'>): void;
 /**
  * Reports secret reads the catalogue does not account for.
  *
@@ -193,8 +193,8 @@ export declare function validateNoSecretAliasServices(logger: InspectorLogger, c
  * deployment is asked for the client id and secret every connect flow needs
  * without an author restating a shape the runtime already fixes.
  */
-export declare function registerDerivedOAuth2AppSecrets(state: InspectorState | Omit<InspectorState, "typesLookup">): void;
-export declare function validateSecretUsage(logger: InspectorLogger, state: InspectorState | Omit<InspectorState, "typesLookup">): void;
+export declare function registerDerivedOAuth2AppSecrets(state: InspectorState | Omit<InspectorState, 'typesLookup'>): void;
+export declare function validateSecretUsage(logger: InspectorLogger, state: InspectorState | Omit<InspectorState, 'typesLookup'>): void;
 export declare function computeDiagnostics(state: InspectorState): void;
 /**
  * Validates that every scope referenced by a function is declared via
@@ -203,7 +203,7 @@ export declare function computeDiagnostics(state: InspectorState): void;
  * A `*` suffix is a wildcard requirement: `admin:*` requires the `admin` scope
  * to be declared, and grants its whole subtree.
  */
-export declare function validateScopeReferences(logger: InspectorLogger, state: InspectorState | Omit<InspectorState, "typesLookup">): void;
+export declare function validateScopeReferences(logger: InspectorLogger, state: InspectorState | Omit<InspectorState, 'typesLookup'>): void;
 /**
  * Resolves every `tools:` entry on every agent and reports the ones that do not
  * land on a real function, or that land on one with nothing to tell the model.
@@ -220,7 +220,7 @@ export declare function validateScopeReferences(logger: InspectorLogger, state:
  * quality loss rather than a failure. A title deliberately does not satisfy it —
  * a title labels a tool in a UI, it does not tell a model when to reach for it.
  */
-export declare function validateAgentToolReferences(logger: InspectorLogger, state: InspectorState | Omit<InspectorState, "typesLookup">, options?: InspectorOptions): void;
+export declare function validateAgentToolReferences(logger: InspectorLogger, state: InspectorState | Omit<InspectorState, 'typesLookup'>, options?: InspectorOptions): void;
 /**
  * Validates that every scorer an agent asks to be graded by exists.
  *
@@ -228,7 +228,7 @@ export declare function validateAgentToolReferences(logger: InspectorLogger, sta
  * that has already answered the user — which means a typo would otherwise cost
  * nothing visible and simply grade nothing, forever.
  */
-export declare function validateAgentScorerReferences(logger: InspectorLogger, state: InspectorState | Omit<InspectorState, "typesLookup">): void;
+export declare function validateAgentScorerReferences(logger: InspectorLogger, state: InspectorState | Omit<InspectorState, 'typesLookup'>): void;
 /**
  * Validates that every scope granted by a system role is declared via
  * `defineScope`. Runs after all visitors, so declaration order does not matter.
@@ -236,21 +236,21 @@ export declare function validateAgentScorerReferences(logger: InspectorLogger, s
  * The same rule functions get, for a sharper reason: a role granting an
  * undeclared scope is not merely useless, it is *invisibly* useless. No
  * function checks the scope, so the role appears to work — every call a
- * persona holding it makes succeeds or fails for unrelated reasons, and the
+ * virtual user holding it makes succeeds or fails for unrelated reasons, and the
  * authorization boundary it was written to describe is never exercised.
  *
  * A `*` suffix grants a subtree; the node it hangs off must exist.
  */
-export declare function validateSystemRoleScopes(logger: InspectorLogger, state: InspectorState | Omit<InspectorState, "typesLookup">): void;
+export declare function validateSystemRoleScopes(logger: InspectorLogger, state: InspectorState | Omit<InspectorState, 'typesLookup'>): void;
 /**
- * Validates that every role a persona names is declared with
+ * Validates that every role a virtual user names is declared with
  * `defineSystemRole`. Runs after all visitors, so declaration order does not
  * matter.
  *
  * Custom roles are refused rather than tolerated. A role composed in the
  * console does not exist at build time and can be deleted after it, so a
- * persona pinned to one silently stops testing what it claims to — and the
+ * virtual user pinned to one silently stops testing what it claims to — and the
  * symptom is a scatter of 403s that read like authorization findings rather
  * than like a deleted role.
  */
-export declare function validatePersonaRoles(logger: InspectorLogger, state: InspectorState | Omit<InspectorState, "typesLookup">): void;
+export declare function validateVirtualUserRoles(logger: InspectorLogger, state: InspectorState | Omit<InspectorState, 'typesLookup'>): void;