6.0 KiB
Preserved chat catalog source
This branch consolidates reviewed eval changes for all 244 frozen scenarios:
242 lazy catalog entries and the two existing standalone chat flows. It preserves
source implementations, controls and evidence contracts. It does not establish
that all scenarios are ready to run or that this composed head has passed a live
campaign. The machine-readable inventory is chat-catalog-preservation.json.
The production baseline remains 39e811c9c5226979fce42e052a27cfb28301018a.
No production, workflow, lockfile or SDK source change is included. The real
new-company, formal-hire and routine-history definitions retain prerequisites
18103, 18105 and 18033 respectively. Those focused fixes are excluded here; their
candidate outcomes remain separate from frozen-baseline qualification.
Composition preserves the per-scenario descriptor union, both independent SDK privacy and new-company security sections, the final formal-hire clock module, and the stronger shared Notes provider used by status cards and routine history. The accepted original-deadline and multipart controls are included, as is the new-company successor's original phase deadline and remaining-time wizard clamp. Frozen queries, contexts, outcomes, turn/human counts and overall caps are retained.
The accepted SDK2 overlay binds least-scope setup to the actual public Agent lifecycle/version and a new real plugin resume receipt within the existing 90-second wait. Managed-routine setup identifies only its saved routine and plugin through ordinary conversation context and independent CEO readback; structural JSON comparisons ignore object key order while preserving all values, arrays, ownership and explanation checks. A pending question still fails the required outcome.
The task prerequisite overlay binds two genuine ready owners to their completed public manual pauses, exact versions and holds before inventory seeding. It also adds the owned browser Origin to the existing human attachment upload, preserving the real board mutation guard and exact company/task/comment/byte checks. Neither overlay changes canonical messages, native/human counts, overall caps or an exhausted case's result. The production core fixes remain excluded.
The document and decision-audience overlay preserves exact public document identity, revision and bytes through the shipped Plans control, and reads a pending addressed decision through the actual authenticated recipient's feed. It requires both the owner and recipient identities. Its measured final failures remain unchanged and exhausted; source preservation gives them no new cycle.
The outbound-email observer accepts ordinary standing-chat work with a null parent only when the canonical source run, creator, public audit and real native assignment admission agree. It also preserves the supported public issue-create wake shape. The email task still links explicitly to that work and the exact owned thread/endpoint; original draft, recipient, native send, provider receipt, duplicate and truthful delivery checks remain. Actual authorized AgentMail resources and input delivery are separate prerequisites, with no source-only runtime pass or implicit credential-transfer permission.
Readiness is separate from importability. Declared unsupported fresh contexts, public capability/profile gaps and external resource/authorization requirements remain explicit. The preserved plugin configure/disable fixture still has a known secret-ref schema mismatch: it sends an object where its public string schema requires a secret UUID. Disable's returned final reached that setup request and received HTTP 400. Configure's returned final stopped earlier while waiting for the initial chat response; its later UI/configuration leg was not exercised, so the schema mismatch there is a source finding. Both spent raw failures remain unchanged and are not rerun by this consolidation. Other measured failures retain their actual interpretation. The legacy Projects manual-order surface required by sidebar-order is absent from both frozen-production layouts; this source does not revive it or inject a classic interface to manufacture the frozen context.
Every historical result remains attached to its original source revision, full fingerprint, provider/model/build/database evidence, ordinal, usage, cost, privacy and cleanup. The integrated source changes broad fingerprint closures; none of the older qualified passes is transferred to this head. No attempt budget is reset, and no live launch or publication authority comes from this source preservation.
Integration candidate, 2026-10-31
This owned integration branch combines preserved source e2b35be76f with
master 51ea624344. The original preservation branch and its historical results
remain unchanged. No historical pass transfers to this composed source.
The frozen 244-case OpenCode catalog keeps its historical IDs and DeepSeek 1017
model. The two shipped subscription aliases and the separate TestOps backlog cell
remain selectable alongside it; they do not change the frozen denominator.
The standalone aliases retain the current shipped 120-second turn limit.
Catalog phase and attempt budgets remain separately declared by their fixtures.
The integration compatibility checks distinguish the 244 historical cells from the three shipped aliases. Fixtures implement current run-observation and conversation-link custody contracts. The standalone flows keep shipped timeout behavior; catalog-native setup still verifies its separately declared policy. Synthetic public-schema tests hash their copied synthetic inputs, while the production frozen source manifest and all private-value rejection checks remain unchanged. No SDK runtime qualification follows from those synthetic tests.
The refreshed base includes current master's committed Agent Chat reply recovery and durable retry deadlines. It also contains event-driven issue/receipt recovery and the guard against a native run changing its own task status. These are upstream product changes, not qualifications of the preserved scenarios. Fresh pilots remain bound to their exact source.