Skip to content

ReasonFirst v0.5.0

Choose a tag to compare

View all tags
@phoenixjyb phoenixjyb released this 30 Sep 02:00
v0.5.0
6b3b198
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

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

Assets 2
Loading