@ai-outfitter/outfitter 0.11.0 → 1.0.2

package/docs/documentation/usecases/persona-reviews.md

@@ -1,173 +1,167 @@
 # Persona Reviews
 
-A persona review catalog is a shared setup source that publishes profiles representing the kinds of people who might use a product, service, internal tool, or documentation site. Teams can launch these personas to get structured feedback on docs, onboarding, website copy, setup flows, and UX before asking real prospects or customers to spend time on a review.
+A persona review catalog gathers structured feedback on a product, docs, onboarding flow, or UX from the points of view of the people who might use it — before asking real prospects to spend time. It uses the [persona convention](../personas.md): **one base review agent** plus a **directory of persona description documents**, run once per document.
 
-The example below uses Outfitter itself as the product being reviewed, but the pattern is meant for your own product. Replace the persona files, concerns, and review prompts with the customer types you care about.
+There is no `personas:` map and no agent per customer type. The review rules live in a single agent; each persona is a cheap markdown file you feed it as input.
 
 ```text
-customer-persona-reviews/
+customer-review/                 # standalone .agents repo; root is the payload
+  agents/
+    reviewer/agent.md            # the base review agent
   settings.yml
-  personas/
-    base-customer-persona.yml
-    founder-operator.yml
-    staff-engineer.yml
-    engineering-manager.yml
-    platform-lead.yml
-    agency-consultant.yml
+docs/user-personas/
+  roles/                         # reusable job archetypes (shared segment priorities)
+    staff-engineer.md
+    founder-operator.md
+    platform-lead.md
+  individuals/                   # specific named people, each naming one or more roles
+    marcus-bell.md               # roles: [staff-engineer]
+    dana-okafor.md               # roles: [founder-operator]
+    priya-nair.md                # roles: [platform-lead]
 ```
 
-## Catalog settings
+Personas come in two kinds of file, and a review **mixes and matches** them: a **role** carries the priorities everyone in a customer segment shares, and an **individual** is one named person who inherits one or more roles and adds their own demographics and voice. Keep roles reusable and individuals concrete, and you can cover a lot of viewpoints from a small set of files.
 
-```yaml
-# customer-persona-reviews/settings.yml
-profile_sources:
-  - path: ./personas
-    only:
-      - founder-operator
-      - staff-engineer
-      - engineering-manager
-      - platform-lead
-      - agency-consultant
-```
+## Settings
 
-## Shared base profile
+Settings only names the default agent and where resources resolve from — no persona list:
 
 ```yaml
-# personas/base-customer-persona.yml
-id: base-customer-persona
-label: Customer Persona Base
-template: true
-description: Shared rules for reviewing an artifact from a customer persona's point of view.
-controls:
-  append_system_prompt: |
-    Review as the assigned customer persona. Read or experience the provided artifact
-    from that persona's point of view: docs, screenshots, website, prototype, product
-    flow, or onboarding path. Distinguish evidence from assumptions, cite the exact
-    page or UI moment that shaped your reaction, and do not invent real customer research.
+# settings.yml
+default_agent: reviewer
 ```
 
-## Persona profiles
+## The base review agent
 
-Persona review catalogs SHOULD make each potential customer's job, anxieties, buying triggers, and expected feedback shape explicit. These examples use Outfitter as the reviewed product so the pattern is concrete; replace the product references with your own product, audience, and UX.
+One agent holds the review method and the output shape. It does not name any customer type; it reads the persona files it is told to adopt, in order.
 
-```yaml
-# personas/founder-operator.yml
-id: founder-operator
-label: Founder Operator
-description: Reviews whether a product helps a hands-on founder get leverage quickly.
-inherits:
-  - base-customer-persona
-controls:
-  provider: anthropic
-  model: anthropic/claude-sonnet-4
-  thinking: high
-  append_system_prompt: |
-    You are a technical founder who writes product specs, edits docs, ships small
-    features, and manages a thin team. For this example, review Outfitter as the
-    product. Say whether the first hour feels obviously valuable. Flag jargon, setup
-    friction, unclear pricing or trust boundaries, and anything that delays the first
-    useful outcome.
 ```
