Conversation
🔬 Gate certification — GREEN ✅ (Transparent Stream final replies stay visible after settle)Certified head: What I ran (rebased worktree
|
| Gate | Result |
|---|---|
| Rebase onto current master | ✅ git apply clean; diff = messages.js + tests only |
| Threat-scan SUSPICIOUS | ✅ benign FP confirmed — eval(extractFunc('_anchorScene…')) is the standard Node-harness idiom in the TEST file; no shipped-code eval |
| Codex (reproduce) | SAFE TO SHIP — 0 findings |
| Full pytest suite | ✅ 12001 passed, 0 failed |
| anchor-visible-order tests | ✅ 63 passed |
Findings
✅ Mode-aware visibility fix: _anchorSceneActiveMode() reads window._chatActivityDisplayMode; _anchorSceneRowDisplayHintForMode(row, sceneMode) resolves the right display_hint per scene mode (compact_worklog → hints.compact_worklog || row.display_hint || 'activity_row'; transparent_stream/default → row.display_hint || 'activity_row'), so the final-answer row keeps a visible display_hint through the settle transition (#5550). Codex confirmed the final reply stays visible after settle across all activity display modes, the fallback chain can't pick a hidden hint for a final answer, live→final anchor order is intact, and no regression to compact-worklog/activity-row rendering. Coexists with shipped #5400/#5454/#5506 (0 transparent-event-enter refs — no flicker/entrance-replay). 63 targeted + full suite green (0 failures).
Recommendation to the next agent
Ready to merge — use branch gate-rebase/5558-transparent-final-visible (sha:585f1f59), NOT the PR's stale head d270f077. A real transparent-stream reliability fix (final replies no longer vanish after settle), Codex SAFE + 63 targeted tests + full suite green (0 failures), coexists with the shipped transparent-stream family. Light-visible (makes an existing behavior correct — final reply stays); a quick glance at a settled transparent-stream reply confirms, but the fix is verified + test-covered. concept 4/5 (real #5550 fix). Author @rodboev (T1). crit=3.
Gate-certifier layer (warm-up → gate → release). I do not merge/tag/deploy. Rebased onto current master; verified mode-aware display-hint keeps final-answer row visible through settle (no hidden-hint pick), coexists w/ #5400/#5454/#5506 (0 entrance-keyframe refs), threat-scan SUSPICIOUS = benign eval(extractFunc) test-harness FP (test-only, no shipped eval), Codex SAFE + 63 targeted + full suite green (0 failed). Cert valid for sha:585f1f59.
release #5558: keep Transparent Stream final replies visible after settle
|
Shipped in v0.51.865 — thanks @rodboev! 🎉 Your fix for the Transparent Stream settle-fold regression (#5550) is live. In Transparent Stream mode, a turn's final reply no longer folds into the collapsed worklog the instant it settles — it stays a visible chronological answer. Root cause was the live-anchor scene renderer hardcoding Gate (all green):
Merged via release PR #5590 with your authorship preserved ( |
…after settle + CHANGELOG
Thinking Path
What Changed
static/messages.js: preserve the active activity display mode when projecting and completing the live anchor scene at settle time, and normalize settled row hints for that mode.tests/test_live_to_final_anchor_visible_order.py: add focused regression coverage for Transparent Stream settle, plus Compact Worklog and all-prose guard preservation checks.Why It Matters
Transparent Stream no longer hides the completed assistant reply behind a collapsed "Processed ..." row right after generation finishes. The change is scoped to the live-to-final boundary, so existing transcript hydration and Compact Worklog behavior stay intact.
Verification
python -m pytest tests/test_live_to_final_anchor_visible_order.py -v --timeout=60(63 passed)npx eslint --no-config-lookup -c eslint.runtime-guard.config.mjs "static/**/*.js"Full-suite CI context, not a required local check unless requested:
python -m pytest tests/ -v --timeout=60.Upstream
Closes #5550.
Model Used
GPT 5.5 via Codex CLI