@bastani/atomic 0.9.45 → 0.9.46

package/dist/builtin/workflows/builtin/goal.js

@@ -1,7 +1,7 @@
 import {
   goal_default
-} from "./chunk-vwx023ge.js";
-import"./chunk-jvna28mq.js";
+} from "./chunk-qhm35ntx.js";
+import"./chunk-zhyqnf5g.js";
 import"./chunk-2377r57g.js";
 import"./chunk-z0d03ktm.js";
 import"./chunk-n1910xc4.js";

package/dist/builtin/workflows/builtin/index.js

@@ -16,8 +16,8 @@ import {
 } from "./chunk-z3pajrfs.js";
 import {
   goal_default
-} from "./chunk-vwx023ge.js";
-import"./chunk-jvna28mq.js";
+} from "./chunk-qhm35ntx.js";
+import"./chunk-zhyqnf5g.js";
 import"./chunk-z0d03ktm.js";
 import {
   open_claude_design_default
@@ -27,7 +27,7 @@ import {
 } from "./chunk-dcxscfnb.js";
 import {
   ralph_default
-} from "./chunk-6901nsd6.js";
+} from "./chunk-6jpwc09k.js";
 import {
   tournament_default
 } from "./chunk-49kkbdpr.js";

package/dist/builtin/workflows/builtin/ralph.js

@@ -1,7 +1,7 @@
 import {
   ralph_default
-} from "./chunk-6901nsd6.js";
-import"./chunk-jvna28mq.js";
+} from "./chunk-6jpwc09k.js";
+import"./chunk-zhyqnf5g.js";
 import"./chunk-2377r57g.js";
 import"./chunk-z0d03ktm.js";
 import"./chunk-n1910xc4.js";

