ReasonFirst v0.5.3

All five release assets have been downloaded and verified. The public v0.5.3 wheel installed successfully in an isolated Python 3.12 environment.

ReasonFirst connects GitLab repositories to normal ChatGPT conversations: read the code, discuss the approach, hand implementation and testing to a coding worker, then bring the evidence back for review.

Quick packaged installation and building from source are both available.

What’s new in 0.5.3

• More resilient tunnel downloads. Eligible Python HTTPS transport interruptions can recover through one bounded curl attempt. TLS verification, HTTPS-only redirects, checksums and complete bundle validation remain enforced.
• More accurate diagnostics. actual-coder doctor now finds the ReasonFirst-managed tunnel client outside PATH and distinguishes executable discovery from live service health and authentication.
• Clearer onboarding and platform evidence. Updated English/Chinese installation guides, troubleshooting and dated macOS, Windows and Linux validation records.

Changes: #111 · Release preparation: #112

Install

Have Git, uv and a supported coding worker ready. Complete that worker’s own login before running a coding task.

Quick install

uv tool install --python 3.12 https://github.com/phoenixjyb/reasonFirst/releases/download/v0.5.3/chatgpt_selfhosted_gitlab_mcp-0.5.3-py3-none-any.whl
reasonfirst setup

Build from source

git clone --branch v0.5.3 --depth 1 https://github.com/phoenixjyb/reasonFirst.git
cd reasonFirst
uv sync --python 3.12
uv build --no-create-gitignore
uv run reasonfirst setup

Existing users: follow the upgrade guide before replacing a package used by a running service. This patch does not automatically restart services.

English release notes · 中文发布说明 · 中文安装与升级

中文说明

这次更新整理了 Linux 首次安装中遇到的问题：符合条件的隧道下载中断可以通过 curl 恢复，doctor 也能识别 ReasonFirst 管理目录中、未加入 PATH 的 tunnel-client。安装、排障和三平台测试记录都已同步更新。

可以用安装包快速安装，也可以从源码构建。 欢迎试用、反馈安装体验、补充文档和提交 PR。

Validation scope

The final source commit passed the core and macOS/Windows/Linux regression and packaged/source installation checks, Bridge checks, tunnel command boundaries, documentation, packaging and source/history scans. The exact runs are linked below.

The dated real-machine evidence remains version-specific: the October 12 Ubuntu 22.04.5 run used v0.5.2, completed setup, live MCP reads, managed Git and a Codex worker with 10 tests passing, and made no file changes. Earlier macOS/Windows records include v0.5.1 and historical source builds. These records do not claim every feature was retested on every OS using v0.5.3. See the platform validation record.

Source and verification

• Source commit: 59eddb74e5d92ce55178eb6509bb22db15ab5f9b
• Source tree: 52d60a36a96de63f0b14c4159af4c49519e7abd9
• Final-source CI, Docs, Tunnel command boundary and Candidate download.

Public download and installation verification

Completed 2026-10-12 at 15:25 UTC after the Release assets workflow succeeded on attempt 1 at the source commit above.

• All five public assets were downloaded anonymously over HTTPS. Their actual byte sizes and SHA-256 values match GitHub’s asset metadata.
• SHA256SUMS.txt matches all four covered files; RELEASE.json matches the exact source commit, tree, workflow run/attempt and build-artifact hashes.
• A fresh isolated installation of the public wheel, outside the source checkout, passed on Python 3.12.14. Package and CLI versions are 0.5.3, and all 11 declared console entrypoints are present.
• Detect-only setup status, the 22-tool Bridge inventory, and static HTTP inspection passed. No provider authentication, worker, service or tunnel activation was performed by this package check.

