@ai-outfitter/outfitter 0.6.1 → 0.7.1

package/LICENSE.md

@@ -1,58 +1,28 @@
-# Business Source License 1.1
+Portions of this software are licensed as follows:
 
-## Parameters
-
-**Licensor:** Unsupervised.com, Inc.
-
-**Licensed Work:** Outfitter
-
-The Licensed Work is © 2026 Unsupervised.com, Inc.
-
-**Additional Use Grant:** You may use the Licensed Work without a commercial license only when it is used with or for:
-
-- repositories that are publicly available under an open source license approved by the Open Source Initiative; or
-- repositories with fewer than 10 contributors.
-
-Use of the Licensed Work with or for a private repository with 10 or more contributors requires a commercial license from the Licensor.
-
-**Change Date:** 2030-01-14
-
-**Change License:** Apache License, Version 2.0
-
----
-
-## License Terms
-
-The Licensor hereby grants you the right to copy, modify, create derivative works, redistribute, and make non-production use of the Licensed Work.
-The Licensor may make an Additional Use Grant, above, permitting limited production use.
-
-Effective on the Change Date, or the fourth anniversary of the first publicly available distribution of a specific version of the Licensed Work under this License, whichever comes first, the Licensor hereby grants you rights under the terms of the Change License, and the rights granted in the paragraph above terminate.
-
-If your use of the Licensed Work does not comply with the requirements currently in effect as described in this License, you must purchase a commercial license from the Licensor, its affiliated entities, or authorized resellers, or you must refrain from using the Licensed Work.
-
-All copies of the original and modified Licensed Work, and derivative works of the Licensed Work, are subject to this License.
-This License applies separately for each version of the Licensed Work and the Change Date may vary for each version of the Licensed Work released by Licensor.
-
-You must conspicuously display this License on each original or modified copy of the Licensed Work.
-If you receive the Licensed Work in original or modified form from a third party, the terms and conditions set forth in this License apply to your use of that work.
-
-Any use of the Licensed Work in violation of this License will automatically terminate your rights under this License for the current and all other versions of the Licensed Work.
-
-This License does not grant you any right in any trademark or logo of Licensor or its affiliates (provided that you may use a trademark or logo of Licensor as expressly required by this License).
-
-TO THE EXTENT PERMITTED BY APPLICABLE LAW, THE LICENSED WORK IS PROVIDED ON AN "AS IS" BASIS.
-LICENSOR HEREBY DISCLAIMS ALL WARRANTIES AND CONDITIONS, EXPRESS OR IMPLIED, INCLUDING (WITHOUT LIMITATION) WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT, AND TITLE.
+- All content that resides under the `code/enterprise/` directory of this repository, if that directory exists, is licensed under the license defined in `code/enterprise/LICENSE`.
+- Content outside of the above mentioned directory or restrictions above is available under the MIT license as defined below.
 
 ---
 
-## Prohibited Uses
+MIT License
 
-You may not use the Licensed Work with or for a private repository with 10 or more contributors unless you have purchased a commercial license from the Licensor, its affiliated entities, or authorized resellers.
+Copyright (c) 2026 Unsupervised
 
-For purposes of this License, a repository's contributor count is the number of people who have made commits or other accepted contributions to that repository, or who otherwise have permission to contribute code to that repository, whichever is greater.
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
 
-**Clarification**: This prohibition does not prevent you from using the Licensed Work without a commercial license with or for:
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
 
-- repositories that are publicly available under an open source license approved by the Open Source Initiative, regardless of contributor count;
-- private repositories with fewer than 10 contributors;
-- educational or research contexts that satisfy one of the preceding repository-use allowances.
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -1,295 +1,56 @@
-# outfitter
+# Outfitter
 