package/dist/builtin/workflows/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bastani/workflows",
-  "version": "0.9.45",
+  "version": "0.9.46",
   "private": true,
   "description": "Atomic extension for multi-stage workflow authoring and execution.",
   "contributors": [

package/dist/builtin/workflows/skills/prompt-engineer/SKILL.md

@@ -29,6 +29,7 @@ Create or revise prompts for the user's target model. Keep the common prompt por
 | Target | Read | Main distinctions |
 | --- | --- | --- |
 | GPT-6.1 Sol | `references/gpt_6_1_sol.md` | Supported-effort migration, task and approval contracts, selective Astra-observed templates, tool and conversation compatibility |
+| GPT-6.1 Terra | `references/gpt_6_1_terra.md` | Visual, computer-use, and writing task contracts; start at `medium` effort (`none` supported); same-effort migration from GPT-5.6 Terra; selective Astra-observed templates |
 | GPT-6 Astra, Sol, Luna | `references/gpt_6.md` | OpenAI's official templates for approval pauses, skill-instruction conflicts, writing style, delegation, and verification; Sol/Luna effort sensitivity |
 | GPT-5.6 Sol, Terra, Luna | `references/gpt_5_6.md` | Lean prompts, concise defaults, high-effort and pro-mode prompts, programmatic tool stages, cache-friendly ordering |
 | GPT-5.5 | `references/gpt_5_5.md` | Outcome-first baseline, retrieval limits, grounded drafts, explicit validation |

package/dist/builtin/workflows/skills/prompt-engineer/references/gpt_6.md

@@ -2,7 +2,7 @@
 
 Use this reference when targeting `gpt-6-astra`, `gpt-6-sol`, or `gpt-6-luna`, migrating a prompt to the GPT-6 family, or diagnosing early stops, excessive verification, under-delegation, or writing-style drift. Guidance checked on September 22, 2026 against [OpenAI's GPT-6 guide](https://developers.openai.com/api/docs/guides/latest-model). The prompt blocks labeled **OpenAI template** are quoted verbatim from that guide. Start from them, then edit the wording to fit the product's approval gates and house style.
 
-OpenAI positions the three models by reasoning demand, latency, and cost: Astra for the highest capability and long multi-step work across code, browsers, and professional software; Sol for strong reasoning on demanding tasks; Luna for efficient, repeatable work at scale. OpenAI offers the templates below as a starting point for the whole family, but the behaviors they address were observed on Astra. Evaluate them on the chosen model and workload. See [Sol and Luna differences](#sol-and-luna-differences) before choosing effort or a tool-calling API.
+OpenAI positions the three models by reasoning demand, latency, and cost: Astra for the highest capability and long multi-step work across code, browsers, and professional software; Sol for strong reasoning on demanding tasks; Luna for efficient, repeatable work at scale. OpenAI offers the templates below as a starting point for the whole family, but the behaviors they address were observed on Astra. Evaluate them on the chosen model and workload. See [Sol and Luna differences](#sol-and-luna-differences) before choosing effort or a tool-calling API. For `gpt-6.1-sol` and `gpt-6.1-terra`, start with [gpt_6_1_sol.md](gpt_6_1_sol.md) or [gpt_6_1_terra.md](gpt_6_1_terra.md), which link back here for the shared templates.
 
 ## When it asks before doing authorized work
 
@@ -79,7 +79,7 @@ OpenAI template, for reducing jargon and stock phrases:
 ```text
 Avoid using slop words or phrases like "Bottom Line:" in conclusions, "delve," "foster," "leverage," "it's worth noting," "importantly," "Question? Answer." or "This isn't about X. It's about Y.", "genuinely" or hyphenated compound descriptions and adjectives. Do not use concluding summary statements such as "In short:..", "The simplest mental model is:...".
 
-State the intended action directly. Avoid adding what you won't do, what will remain unchanged, or how you'll separate or categorize results. Do not use contrastive framing such as "X, not Y" or "X—not Y" that introduces an unprompted alternative that the user didn't ask about. Avoid invented compound labels like "exact-head checks" and "editorial-row layouts", vague qualifiers, and canned transitions; use plain verbs and prepositions to state the actual relationship directly.
+State the intended action directly. Avoid adding what you won't do, what will remain unchanged, or how you'll separate or categorize results. Do not use contrastive framing such as "X, not Y" that introduces an unprompted alternative that the user didn't ask about. Avoid invented compound labels like "exact-head checks" and "editorial-row layouts", vague qualifiers, and canned transitions; use plain verbs and prepositions to state the actual relationship directly.
 ```
 
 Caveats: do not trim contractual fields, citations, validation evidence, or warnings the reader needs. For technical audiences, plain language still includes exact identifiers, commands, and API names. If a parser or UI requires Markdown, tables, or fixed headings, state that requirement after the style template so it wins.

package/dist/builtin/workflows/skills/prompt-engineer/references/gpt_6_1_sol.md

@@ -1,6 +1,6 @@
 # GPT-6.1 Sol prompting and migration
 
-Use this reference when targeting `gpt-6.1-sol` or migrating from `gpt-6-sol`. Distilled from [OpenAI's GPT-6 Astra and GPT-6.1 Sol guide](https://developers.openai.com/api/docs/guides/latest-model?model=gpt-6-astra#gpt-6-astra-gpt-61-sol), checked September 30, 2026. OpenAI recommends Sol 6.1 for complex coding, computer use, and professional work when balancing quality and cost. Compare models on your own tasks; this positioning is not a measured improvement for your workload.
+Use this reference when targeting `gpt-6.1-sol` or migrating from `gpt-6-sol`. Distilled from [OpenAI's GPT-6 Astra and GPT-6.1 Sol guide](https://developers.openai.com/api/docs/guides/prompt-guidance#gpt-61-sol), checked September 30, 2026; the Sol section was rechecked October 26, 2026. OpenAI describes Sol 6.1 as delivering near-Astra performance at a lower cost for complex coding, computer use, and professional work. Compare models on your own tasks; this positioning is not a measured improvement for your workload. For GPT-6.1 Terra, see [gpt_6_1_terra.md](gpt_6_1_terra.md).
 
 The source separates Sol 6.1 specifications and migration guidance from shared prompt templates. Those templates address behavior observed with Astra, not independently established Sol 6.1 behavior. Apply them only to failures you observe on Sol 6.1. The snippets below are adaptations, not verbatim OpenAI quotations.
 
@@ -59,7 +59,7 @@ Sol 6.1 tool calling requires the Responses API; Chat Completions supports reque
 
 The official guide also describes shared GPT-6 async tool calling, mid-turn steering, and changing reasoning effort while preserving the prompt cache. These require application support. Do not assume Atomic or another host implements each feature because a prompt names it. Check the relevant [async tool calling](https://developers.openai.com/api/docs/guides/async-tool-calling), [steering](https://developers.openai.com/api/docs/guides/steering), or [reasoning configuration](https://developers.openai.com/api/docs/guides/reasoning#change-reasoning-mid-conversation) contract before relying on it.
 
-For application migration details, consult the source's [API and model parameters checklist](https://developers.openai.com/api/docs/guides/latest-model?model=gpt-6-astra#gpt-6-astra-migration-quickstart). It covers unsupported sampling and logprob parameters during reasoning, cache configuration changes, and feature compatibility. Those are host changes, not extra prompt instructions. Astra's monitoring and speed-availability descriptions are not Sol 6.1-specific prompting recommendations.
+For application migration details, consult the source's [API and model parameters checklist](https://developers.openai.com/api/docs/guides/prompt-guidance#update-api-and-model-parameters). It covers unsupported sampling and logprob parameters during reasoning, cache configuration changes, and feature compatibility. Those are host changes, not extra prompt instructions. Astra's monitoring and speed-availability descriptions are not Sol 6.1-specific prompting recommendations.
 
 ## Validate one adjustment
 

package/dist/builtin/workflows/skills/prompt-engineer/references/gpt_6_1_terra.md

@@ -0,0 +1,77 @@
+# GPT-6.1 Terra prompting and migration
+
+Use this reference when targeting `gpt-6.1-terra` or migrating from GPT-5.6 Terra. Distilled from the GPT-6.1 Terra section and migration checklist of [OpenAI's GPT-6 guide](https://developers.openai.com/api/docs/guides/prompt-guidance#gpt-61-terra), the [model page](https://developers.openai.com/api/docs/models/gpt-6.1-terra), the [GPT-6.1 Terra announcement](https://openai.com/index/introducing-gpt-6-1-terra), and [A model guide for the GPT-6 family](https://openai.com/index/practical-guide-building-gpt-6/), all checked October 26, 2026.
+
+The guide's shared prompt templates address behavior observed with GPT-6 Astra, not independently established Terra behavior. OpenAI gives no Terra-specific prompt wording. Apply the shared templates only to failures you observe on Terra. The snippets below are adaptations, not verbatim OpenAI quotations.
+
+## When to choose Terra
+
+OpenAI positions Terra as a fast, efficient model for visual reasoning, precise computer use, and clear, natural writing. Its stated uses are matching product photos to catalog entries, comparing or interpreting technical drawings, acting on application screens, and drafting and revising text. The announcement also names high-volume automation, such as reading incoming invoices and entering their details into accounting software, and says GPT-6.1 Sol and GPT-6 Astra remain the better choice for the most complex coding tasks. Terra accepts text and image input and returns text.
+
+This positioning is not a measured result for your workload. Compare Terra with the model you would otherwise use on representative inputs before routing work to it.
+
+## Start with the task contract
+
+State the result, who it is for, the relevant context and constraints, and what counts as done. For visual work, name the inputs and what to compare them against. Begin with the prompt that already works, then change one prompt or configuration variable at a time.
+
+```text
+Complete [requested outcome] using [images, screens, or documents provided].
+Compare against [criteria or reference entries]. Stay within [scope].
+Preserve [binding constraints] and stop before [actions requiring approval].
+Return [required format], including [evidence and validation results].
+If a required detail is not present or legible in the input, identify it
+rather than inventing it.
+```
+
+Replace the placeholders with the actual task. A request to read or extract does not authorize submitting forms, and a drafting request does not authorize sending the text.
+
+## Choosing reasoning effort
+
+Terra supports `none`, `low`, `medium` (default), `high`, `xhigh`, and `max`. OpenAI's advice is to start with `medium` and increase effort only if the quality improvement is worth the added time and tokens. Unlike GPT-6 Astra and GPT-6.1 Sol, Terra supports `none`.
+
+The family model guide maps effort to work type across GPT-6 models: `low` for routine tasks such as extracting facts or making small edits, `medium` for work requiring judgment such as planning or comparing options, `high` for difficult debugging, deeper analysis, or careful review, and `xhigh` or `max` to test when `high` falls short, kept only if the improvement justifies the time and cost. The sources do not describe how sensitive Terra is to effort, so measure it rather than assuming the Sol and Luna behavior in the [GPT-6 family reference](gpt_6.md#sol-and-luna-differences) applies.
+
+Keep the prompt fixed while comparing efforts. Do not compensate for a lower effort by adding repeated instructions; that hides which change caused the result. A prompt cannot select effort; the application's request does.
+
+## When migrating from GPT-5.6 Terra
+
+OpenAI's migration advice is specific: compare both models on representative images and workflows using the same reasoning effort. Preserve the current effective effort where Terra supports it. If the existing request uses `minimal`, start with `low` and compare representative tasks.
+
+Run the unchanged prompt on both models first. Measure task success, answer correctness on your images, completion of screen workflows, tool behavior, latency, tokens, and cost per successful task. Change the prompt only for a regression you can point to, and retest after each change.
+
+Two host changes are not prompt fixes. If the application calls tools through Chat Completions, move those requests to the Responses API; Terra supports Chat Completions only for requests without tools. When effort is not `none`, sampling and logprob parameters must be removed; see the source's [API and model parameters checklist](https://developers.openai.com/api/docs/guides/prompt-guidance#update-api-and-model-parameters).
+
+## Computer use and screen work
+
+OpenAI points to the [computer use guide](https://developers.openai.com/api/docs/guides/tools-computer-use) for acting on screens and the [image inputs guide](https://developers.openai.com/api/docs/guides/images-vision) for visual analysis. The family model guide, whose model and computer-use sections name Astra, Sol, and Luna but not Terra, recommends choosing the simplest reliable way to do each step: use an API or connected tool when it can do the job directly, and use computer use when the model needs to read a screen, click buttons, or fill in a form. It also recommends replacing blanket "always ask" rules with explicit boundaries for what can proceed independently.
+
+```text
+For each step, use [API or connected tool] when it can complete the step
+directly. Use the screen only to read information, click, or fill in fields
+that no tool covers. You may [independent actions]. Before [submitting,
+sending, purchasing, or deleting], stop and show what you will submit.
+```
+
+Computer use requires the host to provide the tool and a harness that controls the browser or desktop. Naming it in a prompt does not enable it.
+
+## Writing and revision
+
+For drafting and revision, the family model guide recommends describing what a useful response looks like, for example plain language, technical detail suited to the audience, and a short handoff covering what changed, what was checked, and what still needs attention. Name the audience, register, length, and the facts the text must keep. The sources do not say whether Terra shares Astra's tendency toward formatted, detailed answers; use the [writing-style templates](gpt_6.md#when-responses-are-too-formatted-or-too-long) only if you observe it.
+
+## When an Astra template addresses an observed failure
+
+| Observed failure on your Terra task | Selective reference | Boundary to preserve |
+| --- | --- | --- |
+| Stops before completing authorized work, or asks non-blocking questions | [Initiative and follow-through](gpt_6.md#when-it-asks-before-doing-authorized-work) | Real approval gates, especially form submissions and external writes |
+| A skill or repository instruction causes an unexplained pause | [Instruction following](gpt_6.md#when-skills-or-repo-instructions-change-behavior) | System, security, permission, and higher-priority repository rules |
+| Answers are too detailed, formatted, or repetitive | [Writing style](gpt_6.md#when-responses-are-too-formatted-or-too-long) | Required fields, citations, evidence, and parser format |
+| Useful independent work is not delegated | [Delegation](gpt_6.md#when-it-under-delegates-or-over-serializes-work) | Actual host capabilities, concurrency, cost, and file ownership |
+| Small changes trigger repeated or unrelated verification | [Testing and verification](gpt_6.md#when-it-tests-too-broadly-or-repeats-checks) | Required project checks, safety checks, and user-requested validation |
+
+Do not treat these as Terra tendencies merely because the templates are shared. Test the smallest applicable adjustment first.
+
+Async tool calling, mid-turn steering, and changing effort with `configuration_update` are shared GPT-6 features that need application support. Check the [async tool calling](https://developers.openai.com/api/docs/guides/async-tool-calling), [steering](https://developers.openai.com/api/docs/guides/steering), or [reasoning configuration](https://developers.openai.com/api/docs/guides/reasoning#change-reasoning-mid-conversation) contract before relying on one. Fast mode and data-residency availability are deployment choices, not prompting recommendations.
+
+## Validate one adjustment
+
+Use representative cases for your workload: an image-matching or extraction case with a known answer, a drawing or document comparison, a screen workflow that reaches an approval boundary, a drafting or revision task, an early-stop case, and a format-sensitive answer. Compare the unchanged baseline with one adjustment at the same effort. Verify correctness against the known answers, completed workflows, output validity, respected approval boundaries, and cost per successful task. Then compare effort separately if needed. Report checks that were not run; do not claim an improvement without observed results.

package/dist/builtin/workflows/src/authoring.d.ts

@@ -8,7 +8,7 @@ export type { RunJournalOption, RunJournalSettings } from "./durable/journal/res
 export { resolveRunJournal } from "./durable/journal/resolution.js";
 export { openSqlRunJournal, SqlRunJournal } from "./durable/journal/sqlite-run-journal.js";
 export * from "./durable/journal/types.js";
-export type { AgentSessionAdapter, CompleteAdapter, CompleteStageOpts, EffectiveBudget, GitWorktreeSetupOptions, GitWorktreeSetupResult, PromptAdapter, PromptOptions, ResolvedInputs, RunResult, RunStatus, StageAdapters, StageContext, StageExecutionMeta, StageMcpOptions, StageOptions, StageOutputOptions, StagePromptOptions, StageSendUserMessageOptions, StageSessionCreateOptions, StageSessionCreateResult, StageSessionEvent, StageSessionRuntime, StageSnapshot, StageStatus, StageUserMessageContent, StageUserMessageDelivery, ToolNodeSnapshot, WorkflowAction, WorkflowArtifact, WorkflowBudget, WorkflowChainOptions, WorkflowChildResult, WorkflowContextMode, WorkflowControlEvent, WorkflowCustomToolDefinition, WorkflowCustomUiComponent, WorkflowCustomUiFactory, WorkflowCustomUiKeybindings, WorkflowCustomUiOptions, WorkflowCustomUiOverlayHandle, WorkflowCustomUiOverlayOptions, WorkflowCustomUiTheme, WorkflowCustomUiTui, WorkflowDetails, WorkflowDetailsMode, WorkflowDetailsStatus, WorkflowExecutionMode, WorkflowExecutionPolicy, WorkflowExitOptions, WorkflowExitStatus, WorkflowInputBindings, WorkflowInputSchema, WorkflowInputSchemaMap, WorkflowInputValues, WorkflowIntercomSummary, WorkflowMaxOutput, WorkflowMcpPort, WorkflowModelAttempt, WorkflowModelCatalogPort, WorkflowModelFallbackFields, WorkflowModelInfo, WorkflowModelUsage, WorkflowModelValue, WorkflowOutputMode, WorkflowOutputSchema, WorkflowOutputSchemaMap, WorkflowOutputValues, WorkflowParallelFailure, WorkflowParallelOptions, WorkflowPersistencePort, WorkflowProgressSummary, WorkflowProviderRateLimit, WorkflowRunChildArgs, WorkflowRunChildOptions, WorkflowRunChildOptionsArgument, WorkflowRunOutput, WorkflowRuntimeConfig, WorkflowSerializableObject, WorkflowSerializablePrimitive, WorkflowSerializableValue, WorkflowSharedTaskDefaults, WorkflowTaskContext, WorkflowTaskContextInput, WorkflowTaskOptions, WorkflowTaskResult, WorkflowTaskSessionFields, WorkflowTaskSessionOptions, WorkflowTaskStep, WorkflowThinkingLevel, WorkflowToolContext, WorkflowToolError, WorkflowToolFailure, WorkflowToolOptions, WorkflowToolOutcome, WorkflowToolPrimitive, WorkflowToolReturnOptions, WorkflowToolSuccess, WorkflowToolThrowOptions, WorkflowUIAdapter, WorkflowUIContext, WorkflowWorktreeInputBinding, } from "./shared/authoring-contract.js";
+export type { AgentSessionAdapter, CompleteAdapter, CompleteStageOpts, EffectiveBudget, GitWorktreeSetupOptions, GitWorktreeSetupResult, PromptAdapter, PromptOptions, ResolvedInputs, RunFailureClassification, RunResult, RunStatus, StageAdapters, StageContext, StageExecutionMeta, StageMcpOptions, StageOptions, StageOutputOptions, StagePromptOptions, StageSendUserMessageOptions, StageSessionCreateOptions, StageSessionCreateResult, StageSessionEvent, StageSessionRuntime, StageSnapshot, StageStatus, StageUserMessageContent, StageUserMessageDelivery, ToolNodeSnapshot, WorkflowAction, WorkflowArtifact, WorkflowBudget, WorkflowChainOptions, WorkflowChildResult, WorkflowContextMode, WorkflowControlEvent, WorkflowCustomToolDefinition, WorkflowCustomUiComponent, WorkflowCustomUiFactory, WorkflowCustomUiKeybindings, WorkflowCustomUiOptions, WorkflowCustomUiOverlayHandle, WorkflowCustomUiOverlayOptions, WorkflowCustomUiTheme, WorkflowCustomUiTui, WorkflowDetails, WorkflowDetailsMode, WorkflowDetailsStatus, WorkflowExecutionMode, WorkflowExecutionPolicy, WorkflowExitOptions, WorkflowExitStatus, WorkflowInputBindings, WorkflowInputSchema, WorkflowInputSchemaMap, WorkflowInputValues, WorkflowIntercomSummary, WorkflowMaxOutput, WorkflowMcpPort, WorkflowModelAttempt, WorkflowModelCatalogPort, WorkflowModelFallbackFields, WorkflowModelInfo, WorkflowModelUsage, WorkflowModelValue, WorkflowOutputMode, WorkflowOutputSchema, WorkflowOutputSchemaMap, WorkflowOutputValues, WorkflowParallelFailure, WorkflowParallelOptions, WorkflowPersistencePort, WorkflowProgressSummary, WorkflowProviderRateLimit, WorkflowRunChildArgs, WorkflowRunChildOptions, WorkflowRunChildOptionsArgument, WorkflowRunOutput, WorkflowRuntimeConfig, WorkflowSerializableObject, WorkflowSerializablePrimitive, WorkflowSerializableValue, WorkflowSharedTaskDefaults, WorkflowTaskContext, WorkflowTaskContextInput, WorkflowTaskOptions, WorkflowTaskResult, WorkflowTaskSessionFields, WorkflowTaskSessionOptions, WorkflowTaskStep, WorkflowThinkingLevel, WorkflowToolContext, WorkflowToolError, WorkflowToolFailure, WorkflowToolOptions, WorkflowToolOutcome, WorkflowToolPrimitive, WorkflowToolReturnOptions, WorkflowToolSuccess, WorkflowToolThrowOptions, WorkflowUIAdapter, WorkflowUIContext, WorkflowWorktreeInputBinding, } from "./shared/authoring-contract.js";
 import type * as AuthoringContract from "./shared/authoring-contract.js";
 import type { AuthoredWorkflowSpec as SharedAuthoredWorkflowSpec, WorkflowInputsFromSchemas, WorkflowOutputsFromSchemas, WorkflowProvidedInputsFromSchemas } from "./shared/workflow-authoring-types.js";
 export type { WorkflowInputsFromSchemas, WorkflowOutputsFromSchemas, WorkflowProvidedInputsFromSchemas, } from "./shared/workflow-authoring-types.js";

package/dist/builtin/workflows/src/durable/journal/internal.d.ts

@@ -18,6 +18,8 @@ export declare function runJournalAppendMany(journal: RunJournal): RunJournalApp
 export type JournalAppendGuard = (tx: SqliteExecutor, runId: string) => Promise<void>;
 export interface SqlPoolStorage {
     transaction<T>(body: (tx: SqliteExecutor) => Promise<T>): Promise<T>;
+    /** Statements outside any transaction: they read the last commit without taking the shared write lock. */
+    read<T>(body: (executor: SqliteExecutor) => Promise<T>): Promise<T>;
     withAppendGuard<T>(guard: JournalAppendGuard, action: () => Promise<T>): Promise<T>;
     readonly tables: Readonly<{
         runs: string;