Public asset	Bytes	Verified SHA-256
chatgpt_selfhosted_gitlab_mcp-0.5.3-py3-none-any.whl	335752	50a17568684a5ae4e50229041b4f340880283671f9cb0aab393d59561878c1cc
chatgpt_selfhosted_gitlab_mcp-0.5.3.tar.gz	1002536	14f3f588a19d45228b240f7c41bdaefc5358cc1195f14f6f8d322a06fb49f5f1
reasonfirst.rb	1197	e3d181f3b29ab68ecfa5ca4e28f28edca1f162dc306dd150e2433cf143f33fbb
RELEASE.json	921	d2ea021fb39c4a6fc7242463257bf9af426b09373f0577d3833173c79c6a23bf
SHA256SUMS.txt	388	3eda76aca655b849dfc00c3f8cbcb6e9f9ee3b381b2db25cc7ca2d7e1f54947a

The v0.5.2 tag and its published assets remain unchanged.

ReasonFirst v0.5.2

ReasonFirst v0.5.2

Reuse existing configuration, inspect the installed CLI and service state more clearly, and get the runtime/deployment improvements already integrated after v0.5.1 in a versioned package.

Release identity

• Release source: a4aa63b91109c6ddb8a721d93fe4b9be2543bc23
• Source tree: acc799593658c4fcfc7f03531a20f5c77ca42ea4
• Preparation: PR #110
• This stable release targets standard CLI/read workflows. Optional privileged Bridge and advanced internal integrations retain their documented boundaries.

Public downloads verified — 2026-10-10. The Release assets workflow succeeded. All five attached files were downloaded anonymously and verified against the checksums, source/build manifest and GitHub asset digests. The downloaded wheel installed successfully in an isolated Linux/Python 3.12.14 environment outside the source checkout.

Install and configure

With uv, a suitable Python and Git available:

uv tool install https://github.com/phoenixjyb/reasonFirst/releases/download/v0.5.2/chatgpt_selfhosted_gitlab_mcp-0.5.2-py3-none-any.whl
reasonfirst setup

Existing users can inspect first and reuse valid settings:

reasonfirst setup --status --json
reasonfirst setup --reuse-existing --json
reasonfirst status --json

The new reuse/status commands require v0.5.2. For an existing package install, first identify which environment any live service uses; replace the intended tool installation with the reviewed wheel using uv tool install --force only when that environment can safely be replaced. Installing new package files does not update code already loaded by a running service.

The source route stays supported:

git clone --branch v0.5.2 https://github.com/phoenixjyb/reasonFirst.git
cd reasonFirst
uv sync --python 3.12
uv run reasonfirst setup

Each user supplies their own authorized GitLab access, coding-worker login and ChatGPT connection. Preserve existing config, project grants, workspaces and tunnel identities during upgrades.

Included in this release

• Configuration reuse and clearer status: valid existing settings can be reused without rewriting them, recreating tunnels or rerunning onboarding. Installed CLI identity is separate from uninspected running-service identity.
• Packaged HTTP transport: an explicit loopback-only Bridge HTTP entry point uses the shared packaged core. The normal Bridge command remains stdio; the HTTP wrapper supplies neither authentication nor the legacy /control route.
• Optional operator tools: known macOS deployment registration, offline macOS/Linux runtime preparation, macOS deployment/runtime pairing, static launch review and selected loaded-job observation.
• Internal service safeguards: explicitly integrated managed HTTP ownership, request/worker/approval admission, maintenance leases, retained child-launch inputs and GitLab API trust binding. These are internal opt-in mechanisms, not automatic service migration, activation or updating.
• Release staging correction: normal builds suppress uv's extra staging marker while preserving the exact asset allowlist and collision checks.

Windows quoting/UTF-8 decoding, managed Git credential isolation, approved project Python and portable worker handoffs were already in v0.5.1 and remain included. The frozen v0.5.1 tag, assets and one-version recovery workflow are unchanged.

Validation and support scope

The final release source passed its own CI, documentation/Pages, native tunnel-boundary checks and candidate packaging. All three operating systems passed package/source installation E2E and the relevant regression jobs. Principal interpreter coverage is Python 3.12.