-`outfitter` is intended to be a management wrapper for launching [`pi`](https://github.com/earendil-works/pi-coding-agent) and Claude Code with configurable, reusable profiles.
+Outfitter builds effective agent profiles and launches them through wrapped agent CLIs like [`pi`](https://github.com/earendil-works/pi-coding-agent), Claude Code, and future adapters. Individuals, teams, and organizations can share and compose repeatable agent profiles.
 
-The goal is manageable agent CLI configuration:
+If you have not tried [Pi](https://pi.dev) yet, Outfitter is the quickest path to a recommended Pi loadout for engineering work.
 
-- Organizations can define standard pi or claude loadouts, share them, and launch agent CLIs consistently across different environments.
-- Individuals can swap between configurations of their coding agent, share those, and easily migrate to new machines.
-
-If you haven't tried [Pi](https://pi.dev) yet — we think it's a great coding harness & Outfitter is an easy way to try it.
-
-- Install and run `outfitter` to load pi with our standard configuration for engineers.
-
-## Install
-
-Install Outfitter globally from npm so the `outfitter` command is available on your PATH:
+## Quick start
 
 ```bash
 npm install -g @ai-outfitter/outfitter
-outfitter --help
-```
-
-Upgrade with:
-
-```bash
-npm update -g @ai-outfitter/outfitter
-```
-
-Use `npx` when you want to test Outfitter without adding a global command:
-
-```bash
-npx --yes @ai-outfitter/outfitter@latest --help
-```
-
-For source development, see [`CONTRIBUTING.md`](./CONTRIBUTING.md).
-
-Outfitter launches agent CLIs but does not install them.
-Install the agents you plan to use separately:
-
-- [pi](https://github.com/earendil-works/pi-coding-agent) — follow its installation instructions; the `pi` command must be on your PATH.
-- [Claude Code](https://docs.anthropic.com/en/docs/claude-code) — only needed if you launch with `--agent claude`.
-
-## Why this exists
-
-Pi is highly configurable through settings directories, extensions, skills, prompts, themes, model settings, environment variables, and CLI flags.
-That flexibility is powerful, but businesses often need a higher-level control plane for repeatable deployments.
-
-`outfitter` should make it easy to answer questions like:
-
-- Which pi configuration should this employee or team use?
-- Which extensions, skills, prompts, models, and providers are approved?
-- Which credentials or environment variables should be present?
-- Should project-local `.pi` configuration be allowed, merged, or ignored?
-- How do we ship multiple standardized pi loadouts without manual setup?
-
-## Intended use case
-
-Example profile concepts:
-
-- `engineering-default` — standard engineering loadout with approved tools, prompts, and models.
-- `support` — customer-support-focused prompt and restricted tool set.
-- `sandbox` — isolated experimentation profile with disposable config and sessions.
-- `regulated` — locked-down profile with stricter extensions, context, and session behavior.
-
-A launch flow is intended to look like:
-
-```bash
-outfitter
-outfitter run --profile engineering-default
-outfitter run -p support -- --cwd ~/work/customer-issue
-outfitter sync
 outfitter setup
-outfitter setup https://github.com/my_account/outfitter_config
-outfitter welcome
-outfitter profile list
-outfitter profile create regulated --scope user
-```
-
-Under the hood, `outfitter` translates a selected profile into the selected agent launch environment.
-Pi runs use `PI_CODING_AGENT_DIR`; Claude Code runs use `CLAUDE_CONFIG_DIR`; both receive supported CLI flags, prompts, model settings, and environment variables.
-Select the adapter with `outfitter run --agent <pi|claude>`, or set `default_agent` in `settings.yml`.
-If neither is set, Outfitter defaults to pi for backward compatibility.
-If `outfitter` is run before `outfitter setup`, it creates the initial settings and default profile automatically before launching.
-When that first-run setup has an interactive terminal, Outfitter continues into the same welcome onboarding used by `outfitter welcome`.
-
-`outfitter welcome` explains Outfitter and Pi, asks you to choose an initial built-in role, and recommends a Pi productivity loadout.
-The current built-in role choices are `engineer` and `data_analyst`; Outfitter creates the selected local profile on the fly.
-The recommended loadout includes `ulta-tasklist`, `deepwork`, `pi-subagents`, and `pi-mcp-adapter`; you can accept it, choose individual items, or skip loadout installation.
-If you skip loadout installation, the generated profile has no extensions or skills.
-If Pi does not appear to be logged in after welcome onboarding, Outfitter opens Pi with `/login` automatically; outside welcome onboarding it prints a `/login` reminder instead.
-Outfitter never collects or persists provider API keys itself.
-
-`settings.yml` can point at local profiles, full Git URIs, or GitHub shorthand sources with optional refs and repository subpaths:
-
-```yaml
-remote_settings:
-  - github: my_account/outfitter_config
-    ref: main
-    path: settings.yml
-
-profile_sources:
-  - github: my_account/outfitter_config
-    ref: main
-    path: profiles
-```
-
-Run `outfitter sync` to fetch/update remote settings and profiles before using them.
-
-By default, Outfitter keeps reusable runtime cache files under `~/.outfitter/cache`.
-Set `cache_directory` in `settings.yml` to choose a different cache root; relative values resolve from the settings file that declares them.
-The pi adapter symlinks composite profile `utilities/` and `bin/` paths into this cache so pi-managed utilities such as `fd` and `rg` survive across temporary composite profile directories.
-
-Settings can also define arbitrary nested `custom_settings` values for Outfitter-time composite profile templating:
-
-```yaml
-custom_settings:
-  build_commands:
-    lint: npm run lint
-```
-
-Generated composite profile files can reference them with Outfitter's LiquidJS-based custom delimiters:
-
-```yaml
-command: '[[= outfitter.custom_settings.build_commands.lint ]]'
-```
-
-Control tags use `[[% ... %]]`, for example `[[% for item in outfitter.custom_settings.items %]]`.
-Outfitter intentionally does not use common `{{ ... }}` delimiters, and plain shell expressions like `[[ -f package.json ]]` are left alone.
-
-## Setup from a settings repository
-
-You can bootstrap a machine from a Git repository:
-
-```bash
-outfitter setup https://github.com/my_account/outfitter_config
-```
-
-`outfitter setup` requires an interactive terminal on both stdin and stdout.
-When a repository is provided, it clones or updates the repository in Outfitter's shared repository cache, then uses it as a non-overwriting starting point:
-
-- interactive setup-source onboarding shows the Outfitter welcome first, explains which source is being imported, asks whether to install profiles into user home or the current project, then asks one source-profile/default prompt;
-- if the user chooses home and `~/.outfitter/settings.yml` does not exist, Outfitter copies the starter `settings.yml`;
-- if the user chooses project and `<project>/.outfitter/settings.yml` does not exist, Outfitter copies the starter `settings.yml` and ensures `./profiles` is exposed;
-- if starter profiles exist, Outfitter copies missing profile files into the selected `profiles/` folder;
-- existing settings and profile files are otherwise left unchanged;
-- after setup, Outfitter runs the same sync behavior used by `outfitter sync`, then offers to start with the selected default profile or shows both `outfitter` and `outfitter --profile <profile>` start commands;
-- on initial interactive first-run setup, Outfitter skips the older default-profile prompt and lets welcome onboarding choose the generated local default profile;
-- outside that initial welcome handoff and outside setup-source import onboarding, Outfitter shows a short setup wizard that lists synced profiles and writes the selected default profile to user settings;
-- no-source interactive setup continues into welcome onboarding to record role and loadout choices.
-
-A setup repository can use either root-level Outfitter files:
-
-```text
-outfitter_config/
-  settings.yml
-  profiles/
-    engineering-default/
-      profile.yml
-    support/
-      profile.yml
-```
-
-or a `.outfitter/` layout:
-
-```text
-outfitter_config/
-  .outfitter/
-    settings.yml
-    profiles/
-      engineering-default/
-        profile.yml
-      support/
-        profile.yml
-```
-
-Example `settings.yml` for a setup repository:
-
-```yaml
-default_profile: engineering-default
-
-profile_sources:
-  - path: ./profiles
-
-  # Optional: keep loading future updates from this same repo.
-  - github: my_account/outfitter_config
-    ref: main
-    path: profiles
-```
-
-If you want ongoing centralized settings, use a small local `~/.outfitter/settings.yml` that points at remote settings:
-
-```yaml
-remote_settings:
-  - github: my_account/outfitter_config
-    ref: main
-    path: settings.yml
-```
-
-Then run:
-
-```bash
-outfitter sync
-```
-
-## Profile model sketch
-
-A profile will use YAML.
-An initial profile shape is:
-
-```yaml
-id: engineering-default
-label: Engineering Default
-description: General software engineering profile for coding, tests, reviews, and repo navigation.
-inherits:
-  - base-typescript
-  - shared-prose
-
-controls:
-  model: anthropic/claude-sonnet-4
-  environment:
-    TEAM_MODE: engineering
+outfitter
 ```
 
-Set `template: true` on profiles such as `shared-prose` that should only be inherited by runnable profiles, not selected directly with `outfitter run`.
+Outfitter launches agent CLIs; install the agents you plan to use separately.
 
-The exact stable schema is governed by the requirements in `requirements/` and the JSON Schema files in `src/schemas/`, which are still expected to evolve with implementation.
+For the full walkthrough, see [Getting started](./docs/documentation/getting-started.md).
 
-Profiles can also ship DeepWork jobs for that profile under `deepwork/jobs/`.
-When Outfitter launches Pi, it adds contributing profile job folders to `DEEPWORK_ADDITIONAL_JOBS_FOLDERS` so the DeepWork frontend can discover profile-owned workflows without copying them into a project `.deepwork/jobs/` directory.
-By default, profiles with bundled jobs receive only their profile-bundled jobs; set `controls.pi.allow_external_deepwork_jobs: true` to also include inherited `DEEPWORK_ADDITIONAL_JOBS_FOLDERS` entries.
-Pi-specific job overrides remain supported under `cli_specific/pi/deepwork/jobs/`.
+## Profiles
 
-### Updating profile-managed Pi extensions
-
-Profiles can request Pi extensions with `controls.pi.extensions`, for example:
+[Profiles](./docs/documentation/profiles.md) compose the context, tools, prompts, skills, extensions, subagents, and DeepWork workflows that shape an agent. Profiles can be shared using [Profile Catalog Repos](./docs/documentation/profile-repository.md).
 
 ```yaml
+# ~/.outfitter/profiles/home-default.yml
+id: home-default
+label: Home Default
+description: Reusable personal defaults for Outfitter-managed Pi runs.
 controls:
-  pi:
-    extensions:
-      - git:github.com/ai-outfitter/deepwork
-```
-
-For normal users, extension updates should flow through the profile rather than
-through hand-edited Pi cache directories:
-
-1. If your profile is remote-managed, run `outfitter sync` to fetch the latest
-   Outfitter settings and profile sources.
-2. Confirm the active profile names the desired extension source, such as
-   `git:github.com/ai-outfitter/deepwork` after a repository move.
-3. Start a new Outfitter-managed Pi session with `outfitter` or
-   `outfitter run --profile <profile>`. Restart any already-running Pi session;
-   newly registered tools and extension code are only loaded when Pi starts or
-   reloads resources.
-
-`outfitter sync` updates Outfitter's own remote profile/settings cache. Pi still
-owns installation and loading of the `git:` extension declared by the resolved
-profile. Outfitter keeps Pi's `git/` and `tmp/` state paths persistent across
-runs so installed extensions are reusable, but users should not need one-off
-scripts that modify temporary extension cache paths.
-
-If an extension still appears stale after syncing profiles and restarting Pi,
-check the resolved profile first. A future Outfitter command may add a
-first-class extension-cache refresh path, but direct cache surgery is a
-troubleshooting fallback rather than the normal update flow.
-
-## Design direction
-
-The current recommendation is to build `outfitter` around pi's existing native configuration mechanisms:
-
-1. Use a temporary composite profile directory as `PI_CODING_AGENT_DIR` for each run.
-2. Persist intentional pi state through adapter-declared symlinks to profile, native pi, or Outfitter cache files.
-   Native pi fallback is only a durable target for declared state symlinks; it is not an inherited base profile layer.
-3. Layer profile-controlled environment variables and pi CLI flags on top.
-4. Use explicit `--extension` / `-e` injection for bootstrap behavior that needs to run inside pi.
-5. Decide per profile whether project-local `.pi` overrides are allowed.
-6. Keep the wrapper responsible for anything that must happen before pi starts, such as selecting config directories, setting credentials, or choosing session locations.
-
-## Status
-
-This repository is under phased implementation.
-
-A minimal executable CLI exists, with initial settings/profile schemas, local and URI-backed profile loading, profile resolution internals, first-pass `setup`, `sync`, `profile list`, and `profile create` commands, and a first-pass `run` command for assembling a temporary composite profile and launching pi or Claude Code.
-Stable end-to-end pi launch behavior and user-facing examples will be hardened in a later phase.
-The initial dependency and architecture decisions are documented in `package.json`, `doc/architecture.md`, and `requirements/`.
-
-## Future work
-
-- Define a stable profile schema.
-- Decide where organization-managed profiles are discovered from.
-- Harden stable `outfitter run --profile <profile>` behavior.
-- Add validation and inspection commands.
-- Expand user-facing documentation for resolved profile inheritance and composition.
-- Add locking / policy controls for business-managed environments.
-- Add examples for common organizational deployments.
+  provider: openai-codex
+  model: gpt-5.5
+  thinking: high
+  append_system_prompt:
+    - |
+      Use concise, evidence-backed engineering prose.
+      Prefer small, reviewable changes.
+      Keep durable decisions in repo files.
+    - repo_file: docs/architecture.md
+```
+
+## Documentation
+
+- [Getting started](./docs/documentation/getting-started.md)
+- [Profiles](./docs/documentation/profiles.md)
+- [Profile repositories](./docs/documentation/profile-repository.md)
+- [State persistence](./docs/documentation/state.md)
+- [First-time CLI agent users](./docs/documentation/first-time-cli-agent-users.md)
+- [Switching to Outfitter](./docs/documentation/switching-to-outfitter.md)
+- [Documentation index](./docs/documentation/README.md)
+
+Use cases:
+
+- [Organization profile catalog](./docs/documentation/usecases/orginization-profile-catalog.md) — Publish shared team roles so new users can start with organization-approved defaults.
+- [Engineering profile catalog](./docs/documentation/usecases/engineering.md) — Package coding, platform, and review profiles for repeatable engineering workflows.
+- [Persona reviews](./docs/documentation/usecases/persona-reviews.md) — Create customer personas to get feedback on ideas, documentation, and designs.
+
+For local development, repository structure, and release workflow details, see [Contributing](./CONTRIBUTING.md).

package/code/enterprise/LICENSE

@@ -0,0 +1,35 @@
+The Unsupervised Enterprise license (the "Enterprise License")
+Copyright (c) 2026 - present Unsupervised.com, Inc.
+
+With regard to the Unsupervised Software:
+
+This software and associated documentation files (the "Software") may only be
+used in production, if you (and any entity that you represent) have agreed to,
+and are in compliance with, the Unsupervised Subscription Terms of Service,
+available via email (info@unsupervised.com) (the "Enterprise Terms"), or other
+agreement governing the use of the Software, as agreed by you and Unsupervised,
+and otherwise have a valid Unsupervised Enterprise license for the correct
+number of user seats. Subject to the foregoing sentence, you are free to modify
+this Software and publish patches to the Software. You agree that Unsupervised
+and/or its licensors (as applicable) retain all right, title and interest in and
+to all such modifications and/or patches, and all such modifications and/or
+patches may only be used, copied, modified, displayed, distributed, or otherwise
+exploited with a valid Unsupervised Enterprise license for the correct number of
+user seats. Notwithstanding the foregoing, you may copy and modify the Software
+for development and testing purposes, without requiring a subscription. You agree
+that Unsupervised and/or its licensors (as applicable) retain all right, title
+and interest in and to all such modifications. You are not granted any other
+rights beyond what is expressly stated herein. Subject to the foregoing, it is
+forbidden to copy, merge, publish, distribute, sublicense, and/or sell the
+Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS
+FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR
+COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER
+IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
+CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+
+For all third party components incorporated into the Unsupervised Software,
+those components are licensed under the original license provided by the owner of
+the applicable component.

package/code/enterprise/README.md

@@ -0,0 +1,7 @@
+# Outfitter Enterprise Code
+
+Files in this directory and its descendants are licensed under the Outfitter Enterprise/Business Source License in [`LICENSE`](./LICENSE).
+
+Everything outside `code/enterprise/**` is licensed under the root [`LICENSE.md`](../../LICENSE.md) terms.
+
+`privateCatalog.js` defines the package-visible commercial boundary for private profile catalog support. Shared policy lives in `shared/`, CLI sync/settings helpers live in `cli/`, and Pi-native onboarding helpers live in `pi-extension/`. Package staging imports the policy marker and emits `private-catalog-boundary.json` so the published package carries executed enterprise policy artifacts, while public sync/setup behavior remains non-enforcing and continues to rely on the user's ambient Git configuration.

package/code/enterprise/cli/privateCatalogGate.cjs

@@ -0,0 +1,134 @@
+const { spawnSync } = require('node:child_process');
+const { dirname, join } = require('node:path');
+
+const {
+  formatPrivateCatalogCliPrompt,
+  formatPrivateCatalogSkippedMessage,
+  formatPrivateCatalogSkipResultMessage,
+  privateCatalogEnabledMessage,
+} = require('../shared/privateCatalogPolicy.cjs');
+const { enablePrivateProfileCatalogs, isPrivateProfileCatalogsEnabled } = require('./privateCatalogSettings.cjs');
+
+const createPrivateCatalogGate = ({ homeDirectory, classifier, prompt }) => {
+  const settingsPath = join(homeDirectory, '.outfitter', 'settings.yml');
+
+  return {
+    classifier,
+    enabled: isPrivateProfileCatalogsEnabled(settingsPath),
+    homeDirectory,
+    prompt: prompt ?? createTtyPrivateCatalogPrompt(),
+    promptedRepositories: new Set(),
+    settingsPath,
+    skippedRepositories: new Set(),
+  };
+};
+
+const gatePrivateCatalogSources = (sources, gate, helpers) => {
+  const allowedSources = [];
+  const skippedResults = [];
+  const messages = [];
+
+  for (const source of sources) {
+    const repository = source.github;
+    if (repository === undefined || gate.enabled || gate.classifier.classify(repository) !== 'private') {
+      allowedSources.push(source);
+      continue;
+    }
+
+    if (!gate.promptedRepositories.has(repository) && gate.prompt.interactive && gate.prompt.confirm(repository)) {
+      enablePrivateProfileCatalogs(gate.settingsPath);
+      gate.enabled = true;
+      messages.push(privateCatalogEnabledMessage);
+      allowedSources.push(source);
+      continue;
+    }
+
+    gate.promptedRepositories.add(repository);
+    if (!gate.skippedRepositories.has(repository)) {
+      messages.push(formatPrivateCatalogSkippedMessage(repository, gate.prompt.interactive));
+      gate.skippedRepositories.add(repository);
+    }
+    skippedResults.push({
+      uri: helpers.formatDisplayUri(source),
+      cachePath: helpers.createRemoteRepositoryCachePath(dirname(dirname(gate.settingsPath)), source),
+      status: 'skipped',
+      message: formatPrivateCatalogSkipResultMessage(repository),
+    });
+  }
+
+  return { allowedSources, skippedResults, messages };
+};
+
+const createTtyPrivateCatalogPrompt = () => ({
+  interactive: process.stdin.isTTY === true && process.stdout.isTTY === true,
+  confirm(repository) {
+    const prompt = formatPrivateCatalogCliPrompt(repository);
+    const result = spawnSync(
+      'sh',
+      [
+        '-c',
+        'printf "%s" "$OUTFITTER_PRIVATE_CATALOG_PROMPT" > /dev/tty && IFS= read -r answer < /dev/tty && case "$answer" in y|Y|yes|YES) exit 0 ;; *) exit 1 ;; esac',
+      ],
+      { env: { ...process.env, OUTFITTER_PRIVATE_CATALOG_PROMPT: prompt }, stdio: 'inherit' },
+    );
+    return result.status === 0;
+  },
+});
+
+const createGitHubRepositoryVisibilityClassifier = () => ({
+  classify(repository) {
+    if (process.env.VITEST !== undefined) {
+      return 'unknown';
+    }
+
+    const [owner, repo] = repository.split('/');
+
+    if (!owner || !repo) {
+      return 'unknown';
+    }
+
+    const script = `
+      import https from 'node:https';
+      const [owner, repo] = process.argv.slice(1);
+      const request = https.get({
+        hostname: 'api.github.com',
+        path: '/repos/' + encodeURIComponent(owner) + '/' + encodeURIComponent(repo),
+        headers: { 'Accept': 'application/vnd.github+json', 'User-Agent': 'ai-outfitter-cli' },
+        timeout: 2000,
+      }, (response) => {
+        let body = '';
+        response.setEncoding('utf8');
+        response.on('data', (chunk) => { body += chunk; });
+        response.on('end', () => {
+          if (response.statusCode !== 200) {
+            console.log('unknown');
+            return;
+          }
+          try {
+            const document = JSON.parse(body);
+            console.log(document.private === true ? 'private' : document.private === false ? 'public' : 'unknown');
+          } catch {
+            console.log('unknown');
+          }
+        });
+      });
+      request.on('timeout', () => request.destroy());
+      request.on('error', () => console.log('unknown'));
+    `;
+    const result = spawnSync(process.execPath, ['--input-type=module', '--eval', script, owner, repo], {
+      encoding: 'utf8',
+      stdio: 'pipe',
+      timeout: 3000,
+    });
+    const visibility = result.stdout.trim();
+
+    return visibility === 'private' || visibility === 'public' ? visibility : 'unknown';
+  },
+});
+
+module.exports = {
+  createGitHubRepositoryVisibilityClassifier,
+  createPrivateCatalogGate,
+  createTtyPrivateCatalogPrompt,
+  gatePrivateCatalogSources,
+};

package/code/enterprise/cli/privateCatalogSettings.cjs

@@ -0,0 +1,59 @@
+const { existsSync, mkdirSync, readFileSync, writeFileSync } = require('node:fs');
+const { dirname } = require('node:path');
+
+const { parse, stringify } = require('yaml');
+
+const isPrivateProfileCatalogsEnabled = (settingsPath) => {
+  if (!existsSync(settingsPath)) {
+    return false;
+  }
+
+  try {
+    const parsed = parse(readFileSync(settingsPath, 'utf8'));
+    return readPrivateProfileCatalogsSetting(parsed) === true;
+  } catch {
+    return false;
+  }
+};
+
+const enablePrivateProfileCatalogs = (settingsPath) => {
+  const document = readSettingsRecord(settingsPath);
+  const enterprise = readMutableRecord(document.enterprise);
+
+  mkdirSync(dirname(settingsPath), { recursive: true });
+  writeFileSync(
+    settingsPath,
+    stringify({
+      ...document,
+      enterprise: {
+        ...enterprise,
+        private_profile_catalogs: true,
+      },
+    }),
+  );
+};
+
+const readPrivateProfileCatalogsSetting = (value) => {
+  if (value === null || typeof value !== 'object' || Array.isArray(value)) {
+    return undefined;
+  }
+
+  return value.enterprise?.private_profile_catalogs;
+};
+
+const readSettingsRecord = (settingsPath) => {
+  if (!existsSync(settingsPath)) {
+    return {};
+  }
+
+  const parsed = parse(readFileSync(settingsPath, 'utf8'));
+  return readMutableRecord(parsed);
+};
+
+const readMutableRecord = (value) =>
+  value !== null && typeof value === 'object' && !Array.isArray(value) ? { ...value } : {};
+
+module.exports = {
+  enablePrivateProfileCatalogs,
+  isPrivateProfileCatalogsEnabled,
+};