winter-super-cli 2026.5.26 → 2026.5.28

package/resources/local/codex/skills/.system/openai-docs/SKILL.md

@@ -1,88 +0,0 @@
----
-name: "openai-docs"
-description: "Use when the user asks how to build with OpenAI products or APIs and needs up-to-date official documentation with citations, help choosing the latest model for a use case, or model upgrade and prompt-upgrade guidance; prioritize OpenAI docs MCP tools, use bundled references only as helper context, and restrict any fallback browsing to official OpenAI domains."
----
-
-
-# OpenAI Docs
-
-Provide authoritative, current guidance from OpenAI developer docs using the developers.openai.com MCP server. Always prioritize the developer docs MCP tools over web.run for OpenAI-related questions. This skill also owns model selection, API model migration, and prompt-upgrade guidance. Only if the MCP server is installed and returns no meaningful results should you fall back to web search.
-
-## API Key Setup
-
-For requests to build, run, configure, debug, or implement an API-backed app, script, CLI, generator, or tool, use `openai-platform-api-key` first when available. After that credential gate is resolved, return here for current docs as needed.
-
-Use this skill directly for docs-only questions, citations, model/API guidance, conceptual explanations, and examples that do not require building or running an API-backed artifact.
-
-## Quick start
-
-- Use `mcp__openaiDeveloperDocs__search_openai_docs` to find the most relevant doc pages.
-- Use `mcp__openaiDeveloperDocs__fetch_openai_doc` to pull exact sections and quote/paraphrase accurately.
-- Use `mcp__openaiDeveloperDocs__list_openai_docs` only when you need to browse or discover pages without a clear query.
-- For model-selection, "latest model", or default-model questions, fetch `https://developers.openai.com/api/docs/guides/latest-model.md` first. If that is unavailable, load `references/latest-model.md`.
-- For model upgrades or prompt upgrades, run `node scripts/resolve-latest-model-info.js` only when the target is latest/current/default or otherwise unspecified; otherwise preserve the explicitly requested target.
-- Preserve explicit target requests: if the user names a target model like "migrate to GPT-5.4", keep that requested target even if `latest-model.md` names a newer model. Mention newer guidance only as optional.
-- If current remote guidance is needed, fetch both the returned migration and prompting guide URLs directly. If direct fetch fails, use MCP/search fallback; if that also fails, use bundled fallback references and disclose the fallback.
-
-## OpenAI product snapshots
-
-1. Apps SDK: Build ChatGPT apps by providing a web component UI and an MCP server that exposes your app's tools to ChatGPT.
-2. Responses API: A unified endpoint designed for stateful, multimodal, tool-using interactions in agentic workflows.
-3. Chat Completions API: Generate a model response from a list of messages comprising a conversation.
-4. Codex: OpenAI's coding agent for software development that can write, understand, review, and debug code.
-5. gpt-oss: Open-weight OpenAI reasoning models (gpt-oss-120b and gpt-oss-20b) released under the Apache 2.0 license.
-6. Realtime API: Build low-latency, multimodal experiences including natural speech-to-speech conversations.
-7. Agents SDK: A toolkit for building agentic apps where a model can use tools and context, hand off to other agents, stream partial results, and keep a full trace.
-
-## If MCP server is missing
-
-If MCP tools fail or no OpenAI docs resources are available:
-
-1. Run the install command yourself: `codex mcp add openaiDeveloperDocs --url https://developers.openai.com/mcp`
-2. If it fails due to permissions/sandboxing, immediately retry the same command with escalated permissions and include a 1-sentence justification for approval. Do not ask the user to run it yet.
-3. Only if the escalated attempt fails, ask the user to run the install command.
-4. Ask the user to restart Codex.
-5. Re-run the doc search/fetch after restart.
-
-## Workflow
-
-1. Clarify whether the request is general docs lookup, model selection, a model-string upgrade, prompt-upgrade guidance, or broader API/provider migration.
-2. For model-selection or upgrade requests, prefer current remote docs over bundled references when the user asks for latest/current/default guidance.
-   - Fetch `https://developers.openai.com/api/docs/guides/latest-model.md`.
-   - Find the latest model ID and explicit migration or prompt-guidance links.
-   - Prefer explicit links from the latest-model page over derived URLs.
-   - For explicit named-model requests, preserve the requested model target and do not silently retarget to the latest model. Mention newer remote guidance only as optional.
-   - For dynamic latest/current/default upgrades, run `node scripts/resolve-latest-model-info.js`, then fetch both returned guide URLs directly when possible.
-   - If direct guide fetch fails, use the developer-docs MCP tools or official OpenAI-domain search to find the same guide content.
-   - If remote docs are unavailable, use bundled fallback references and say that fallback guidance was used.
-3. For model upgrades, keep changes narrow: update active OpenAI API model defaults and directly related prompts only when safe.
-4. Leave historical docs, examples, eval baselines, fixtures, provider comparisons, provider registries, pricing tables, alias defaults, low-cost fallback paths, and ambiguous older model usage unchanged unless the user explicitly asks to upgrade them.
-5. Do not perform SDK, tooling, IDE, plugin, shell, auth, or provider-environment migrations as part of a model-and-prompt upgrade.
-6. If an upgrade needs API-surface changes, schema rewiring, tool-handler changes, or implementation work beyond a literal model-string replacement and prompt edits, report it as blocked or confirmation-needed.
-7. For general docs lookup, search docs with a precise query, fetch the best page and exact section needed, and answer with concise citations.
-
-## Reference map
-
-Read only what you need:
-
-- `https://developers.openai.com/api/docs/guides/latest-model.md` -> current model-selection and "best/latest/current model" questions.
-- `references/latest-model.md` -> bundled fallback for model-selection and "best/latest/current model" questions.
-- `references/upgrade-guide.md` -> bundled fallback for model upgrade and upgrade-planning requests.
-- `references/prompting-guide.md` -> bundled fallback for prompt rewrites and prompt-behavior upgrades.
-
-## Quality rules
-
-- Treat OpenAI docs as the source of truth; avoid speculation.
-- Keep migration changes narrow and behavior-preserving.
-- Prefer prompt-only upgrades when possible.
-- Do not invent pricing, availability, parameters, API changes, or breaking changes.
-- Keep quotes short and within policy limits; prefer paraphrase with citations.
-- If multiple pages differ, call out the difference and cite both.
-- If official docs and repo behavior disagree, state the conflict and stop before making broad edits.
-- If docs do not cover the user’s need, say so and offer next steps.
-
-## Tooling notes
-
-- Always use MCP doc tools before any web search for OpenAI-related questions.
-- If the MCP server is installed but returns no meaningful results, then use web search as a fallback.
-- When falling back to web search, restrict to official OpenAI domains (developers.openai.com, platform.openai.com) and cite sources.