All 16 pre-publication checks on the merged source completed successfully, with no skips or reruns, including documentation deployment. The separate local full-install rehearsal stopped when its isolated pip environment could not acquire certifi>=2024.2.2; it is not counted as a local full-E2E pass. Hosted package/source install E2E passed on Ubuntu, macOS and Windows. Public-download acceptance verified the installed package/runtime version as 0.5.2, all seven command entry points, non-mutating setup/status and Bridge inventory, runtime/HTTP help, and static HTTP inspection with no server start. Imports resolved inside the isolated wheel installation. This acceptance did not authenticate a live provider or activate a user service.

The installation/native fixtures use synthetic local inputs and do not authenticate real providers. Historical Windows setup/read, managed clone/fetch, approved-interpreter validation and initial worker handoff evidence keeps its original source revisions. Windows healthy-runtime repair/no-op, controlled restart without the temporary UTF-8 workaround, reboot recovery and optional privileged Bridge/write live acceptance remain unverified (#88).

The few-minute onboarding goal remains unmeasured (#80). A generated Homebrew formula is not a published/tested tap. Native Git trust/diagnostics and task-loop hardening remain tracked in #10 and #6.

The internal managed HTTP owner uses its reviewed MCP 2.3.0/Uvicorn 0.54.0 pair and explicit protocol profile. This narrower integration contract does not change the package's general dependency range or certify arbitrary later dependency combinations. Copilot CLI remains available through terminal ActualCoder; full-chat worker control uses Codex App Server.

Release files

• chatgpt_selfhosted_gitlab_mcp-0.5.2-py3-none-any.whl
• chatgpt_selfhosted_gitlab_mcp-0.5.2.tar.gz
• reasonfirst.rb
• RELEASE.json
• SHA256SUMS.txt

For a manual download, compare the wheel hash with its exact checksum entry before installation. The manifest binds source/tree, build run and artifact hashes; it is not an independent signature. GitHub's automatic source-code archives are separate from the built sdist above.

中文摘要

v0.5.2 把 v0.5.1 之后已经合并的改进整理成正式安装包：复用已有配置、区分已安装 CLI 与运行中服务状态，并提供按需使用的运行环境准备、部署检查和内部服务保障。普通 ChatGPT 负责读代码、聊方案和审阅，编程工具负责执行，两条安装路径继续支持。

安装新包不会自动升级或重启已有后台服务。Windows 的健康 runtime 修复、受控重启、机器重启恢复和可选高权限写入仍有待现场验收；“几分钟完成接入”尚无实测数据。发布流水线已成功，五项附件已完成公开下载与校验；Linux / Python 3.12.14 的独立安装和只读命令验收也已通过。下载后可对照 SHA256SUMS.txt 核对文件。

English release notes · 中文发布说明 · Install and update · 中文安装

ReasonFirst v0.5.1

ReasonFirst v0.5.1

Reasoning-first coding orchestration, with guided setup, packaged installation, and cross-platform reliability fixes.

Release source: 9b0f488ab0dc2e836c10699b2b45c4bfd8009e9b
Source tree: 79de51314f887589f77931f9d264f2db86f1fa29

Publishing this Release starts the Release assets workflow. The installation instructions below apply only after that workflow succeeds and the complete five-file asset set is attached. The source tag alone does not establish that packaged downloads are ready.

Install and configure

With uv and the appropriate prerequisites available:

uv tool install https://github.com/phoenixjyb/reasonFirst/releases/download/v0.5.1/chatgpt_selfhosted_gitlab_mcp-0.5.1-py3-none-any.whl
reasonfirst setup

For manual downloads, compare the wheel's SHA-256 with its exact entry in this Release's SHA256SUMS.txt before installing it. Each user supplies their own authorized GitLab access and coding-worker login. Git is required for managed repositories. The wheel contains neither user credentials nor pre-authorized ChatGPT connections; it is not a standalone desktop installer.

The source route remains supported:

git clone --branch v0.5.1 https://github.com/phoenixjyb/reasonFirst.git
cd reasonFirst
uv sync --python 3.12
uv run reasonfirst setup

Included in this release

• Guided onboarding and packaged services: reasonfirst setup, detect-only status, explicit project grants, worker selection, packaged read MCP, and optional Bridge setup. The detailed/manual route remains supported.
• Cross-platform reliability: correct tunnel executable quoting and UTF-8 protocol handling; managed Git credentials isolated from inherited helpers without changing global Git configuration.
• Approved project Python: explicit workspace-local interpreter bindings preserve the pinned project contract and support host-side validation without depending on a python3 command or Windows launcher discovery.
• Normal worker handoffs include the execution recipe: one standard-library supervisor, PowerShell 5.1/7 or POSIX shell transport, exact command arguments, bounded output, timeout reporting, and actual child exit codes. Process success is distinguished from project test acceptance.
• Public package integrity metadata: wheel, built source distribution, formula, source/build manifest, and checksums. The uploader refuses existing target filenames instead of silently replacing assets.

Validation and support boundaries

The final source commit passed all ten CI jobs, including Windows/macOS/Ubuntu regressions and packaged/source installation, the two Bridge regression jobs, packaging and source/history scans. Documentation and Pages and tunnel-boundary checks also passed. CI's principal interpreter coverage is Python 3.12; package metadata's broader Python range is not equivalent coverage.

The maintainer supplied live Windows evidence for setup/read access, managed clone/fetch, pinned host validation, and a normal Codex CLI handoff delivering both the approved interpreter and complete recipe. That recipe ran all ten synthetic practice tests with OK, complete output, and actual child exit code zero, without a corrective prompt. Supplied terminal closeout showed the original workspace unchanged. Earlier unsuccessful diagnostic attempts remain separate records. See the release integration and acceptance record.

Stable v0.5.1 does not mean every optional integration has been accepted on every operating system. Standard CLI/read workflows are the focus of this release. The more privileged full-chat Bridge remains optional/preview and client-eligibility-dependent. Live Windows full-chat/write acceptance and controlled restart/reboot recovery were deferred and are not certified by these tests. No unattended restart-recovery guarantee or universal sandbox/provider attestation is made. The host validation runner and a Git worktree are not filesystem security sandboxes. Worker authentication, quotas, approval policy and sandbox behavior remain separate controls.

Upgrading a package does not replace code already loaded by running services. Do not overwrite an active runtime blindly; preserve configuration and use a planned update/restart window. No Homebrew tap or PyPI publication is promised by this release.

Expected attached files

chatgpt_selfhosted_gitlab_mcp-0.5.1-py3-none-any.whl
chatgpt_selfhosted_gitlab_mcp-0.5.1.tar.gz
reasonfirst.rb
RELEASE.json
SHA256SUMS.txt

reasonfirst.rb is a generated formula, not proof of a working public tap. The built source distribution is separate from GitHub's automatic source-code archives. Checksums and the build manifest provide integrity/source metadata, not independent signatures or full supply-chain attestation. The final public downloads must be checked separately from earlier Actions candidates.

Install and update · 中文安装 · Security

中文摘要

v0.5.1 将引导式安装、共享跨平台修复、工作区 Python 审批和内置 worker 执行配方整合到同一版本。Windows 的正常初始 handoff 已在用户提供的现场记录中完成十项测试，无需另贴修复提示；结束后工作区保持不变。正式版主要面向标准 CLI 与只读连接，Windows 高权限全聊天写入及受控重启恢复仍未完成现场验收，不能视为已认证。请等 Release assets 工作流成功且五项附件齐全后，再按校验和安装并对外分享。源码安装继续支持，每位用户使用自己的授权和凭据。

ReasonFirst v0.5.0

ReasonFirst v0.5.0

Source/manual-setup release.

Tag: v0.5.0
Exact release commit: 6b3b1983b3dd8ad56f214393d00e7a74c60c7f95
Package/runtime version: 0.5.0

Release overview

ReasonFirst v0.5.0 is a compatibility, safety, and public-usability release over the v0.3.0 ActualCoder lifecycle. It keeps the same division of responsibilities: a strong reasoning interface defines and reviews the work, replaceable coding workers implement it, and a human controls publication and final merge.

Highlights

• A documented, exercised chat-only workflow: pinned TaskSpec, one managed workspace, Bridge-managed Codex App Server execution, reviewed diff, snapshot-bound finish preview, explicit human publication approval, GitLab Merge Request, matching-HEAD CI, and EvidencePack review.
• Codex App Server worker-start compatibility fixes and safe handling when a ReasonFirst MCP entry is absent.
• macOS session-scoped launchd proxy synchronization and startup health polling, without writing proxy values into source or LaunchAgent plists.
• Durable task and attempt records, bounded evidence, worker-policy reporting, explicit approval mediation, and safer finish gates accumulated since v0.3.0.
• English and Chinese onboarding, practice, architecture, troubleshooting, contribution, and release-maintainer documentation, with rendered internal-link checks for the documentation site.

Exact-commit validation evidence

The following existing GitHub Actions results were re-read during the September 30, 2026 continuation audit. This audit did not rerun them.

Evidence	Result
Source commit	6b3b1983b3dd8ad56f214393d00e7a74c60c7f95
CI run	36515944346, successful
Main validate job	109238110654, 450 tests, OK
Cross-platform regression jobs	Ubuntu, macOS, and Windows: successful
Bridge regression jobs	Ubuntu and macOS: successful
Package release-candidate job	Wheel and sdist build, archive-path inspection, clean-wheel checks, and secret/history scanning: successful
Documentation site	36515944332, successful

All seven CI jobs succeeded on this exact commit. The validate log also reports that scanning tracked files and the full available Git history passed.

The 445-test figure in the committed release notes refers explicitly to the earlier 7d16061061f6337604bd3135c9e4a693ad1fd68a audit baseline. The final frozen commit's main validation count is 450. The 534-test figure in the prior conversation's handoff belongs to the later Slice 5 development head, not this release.

These checks do not establish every deployment topology, a live provider login on every operating system, or complete privacy review of all repository-related surfaces. The documented September 28 synthetic GitLab rehearsal is separate live-workflow evidence.

Installation scope

This is the v0.5.0 source/manual-setup baseline. The canonical reasonfirst setup command, packaged read-MCP and Bridge entry points, repair/resume wizard, and new release-asset workflow belong to the later v0.5.1 work and must not be advertised as v0.5.0 features.

For a new source checkout of this release:

git clone --branch v0.5.0 https://github.com/phoenixjyb/reasonFirst.git reasonFirst-v0.5.0
cd reasonFirst-v0.5.0
uv sync --python 3.12
uv run actual-coder --help

Use the detailed setup guide in that checkout for a real GitLab/MCP connection. A successful CLI help command is not proof of authenticated provider or ChatGPT readiness.

The frozen commit contains no release-assets workflow. Publishing its GitHub Release will not automatically build or attach the v0.5.1-style install artifacts. Any separately requested v0.5.0 package asset must be built from this exact frozen commit, inspected, and approved before upload.

Known boundaries

GitLab is the implemented target SCM/CI adapter. Hosting ReasonFirst's source on GitHub does not provide a GitHub-target task adapter.

Git worktrees and worker subprocess controls are not operating-system security sandboxes. Use trusted development hosts and appropriately approved repositories and credentials.

The privileged Bridge and the read-oriented GitLab MCP are separate trust surfaces. Whether the connected client exposes write-capable Bridge tools requires actual client-side acceptance; a healthy local daemon alone does not establish it.

Python API/MCP TLS handling remains separate from native Git trust and destination policy. External coding tools retain their own authentication, quotas, billing, and terms. Final merge remains a human decision; ReasonFirst does not auto-merge.

Documentation

Release notes in the frozen source · Detailed setup guide at v0.5.0