Foursday v0.8.0-rc.1 — control from Codex and Claude

Foursday v0.8.0-rc.1 adds one revision-fenced Control MCP shared by Codex and Claude, persistent Codex Thread continuity, owner intervention fencing, DWS attachment handling, marketplace installation, and an optional read-only status page.

Safety remains explicit: this release does not enable real sending, scheduled execution, proactive work, deployment, production writes, or permission expansion during installation. Legacy 9465 state is not a source of truth.

Validated on the exact release commit with Node.js 22 and 24, isolated PostgreSQL, Python plugin tests, locked Hermes installation, package dry-run, gitleaks, CodeQL, and plugin manifest validation.

Foursday v0.7.0-rc.1 — one Codex work loop

Foursday now has one work loop: Codex.

This breaking preview replaces the legacy custom Runtime with a minimal Foursday distribution layer:

• personal DingTalk through DWS
• automatic project routing into the real workspace
• authorized personal gbrain context
• one Codex App Server loop with a Foursday policy proxy
• one bounded Foursday MCP for evidence-backed memory promotion
• embedded Gateway, Session, scheduling, and future channel infrastructure

Safety and verification:

• caller permission, sandbox, environment, and dynamic-tool overrides are stripped
• project command network and secret-bearing environments are denied
• push, merge, deployment, production writes, service control, destructive commands, and permission escalation remain blocked inside the work loop
• upstream memory, skill-review, title, background-review, built-in-memory, and curator model loops are disabled
• 143/143 JavaScript/PostgreSQL tests, 25/25 Python tests, and 21/21 install-reuse tests passed
• Node 22, Node 24, and CodeQL passed on the exact release SHA
• a real isolated Codex shadow turn completed with tool evidence and an unchanged workspace digest

Breaking boundary:

This is not an in-place upgrade for the legacy 0.6.x custom Runtime. Keep existing installations pinned until they are reconfigured as a fresh Foursday Profile. The minimal PostgreSQL schema is for new installs; rollback is release restoration, not reverse migration.

Production was not deployed or activated by this release.