package/resources/local/codex/skills/.system/openai-docs/agents/openai.yaml

@@ -1,14 +0,0 @@
-interface:
-  display_name: "OpenAI Docs"
-  short_description: "Reference docs, choose models, and migrate OpenAI API integrations"
-  icon_small: "./assets/openai-small.svg"
-  icon_large: "./assets/openai.png"
-  default_prompt: "Use OpenAI Docs for official docs lookup, model selection, model migration, and prompt-upgrade work."
-
-dependencies:
-  tools:
-    - type: "mcp"
-      value: "openaiDeveloperDocs"
-      description: "OpenAI Developer Docs MCP server"
-      transport: "streamable_http"
-      url: "https://developers.openai.com/mcp"

package/resources/local/codex/skills/.system/openai-docs/assets/openai-small.svg

@@ -1,3 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" width="14" height="14" fill="currentColor" viewBox="0 0 14 14">
-  <path d="M10.931 3.34a.112.112 0 0 0-.069-.104l-.038-.007c-1.537.05-2.45.318-3.714 1.002v6.683c.48-.248.936-.44 1.414-.58.695-.203 1.417-.292 2.303-.305l.038-.008a.113.113 0 0 0 .066-.104V3.341ZM2.363 9.919c0 .064.051.11.105.111l.33.008c1.162.046 2.042.243 2.975.662-.403-.585-1.008-1.075-1.654-1.292a.991.991 0 0 1-.674-.941v-5.14a6.36 6.36 0 0 0-.59-.076l-.37-.02a.115.115 0 0 0-.122.111v6.577Zm9.455-.001a.998.998 0 0 1-.877.992l-.101.007c-.832.012-1.47.095-2.066.27-.599.174-1.176.448-1.883.863a.444.444 0 0 1-.449 0c-1.299-.763-2.229-1.07-3.689-1.125l-.299-.008a.997.997 0 0 1-.977-.998V3.342c0-.573.478-1.017 1.038-.999l.417.023c.188.015.35.037.513.062v-.754c0-.708.749-1.244 1.429-.903.984.492 1.836 1.449 2.15 2.505 1.216-.617 2.222-.884 3.771-.934l.105.003a.998.998 0 0 1 .918.996v6.576ZM4.332 8.466c0 .049.03.087.07.1l.24.091a4.319 4.319 0 0 1 1.581 1.176V3.721c-.164-.803-.799-1.617-1.584-2.07l-.162-.088c-.025-.012-.054-.013-.088.009a.12.12 0 0 0-.057.102v6.792Z"/>
-</svg>

