Skip to content

Roll up integration into dev#137

Merged
loning merged 2 commits into
devfrom
integration
Jun 18, 2026
Merged

Roll up integration into dev#137
loning merged 2 commits into
devfrom
integration

Conversation

@loning

@loning loning commented Jun 18, 2026

Copy link
Copy Markdown
Contributor

Release notes

Rolled up 2 commits from integration at e0977597162c5a58f2f6265b8d62f1bf801c2a18, ahead of origin/dev.

This rollup fixes #135 via PR #136: raises emitted before a long spawn_codex_sync call are now made visible before the Codex subprocess finishes, instead of staying buffered until department pipeline exit.

Key change:

  • Flushes the live RaiseBuffer before spawn_codex_sync enters its blocking Codex run.
  • Allows the supervisor to observe/process authenticated raised events incrementally during child execution.
  • Prevents progress markers such as implementation attempts from remaining invisible during long Codex runs.
  • Reduces false terminal handling and duplicate Codex spawns caused by redelivery while markers were still buffered.

Operational impact:

  • raise() visibility is no longer strictly end-of-pipeline for pre-spawn_codex_sync raises.
  • Pre-spawn progress facts can be published before the Codex result is known.
  • Retry safety continues to rely on idempotent raised-event handling.

中文摘要:

  • 修复 spawn_codex_sync 长时间阻塞期间 raise() 不可见的问题。
  • 让实现中/尝试中等进度标记能在 Codex 运行期间被 supervisor 看到。
  • 降低误判终态和重复启动 Codex 的风险。
    ⟦AI:FKST⟧

loning added 2 commits June 19, 2026 06:00
…s in spawn_codex_sync (raises are invisible for the entire long codex run → false-terminal + double-spawn)
…oject/fkst-substrate/135/ready-consensus-github-devloop-issue-ChronoAIProject-fkst-substrate-135-intake-1355254712-loop-1-2432932907

Flush the raise buffer before a department blocks in spawn_codex_sync (raises are invisible for the entire long codex run → false-terminal + double-spawn)
@loning loning merged commit ee222f2 into dev Jun 18, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

1 participant