chore: release main

[github-actions]

🤖 I have created a release beep boop

franken-critique: 0.12.0

0.12.0 (2026-08-09)

Features

• learning: add lesson effectiveness telemetry (#3803) (33ab5c1)

Performance

• critique: bound ConcisenessEvaluator input memory and processing (#3657) (#3684) (b50d3bb)

franken-governor: 0.9.4

0.9.4 (2026-08-09)

Bug Fixes

• governor: redact CLI approval prompt secrets (#3897) (5604f36)

franken-mcp-suite: 0.12.3

0.12.3 (2026-08-09)

Dependencies

• The following workspace dependencies were updated
  • dependencies
    • @franken/critique bumped from 0.11.3 to 0.12.0
    • @franken/governor bumped from 0.9.3 to 0.9.4
    • @franken/orchestrator bumped from 0.61.1 to 0.61.2

@franken/orchestrator: 0.61.2

0.61.2 (2026-08-09)

Dependencies

• The following workspace dependencies were updated
  • dependencies
    • @franken/critique bumped from 0.11.3 to 0.12.0
    • @franken/governor bumped from 0.9.3 to 0.9.4

0.68.0

0.68.0 (2026-08-09)

Features

• learning: add lesson effectiveness telemetry (#3803) (33ab5c1)

Bug Fixes

• governor: redact CLI approval prompt secrets (#3897) (5604f36)

Performance

• critique: bound ConcisenessEvaluator input memory and processing (#3657) (#3684) (b50d3bb)

Documentation

• tasks: record CLI stdin error lesson (81696aa)

CI/CD

• deps: baseline better-sqlite3 type major gap (7907b5b)

---

This PR was generated with Release Please. See documentation.

[djm204]

@codex review

[djm204]

Closing this generated Release Please PR without merge because the immutable head 57a77be4d439b43f1d498e9526d8c51f404cd541 cannot satisfy the no-bypass exact-head CI gate.

Evidence:

• I close/reopened the PR to force the previously missing pull_request CI run without changing the head.
• Exact-head CI run https://github.com/djm204/frankenbeast/actions/runs/31315781366 failed in Dependency vulnerability SLA dashboard on five high findings: brace-expansion, fast-uri, ip-address, nanoid, and undici. No admin/bypass merge is permitted.
• The other exact-head jobs passed: publish smoke, Codex CLI compatibility 0.143.0, and Codex CLI compatibility latest.
• Isolated exact-head verification passed npm ci, build (10/10), typecheck (17/17), lint (10/10, zero errors), and release-version parity across package manifests, lockfile, and .release-please-manifest.json for 0.68.0, critique 0.12.0, governor 0.9.4, MCP suite 0.12.3, and orchestrator 0.61.2.
• Fully paginated GraphQL review-thread audit returned hasNextPage=false, zero threads, and zero unresolved Codex threads before closure.

The release payload itself is mechanically consistent, but merging it while the required exact-head CI run is red would be a gate bypass. Release Please can regenerate a fresh release PR after the dependency baseline is remediated.

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. Delightful!

Reviewed commit: 57a77be4d4

ℹ️ 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".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".