package/resources/local/codex/skills/.system/openai-docs/references/latest-model.md

@@ -1,37 +0,0 @@
-# Latest model guide
-
-This file is a curated helper. Every recommendation here must be verified against current OpenAI docs before it is repeated to a user.
-
-## Current model map
-
-| Model ID | Use for |
-| --- | --- |
-| `gpt-5.5` | Latest/default text and reasoning model for most new apps, including coding and tool-heavy workflows |
-| `gpt-5.5-pro` | Maximum reasoning or quality when latency and cost matter less |
-| `gpt-5.4` | Previous default text and reasoning model; use for existing GPT-5.4 integrations |
-| `gpt-5.4-mini` | Lower-cost testing and lighter production workflows |
-| `gpt-5.4-nano` | High-throughput simple tasks and classification |
-| `gpt-5.5` | Explicit no-reasoning text path via `reasoning.effort: none` |
-| `gpt-4.1-mini` | Cheaper no-reasoning text |
-| `gpt-4.1-nano` | Fastest and cheapest no-reasoning text |
-| `gpt-5.3-codex` | Agentic coding, code editing, and tool-heavy coding workflows |
-| `gpt-5.1-codex-mini` | Cheaper coding workflows |
-| `gpt-image-2` | Best image generation and edit quality |
-| `gpt-image-1.5` | Less expensive image generation and edit quality |
-| `gpt-image-1-mini` | Cost-optimized image generation |
-| `gpt-4o-mini-tts` | Text-to-speech |
-| `gpt-4o-mini-transcribe` | Speech-to-text, fast and cost-efficient |
-| `gpt-realtime-1.5` | Realtime voice and multimodal sessions |
-| `gpt-realtime-mini` | Cheaper realtime sessions |
-| `gpt-audio` | Chat Completions audio input and output |
-| `gpt-audio-mini` | Cheaper Chat Completions audio workflows |
-| `sora-2` | Faster iteration and draft video generation |
-| `sora-2-pro` | Higher-quality production video |
-| `omni-moderation-latest` | Text and image moderation |
-| `text-embedding-3-large` | Higher-quality retrieval embeddings; default in this skill because no best-specific row exists |
-| `text-embedding-3-small` | Lower-cost embeddings |
-
-## Maintenance notes
-
-- This file will drift unless it is periodically re-verified against current OpenAI docs.
-- If this file conflicts with current docs, the docs win.

package/resources/local/codex/skills/.system/openai-docs/references/prompting-guide.md

