release: v0.8.68

[Hmbown]

v0.8.68 release preparation

This release PR is intentionally last: all feature work and CI-speed work are already merged, and this branch only carries the release version/changelog plus final public docs/site language.

Included

• Bump workspace crates, Cargo.lock, npm wrapper, README/install snippets, and generated web facts to 0.8.68.
• Add the dated CHANGELOG.md / crates/tui/CHANGELOG.md entries and compare link.
• Align public docs/site copy with the shipped Plan / Act / Operate modes, orthogonal approval posture, and durable Fleet/Workflow overlay.
• Keep the provider-honest/open-model-first positioning and no hosted-account/inference-markup claims.

Verification

• ./scripts/release/check-versions.sh
• cargo build --release --locked --bin codewhale
• ./target/release/codewhale --version → codewhale 0.8.68 (5dbd47739b82)
• Website npm run build → Next.js production build, 39 static pages
• git diff --check

The local npm install generated an uncommitted lockfile normalization in the worktree only; it is intentionally not part of this PR.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[claude]

Claude finished @Hmbown's task in 4m 11s —— View job

---

Review: PR #4327 — v0.8.68 release prep

Todo list

• Gather context (PR body, diff, repo guidance)
• Review Cargo.toml/version bump consistency
• Review CHANGELOG.md entries
• Review README/docs/web copy changes
• Check for provider/model-route safety issues (EPIC v0.8.65 EPIC: Separate provider facts, model facts, offerings, and route resolution #2608 invariant)
• Post final review summary

Summary

This is a docs/version-bump-only release PR as advertised. The mechanical parts (workspace + per-crate Cargo.toml version bumps, Cargo.lock, npm wrapper version, CHANGELOG.md / crates/tui/CHANGELOG.md dated entries + compare links, web/lib/facts.generated.ts) are all internally consistent — every crate's version = "0.8.68" and path-dependency version = "0.8.68" pins line up, and I found no leftover 0.8.67 in files this PR touches. No provider/model-route logic is touched at all, so the EPIC #2608 invariant isn't implicated here.

However, the Plan/Act/Operate copy alignment (the stated purpose of this PR) has two real inconsistencies:

1. Self-contradicting FAQ entry (bug, introduced by this PR)
web/app/[locale]/faq/page.tsx — the question was renamed from "What are Plan, Agent, and YOLO modes?" to "What are Plan, Act, and Operate modes?" (English ~line 166, Chinese ~line 510), but the answer body directly underneath was left unchanged and still describes Agent/YOLO:

• English lines 171–172: <li><strong>Agent</strong> — Default mode... / <li><strong>YOLO</strong> — Auto-approves..., and line 176: "you can be in Agent mode with auto-approval"
• Chinese lines 515–516, 520: same pattern (Agent（代理）, YOLO（全权）)

The question now asks about Act/Operate but the answer never mentions either — this ships a self-contradicting FAQ. Fix this →

2. README documents CLI subcommands that don't exist (bug, introduced by this PR)
README.md's new "Workflow" section shows:

codewhale workflow run my-workflow.js --verify
codewhale workflow status
codewhale workflow logs <run-id>

But WorkflowCommand in crates/cli/src/lib.rs:472 only defines a Run variant, and Run requires a mandatory --fleet <ROSTER> argument (plain String, no default) — so even the first example line is missing a required flag. There is no status or logs CLI subcommand anywhere in the enum. The closest real thing is the in-session agent tool's JSON "status" action (crates/tui/src/tools/workflow.rs), which is not invoked as codewhale workflow status. As written, none of the three example commands would actually run. Fix this →

Minor, pre-existing, not introduced by this PR: README.zh-CN.md, README.ja-JP.md, and README.vi.md still carry a stale "current release is 0.8.67 (Fleet/Workflow usability)…" roadmap sentence that the English README.md no longer has. Not this PR's fault (it didn't touch those lines), but worth a follow-up since the PR's goal is doc/site alignment.

Good choices worth calling out: the docs/MODES.md removal of "Multitask" from the mode cycle and /mode subcommand list is correct, not a regression — crates/tui/src/tui/app.rs:999 confirms Multitask "never shipped" and normalizes to Operate, so the docs now match the actual shipped surface. The .codewhale/workflow-runs.jsonl filename referenced in the new README Workflow blurb does match crates/tui/src/tools/workflow.rs:2765.

I was not able to run ./scripts/release/check-versions.sh, cargo build, or the website npm run build in this sandboxed environment (script/binary execution required approval that wasn't available); verified version/consistency manually via grep/diff instead. The PR body states these were already run locally with passing results.

[claude]

Claude finished @Hmbown's task in 1m 37s —— View job

---

Review: PR #4327 — v0.8.68 release prep (update after synchronize)

Todo list

• Gather context (new commit since last review, PR body, repo guidance)
• Review new commit 11ee494 (workflow declarative read_write mode / verifier posture)
• Re-check previously flagged issues (FAQ contradiction, README workflow subcommands)
• Post final review summary

Summary

New commit 11ee494 (fix(workflow): use declarative read_write mode and valid verifier posture) is a correct, narrowly-scoped fix:

• Mode value fix is real and necessary. TaskMode (crates/workflow/src/lib.rs:497-503) is #[serde(rename_all = "snake_case")] over just ReadOnly/ReadWrite — there is no Write variant, so the previously checked-in "mode": "write" in the five workflows/v0868_*.workflow.js fixtures would have failed strict deserialization rather than silently defaulting. Renaming all five to "read_write" aligns them with the actual schema. I confirmed no "mode": "write" remains anywhere under workflows/.
• Verifier posture change is sound. v0868_stopship_lane.workflow.js's verify-dogfood task moved from "write" (invalid) to "read_only", and its prompt was reworded from "if missing, implement minimal fixes" to "if missing, report them as missing rather than editing" — this keeps the verifier role read-only in practice, not just in the mode field, so named_fleet.rs's validate_stopship_roles() role-resolution and the runtime's read/write task split (crates/workflow/src/lib.rs:548, :2022) stay consistent with what the task actually does.
• No correctness bugs, provider/model-route logic, or security-relevant code is touched by this commit.

Previously flagged issues are unchanged (not addressed by this commit, still open):

1. web/app/[locale]/faq/page.tsx — the FAQ question now asks about Plan/Act/Operate but the answer bullets still describe Agent/YOLO (English lines 171–172, 176; Chinese lines 515, 520). Self-contradicting as shipped.
2. README.md's new Workflow section (~lines 200-204) still shows codewhale workflow status and codewhale workflow logs <run-id>, which don't exist in WorkflowCommand (crates/cli/src/lib.rs:471-510 — only a Run variant, with a mandatory --fleet flag not shown in the first example either).

Neither of these is touched by the workflow-fixture commit, so they remain accurate as filed in my prior review pass.