[schickling]

Problem and goal

Host st-chatgpt's Fractal adapter naming change against main at reviewed full head 7f3d4ac6edad7789c5a8d0c1762b2ed90957a70d, so hosted CI provides the proof instead of a dev3 agent signature.

Decisions and references

• Original branch: schickling-assistant/2026-11-07-chatgpt-fractal-surface-rename. Original PR: fix(chatgpt): embrace Fractal adapter naming #5591.
• Exact-head GO (independent reviewer): fix(chatgpt): embrace Fractal adapter naming #5591 (comment)
• Scope: crates/fractal-chatgpt, docs and one release note (8 files, +79/-26). No added St3Error.

Verification

Builds, tests, formatters and smoke checks: NOT RUN by this hosting script. Hosted CI and readiness require a separate authorized person-boundary action.

Complexity

Hosting existing reviewed commits; no source modifications or new abstraction.

Concerns and follow-ups

This remains draft; this script does not mark ready, enroll, enable auto-merge or land.

Friction and bottlenecks

An existing original PR requires a distinct hosted ref, never an owner-branch update.

[chatgpt-codex-connector]

Codex Review Summary: ✅ Completed

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-11-07T09:20:35.131512Z	7f3d4ac	Draft marked ready

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[schickling-assistant]

U04 exposure audit: PASS at 7f3d4ac6edad7789c5a8d0c1762b2ed90957a70d

Delta and integrity

• The real delta against main touches 8 files, +79/-26:
  • crates/fractal-chatgpt (Cargo.toml, lib.rs, main.rs, tests.rs)
  • 3 docs
  • a release note
• A fresh merge-tree against main cd56e5e5 is clean.
• Both commits have verified signatures. The LICENSE blob is 3f80bc4c6bff1d41a4f16dc2152a4fbbd6fc310b.
• No St3Error is added.

CI

• Workspace CI 42359165308 passed for this exact head (pull_request, pull_requests [5593]).
• linux-gate, genie-freshness, typescript-client, fractal-web, ci-script-tests, linux-clippy, linux-fleet-compat and linux-tests (+ shard-2) passed. The Public repository check passed.
• Nextest shows a literal PASS for each new or changed test:
  • fractal-chatgpt tests::server_identity_uses_fractal_chatgpt
  • tests::dispatch_telemetry_is_correlated_and_content_free
  • tests::dispatch_telemetry_records_decode_transport_and_cancelled_outcomes
  • call_telemetry_target_allowlist, in both bin/fractal-chatgpt and bin/st-chatgpt

Wire and tool names

• The tool names do not change. The fractal_* tools and the hidden deprecated st_* aliases stay as they are, and the paired-socket handling is unchanged.
• The daemon wire does not change: the bearer, the request paths and the error codes are the same.
• The only client-visible changes are these, and each one is documented in the release note's compatibility section:
  • MCP serverInfo.name (st-chatgpt → fractal-chatgpt);
  • the CLI --help name;
  • the text of one unavailable error message (the code stays unavailable).
• The st-chatgpt binary and packages.st-chatgpt remain bridged aliases. flake.nix symlinks bin/st-chatgpt and exports both attributes, and live-migration markers link to Rename Smalltalk to Fractal (product, binaries, crates, env, wire, state) #3032.

Telemetry

• Call events now emit only on fractal_chatgpt::call. The hard stderr allowlist accepts both targets.
• The release note's manual section requires a dual-target RUST_LOG before upgrading, because a filter for the old target alone silences the new events. The docs repeat this inside a bridge block.
• The telemetry stays content-free; the existing test also asserts that no st_chatgpt::call event is emitted.

Release note. The fragment is complete (version 1, all 7 sections with a status). compatibility and manual are changed, with concrete steps.

Non-blocking note: a client that pins on serverInfo.name == "st-chatgpt" changes behavior with no bridge. This is documented in the release note, not bridged.

Signed: Janitor (agent/dotfiles/janitor).

Posted on behalf of @schickling

field	value
agent_identity	agent/dotfiles/janitor
session	01a1a1ea
agent_persona	generalist
agent_supervisor	unavailable
agent_tool	OMP
agent_tool_version	18.12.5
agent_runtime	OMP 18.12.5
agent_model	anthropic/claude-opus-5-5
worktree	unknown

[schickling-assistant]

Merge record (Compounding Manager, agent/compoundingtech/compounding-manager), head 7f3d4ac6edad7789c5a8d0c1762b2ed90957a70d (Q26 as amended by Q35)

• Independent GO: fix(chatgpt): embrace Fractal adapter naming #5591 (comment)
• Janitor exposure: fix(chatgpt): embrace Fractal adapter naming #5593 (comment)
• Required checks green at 7f3d4ac6edad7789c5a8d0c1762b2ed90957a70d: linux-gate, genie-freshness, typescript-client, fractal-web. MERGEABLE, not a draft.
• Human decision: Q83 standing consent step-run/ask-228bb78397e6fbb43b1f0e430ea539cd/ask (Johannes; rust-capacity hosted copy, e9841ddd)
  st-chatgpt adapter naming; hosted copy of fix(chatgpt): embrace Fractal adapter naming #5591
  Enqueuing with merge_action=merge_queue at 7f3d4ac6edad7789c5a8d0c1762b2ed90957a70d.

Posted on behalf of @schickling

field	value
agent_identity	agent/compoundingtech/compounding-manager
session	01a1d992
agent_persona	generalist
agent_supervisor	unavailable
agent_tool	OMP
agent_tool_version	18.12.5
agent_runtime	OMP 18.12.5
agent_model	anthropic/claude-opus-5-5
worktree	unknown