@@ -1,244 +0,0 @@
-GPT-5.5 works best when prompts define the outcome and leave room for the model to choose an efficient solution path. Compared with earlier models, you can often use shorter, more outcome-oriented prompts: describe what good looks like, what constraints matter, what evidence is available, and what the final answer should contain.
-
-Avoid carrying over every instruction from an older prompt stack. Legacy prompts often over-specify the process because earlier models needed more help staying on track. With GPT-5.5, that can add noise, narrow the model's search space, or lead to overly mechanical answers.
-
-For more detail on GPT-5.5 behavior changes, start with the [Using GPT-5.5 guide](/api/docs/guides/latest-model). This guide focuses on prompt changes that follow from those behavior changes.
-
-The patterns here are starting points. Adapt them to your product surface, tools, evals, and user experience goals.
-
-## Personality and behavior
-
-GPT-5.5's default style is efficient, direct, and task-oriented. This is useful for production systems: responses stay focused, behavior is easier to steer, and the model avoids unnecessary conversational padding.
-
-For customer-facing assistants, support workflows, coaching experiences, and other conversational products, define both personality and collaboration style.
-
-- **Personality** controls how the assistant sounds: tone, warmth, directness, formality, humor, empathy, and level of polish.
-- **Collaboration style** controls how the assistant works: when it asks questions, when it makes assumptions, how proactive it should be, how much context it gives, when it checks work, and how it handles uncertainty or risk.
-
-Keep both short. Personality instructions should shape the user experience. Collaboration instructions should shape task behavior. Neither should replace clear goals, success criteria, tool rules, or stopping conditions.
-
-Example personality block for a steady task-focused assistant:
-
-```text
-# Personality
-You are a capable collaborator: approachable, steady, and direct. Assume the user is competent and acting in good faith, and respond with patience, respect, and practical helpfulness.
-
-Prefer making progress over stopping for clarification when the request is already clear enough to attempt. Use context and reasonable assumptions to move forward. Ask for clarification only when the missing information would materially change the answer or create meaningful risk, and keep any question narrow.
-
-Stay concise without becoming curt. Give enough context for the user to understand and trust the answer, then stop. Use examples, comparisons, or simple analogies when they make the point easier to grasp. When correcting the user or disagreeing, be candid but constructive. When an error is pointed out, acknowledge it plainly and focus on fixing it.
-
-Match the user's tone within professional bounds. Avoid emojis and profanity by default, unless the user explicitly asks for that style or has clearly established it as appropriate for the conversation.
-```
-
-Example personality block for an expressive collaborative assistant:
-
-```text
-# Personality
-Adopt a vivid conversational presence: intelligent, curious, playful when appropriate, and attentive to the user's thinking. Ask good questions when the problem is blurry, then become decisive once there is enough context.
-
-Be warm, collaborative, and polished. Conversation should feel easy and alive, but not chatty for its own sake. Offer a real point of view rather than merely mirroring the user, while staying responsive to their goals and constraints.
-
-Be thoughtful and grounded when the task calls for synthesis or advice. State a clear recommendation when you have enough context, explain important tradeoffs, and name uncertainty without becoming evasive.
-```
-
-For more expressive products, add warmth, curiosity, humor, or point of view explicitly, but keep the block short. Use personality to shape the experience, not to compensate for unclear goals or missing task instructions.
-
-## Improve time to first visible token with a preamble
-
-In streaming applications, users notice how long it takes before the first visible response appears. GPT-5.5 may spend time reasoning, planning, or preparing tool calls before emitting visible text.
-
-For longer or tool-heavy tasks, prompt the model to start with a short preamble: a brief visible update that acknowledges the request and states the first step. This can improve perceived responsiveness without changing the underlying task.
-
-Use this pattern when the task may take more than one step, require tool calls, or involve a long-running agent workflow.
-
-```text
-Before any tool calls for a multi-step task, send a short user-visible update that acknowledges the request and states the first step. Keep it to one or two sentences.
-```
-
-For coding agents that expose separate message phases, you can be more explicit:
-
-```text
-You must always start with an intermediary update before any content in the analysis channel if the task will require calling tools. The user update should acknowledge the request and explain your first step.
-```
-
-## Outcome-first prompts and stopping conditions
-
-GPT-5.5 is strongest when the prompt defines the target outcome, success criteria, constraints, and available context, then lets the model choose the path.
-
-For many tasks, describe the destination rather than every step. This gives the model room to choose the right search, tool, or reasoning strategy for the task.
-
-Prefer this:
-
-```text
-Resolve the customer's issue end to end.
-
-Success means:
-- the eligibility decision is made from the available policy and account data
-- any allowed action is completed before responding
-- the final answer includes completed_actions, customer_message, and blockers
-- if evidence is missing, ask for the smallest missing field
-```
-
-**Avoid unnecessary absolute rules.** Older prompts often use strict instructions like `ALWAYS`, `NEVER`, `must`, and `only` to control model behavior. Use those words for true invariants, such as safety rules, required output fields, or actions that should never happen. For judgment calls, such as when to search, ask for clarification, use a tool, or keep iterating, prefer decision rules instead.
-
-Avoid this style of instruction unless every step is truly required:
-
-```text
-First inspect A, then inspect B, then compare every field, then think through
-all possible exceptions, then decide which tool to call, then call the tool,
-then explain the entire process to the user.
-```
-
-Add explicit stopping conditions:
-
-```text
-Resolve the user query in the fewest useful tool loops, but do not let loop minimization outrank correctness, accessible fallback evidence, calculations, or required citation tags for factual claims.
-
-After each result, ask: "Can I answer the user's core request now with useful evidence and citations for the factual claims?" If yes, answer.
-```
-
-Define missing-evidence behavior:
-
-```text
-Use the minimum evidence sufficient to answer correctly, cite it precisely, then stop.
-```
-
-## Formatting
-
-GPT-5.5 is highly steerable on output format and structure. Use that control when it improves comprehension or product fit.
-
-Set `text.verbosity`, describe the expected output shape, and reserve heavier structure for cases where it improves comprehension or your product UI needs a stable artifact. The API default for `text.verbosity` is `medium`; use `low` when you prefer shorter, more concise responses.
-
-Plain conversational formatting:
-
-```text
-Let formatting serve comprehension. Use plain paragraphs as the default format for normal conversation, explanations, reports, documentation, and technical writeups. Keep the presentation clean and readable without making the structure feel heavier than the content.
-
-Use headers, bold text, bullets, and numbered lists sparingly. Reach for them when the user requests them, when the answer needs clear comparison or ranking, or when the information would be harder to scan as prose. Otherwise, favor short paragraphs and natural transitions.
-
-Respect formatting preferences from the user. If they ask for a terse answer, minimal formatting, no bullets, no headers, or a specific structure, follow that preference unless there is a strong reason not to.
-```
-
-Add explicit audience and length guidance:
-
-```text
-Write for a senior business audience. Keep the answer under 400 words. Use short paragraphs and only include bullets when they improve scannability. Prioritize the conclusion first, then the reasoning, then caveats.
-```
-
-For editing, rewriting, summaries, or customer-facing messages, tell the model what to preserve before asking it to improve style. This pattern is useful when you want polish without expansion.
-
-```text
-Preserve the requested artifact, length, structure, and genre first. Quietly improve clarity, flow, and correctness. Do not add new claims, extra sections, or a more promotional tone unless explicitly requested.
-```
-
-## Grounding, citations, and retrieval budgets
-
-For grounded answers, citation behavior should be part of the prompt. Define what needs support, what counts as enough evidence, and how the model should behave when evidence is missing. Absence of evidence shouldn't automatically become a factual "no." For more details and examples, see the [citation formatting guide](/api/docs/guides/citation-formatting).
-
-### Add an explicit retrieval budget
-
-Retrieval budgets are stopping rules for search. They tell the model when enough evidence is enough.
-
-```text
-For ordinary Q&A, start with one broad search using short, discriminative keywords. If the top results contain enough citable support for the core request, answer from those results instead of searching again.
-
-Make another retrieval call only when:
-- The top results do not answer the core question.
-- A required fact, parameter, owner, date, ID, or source is missing.
-- The user asked for exhaustive coverage, a comparison, or a comprehensive list.
-- A specific document, URL, email, meeting, record, or code artifact must be read.
-- The answer would otherwise contain an important unsupported factual claim.
-
-Do not search again to improve phrasing, add examples, cite nonessential details, or support wording that can safely be made more generic.
-```
-
-## Creative drafting guardrails
-
-For drafting tasks, tell the model which claims must come from sources and which parts may be creatively written. This is especially important for slides, launch copy, customer summaries, talk tracks, leadership blurbs, and narrative framing.
-
-```text
-For creative or generative requests such as slides, leadership blurbs, outbound copy, summaries for sharing, talk tracks, or narrative framing, distinguish source-backed facts from creative wording.
-
-- Use retrieved or provided facts for concrete product, customer, metric, roadmap, date, capability, and competitive claims, and cite those claims.
-- Do not invent specific names, first-party data claims, metrics, roadmap status, customer outcomes, or product capabilities to make the draft sound stronger.
-- If there is little or no citable support, write a useful generic draft with placeholders or clearly labeled assumptions rather than unsupported specifics.
-```
-
-## Frontend engineering and visual taste
-
-For frontend work, refer to the [example instructions](/api/docs/guides/frontend-prompt) for practical ways to steer UI quality. They cover product and user context, design-system alignment, first-screen usability, familiar controls, expected states, responsive behavior, and common generated-UI defaults to avoid, such as generic heroes, nested cards, decorative gradients, visible instructional text, and broken layouts.
-
-## Prompt the model to check its work
-
-Give GPT-5.5 access to tools that let it check outputs when validation is possible.
-
-For coding agents, ask for concrete validation commands:
-
-```text
-After making changes, run the most relevant validation available:
-- targeted unit tests for changed behavior
-- type checks or lint checks when applicable
-- build checks for affected packages
-- a minimal smoke test when full validation is too expensive
-
-If validation cannot be run, explain why and describe the next best check.
-```
-
-For visual artifacts, ask for inspection after rendering:
-
-```text
-Render the artifact before finalizing. Inspect the rendered output for layout, clipping, spacing, missing content, and visual consistency. Revise until the rendered output matches the requirements.
-```
-
-For engineering and planning tasks, make implementation plans traceable:
-
-```text
-For implementation plans, include:
-- requirements and where each is addressed
-- named resources, files, APIs, or systems involved
-- state transitions or data flow where relevant
-- validation commands or checks
-- failure behavior
-- privacy and security considerations
-- open questions that materially affect implementation
-```
-
-## Phase parameter
-
-Starting with GPT-5.4, long-running or tool-heavy Responses workflows can use assistant-item `phase` values to distinguish intermediate updates from final answers. GPT-5.5 uses the same pattern.
-
-If you use `previous_response_id`, the API preserves prior assistant state automatically. If your application manually replays assistant output items into the next request, preserve each original `phase` value and pass it back unchanged. This matters most when a response includes preambles, repeated tool calls, or a final answer after intermediate assistant updates.
-
-```text
-If manually replaying assistant items:
-- Preserve assistant `phase` values exactly.
-- Use `phase: "commentary"` for intermediate user-visible updates.
-- Use `phase: "final_answer"` for the completed answer.
-- Do not add `phase` to user messages.
-```
-
-## Suggested prompt structure
-
-Use this structure as a starting point for complex prompts. Keep each section short. Add detail only where it changes behavior.
-
-```text
-Role: [1-2 sentences defining the model's function, context, and job]
-
-# Personality
-[tone, demeanor, and collaboration style]
-
-# Goal
-[user-visible outcome]
-
-# Success criteria
-[what must be true before the final answer]
-
-# Constraints
-[policy, safety, business, evidence, and side-effect limits]
-
-# Output
-[sections, length, and tone]
-
-# Stop rules
-[when to retry, fallback, abstain, ask, or stop]
-```

