Repository navigation
fix: backport required 0.7.0 runtime hotfixes - #11645
Conversation
|
Intent: Backport the already-merged MUST-HAVE process cleanup, frontend memory bounds, and explicit private-member selection fixes to release/0.7.0 in one PR. Collect the currently pending must-haves into this SAME PR only after their source PRs merge to main, then rerun release-relative validation. |
|
Release-worktree rendered evidence for head 94506a1. Both themes passed all ten capture assertions: raw=144069, rendered=60044, one marker with count=84080, whole head/tail lines preserved, elided sentinel absent, no page errors. These captures are from this backport, unlike the explicitly attributed source-PR images in the description. |
GPT 5.6 Review — ✅ no blocking findingsGPT 5.6 completed its review of This comment is updated in place on each push. Review detailsNo findings. False positive or not applicable? A repository writer can comment: |
Design Review (Fable 5) — 🟡 CONCERNSDesign-level review of Design-Verdict: CONCERNS Nine hand-adapted backports — including a brand-new 734-line scope reaper — reach release/0.7.0 with no release-target CI and no native macOS/Windows execution. Watch
Suggestions
[DESIGN-REVIEWED] 698a523 |
UX Review (Fable 5) — 🟡 CONCERNSUX-level review of UX-Verdict: CONCERNS The truncation marker's only remedy is one the cold reader feared to use — "full output on reload" names a recovery it doesn't offer. Watch
[UX-REVIEWED] 698a523 |
First Principles Review (Fable 5) — 🟡 CONCERNSPremise-level review of First-Principles-Verdict: CONCERNS Item 7 flips what every newly discovered agent gets by default — private V2 to Global V1 — on the authority of a source-PR link this run cannot verify. Not justified as shipped
What this change shipsInventory (10 items) — 9 justifiedIntent: FIX — backport nine already-merged runtime/memory hotfixes from main onto release/0.7.0 without importing the rest of main.
[FIRST-PRINCIPLES-REVIEWED] 698a523 |
Opus 4.8 Review — ✅ no blocking findingsReviewed Review detailsBoth candidates fail the falsification bar. Candidate 1 — the "leak" requires a timing race in the degraded fallback path ( Candidate 2 — requires a transient non-ENOENT No self-originated finding survived falsification to the same bar. No findings. [OPUS-REVIEWED] 698a523 Verdict parsed from the review's SHA-scoped output markers for commit False positive or not applicable? A repository writer can comment: |
Backport #11565, #11456, #11630 and #11594 onto the existing release hotfix branch. Track runtime descendants, recover witnessed process groups, preserve V1 discovery defaults, and reap abandoned Linux scopes. Use the first-parent delta of e66570d; retain release session APIs, existing memory bindings and conservative cleanup ownership checks. Carry source regressions and add release-specific binding and hook tests. No workflow, dependency, version or live configuration changes.
|
span=99fb501fe250
|
|
span=c38293b0418e
|
|
span=314ce35fc5a6
|
|
span=e9815ad6d5e7
|
|
span=50bbc427f21c
|
|
span=413cf50ff450
|


Problem / Motivation
Bring nine already-merged must-have fixes to release/0.7.0 without importing the rest of main. Abandoned provider/browser processes retain memory, long-running dashboards retain oversized strings, an owner member pick in an empty chat can fail private-memory admission, and discovery can allocate private memory without an explicit owner choice.
Why it matters
Keep the 0.7.0 candidate usable without changing existing memory bindings or weakening cleanup ownership checks. This is a bounded release backport, not a claim that every leak is cured. The nine sources are collected in this same PR as authorized. Nothing here merges, tags, publishes, deploys, or changes a live installation.
What changed (motivation → approach → change)
Release base: c359f83. Verified main snapshot: 9628c8c. All nine source commits are ancestors of that snapshot.
No extra dependency commit or package is needed. No wholesale main merge, optional #11367/#10804, #11577 or #11607, apps-permission expansion, SSH forwarding, version bump or changelog edit. No V1-to-V2 migration or private-session downgrade. Scope survivors without a provable runtime anchor remain an explicit fail-closed residual.
Changed surfaces include acp/client.py and acp/runtime.py; dashboard/chat_handlers.py, dashboard/chat_persistence.py, dashboard/chat_runner.py and dashboard/handlers; website/capture, website/scripts, website/src/hooks, website/src/i18n, website/src/pages, website/src/pierre, website/src/store, website/src/test and website/src/types. No workflow, permission, check/protection configuration or trigger changes. The second commit makes no .github changes.
Tests
Final reviewed commit: 698a523. It is the one new commit on top of 94506a1; total PR history is two commits.
Manual verification
The source tool-output capture was run on this release worktree at 94506a1 in light and dark themes and its rendered images inspected. A 144,069-character result renders 60,044 characters; one marker reports 84,080 removed characters and preserves whole head/tail lines. Both themes passed all ten assertions without page errors. The new commit has no frontend delta, so these remain evidence for identical UI code, not newly captured images of a different head.
Process tests use fixture-owned processes and process tables. Native macOS/Windows execution and long-duration leak trends were not exercised on this Linux host. POSIX retains the source-documented read-to-signal interval; no new atomic-PID-signaling guarantee is claimed. No live cleanup, config write or deployment was performed. Existing marker wording and the absence of an inline full-output action remain unchanged; the advisory UX concerns are answered in the PR thread rather than expanded into a new UI feature.
Screenshots / video
Unchanged release UI captured at 94506a1, with assertion evidence.
Full release-target CI is UNAVAILABLE: the release-base CI, Fast Gate and Build workflows accept only main for pull_request/push and have no workflow_dispatch entry. Review/portability/screenshot/scope/readiness workflows are not the full build/test matrix. Per maintainer direction, no workflow, branch filter, PR target, permission or protection is changed to obtain green. Native macOS/Windows and full release-target build/test results remain a pre-merge validation gap; local results do not replace them.
Related Issues
no linked issue: this bounded release backport deliberately closes no original leak issue.
Pattern harvest
Rule candidate: review-prompt
Pattern: backport process-identity producers and consumers together; persist only identities captured under ownership confirmation; keep discovery separate from private-memory consent.
Checklist