-
-```yaml
-# personas/staff-engineer.yml
-id: staff-engineer
-label: Staff Engineer
-description: Reviews whether a product is credible for complex technical work.
-inherits:
-  - base-customer-persona
-controls:
-  provider: anthropic
-  model: anthropic/claude-sonnet-4
-  thinking: high
-  append_system_prompt: |
-    You are a staff engineer responsible for large codebases, architecture decisions,
-    reviews, and cross-team technical quality. For this example, review Outfitter as
-    the product. Say whether the docs explain how the product improves real engineering
-    work. Flag missing examples, weak verification paths, and claims that need evidence.
+<!-- agents/reviewer/agent.md -->
+---
+name: reviewer
+description: Reviews an artifact from the point of view of an assigned customer persona.
+---
+
+Adopt the persona files named in your instructions, in order: a role file
+establishes the segment's priorities, and an individual file layers that
+person's demographics and voice on top (later files refine earlier ones). If
+an individual names roles in its frontmatter, treat those as its baseline.
+
+Read or experience the provided artifact from that persona's point of view:
+docs, screenshots, website, prototype, product flow, or onboarding path.
+Distinguish evidence from assumptions, cite the exact page or UI moment that
+shaped your reaction, and do not invent real customer research.
+
+Return feedback as: persona, artifact reviewed, first impression, top blocker,
+strongest value signal, confusing language, suggested change, and confidence.
+If you need more context, ask for the smallest missing artifact.
 ```
 
-```yaml
-# personas/engineering-manager.yml
-id: engineering-manager
-label: Engineering Manager
-description: Reviews whether a product helps a team standardize work safely.
-inherits:
-  - base-customer-persona
-controls:
-  provider: openai
-  model: openai/gpt-4.1
-  thinking: medium
-  append_system_prompt: |
-    You manage engineers with different tool habits. For this example, review Outfitter
-    as the product. Say whether team defaults, onboarding, review expectations, and
-    governance are understandable. Flag anything that makes rollout, support, training,
-    or risk ownership unclear.
-```
+## Roles: reusable job archetypes
+
+A role captures what everyone in a customer segment shares — the job, its goals, anxieties, buying triggers, and what its feedback focuses on — with no personal detail. Roles are reused across many individuals.
 
-```yaml
-# personas/platform-lead.yml
-id: platform-lead
-label: Platform Lead
-description: Reviews whether a product can fit into internal developer platform workflows.
-inherits:
-  - base-customer-persona
-controls:
-  provider: anthropic
-  model: anthropic/claude-opus-4
-  thinking: xhigh
-  append_system_prompt: |
-    You own internal developer tooling, CI, secrets, and fleet-wide standards. For this
-    example, review Outfitter as the product. Focus on trust boundaries, credential
-    handling, catalog governance, private repo assumptions, reproducibility, and
-    operational failure modes. Prioritize risks that would block enterprise rollout.
+```
+<!-- docs/user-personas/roles/staff-engineer.md -->
+---
+kind: role
+title: Staff Engineer
+segment: large-eng-org
+goals: [reduce cross-team friction, raise technical quality, adopt tools that survive scrutiny]
+anxieties: [tools that demo well but fail on a real codebase, unproven claims]
+buying_triggers: [credible examples, verifiable outcomes, a clean migration path]
+feedback_focus: [depth, verification paths, missing examples, evidence behind claims]
+---
+
+Responsible for large codebases, architecture decisions, reviews, and
+cross-team technical quality. Cares whether the docs explain how the product
+improves real engineering work. Flags missing examples, weak verification
+paths, and claims that need evidence.
 ```
 
-```yaml
-# personas/agency-consultant.yml
-id: agency-consultant
-label: Agency Consultant
-description: Reviews whether a product helps switch between multiple client contexts cleanly.
-inherits:
-  - base-customer-persona
-controls:
-  provider: openai
-  model: openai/gpt-4.1-mini
-  thinking: low
-  append_system_prompt: |
-    You work across multiple client contexts and need repeatable setup without leaking
-    one client's context into another. For this example, review Outfitter as the product.
-    Say whether the docs and UX make isolation, project settings, and switching contexts
-    obvious.
+```
+<!-- docs/user-personas/roles/founder-operator.md -->
+---
+kind: role
+title: Founder-operator
+segment: seed-stage-startup
+goals: [ship weekly, keep the team small, reach the next milestone before the runway ends]
+anxieties: [tool sprawl, hidden pricing, time lost to setup]
+buying_triggers: [obvious value in the first hour, no credit card to try]
+feedback_focus: [time-to-first-value, jargon, trust boundaries, pricing clarity]
+---
+
+A hands-on founder who writes product specs, edits docs, ships small features,
+and manages a thin team. Cares whether the first hour feels obviously valuable.
 ```
 