package/resources/local/codex/skills/.system/openai-docs/references/upgrade-guide.md

@@ -1,181 +0,0 @@
-# Upgrading to GPT-5.5
-
-Use this guide when the user explicitly asks to upgrade an existing integration to GPT-5.5. Pair it with current OpenAI docs lookups. The default target string is `gpt-5.5`.
-
-## Freshness check
-
-Before applying this bundled guide for a latest/current/default model upgrade, run `node scripts/resolve-latest-model-info.js` from the OpenAI Docs skill directory.
-
-- If the command returns `modelSlug: "gpt-5p5"`, continue with this bundled guide and use `references/prompting-guide.md` when prompt updates are needed.
-- If the command returns a different `modelSlug`, fetch both the returned `migrationGuideUrl` and `promptingGuideUrl` and use them as the current source of truth instead of the bundled references.
-- If the command fails, metadata is missing, or either remote guide cannot be fetched, continue with bundled fallback references and say the remote freshness check was unavailable.
-- If the user explicitly named a target model, preserve that target and use current docs only to check compatibility or caveats.
-
-## Upgrade posture
-
-Upgrade with the narrowest safe change set:
-
-- replace the model string first
-- update only the prompts that are directly tied to that model usage
-- do not automatically upgrade older or ambiguous model usages that may be intentionally pinned, such as historical docs, examples, tests, eval baselines, comparison code, or low-cost fallback/routing paths. Unless the user explicitly asks to upgrade all model usage, leave those sites unchanged and list them as confirmation-needed
-- prefer prompt-only upgrades when possible
-- if the upgrade would require API-surface changes, parameter rewrites, tool rewiring, provider migration, or broader code edits, mark it as blocked instead of stretching the scope
-
-## Upgrade workflow
-
-1. Inventory current model usage.
-   - Search for model strings, client calls, and prompt-bearing files.
-   - Include inline prompts, prompt templates, YAML or JSON configs, Markdown docs, and saved prompts when they are clearly tied to a model usage site.
-2. Pair each model usage with its prompt surface.
-   - Prefer the closest prompt surface first: inline system or developer text, then adjacent prompt files, then shared templates.
-   - If you cannot confidently tie a prompt to the model usage, say so instead of guessing.
-3. Classify the source model family.
-   - Common buckets: GPT-5.4, GPT-5.3-Codex or GPT-5.2-Codex, earlier GPT-5.x, GPT-4o or GPT-4.1, reasoning models such as o1 or o3 or o4-mini, third-party model, or mixed and unclear.
-4. Decide the upgrade class.
-   - `model string only`
-   - `model string + light prompt rewrite`
-   - `blocked without code changes`
-5. Run the compatibility gate.
-   - Check whether the current integration can accept `gpt-5.5` without API-surface changes or implementation changes.
-   - Check whether structured outputs, tool schemas, function names, and downstream parsers can remain unchanged.
-   - For long-running Responses or tool-heavy agents, check whether `phase` is already preserved or round-tripped when the host replays assistant items or uses preambles.
-   - If compatibility depends on code changes, return `blocked`.
-   - If compatibility is unclear, return `unknown` rather than improvising.
-6. Apply the upgrade when it is in scope.
-   - Default replacement string: `gpt-5.5`.
-   - Keep the intervention small and behavior-preserving.
-   - Start from the current reasoning effort when it is visible unless there is a measured reason to change it.
-   - For in-scope changes, update the model string and directly related prompts.
-   - For blocked or unknown changes, do not edit; report the blocker or uncertainty.
-7. Summarize the result.
-   - `Current model usage`
-   - `Model-string updates`
-   - `Reasoning-effort handling`
-   - `Prompt updates`
-   - `Structured output and formatting assessment`
-   - `Tool-use assessment` when the flow uses tools, retrieval, or terminal actions
-   - `Phase assessment` when the flow is long-running, replayed, or tool-heavy
-   - `Compatibility check`
-   - `Validation performed`
-
-Output rule:
-
-- For each usage site, state the starting reasoning-effort recommendation.
-- If the repo exposes the current reasoning setting, recommend preserving it first unless current OpenAI docs say otherwise.
-- If the repo does not expose the current setting, recommend not adding one unless current OpenAI docs require it.
-
-## Upgrade outcomes
-
-### `model string only`
-
-Choose this when:
-
-- the source model is GPT-5.4
-- the existing prompts are already short, explicit, and task-bounded
-- the workflow does not rely on strict output formats, tool-call behavior, batch completeness, or long-horizon execution that should be validated after the upgrade
-- there are no obvious compatibility blockers
-
-Default action:
-
-- replace the model string with `gpt-5.5`
-- preserve the current reasoning effort
-- keep prompts unchanged
-- validate behavior with existing tests, realistic spot checks, or an existing eval suite when one is already available
-
-### `model string + light prompt rewrite`
-
-Choose this when:
-
-- the task needs stronger completeness, citation discipline, verification, or dependency handling
-- the upgraded model becomes too verbose, too dense, or hard to scan unless formatting is constrained
-- the workflow has strict output shape requirements and lacks an explicit format contract, schema, or parser validation
-- the workflow is research-heavy and needs stronger handling of sparse or empty retrieval results
-- the workflow is coding-oriented, terminal-based, tool-heavy, or multi-agent, but the existing API surface and tool definitions can remain unchanged
-
-Default action:
-
-- replace the model string with `gpt-5.5`
-- preserve the current reasoning effort for the first pass
-- make only the smallest prompt edits needed for the observed workflow risk
-- read the [GPT-5.5 prompting guide](/api/docs/guides/prompt-guidance?model=gpt-5.5) to choose the smallest prompt changes that recover or improve behavior
-- avoid broad prompt cleanup unrelated to the upgrade
-- for research workflows, add citation rules, retrieval budgets, missing-evidence behavior, and validation guidance from the prompting guide
-- for dependency-aware or tool-heavy workflows, add prerequisite checks, missing-context handling, explicit tool budgets, stop conditions, and validation guidance
-- for coding or terminal workflows, add repo-specific constraints, acceptance criteria, and concrete validation commands
-- for multi-agent support or triage workflows, add task ownership, handoff, completeness, and stopping criteria
-- for long-running Responses agents with preambles or multiple assistant messages, explicitly review whether `phase` is already handled; if adding or preserving `phase` would require code edits, mark the path as `blocked`
-- do not classify a coding or tool-using Responses workflow as `blocked` just because the visible snippet is minimal; prefer `model string + light prompt rewrite` unless the repo clearly shows that a safe GPT-5.5 path would require host-side code changes
-
-### `blocked`
-
-Choose this when:
-
-- the upgrade appears to require API-surface changes
-- the upgrade appears to require parameter rewrites or reasoning-setting changes that are not exposed outside implementation code
-- the upgrade would require changing tool definitions, tool handler wiring, or schema contracts
-- the user is asking for a tooling, IDE, plugin, shell, or environment migration rather than a model and prompt migration
-- the integration depends on provider-specific APIs that do not map to the current OpenAI API surface without implementation work
-- you cannot confidently identify the prompt surface tied to the model usage
-
-Default action:
-
-- do not improvise a broader upgrade
-- report the blocker and explain that the fix is out of scope for this guide
-- if useful, describe the smallest follow-up implementation task that would unblock the migration
-
-## Compatibility checklist
-
-Before applying or recommending a model-and-prompt-only upgrade, check:
-
-1. Can the current host accept the `gpt-5.5` model string without changing client code or API surface?
-2. Are the related prompts identifiable and editable?
-3. Does the host depend on behavior that likely needs API-surface changes, parameter rewrites, provider migration, or tool rewiring?
-4. Would the likely fix be prompt-only, or would it need implementation changes?
-5. Is the prompt surface close enough to the model usage that you can make a targeted change instead of a broad cleanup?
-6. Do strict structured outputs, schemas, or downstream parsers still have an explicit contract?
-7. For long-running Responses or tool-heavy agents, is `phase` already preserved if the host relies on preambles, replayed assistant items, or multiple assistant messages?
-8. Are latency, token, or price assumptions validated by tests, realistic spot checks, or an existing eval suite rather than inferred from general model positioning?
-
-If item 1 is no, items 3 through 4 point to implementation work, or item 7 is no and the fix needs code changes, return `blocked`.
-
-If item 2 is no, return `unknown` unless the user can point to the prompt location.
-
-Important:
-
-- Existing use of tools, agents, or multiple usage sites is not by itself a blocker.
-- If the current host can keep the same API surface and the same tool definitions, prefer `model string + light prompt rewrite` over `blocked`.
-- Reserve `blocked` for cases that truly require implementation changes, not cases that only need stronger prompt steering.
-- Do not claim token savings without task-level validation.
-
-## Scope boundaries
-
-This guide may:
-
-- update or recommend updated model strings
-- update or recommend updated prompts
-- inspect code and prompt files to understand where those changes belong
-- inspect whether existing Responses flows already preserve `phase`
-- flag compatibility blockers
-- propose validation with existing tests, realistic spot checks, or existing eval suites
-
-This guide may not:
-
-- move Chat Completions code to Responses
-- move Responses code to another API surface
-- migrate SDKs, APIs, IDE configuration, shell hooks, plugins, or provider-specific tooling
-- rewrite parameter shapes
-- change tool definitions or tool-call handling
-- change structured-output wiring
-- add or retrofit `phase` handling in implementation code
-- edit business logic, orchestration logic, SDK usage, IDE configuration, shell hooks, or plugin integration behavior except for model-string replacements and directly related prompt edits
-
-If a safe GPT-5.5 upgrade requires any of those changes, mark the path as blocked and out of scope.
-
-## Validation plan
-
-- Validate each upgraded usage site with existing tests, realistic spot checks, or an existing eval suite when one is already available.
-- Compare against the current GPT-5.4 baseline when available.
-- Check task success, retry count, tool-call count, total tokens, latency, output shape, and user-visible quality.
-- For specialized workflows, validate the contract that matters most instead of judging only general output quality.
-- If prompt edits were added, confirm each block is doing real work instead of adding noise.
-- If the workflow has downstream impact, add a lightweight verification pass before finalization.