@oxygen-agent/cli 1.948.1 → 1.987.20

package/node_modules/@oxygen/shared/dist/capability-discovery.js

@@ -56,11 +56,11 @@ export const OXYGEN_CAPABILITY_ROUTES = [
         primitive: null,
         owns: "First-run setup and interactive Workspace Copilot sessions over the shared primitive contracts.",
         notFor: "Recurring deterministic automation or standing adaptive jobs; use Workflows or Agents.",
-        execution: "Resolve factual onboarding state, then let the user choose a Recipe, Blueprint, or their own outcome before starting a hosted Copilot session.",
+        execution: "Use existing onboarding context to understand the user goal and GTM bottleneck, recommend a useful next improvement, and guide its native implementation when selected.",
         posture: "mixed",
         gatewayTools: ["oxygen_whoami", "oxygen_recipes_list", "oxygen_blueprints_list", "oxygen_context_resolve", "oxygen_copilot_start"],
-        gatewayCommands: ["whoami", "recipes list", "blueprints list", "context resolve", "copilot start"],
-        skills: ["oxygen-quickstart", "oxygen-gtm"],
+        gatewayCommands: ["whoami", "context resolve", "recipes list", "blueprints list", "copilot start"],
+        skills: ["oxygen-onboarding", "oxygen-quickstart", "oxygen-gtm"],
         // `activation` remains an exact legacy API family for saved clients, but it
         // has no recommended gateway and is not an intent term or first-touch path.
         endpointSections: ["activation", "copilot", "home"],
@@ -68,7 +68,7 @@ export const OXYGEN_CAPABILITY_ROUTES = [
         // users say ("next step of this workflow run"), and a 6-point multi-word hit
         // would drag those queries here. The terms kept are the ones only a founder
         // asking where they are in setup actually types.
-        intentTerms: ["onboard", "onboarding", "first run", "first day", "setup oxygen", "copilot", "assistant", "guided", "where am i", "next step in setup", "what do i do next"],
+        intentTerms: ["onboard", "onboarding", "first run", "first day", "setup oxygen", "copilot", "assistant", "guided", "where am i", "next step in setup", "what do i do next", "gtm consultant", "gtm planning", "improve our gtm operation"],
     },
     {
         id: "billing-and-budgets",
@@ -82,7 +82,7 @@ export const OXYGEN_CAPABILITY_ROUTES = [
         gatewayCommands: ["billing balance", "billing usage", "budget list"],
         skills: ["oxygen-gtm", "oxygen-diagnostics"],
         endpointSections: ["billing", "budget", "limits"],
-        intentTerms: ["billing", "credits", "credit balance", "usage", "spend", "cost", "budget", "subscription", "invoice", "cancel plan"],
+        intentTerms: ["billing", "credits", "credit balance", "usage", "spend", "cost", "budget", "subscription", "invoice", "cancel plan", "change plan", "upgrade", "downgrade"],
     },
     {
         id: "support-and-feedback",
@@ -174,7 +174,7 @@ export const OXYGEN_CAPABILITY_ROUTES = [
         gatewayCommands: ["knowledge search", "knowledge index", "knowledge page get"],
         skills: ["oxygen-knowledge"],
         endpointSections: ["context", "knowledge"],
-        intentTerms: ["knowledge", "wiki", "context", "icp", "positioning", "offer", "rubric", "brand", "voice", "company profile"],
+        intentTerms: ["knowledge", "wiki", "context", "icp", "ideal customer", "positioning", "offer", "rubric", "brand", "voice", "company profile", "github", "obsidian", "vault", "repository sync", "markdown import"],
     },
     {
         id: "recipes",
@@ -182,13 +182,13 @@ export const OXYGEN_CAPABILITY_ROUTES = [
         primitive: "recipes",
         owns: "Versioned advisory playbooks that teach when and why to run proven GTM motions through native primitives.",
         notFor: "A hidden runtime, mandatory bundle, or replacement for hosted Workflows.",
-        execution: "Browse or install the Recipe; optional Blueprints scaffold infrastructure while native primitives execute.",
+        execution: "Browse the Recipe, apply its kit (ordered Blueprint stages, one approval, 0 credits, workflows disabled), then run the play through native primitives.",
         posture: "workspace_write",
         gatewayTools: ["oxygen_recipes_list", "oxygen_recipes_get"],
-        gatewayCommands: ["recipes list", "recipes show", "recipes install"],
-        skills: ["oxygen-recipes"],
+        gatewayCommands: ["recipes list", "recipes show", "recipes apply", "recipes install"],
+        skills: ["oxygen-recipes", "oxygen-playbooks"],
         endpointSections: ["blueprints", "recipes", "templates"],
-        intentTerms: ["recipe", "playbook", "proven play", "activation play", "setup play", "journey", "day 1", "day 7", "day 30", "blueprint", "template", "what should i do"],
+        intentTerms: ["recipe", "playbook", "proven play", "activation play", "setup play", "journey", "day 1", "day 7", "day 30", "blueprint", "template", "what should i do", "inbound led outbound", "engagers into a sequence", "warm outbound from my posts", "whole motion", "end to end motion", "kit"],
     },
     {
         id: "records",
@@ -210,18 +210,23 @@ export const OXYGEN_CAPABILITY_ROUTES = [
         primitive: "tables",
         owns: "Typed working datasets, rows, formulas, AI/tool/waterfall columns, reusable Functions with isolated drafts and published versions, cell state, projects, and run provenance.",
         notFor: "Canonical CRM truth, message cadence, or an off-platform spreadsheet runtime.",
-        execution: "Create and run work in hosted OXYGEN Tables; validate a small sample before bounded paid runs. For standard person or company enrichment, `columns add <table> --preset person_enrich|company_enrich` (MCP oxygen_columns_add with preset) adds the maintained bundle in one call before any hand-built tool column.",
+        execution: "Create and run work in hosted OXYGEN Tables; validate a small sample before bounded paid runs. For standard person or company enrichment, `columns add <table> --preset person_enrich|company_enrich` (MCP oxygen_columns_add with preset) adds the maintained bundle in one call before any hand-built tool column. Person questions over that bundle's profile payload (skill set, grad school, location, job fit, current company) and person appearance research (events, keynotes, podcasts, GitHub profile) are `columns catalog --category people` templates, added with `columns add <table> --prompt-key <key> --input <name>=<column>`. For a company fact OXYGEN already knows how to research (founders, parent company, funding, cloud provider, offers demos, industry, NAICS, HQ, LinkedIn/Crunchbase page lookups) or a page extraction, `columns catalog` lists the ready-made template and `columns add <table> --prompt-key <key> --input <name>=<column>` (MCP oxygen_columns_add with prompt_key) adds it with no prompt to write.",
         posture: "mixed",
-        gatewayTools: ["oxygen_tables_create", "oxygen_columns_add", "oxygen_enrich_column_preview", "oxygen_tables_link_bulk", "oxygen_callables_manage"],
-        gatewayCommands: ["tables create", "columns add", "enrich-column preview", "tables link", "functions list", "functions draft"],
+        gatewayTools: ["oxygen_tables_create", "oxygen_columns_add", "oxygen_columns_catalog", "oxygen_enrich_column_preview", "oxygen_tables_link_bulk", "oxygen_callables_manage"],
+        gatewayCommands: ["tables create", "columns add", "columns catalog", "enrich-column preview", "tables link", "functions list", "functions draft"],
         skills: ["oxygen-gtm", "oxygen-table-tidy", "oxygen-diagnostics", "oxygen-clay-migration", "oxygen-linkedin-marketing"],
-        endpointSections: ["action-columns", "callables", "functions", "columns", "company-enrichment", "enrich-column", "enrichment", "projects", "table-action-items", "table-action-runs", "table-ingestion-runs", "tables"],
+        endpointSections: ["action-columns", "callables", "functions", "columns", "company-enrichment", "enrich-column", "enrichment", "projects", "supabase", "table-action-items", "table-action-runs", "table-ingestion-runs", "tables"],
         // "link"/"join"/"connect"/"relate" route here for `tables link`. Added after a
         // blind user eval asked for exactly "link two tables" and was routed to
         // `tables create` / `columns add` / `enrich-column preview` — none of which
         // do it. The agent only found the right command by grepping the raw 25k-line
         // command manifest, which is not a discovery path a customer has.
-        intentTerms: ["table", "rows", "column", "columns", "dataset", "csv", "import", "enrich", "enrichment", "waterfall", "score", "formula", "ai column", "lookup", "link", "link tables", "join", "connect", "relate", "relationship", "function", "functions", "reusable function", "function draft", "function version", "callable"],
+        // "founders" / "parent company" / "cloud provider" / "company research" route
+        // here for `columns catalog`. Added after the 2026-09-16 blind baseline asked
+        // `capabilities search "founders of a company"` and got `route: null` with a
+        // generic sourcing pointer, then hand-wrote four research prompts for
+        // questions the template catalog now answers by key.
+        intentTerms: ["table", "spreadsheet", "rows", "column", "columns", "dataset", "csv", "import", "enrich", "enrichment", "waterfall", "score", "formula", "ai column", "lookup", "link", "link tables", "join", "connect", "relate", "relationship", "function", "functions", "reusable function", "function draft", "function version", "callable", "column template", "skill set", "grad school", "podcast appearance", "keynote", "github profile", "job fit", "founders", "parent company", "subsidiaries", "cloud provider", "company research", "research question", "research column", "web research", "template catalog", "ready-made", "offers demos", "naics"],
     },
     {
         id: "messages",
@@ -324,7 +329,7 @@ export const OXYGEN_CAPABILITY_ROUTES = [
         // to workspace-access — "identity" matched the AUTH sense. The nouns a user
         // reaches for when naming a sending identity or the dialing pool have to land
         // on the group that actually owns `senders profiles` and `voice numbers`.
-        intentTerms: ["sequence", "campaign", "cadence", "enroll", "outreach", "linkedin message", "linkedin dm", "nurture", "follow up", "sender rotation", "stop on reply", "sender identity", "sending identity", "sender profile", "phone number", "dialing", "dialer"],
+        intentTerms: ["sequence", "campaign", "cadence", "enroll", "outreach", "linkedin message", "linkedin dm", "nurture", "follow up", "sender rotation", "stop on reply", "sender identity", "sending identity", "sender profile", "phone number", "dialing", "dialer", "call", "cold call"],
     },
     {
         id: "publishing",
@@ -526,6 +531,7 @@ export function inferCapabilityRoute(query) {
         card,
         recommendedTools: recommendations.tools,
         recommendedCommands: recommendations.commands,
+        ...(recommendations.exactCommand ? { exactCommand: recommendations.exactCommand } : {}),
     };
 }
 export function inferPrimitiveRoute(query) {
@@ -549,6 +555,7 @@ export function serializeCapabilityRoute(route) {
         endpoint_sections: route.card.endpointSections,
         recommended_commands: route.recommendedCommands,
         recommended_tools: route.recommendedTools,
+        ...(route.exactCommand ? { exact_command: route.exactCommand } : {}),
         hydrate: {
             cli: "oxygen commands get <exact-command> --json",
             mcp: "oxygen_capabilities_schema",
@@ -568,6 +575,11 @@ function isLinkedInProfileWatcherIntent(query) {
 function explicitCapabilityIntent(query) {
     if (/\b(infographic|graphic designer|render html|carousel pages|visual design|gtm flow image)\b/.test(query))
         return ROUTE_BY_ID.get("visual-rendering") ?? null;
+    // A whole-motion ask ("set up inbound-led outbound for my posts") is a
+    // Recipe kit + playbook, not the connected-LinkedIn signals card that the
+    // "my LinkedIn … engagers" rule below would otherwise claim. Resolve it first.
+    if (isInboundLedOutboundIntent(query))
+        return ROUTE_BY_PRIMITIVE.get("recipes") ?? null;
     // A unified sender profile is an owned Sequence identity, even when the ask
     // names every attached channel (LinkedIn + WhatsApp + email). Resolve this
     // before public LinkedIn research, whose generic "profile" wording would
@@ -666,9 +678,23 @@ function explicitCapabilityIntent(query) {
         || /\b(day\s*\d+|days?\s+\d|multi[ -]step|rotate senders?|sender rotation|stop on reply|until (?:they )?reply)\b/.test(query)) {
         return ROUTE_BY_PRIMITIVE.get("sequences") ?? null;
     }
+    // Existing reply handling is Messages even without a channel name. Keep this
+    // after the explicit cadence/enrollment rules so reply-stop programs retain
+    // Sequences. The onboarding baseline phrased this as "follow up on replies".
+    if (/\b(follow up|triage|answer|handle)\b.{0,40}\breplies\b/.test(query)) {
+        return ROUTE_BY_PRIMITIVE.get("messages") ?? null;
+    }
     if (/\b(reply|respond)\b.{0,30}\b(conversation|thread|email|linkedin|whatsapp|dm)\b/.test(query)) {
         return ROUTE_BY_PRIMITIVE.get("messages") ?? null;
     }
+    // Resolving websites / domains / LinkedIn pages for company NAMES the user
+    // already holds is the companies-search `url_recovery` intent, not a fresh
+    // sourcing search and not an enrichment column. A 2026-09-11 blind user
+    // asking "get company website URL from company name" got NO route here
+    // (null), never discovered `companies search plan`, and priced the whole
+    // company_enrich preset instead.
+    if (isCompanyUrlRecoveryIntent(query))
+        return ROUTE_BY_ID.get("sourcing-and-provider-tools") ?? null;
     if (/\b(find emails?|find phones?|find companies|find people|source (?:leads?|a list|companies|people)|build (?:me )?a list|tam|prospect)\b/.test(query)) {
         return ROUTE_BY_ID.get("sourcing-and-provider-tools") ?? null;
     }
@@ -677,16 +703,43 @@ function explicitCapabilityIntent(query) {
     }
     return null;
 }
+/**
+ * Does `term` occur in `query` starting on a word boundary?
+ *
+ * A plain `query.includes(term)` is what sent "enrich these le**ad**s" and
+ * "build me a spre**ad**sheet" to the competitor-ad-intelligence card, and
+ * "our i**deal** customer" to CRM Records: a short term matches inside any
+ * longer word that happens to contain its letters, and nothing else scores, so
+ * the wrong card wins outright rather than narrowly.
+ *
+ * Only the START of the match is anchored, deliberately. Requiring a boundary at
+ * BOTH ends looks stricter and is wrong here, because the cards do not list
+ * their own plurals consistently — `sequence`, `workflow`, `table`, `agent` and
+ * `campaign` have no plural term beside them — so whole-word matching silently
+ * stops routing "sequences", "workflows" and "tables", which are the phrasings
+ * people actually type. Anchoring the head keeps every plural and inflection
+ * working while refusing the mid-word accidents, and it is the same
+ * word-boundary treatment v1.915.0 applied to the Tables guard this scorer sits
+ * behind.
+ */
+function matchesIntentTerm(query, term) {
+    for (let at = query.indexOf(term); at >= 0; at = query.indexOf(term, at + 1)) {
+        const preceding = at === 0 ? "" : query[at - 1] ?? "";
+        if (!/[a-z0-9]/.test(preceding))
+            return true;
+    }
+    return false;
+}
 function highestScoringRoute(query) {
     let best = null;
     for (const card of OXYGEN_CAPABILITY_ROUTES) {
         let score = 0;
         for (const term of card.intentTerms) {
-            if (query.includes(term))
+            if (matchesIntentTerm(query, term))
                 score += term.includes(" ") ? 6 : 2;
         }
         for (const term of card.negativeTerms ?? []) {
-            if (query.includes(term))
+            if (matchesIntentTerm(query, term))
                 score -= term.includes(" ") ? 8 : 3;
         }
         if (score > (best?.score ?? 0))
@@ -694,7 +747,16 @@ function highestScoringRoute(query) {
     }
     return best?.card ?? null;
 }
+/** The exact `companies search plan` invocation for the url_recovery intent. */
+export const COMPANY_URL_RECOVERY_COMMAND = 'oxygen companies search plan --prompt "Find the websites for these companies: <company names>" --source-intent url_recovery';
 function recommendationsFor(card, query) {
+    if (card.id === "sourcing-and-provider-tools" && isCompanyUrlRecoveryIntent(query)) {
+        return {
+            tools: ["oxygen_companies_search_plan", "oxygen_companies_search_run"],
+            commands: ["companies search plan", "companies search run"],
+            exactCommand: COMPANY_URL_RECOVERY_COMMAND,
+        };
+    }
     if (card.id === "connected-linkedin" && isMutualLinkedInConnectionsIntent(query)) {
         return {
             tools: ["oxygen_tools_get", "oxygen_tools_run_live", "oxygen_senders_list"],
@@ -781,6 +843,16 @@ function recommendationsFor(card, query) {
                 commands: ["tables watcher preview", "tables watcher create", "tables watcher get", "tables watcher update", "tables watcher pause", "tables watcher resume"],
             };
         }
+        if (isCompanyResearchQuestionIntent(query)) {
+            // A fact the template catalog already answers by key: list the keys first
+            // (free), add the column by key (free), then price and run it. Ahead of
+            // the bare "run" noun below, because "which cloud provider does it run
+            // on" is a question about the company, not about a run.
+            return {
+                tools: ["oxygen_columns_catalog", "oxygen_columns_add", "oxygen_columns_run", "oxygen_tables_describe"],
+                commands: ["columns catalog", "columns add", "columns run", "tables describe"],
+            };
+        }
         if (/\b(table )?(action )?runs?\b/.test(query)) {
             return {
                 tools: ["oxygen_table_runs_get", "oxygen_table_runs_items", "oxygen_table_runs_wait", "oxygen_table_runs_retry_failed"],
@@ -948,6 +1020,35 @@ function isEmailVerificationIntent(query) {
     const addressThenGrade = /\b(e ?mails?|addresses)\b.{0,40}\b(verif(?:y|ied|ication)|validat(?:e|ed|ion)|valid|invalid|deliverable|(?:will|would|might) bounce|bounce risk|risky|safe to (?:send|email)|catch ?all|accept ?all)\b/;
     return gradeThenAddress.test(query) || addressThenGrade.test(query);
 }
+// "get company website URL from company name", "find the websites for this
+// list of company names", "recover domains for company names" — a URL-ish
+// noun, a company noun, a recovery verb, and the hint that the input is NAMES
+// or a LIST (or that URLs are MISSING). Every leg is required so a sourcing
+// ask ("find companies with a website in Germany") keeps its owner. LinkedIn
+// page recovery is deliberately left to the LinkedIn rules above it, which
+// already resolve company pages through the public-research catalog.
+/**
+ * A company fact the template catalog answers by key — founders, parent company,
+ * subsidiaries, cloud provider, NAICS, demos — and the "ready-made / template
+ * catalog / research question" phrasing itself. Kept to nouns no other card
+ * owns: "funding" alone belongs to Signals and "industry" alone to company
+ * search, so both stay off this list.
+ */
+function isCompanyResearchQuestionIntent(query) {
+    return /\b(founders?|founded by|parent compan(?:y|ies)|subsidiar(?:y|ies)|cloud provider|naics|column templates?|template catalog|ready[- ]made|research question|company research|offers? demos?|gives? demos?)\b/.test(query);
+}
+function isCompanyUrlRecoveryIntent(query) {
+    const urlNoun = /\b(websites?|web ?sites?|website urls?|domains?|urls?|homepages?)\b/;
+    const companyNoun = /\b(compan(?:y|ies)|accounts?|organi[sz]ations?|brands?|vendors?)\b/;
+    const recover = /\b(recover|resolve|look ?up|lookup|missing|get|find|fill(?: in)?|add)\b/;
+    const fromNames = /\b(names?|list|missing|these|those)\b/;
+    // An email / phone / contact ask that merely MENTIONS domains is enrichment,
+    // and a column / table ask is a Tables ask — both keep their owners.
+    const otherOwner = /\b(e-?mails?|phones?|mobiles?|numbers?|contacts?|people|persons?|columns?|tables?|enrich\w*|verif\w*)\b/;
+    return urlNoun.test(query) && companyNoun.test(query) && recover.test(query) && fromNames.test(query)
+        && !/\b(scrape|engagers?|comments?|reactions?|posts?)\b/.test(query)
+        && !otherOwner.test(query);
+}
 function isInboxAvatarIntent(query) {
     return /\b(avatar|profile (?:picture|photo)|headshot|hosted (?:picture|image)|mailbox (?:picture|photo))\b/.test(query);
 }
@@ -974,6 +1075,14 @@ function isMailboxDeleteIntent(query) {
     const scopedDetach = /\b(remove|disconnect)\b.{0,48}\b(mailbox(?:es)?|inbox(?:es)?|sender accounts?|email accounts?)\b.{0,24}\b(?:from|in|on)\b.{0,24}\b(sequence|campaign|cadence|sender profile)\b/.test(query);
     return mailboxScope && removal && !scopedDetach;
 }
+// The composed inbound-led outbound motion: engagers → ICP gate → capped
+// sequence → CRM. Hyphens are already normalised to spaces by the caller.
+function isInboundLedOutboundIntent(query) {
+    return /\binbound led outbound\b/.test(query)
+        || /\bengagers?\b.{0,40}\b(into|to) (a |my )?(sequence|pipeline)\b/.test(query)
+        || /\bwarm outbound\b.{0,40}\b(posts?|engagement)\b/.test(query)
+        || /\b(whole|end to end|complete) (gtm )?motion\b/.test(query);
+}
 function isNetNewLinkedInInitiation(query) {
     const mentionsLinkedIn = /\blinkedin\b|\bdm\b/.test(query);
     const startsConversation = /\b(send|message|dm|contact|reach out|initiate|start)\b/.test(query)

package/node_modules/@oxygen/shared/dist/column-output-fields.js

@@ -26,7 +26,7 @@
  * may contain a dot or a space. Such a field carries `referenceable: false` and
  * is display-only.
  */
-import { buildResearchCellSchema, deriveResearchOutputContract, usesServerManagedResearchSchema, } from "./research-output-contract.js";
+import { buildResearchCellSchema, isResearchEnvelopeSchema, researchEvidenceRequired, deriveResearchOutputContract, usesServerManagedResearchSchema, } from "./research-output-contract.js";
 import { isTemplateSafePath, parseJsonPath, readJsonPath } from "./json-path.js";
 const MAX_FIELDS = 40;
 const MAX_SCHEMA_DEPTH = 5;
@@ -263,13 +263,21 @@ function researchContract(definition) {
     const prompt = readString(definition.prompt) ?? "";
     const webSearch = isRecord(definition.webSearch) ? definition.webSearch : null;
     const contract = deriveResearchOutputContract(prompt, {
-        evidenceRequired: webSearch?.evidenceMode === "strict",
+        evidenceRequired: researchEvidenceRequired(webSearch),
     });
     // The STORED shape, not the model-facing one: a research cell carries
-    // `sources`, never the `citations` the model answered with.
+    // `sources`, never the `citations` the model answered with. A column whose
+    // own schema is still the research envelope (a catalog template's typed
+    // answer) gets the same rewrite, so `answer.plan_count` is offered and
+    // `citations` is not; a hand-authored schema that replaced the envelope is
+    // used verbatim, because the cell then holds exactly what it declares.
     const schema = serverManaged
         ? buildResearchCellSchema(contract)
-        : (isRecord(definition.outputSchema) ? definition.outputSchema : null);
+        : isRecord(definition.outputSchema)
+            ? (isResearchEnvelopeSchema(definition.outputSchema)
+                ? buildResearchCellSchema(null, definition.outputSchema)
+                : definition.outputSchema)
+            : null;
     if (!schema)
         return EMPTY_CONTRACT;
     return {

package/node_modules/@oxygen/shared/dist/copilot-errors.js

@@ -21,6 +21,9 @@ const WORKER_STEP_TIMEOUT_MESSAGE = /\bWorker step '[^']+' exceeded \d+ms deadli
 export function customerFacingCopilotError(input) {
     const code = input.code ?? null;
     const message = input.message ?? null;
+    if (code === "agent_response_incomplete") {
+        return { code, message: "I stopped before completing the requested work. Completed actions are saved; ask me to continue." };
+    }
     const isTimeout = code === "worker_step_timeout" ||
         code === COPILOT_TURN_TIMEOUT_CODE ||
         code === COPILOT_TURN_DEADLINE_EXCEEDED_CODE ||

package/node_modules/@oxygen/shared/dist/copilot-journeys.d.ts

@@ -8,6 +8,24 @@ export type CopilotJourney = {
     seedMessage: string;
 };
 export declare const LINKEDIN_NETWORK_COPILOT_JOURNEY_SLUG = "inbound-led-outbound";
-export declare const COPILOT_JOURNEYS: readonly CopilotJourney[];
+export declare const COPILOT_JOURNEYS: readonly [{
+    readonly slug: "inbound-led-outbound";
+    readonly title: "Inbound-led outbound";
+    readonly description: "Turn the people who engage with your LinkedIn posts into a capped, evidence-gated warm sequence with replies routed to your CRM.";
+    readonly recipeSlugs: readonly ["inbound-led-outbound", "linkedin-network-first-motion", "founder-posting-system", "reply-to-meeting"];
+    readonly seedMessage: "I chose the inbound-led-outbound recipe. Help me set up inbound-led outbound for my LinkedIn posts: watch who engages with them every day, assess each person against my ICP, hand me the strong fits, put the possible fits into a draft LinkedIn sequence on a schedule, move replies into my CRM, and write what we learn back into my knowledge wiki. Inspect the workspace first, follow the recipe, and resume from durable evidence instead of starting over. Do not connect an account, enroll anyone, send anything, or spend credits without asking me first.";
+}, {
+    readonly slug: "email-infra-setup";
+    readonly title: "Outbound infrastructure";
+    readonly description: "Domains, inboxes, warmup, sender posture — reviewed and approved before anything is bought or sent.";
+    readonly recipeSlugs: readonly ["email-infra-setup"];
+    readonly seedMessage: "Inspect my current sending setup (domains, inboxes, warmup, senders, caps, deliverability) and propose what's missing for a safe cold-email motion. Show quotes and costs — do not buy or change anything without my approval.";
+}, {
+    readonly slug: "tam-sourcing";
+    readonly title: "Map your market";
+    readonly description: "Source and segment your addressable market from your ICP, starting with a bounded sample.";
+    readonly recipeSlugs: readonly ["icp-to-account-map", "outbound-pilot-50"];
+    readonly seedMessage: "Help me map my total addressable market from my ICP. Ground it in my company profile and website, source a bounded sample first, and show me coverage and credit estimates before expanding.";
+}];
 export type CopilotJourneySlug = (typeof COPILOT_JOURNEYS)[number]["slug"];
 export declare function getCopilotJourney(slug: string): CopilotJourney | null;

package/node_modules/@oxygen/shared/dist/copilot-journeys.generated.d.ts

@@ -0,0 +1,19 @@
+export declare const COPILOT_JOURNEYS_GENERATED: readonly [{
+    readonly slug: "inbound-led-outbound";
+    readonly title: "Inbound-led outbound";
+    readonly description: "Turn the people who engage with your LinkedIn posts into a capped, evidence-gated warm sequence with replies routed to your CRM.";
+    readonly recipeSlugs: readonly ["inbound-led-outbound", "linkedin-network-first-motion", "founder-posting-system", "reply-to-meeting"];
+    readonly seedMessage: "I chose the inbound-led-outbound recipe. Help me set up inbound-led outbound for my LinkedIn posts: watch who engages with them every day, assess each person against my ICP, hand me the strong fits, put the possible fits into a draft LinkedIn sequence on a schedule, move replies into my CRM, and write what we learn back into my knowledge wiki. Inspect the workspace first, follow the recipe, and resume from durable evidence instead of starting over. Do not connect an account, enroll anyone, send anything, or spend credits without asking me first.";
+}, {
+    readonly slug: "email-infra-setup";
+    readonly title: "Outbound infrastructure";
+    readonly description: "Domains, inboxes, warmup, sender posture — reviewed and approved before anything is bought or sent.";
+    readonly recipeSlugs: readonly ["email-infra-setup"];
+    readonly seedMessage: "Inspect my current sending setup (domains, inboxes, warmup, senders, caps, deliverability) and propose what's missing for a safe cold-email motion. Show quotes and costs — do not buy or change anything without my approval.";
+}, {
+    readonly slug: "tam-sourcing";
+    readonly title: "Map your market";
+    readonly description: "Source and segment your addressable market from your ICP, starting with a bounded sample.";
+    readonly recipeSlugs: readonly ["icp-to-account-map", "outbound-pilot-50"];
+    readonly seedMessage: "Help me map my total addressable market from my ICP. Ground it in my company profile and website, source a bounded sample first, and show me coverage and credit estimates before expanding.";
+}];

package/node_modules/@oxygen/shared/dist/copilot-journeys.generated.js

@@ -0,0 +1,26 @@
+// GENERATED by apps/web/scripts/generate-copilot-journeys.ts from the recipe
+// catalog (`journey:` blocks in apps/web/src/agent-skills/oxygen-recipes/recipes).
+// Do not edit by hand — run `npm run skills:metadata -w @oxygen/web`.
+export const COPILOT_JOURNEYS_GENERATED = [
+    {
+        slug: "inbound-led-outbound",
+        title: "Inbound-led outbound",
+        description: "Turn the people who engage with your LinkedIn posts into a capped, evidence-gated warm sequence with replies routed to your CRM.",
+        recipeSlugs: ["inbound-led-outbound", "linkedin-network-first-motion", "founder-posting-system", "reply-to-meeting"],
+        seedMessage: "I chose the inbound-led-outbound recipe. Help me set up inbound-led outbound for my LinkedIn posts: watch who engages with them every day, assess each person against my ICP, hand me the strong fits, put the possible fits into a draft LinkedIn sequence on a schedule, move replies into my CRM, and write what we learn back into my knowledge wiki. Inspect the workspace first, follow the recipe, and resume from durable evidence instead of starting over. Do not connect an account, enroll anyone, send anything, or spend credits without asking me first.",
+    },
+    {
+        slug: "email-infra-setup",
+        title: "Outbound infrastructure",
+        description: "Domains, inboxes, warmup, sender posture — reviewed and approved before anything is bought or sent.",
+        recipeSlugs: ["email-infra-setup"],
+        seedMessage: "Inspect my current sending setup (domains, inboxes, warmup, senders, caps, deliverability) and propose what's missing for a safe cold-email motion. Show quotes and costs — do not buy or change anything without my approval.",
+    },
+    {
+        slug: "tam-sourcing",
+        title: "Map your market",
+        description: "Source and segment your addressable market from your ICP, starting with a bounded sample.",
+        recipeSlugs: ["icp-to-account-map", "outbound-pilot-50"],
+        seedMessage: "Help me map my total addressable market from my ICP. Ground it in my company profile and website, source a bounded sample first, and show me coverage and credit estimates before expanding.",
+    },
+];

package/node_modules/@oxygen/shared/dist/copilot-journeys.js

@@ -1,47 +1,14 @@
-// Workspace Copilot guided journeys (ADR 0013 §11). One canonical copy shared by
-// the runtime (system-prompt grounding on the named recipes) and the web journey
-// cards (seeding a session's first message) — the data is pure and client-safe.
-// Each journey is a thin descriptor over EXISTING advisory catalog Recipes:
-// journeys add no runtime behavior, and every guardrail (never enroll/send/buy/
-// change DNS without approval) rides those recipes' own approval gates.
+import { COPILOT_JOURNEYS_GENERATED } from "./copilot-journeys.generated.js";
 // Stable slug for sessions deliberately launched from the matching Recipe.
 // It is never a default: first-touch surfaces stay outcome-neutral.
 export const LINKEDIN_NETWORK_COPILOT_JOURNEY_SLUG = "inbound-led-outbound";
-export const COPILOT_JOURNEYS = [
-    {
-        slug: LINKEDIN_NETWORK_COPILOT_JOURNEY_SLUG,
-        title: "Inbound-led outbound",
-        description: "Work the LinkedIn network you already have — connections and post engagers — as a capped warm motion.",
-        // The network-first play leads: connections and post engagers are the two
-        // sources a founder actually has on day 1, and profile viewers (the old lead)
-        // are a thin, anonymity-capped sample by comparison. Posting is second because
-        // it CREATES the engager stream this play captures, and replies close the loop.
-        recipeSlugs: [
-            "linkedin-network-first-motion",
-            "founder-posting-system",
-            "reply-to-meeting",
-        ],
-        // Deliberately free of steps, commands, table names, and caps: encoding
-        // mechanics here would fork a second, unversioned copy of the play that no
-        // catalog gate can lint (ADR 0013 §11 — a journey is a thin pointer at
-        // advisory recipes, never a hardcoded kit).
-        seedMessage: "I chose the linkedin-network-first-motion recipe. Help me turn the LinkedIn network I already have — my connections and the people who engage with my posts — into a small, safe, approval-gated outreach motion. Inspect the relevant workspace primitives, follow the recipe, and resume from durable evidence instead of starting over. Do not connect an account, enroll anyone, send anything, or spend credits without asking me first.",
-    },
-    {
-        slug: "tam-sourcing",
-        title: "Map your market",
-        description: "Source and segment your addressable market from your ICP, starting with a bounded sample.",
-        recipeSlugs: ["icp-to-account-map", "outbound-pilot-50"],
-        seedMessage: "Help me map my total addressable market from my ICP. Ground it in my company profile and website, source a bounded sample first, and show me coverage and credit estimates before expanding.",
-    },
-    {
-        slug: "email-infra-setup",
-        title: "Outbound infrastructure",
-        description: "Domains, inboxes, warmup, sender posture — reviewed and approved before anything is bought or sent.",
-        recipeSlugs: ["email-infra-setup"],
-        seedMessage: "Inspect my current sending setup (domains, inboxes, warmup, senders, caps, deliverability) and propose what's missing for a safe cold-email motion. Show quotes and costs — do not buy or change anything without my approval.",
-    },
-];
+// Derived from the recipe catalog (ADR 0025): every recipe carrying a
+// `journey:` block leads one journey. The list is generated into
+// ./copilot-journeys.generated.ts by apps/web/scripts/generate-copilot-journeys.ts
+// (run through `npm run skills:metadata -w @oxygen/web`) and gated against the
+// catalog by apps/web/src/lib/recipes/copilot-journeys.test.ts, because this
+// package cannot read the markdown the catalog is served from.
+export const COPILOT_JOURNEYS = COPILOT_JOURNEYS_GENERATED;
 export function getCopilotJourney(slug) {
     return COPILOT_JOURNEYS.find((journey) => journey.slug === slug) ?? null;
 }

package/node_modules/@oxygen/shared/dist/copilot-playbooks.d.ts

@@ -0,0 +1,18 @@
+export type CopilotPlaybookSlug = "tam-sourcing" | "linkedin-content-strategy" | "inbound-led-outbound" | "signal-based-outbound";
+export type CopilotPlaybook = {
+    /**
+     * The skill slug the Copilot loads through its `skills` tool, and the
+     * `name:` in the playbook file's frontmatter. The two are gated equal.
+     */
+    slug: CopilotPlaybookSlug;
+    /** Customer-facing name, exactly as it is spoken in the composer prompt and shown on the Home chip. */
+    title: string;
+};
+export declare const COPILOT_PLAYBOOKS: readonly CopilotPlaybook[];
+/**
+ * The sentence a Home card writes into the composer. It names the skill the way
+ * a person would say it, and the Copilot's prompt maps that title back to the
+ * slug — so the user reads and sends exactly what the card promised.
+ */
+export declare function copilotPlaybookPrompt(playbook: Pick<CopilotPlaybook, "title">): string;
+export declare function getCopilotPlaybook(slug: string): CopilotPlaybook | null;

package/node_modules/@oxygen/shared/dist/copilot-playbooks.js

@@ -0,0 +1,43 @@
+// The four end-to-end GTM playbooks the Workspace Copilot can run, as pure,
+// client-safe data. One canonical copy is read by three consumers: the Home
+// cards (which pre-write the prompt below into the composer), the Copilot's
+// system prompt (which maps the spoken title back to the skill slug the model
+// loads through its `skills` tool), and the apps/web gate that checks every slug
+// here has a served playbook file with a matching frontmatter `name`.
+//
+// A playbook is the operator contract for one whole motion — stages, owners,
+// exact commands, caps, approval gates, stop conditions, learning loop — served
+// as a product skill (`apps/web/src/agent-skills/oxygen-playbooks/playbooks/`).
+// Loading one is never permission to spend or send: every gate inside it still
+// fires. Founder decision 2026-09-16: Home offers exactly these four, above the
+// composer as compact glass chips (title only), and a chip writes the sentence
+// into the box rather than starting a session, so there stays exactly one door.
+export const COPILOT_PLAYBOOKS = [
+    {
+        slug: "tam-sourcing",
+        title: "TAM sourcing",
+    },
+    {
+        slug: "linkedin-content-strategy",
+        title: "LinkedIn content strategy",
+    },
+    {
+        slug: "inbound-led-outbound",
+        title: "Inbound-led outbound",
+    },
+    {
+        slug: "signal-based-outbound",
+        title: "Signal-based outbound",
+    },
+];
+/**
+ * The sentence a Home card writes into the composer. It names the skill the way
+ * a person would say it, and the Copilot's prompt maps that title back to the
+ * slug — so the user reads and sends exactly what the card promised.
+ */
+export function copilotPlaybookPrompt(playbook) {
+    return `Use the ${playbook.title} skill to get started.`;
+}
+export function getCopilotPlaybook(slug) {
+    return COPILOT_PLAYBOOKS.find((playbook) => playbook.slug === slug) ?? null;
+}

package/node_modules/@oxygen/shared/dist/copilot-skills.d.ts

@@ -0,0 +1,15 @@
+export type CopilotSkillSnapshot = {
+    /** What the model passes to the `skills` tool; equals the bundle's frontmatter `name`. */
+    slug: string;
+    /** Catalog title, shown when the frontmatter carries no description. */
+    title: string;
+    /** Served skill files bundled into `content`, as `skill/path`, for provenance. */
+    sources: readonly string[];
+    /** The exact bundle the tool serves, frontmatter included. */
+    content: string;
+    /** Lowercase hex sha256 of `content`; the runtime re-hashes every served body against it. */
+    sha256: string;
+};
+export declare const COPILOT_SKILL_SNAPSHOTS: readonly CopilotSkillSnapshot[];
+export declare const COPILOT_SKILL_SLUGS: readonly string[];
+export declare function getCopilotSkillSnapshot(slug: string): CopilotSkillSnapshot | null;