-## Review workflows
+## Individuals: named people who inherit roles
 
-A persona review can inspect static docs or interact with a running UX. The prompt should say which artifact is under review and what kind of feedback is useful. For your own product, swap in your own docs, prototype URL, screenshots, local app, or onboarding flow.
+An individual is one concrete person — with the demographics a [Lean Canvas](https://leanstack.com/lean-canvas) customer segment gets — who names one or more roles to inherit and then adds their own attributes and voice. The named person **mixes and matches** roles: usually one, but a founder who also runs the platform can list both.
 
-```text
-Read README.md, docs/getting-started.md, and docs/pricing.md for <your product>.
-As the staff-engineer persona, explain where the product feels credible, where it feels
-underspecified, and what one example would most improve your confidence.
+```
+<!-- docs/user-personas/individuals/marcus-bell.md -->
+---
+kind: individual
+name: Marcus Bell
+roles: [staff-engineer]
+born: 1985-11-02
+location: Seattle, WA
+household_income: 265000
+education: MS Computer Engineering
+employer: ~400-engineer fintech
+hobbies: [rock climbing, sci-fi novels, restoring old synths]
+skills: [distributed systems, code review, architecture, mentoring]
+tone: dry, skeptical, cites sources
+---
+
+Reads new tooling the way he reads a design doc: looking for the failure mode
+first. Warm once convinced, but will not take a benchmark on faith.
 ```
 
-```text
-Browse <your product>'s local documentation site and try the first-run setup flow.
-As the founder-operator persona, report the first confusing moment, the first moment
-that felt valuable, and whether you would keep using the product after setup.
+```
+<!-- docs/user-personas/individuals/dana-okafor.md -->
+---
+kind: individual
+name: Dana Okafor
+roles: [founder-operator, platform-lead] # mixes two roles
+born: 1989-03-14
+location: Austin, TX
+household_income: 180000
+education: BS Computer Science
+employer: 6-person seed-stage startup (also the de facto platform owner)
+hobbies: [trail running, home espresso, mechanical keyboards]
+skills: [product specs, TypeScript, fundraising, hiring]
+tone: fast, pragmatic, allergic to jargon
+---
+
+Wears the founder and the platform hat at once, so she weighs first-hour value
+against fleet-wide safety in the same breath. Impatient with setup friction.
 ```
 
-## Review output pattern
+Keep the role attribute set consistent so reviews stay comparable, and let individuals vary freely in demographics and tone. Add more roles (`platform-lead`, `engineering-manager`, `agency-consultant`) and more individuals the same way.
 
-Persona profiles SHOULD define a repeatable response shape so feedback from different potential customers is comparable.
+## Running the reviews
 
-```yaml
-# personas/founder-operator.yml excerpt
-controls:
-  append_system_prompt: |
-    Return feedback as: persona, artifact reviewed, first impression, top blocker,
-    strongest value signal, confusing language, suggested change, and confidence.
-    If you need more context, ask for the smallest missing artifact.
+Run the base agent once per persona, naming the role and individual files to adopt and the artifact under review:
+
+```bash
+outfitter run reviewer -- --print \
+  "Adopt docs/user-personas/roles/staff-engineer.md refined by \
+   docs/user-personas/individuals/marcus-bell.md. Read README.md, \
+   docs/getting-started.md, and docs/pricing.md, then return the standard \
+   review shape: where the product feels credible, where it feels \
+   underspecified, and the one example that would most improve your confidence."
 ```
 
-This gives a team a reusable customer-persona review catalog: each agent reads docs or experiences a UX from a distinct buyer/user viewpoint, then returns structured feedback without pretending to replace real customer discovery.
+```bash
+outfitter run reviewer -- --print \
+  "Adopt docs/user-personas/individuals/dana-okafor.md and the roles it names. \
+   Browse the local docs site and try the first-run setup flow. Report the \
+   first confusing moment, the first moment that felt valuable, and whether \
+   you would keep using it."
+```
+
+Model and thinking choices — cheaper models for high-volume routing reviews, deeper reasoning for platform-risk reviews — live in the reviewer agent's loadout, or a machine-local override, rather than being duplicated per persona.
+
+Because the base agent fixes the output shape, feedback from every persona document is directly comparable. The result is a reusable customer-persona review catalog that reads docs or experiences a UX from many viewpoints without pretending to replace real customer discovery.

package/docs/philosophy.md

@@ -1,6 +1,6 @@
 # Outfitter Philosophy
 
-Make, share, and switch the profiles your coding agents use — manually or programmatically.
+Make, share, and switch the agent profiles your coding agents use — manually or programmatically. A profile is just an agent and the loadout it composes; there is no separate profile format.
 
 ## Expeditious agents
 
@@ -12,7 +12,7 @@ Tight profiles also make delegation practical. When a role is small and well def
 
 ## Composition over accumulation
 
-The common failure mode is a single, ever-growing agent setup: one configuration that accretes every tool and instruction anyone has ever needed, serving no task particularly well. Outfitter takes the opposite approach. Profiles are small, purpose-built, and composable — you stack a personal baseline, a team convention, and a task-specific role, and switch between combinations as the work changes. Each profile stays sharp because it never has to be everything at once.
+The common failure mode is a single, ever-growing agent setup: one configuration that accretes every tool and instruction anyone has ever needed, serving no task particularly well. Outfitter takes the opposite approach. Agent profiles are small, purpose-built, and composable — you stack a personal baseline, a team convention, and a project-specific role, and switch between agents as the work changes. Each stays sharp because it never has to be everything at once.
 
 ## Individual, team, enterprise
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ai-outfitter/outfitter",
-  "version": "0.11.0",
+  "version": "1.0.2",
   "description": "Profile-oriented wrapper for launching pi, Claude Code, and future agent CLIs with reproducible configuration.",
   "type": "module",
   "repository": {
@@ -26,7 +26,7 @@
     "LICENSE.md"
   ],
   "scripts": {
-    "build": "tsc -p tsconfig.build.json && shx rm -rf dist/schemas && shx mkdir -p dist/schemas && shx cp src/schemas/*.json dist/schemas/ && shx mkdir -p dist/cli/commands/assets && shx cp src/cli/commands/assets/*.txt dist/cli/commands/assets/ && shx chmod +x dist/cli.js",
+    "build": "tsc -p tsconfig.build.json && shx rm -rf dist/schemas && shx mkdir -p dist/schemas && shx cp src/schemas/*.json dist/schemas/ && shx chmod +x dist/cli.js",
     "prepare": "npm run build",
     "prepack": "node scripts/sync-package-assets.mjs",
     "dev_install": "node scripts/dev-install.mjs",
@@ -60,7 +60,7 @@
     "vitest": "^4.1.7"
   },
   "engines": {
-    "node": ">=22.19.0"
+    "node": ">=24.18.0 <25"
   },
   "keywords": [
     "agent",

package/src/schemas/agent.schema.json

@@ -0,0 +1,48 @@
+{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "$id": "https://outfitter.dev/schemas/agent.schema.json",
+  "title": "Outfitter agent definition frontmatter",
+  "type": "object",
+  "required": ["name"],
+  "properties": {
+    "name": { "type": "string", "pattern": "^[a-z0-9]+(?:-[a-z0-9]+)*$", "maxLength": 64 },
+    "description": { "type": "string" },
+    "skills": {
+      "$ref": "#/$defs/slugList",
+      "description": "Skill slugs resolved from agents/<name>/skills first, then catalog-wide skills."
+    },
+    "subagents": {
+      "$ref": "#/$defs/slugList",
+      "description": "Agent slugs delegated to. Resolved catalog-wide (a delegate is a shared agent, not nested under agents/<name>)."
+    },
+    "mcp": {
+      "$ref": "#/$defs/slugList",
+      "description": "MCP server ids. Per-agent agents/<name>/mcp.json is discovered and merges by id over the tree-root mcp.json; projection into the run is deferred (adapter parity, #183)."
+    },
+    "extensions": {
+      "$ref": "#/$defs/slugList",
+      "description": "Harness-native extension selections passed through to the launch; no on-disk agent-local namespace."
+    },
+    "plugins": {
+      "$ref": "#/$defs/slugList",
+      "description": "Harness-native plugin selections passed through to the launch; no on-disk agent-local namespace."
+    },
+    "model": { "type": "string", "minLength": 1 },
+    "thinking": { "type": "string", "minLength": 1 },
+    "tools": {
+      "type": "object",
+      "properties": {
+        "allow": { "type": "array", "items": { "type": "string", "minLength": 1 } },
+        "deny": { "type": "array", "items": { "type": "string", "minLength": 1 } }
+      },
+      "additionalProperties": false
+    }
+  },
+  "additionalProperties": true,
+  "$defs": {
+    "slugList": {
+      "type": "array",
+      "items": { "type": "string", "minLength": 1 }
+    }
+  }
+}

package/src/schemas/settings.schema.json

@@ -4,10 +4,14 @@
   "title": "Outfitter settings",
   "type": "object",
   "properties": {
-    "default_profile": { "type": "string", "minLength": 1 },
-    "default_agent": { "enum": ["pi", "claude"] },
+    "default_agent": { "type": "string", "minLength": 1 },
+    "default_harness": { "enum": ["pi", "claude"] },
     "cache_directory": { "type": "string", "minLength": 1 },
-    "profile_export": { "type": "boolean" },
+    "state_persistence": {
+      "type": "object",
+      "description": "Maps adapter-declared state paths to a persistence strategy.",
+      "additionalProperties": { "enum": ["symlink", "discard", "warn", "error", "prompt"] }
+    },
     "startup": {
       "type": "object",
       "description": "Controls Outfitter startup presentation inside launched agents.",
@@ -21,18 +25,37 @@
     },
     "enterprise": {
       "type": "object",
-      "description": "Enterprise governance settings. User-home ~/.outfitter/settings.yml is the source of truth for these controls.",
+      "description": "Enterprise governance settings. User-home ~/.agents/settings.yml is the source of truth for these controls.",
       "properties": {
-        "private_profile_catalogs": {
+        "private_catalogs": {
           "type": "boolean",
-          "description": "Enable confirmed-private GitHub profile catalogs after reviewing the Outfitter Enterprise license or enterprise agreement."
+          "description": "Enable confirmed-private GitHub catalogs after reviewing the Outfitter Enterprise license or enterprise agreement."
         }
       },
       "additionalProperties": false
     },
-    "profile_sources": {
+    "sources": {
       "type": "array",
-      "items": { "$ref": "profile-source.schema.json" }
+      "items": {
+        "type": "object",
+        "oneOf": [
+          {
+            "required": ["path"],
+            "not": {
+              "anyOf": [{ "required": ["uri"] }, { "required": ["github"] }, { "required": ["ref"] }]
+            }
+          },
+          { "required": ["uri"], "not": { "required": ["github"] } },
+          { "required": ["github"], "not": { "required": ["uri"] } }
+        ],
+        "properties": {
+          "path": { "type": "string", "minLength": 1 },
+          "uri": { "type": "string", "minLength": 1 },
+          "github": { "type": "string", "pattern": "^[A-Za-z0-9_.-]+/[A-Za-z0-9_.-]+$" },
+          "ref": { "type": "string", "minLength": 1 }
+        },
+        "additionalProperties": false
+      }
     },
     "remote_settings": {
       "type": "array",
@@ -53,7 +76,7 @@
     },
     "custom_settings": {
       "type": "object",
-      "description": "Arbitrary YAML-compatible values exposed to Outfitter compositeProfile templates as outfitter.custom_settings."
+      "description": "Arbitrary YAML-compatible values exposed to Outfitter composition templates as outfitter.custom_settings."
     }
   },
   "additionalProperties": true

package/dist/agents/AdapterProfileControls.d.ts

@@ -1,21 +0,0 @@
-import type { AppendSystemPromptControl, ProfileControls } from '../profiles/Profile.js';
-export declare const genericControlNames: Set<string>;
-export declare const supportedControlNames: (controls: ReadonlySet<string>) => readonly string[];
-export declare const controlAliases: readonly [{
-    readonly camelCase: "sessionDirectory";
-    readonly snakeCase: "session_directory";
-}, {
-    readonly camelCase: "promptTemplate";
-    readonly snakeCase: "prompt_template";
-}, {
-    readonly camelCase: "systemPrompt";
-    readonly snakeCase: "system_prompt";
-}, {
-    readonly camelCase: "appendSystemPrompt";
-    readonly snakeCase: "append_system_prompt";
-}];
-export declare const mergeAgentSpecificControls: <T extends ProfileControls>(controls: ProfileControls, agentKey: "pi" | "claude") => T;
-export declare const flagValue: (flag: string, value: string | undefined) => readonly string[];
-export declare const repeatFlag: (flag: string, values: readonly string[] | undefined) => readonly string[];
-export declare const repeatFlagValue: (flag: string, value: AppendSystemPromptControl | undefined) => readonly string[];
-export declare const findUnsupportedControlNames: (controls: Readonly<Record<string, unknown>>, supportedControls: ReadonlySet<string>, knownControls?: ReadonlySet<string>) => string[];

package/dist/agents/AdapterProfileControls.js

@@ -1,76 +0,0 @@
-import { mergeLaunchResourceSources, mergeSkillControlSources } from './LaunchResources.js';
-export const genericControlNames = new Set([
-    'model',
-    'provider',
-    'thinking',
-    'environment',
-    'args',
-    'sessionDirectory',
-    'session_directory',
-    'extensions',
-    'skills',
-    'promptTemplate',
-    'prompt_template',
-    'systemPrompt',
-    'system_prompt',
-    'appendSystemPrompt',
-    'append_system_prompt',
-    'deepwork',
-    'pi',
-    'claude',
-]);
-export const supportedControlNames = (controls) => [...controls].filter((controlName) => !controlName.includes('_') && controlName !== 'pi' && controlName !== 'claude');
-export const controlAliases = [
-    { camelCase: 'sessionDirectory', snakeCase: 'session_directory' },
-    { camelCase: 'promptTemplate', snakeCase: 'prompt_template' },
-    { camelCase: 'systemPrompt', snakeCase: 'system_prompt' },
-    { camelCase: 'appendSystemPrompt', snakeCase: 'append_system_prompt' },
-];
-export const mergeAgentSpecificControls = (controls, agentKey) => {
-    const agentControls = controls[agentKey];
-    return {
-        ...controls,
-        ...definedControls(agentControls),
-        environment: { ...controls.environment, ...agentControls?.environment },
-        args: agentControls?.args ?? controls.args,
-        extensions: mergeLaunchResourceSources('extension', controls.extensions, agentControls?.extensions),
-        skills: mergeSkillControlSources(controls.skills, agentControls?.skills),
-    };
-};
-export const flagValue = (flag, value) => value === undefined ? [] : [flag, value];
-export const repeatFlag = (flag, values) => values === undefined ? [] : values.flatMap((value) => [flag, value]);
-export const repeatFlagValue = (flag, value) => {
-    if (value === undefined) {
-        return [];
-    }
-    if (typeof value === 'string') {
-        return [flag, value];
-    }
-    if (!Array.isArray(value)) {
-        return [];
-    }
-    return repeatFlag(flag, value.filter((entry) => typeof entry === 'string'));
-};
-export const findUnsupportedControlNames = (controls, supportedControls, knownControls = genericControlNames) => {
-    const controlNames = new Set(Object.keys(controls));
-    const unsupported = [];
-    for (const { camelCase, snakeCase } of controlAliases) {
-        if (!controlNames.has(camelCase) && !controlNames.has(snakeCase)) {
-            continue;
-        }
-        if (!supportedControls.has(camelCase) && !supportedControls.has(snakeCase)) {
-            unsupported.push(controlNames.has(snakeCase) ? snakeCase : camelCase);
-        }
-        controlNames.delete(camelCase);
-        controlNames.delete(snakeCase);
-    }
-    unsupported.push(...[...controlNames].filter((controlName) => !knownControls.has(controlName) || !supportedControls.has(controlName)));
-    return unsupported;
-};
-const definedControls = (controls) => {
-    if (controls === undefined) {
-        return {};
-    }
-    return Object.fromEntries(Object.entries(controls).filter((entry) => entry[1] !== undefined));
-};
-//# sourceMappingURL=AdapterProfileControls.js.map

package/dist/agents/AdapterProfileControls.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"AdapterProfileControls.js","sourceRoot":"","sources":["../../src/agents/AdapterProfileControls.ts"],"names":[],"mappings":"AAEA,OAAO,EAAE,0BAA0B,EAAE,wBAAwB,EAAE,MAAM,sBAAsB,CAAC;AAE5F,MAAM,CAAC,MAAM,mBAAmB,GAAG,IAAI,GAAG,CAAC;IACzC,OAAO;IACP,UAAU;IACV,UAAU;IACV,aAAa;IACb,MAAM;IACN,kBAAkB;IAClB,mBAAmB;IACnB,YAAY;IACZ,QAAQ;IACR,gBAAgB;IAChB,iBAAiB;IACjB,cAAc;IACd,eAAe;IACf,oBAAoB;IACpB,sBAAsB;IACtB,UAAU;IACV,IAAI;IACJ,QAAQ;CACT,CAAC,CAAC;AAEH,MAAM,CAAC,MAAM,qBAAqB,GAAG,CAAC,QAA6B,EAAqB,EAAE,CACxF,CAAC,GAAG,QAAQ,CAAC,CAAC,MAAM,CAAC,CAAC,WAAW,EAAE,EAAE,CAAC,CAAC,WAAW,CAAC,QAAQ,CAAC,GAAG,CAAC,IAAI,WAAW,KAAK,IAAI,IAAI,WAAW,KAAK,QAAQ,CAAC,CAAC;AAExH,MAAM,CAAC,MAAM,cAAc,GAAG;IAC5B,EAAE,SAAS,EAAE,kBAAkB,EAAE,SAAS,EAAE,mBAAmB,EAAE;IACjE,EAAE,SAAS,EAAE,gBAAgB,EAAE,SAAS,EAAE,iBAAiB,EAAE;IAC7D,EAAE,SAAS,EAAE,cAAc,EAAE,SAAS,EAAE,eAAe,EAAE;IACzD,EAAE,SAAS,EAAE,oBAAoB,EAAE,SAAS,EAAE,sBAAsB,EAAE;CAC9D,CAAC;AAEX,MAAM,CAAC,MAAM,0BAA0B,GAAG,CACxC,QAAyB,EACzB,QAAyB,EACtB,EAAE;IACL,MAAM,aAAa,GAAG,QAAQ,CAAC,QAAQ,CAAC,CAAC;IAEzC,OAAO;QACL,GAAG,QAAQ;QACX,GAAG,eAAe,CAAC,aAAa,CAAC;QACjC,WAAW,EAAE,EAAE,GAAG,QAAQ,CAAC,WAAW,EAAE,GAAG,aAAa,EAAE,WAAW,EAAE;QACvE,IAAI,EAAE,aAAa,EAAE,IAAI,IAAI,QAAQ,CAAC,IAAI;QAC1C,UAAU,EAAE,0BAA0B,CAAC,WAAW,EAAE,QAAQ,CAAC,UAAU,EAAE,aAAa,EAAE,UAAU,CAAC;QACnG,MAAM,EAAE,wBAAwB,CAAC,QAAQ,CAAC,MAAM,EAAE,aAAa,EAAE,MAAM,CAAC;KACpE,CAAC;AACT,CAAC,CAAC;AAEF,MAAM,CAAC,MAAM,SAAS,GAAG,CAAC,IAAY,EAAE,KAAyB,EAAqB,EAAE,CACtF,KAAK,KAAK,SAAS,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC,CAAC,IAAI,EAAE,KAAK,CAAC,CAAC;AAE3C,MAAM,CAAC,MAAM,UAAU,GAAG,CAAC,IAAY,EAAE,MAAqC,EAAqB,EAAE,CACnG,MAAM,KAAK,SAAS,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC,MAAM,CAAC,OAAO,CAAC,CAAC,KAAK,EAAE,EAAE,CAAC,CAAC,IAAI,EAAE,KAAK,CAAC,CAAC,CAAC;AAEvE,MAAM,CAAC,MAAM,eAAe,GAAG,CAAC,IAAY,EAAE,KAA4C,EAAqB,EAAE;IAC/G,IAAI,KAAK,KAAK,SAAS,EAAE,CAAC;QACxB,OAAO,EAAE,CAAC;IACZ,CAAC;IAED,IAAI,OAAO,KAAK,KAAK,QAAQ,EAAE,CAAC;QAC9B,OAAO,CAAC,IAAI,EAAE,KAAK,CAAC,CAAC;IACvB,CAAC;IAED,IAAI,CAAC,KAAK,CAAC,OAAO,CAAC,KAAK,CAAC,EAAE,CAAC;QAC1B,OAAO,EAAE,CAAC;IACZ,CAAC;IAED,OAAO,UAAU,CACf,IAAI,EACJ,KAAK,CAAC,MAAM,CAAC,CAAC,KAAK,EAAmB,EAAE,CAAC,OAAO,KAAK,KAAK,QAAQ,CAAC,CACpE,CAAC;AACJ,CAAC,CAAC;AAEF,MAAM,CAAC,MAAM,2BAA2B,GAAG,CACzC,QAA2C,EAC3C,iBAAsC,EACtC,gBAAqC,mBAAmB,EAC9C,EAAE;IACZ,MAAM,YAAY,GAAG,IAAI,GAAG,CAAC,MAAM,CAAC,IAAI,CAAC,QAAQ,CAAC,CAAC,CAAC;IACpD,MAAM,WAAW,GAAa,EAAE,CAAC;IAEjC,KAAK,MAAM,EAAE,SAAS,EAAE,SAAS,EAAE,IAAI,cAAc,EAAE,CAAC;QACtD,IAAI,CAAC,YAAY,CAAC,GAAG,CAAC,SAAS,CAAC,IAAI,CAAC,YAAY,CAAC,GAAG,CAAC,SAAS,CAAC,EAAE,CAAC;YACjE,SAAS;QACX,CAAC;QAED,IAAI,CAAC,iBAAiB,CAAC,GAAG,CAAC,SAAS,CAAC,IAAI,CAAC,iBAAiB,CAAC,GAAG,CAAC,SAAS,CAAC,EAAE,CAAC;YAC3E,WAAW,CAAC,IAAI,CAAC,YAAY,CAAC,GAAG,CAAC,SAAS,CAAC,CAAC,CAAC,CAAC,SAAS,CAAC,CAAC,CAAC,SAAS,CAAC,CAAC;QACxE,CAAC;QAED,YAAY,CAAC,MAAM,CAAC,SAAS,CAAC,CAAC;QAC/B,YAAY,CAAC,MAAM,CAAC,SAAS,CAAC,CAAC;IACjC,CAAC;IAED,WAAW,CAAC,IAAI,CACd,GAAG,CAAC,GAAG,YAAY,CAAC,CAAC,MAAM,CACzB,CAAC,WAAW,EAAE,EAAE,CAAC,CAAC,aAAa,CAAC,GAAG,CAAC,WAAW,CAAC,IAAI,CAAC,iBAAiB,CAAC,GAAG,CAAC,WAAW,CAAC,CACxF,CACF,CAAC;IAEF,OAAO,WAAW,CAAC;AACrB,CAAC,CAAC;AAEF,MAAM,eAAe,GAAG,CAAC,QAA2C,EAA4B,EAAE;IAChG,IAAI,QAAQ,KAAK,SAAS,EAAE,CAAC;QAC3B,OAAO,EAAE,CAAC;IACZ,CAAC;IAED,OAAO,MAAM,CAAC,WAAW,CAAC,MAAM,CAAC,OAAO,CAAC,QAAQ,CAAC,CAAC,MAAM,CAAC,CAAC,KAAK,EAAE,EAAE,CAAC,KAAK,CAAC,CAAC,CAAC,KAAK,SAAS,CAAC,CAAC,CAAC;AAChG,CAAC,CAAC"}

package/dist/agents/AdapterStatePaths.d.ts

@@ -1,12 +0,0 @@
-import type { Profile } from '../profiles/Profile.js';
-import type { StatePathDeclaration, StatePersistenceStrategy, CompositeProfileStatePath } from '../compositeProfile/StatePersistence.js';
-export interface DeclaredStatePathInput {
-    readonly adapterId: string;
-    readonly declarations: Readonly<Record<string, StatePathDeclaration>>;
-    readonly profile: Profile;
-    readonly resolveSourcePath: (relativePath: string, directory: boolean) => string;
-}
-export declare const createDeclaredStatePaths: (input: DeclaredStatePathInput) => readonly CompositeProfileStatePath[];
-export declare const assertDeclaredStatePersistenceKeys: (adapterId: string, declarations: Readonly<Record<string, StatePathDeclaration>>, profile: Profile) => void;
-export declare const resolveStateStrategy: (profile: Profile, relativePath: string, declaration: StatePathDeclaration) => StatePersistenceStrategy;
-export declare const findProfileStateSource: (profileFolders: readonly string[], adapterId: string, relativePath: string, directory: boolean) => string | undefined;