You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maka.apache.org by "Phoenix500526 (via GitHub)" <gi...@apache.org> on 2026/08/31 07:49:55 UTC
[I] tracking(runtime): harden safe-boundary continuation for production [maka]
Phoenix500526 opened a new issue, #4324:
URL: https://github.com/apache/maka/issues/4324
## Problem
Maka has landed the core safe-boundary continuation protocol, but the
architecture still records production gates that are not represented by one
focused tracker. The current path can prove immutable history and provider
replay identity; it does not yet bind the complete execution semantics or all
cross-process ownership evidence needed for broader or default auto-resume.
#3731 tracks one required subset: sandbox-boundary negotiation across
continuations. It does not cover the resolved model, system prompt, tool
schemas and recovery contracts, provider materializer, consolidated boundary
verification, or durable Host fencing.
Design sources:
- [Runtime resume architecture](https://github.com/apache/maka/blob/main/docs/architecture/runtime-resume-architecture.md)
- [Runtime resume extraction ledger](https://github.com/apache/maka/blob/main/docs/architecture/runtime-resume-extraction-ledger.zh-CN.md)
- [Phase 3–4 implementation route](https://github.com/apache/maka/blob/main/docs/architecture/runtime-resume-phase3-phase4-workspace-checkpoint-design.zh-CN.md)
Related implementation: #1223, #1521, #1573, and #1996. Related subset:
#3731.
## Current baseline and remaining work
- [x] Recover canonical RuntimeEvent history and create fresh continuation identities (#1223)
- [x] Persist and rebuild recovery facts through one SQLite authority (#1521)
- [x] Derive immutable lineage boundaries and claim them atomically (#1573)
- [x] Expose Host-owned resume query/start and revalidate under the backend activation barrier (#1996)
- [ ] Define `ContinuationExecutionProfileV1` for backend/model, prompt, tool schemas and recovery contracts, protocol, provider materializer, and permission/sandbox policy
- [ ] Bind that profile through plan, claim, continuation-start, and execution, failing closed on drift
- [ ] Incorporate #3731's durable negotiation state without treating it as execution authority
- [ ] Consolidate boundary, lineage, target, start, terminal, and replay validation in one `ContinuationBoundaryVerifier`
- [ ] Add durable workspace-scoped owner epoch/fencing and append-if-absent/CAS where repair could duplicate facts
- [ ] Prove repair ordering, shutdown/restart, competing Hosts, and live-start-indeterminate behavior with crash/race tests
- [ ] Define rollout gates for manual resume and startup auto-resume, and keep the architecture status current
## Non-goals
- Production Write/Edit reconciliation (#4319)
- Reimplementing the sandbox-negotiation work in #3731
- Phase 4 Git workspace restore or rebaseline
- Generic provider retry, Bash replay, or ShellRun reattachment
- TUI/session-list discovery and bulk-resume UX (#3508, #3712)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@maka.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@maka.apache.org
For additional commands, e-mail: commits-help@maka.apache.org
Re: [I] tracking(runtime): harden safe-boundary continuation for production [maka]
Posted by "M4n5ter (via GitHub)" <gi...@apache.org>.
M4n5ter closed issue #4324: tracking(runtime): harden safe-boundary continuation for production
URL: https://github.com/apache/maka/issues/4324
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@maka.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@maka.apache.org
For additional commands, e-mail: commits-help@maka.apache.org
Re: [I] tracking(runtime): harden safe-boundary continuation for production [maka]
Posted by "M4n5ter (via GitHub)" <gi...@apache.org>.
M4n5ter commented on issue #4324:
URL: https://github.com/apache/maka/issues/4324#issuecomment-5566406364
Closing this broad roadmap tracker as **not planned in its remaining form**, not as a claim that all listed production gates have shipped.
#4958 implements the concrete cooperative-handoff requirements: persist and validate the actual Run composition before successor dispatch, fail closed on unsupported preparation or semantic drift, and retain explicit sandbox denial through authenticated lineage. It builds on the existing SQLite continuation claim and State Root single-writer authority. Missing/drifting composition regression coverage is in `packages/runtime/src/__tests__/runtime-handoff.test.ts`.
That does **not** establish universal startup auto-resume, apply the new handoff-specific composition preparation to every generic manual continuation, or prove arbitrary repair exactly-once. These are deferred capabilities, not promises added by #4958. We do not need a parallel execution-profile envelope, a specifically named consolidated verifier, or another fencing layer solely to complete an old architectural checklist; each would need a concrete uncovered invariant and supported consumer.
Concrete unresolved work still has focused trackers: #4319 for production Write/Edit reconciliation, #4423 for undispatched-tool classification, and #4424 for actionable parked-run recovery. If broader auto-resume is proposed, or a reproducible ownership/repair race is found, open a bounded issue with that scenario and its required evidence. This closure does not enable broader resume behavior or remove existing safety gates.
本次关闭过宽的路线 tracker，不把未实现的通用自动恢复标为完成。#4958 承接具体交接门禁；文件恢复、未派发分类和 parked UX 继续由现有专项 issue 跟踪，其余能力等出现明确需求或问题再开。
AI assistance: Codex assisted with the current-code and scope assessment.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@maka.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@maka.apache.org
For additional commands, e-mail: commits-help@maka.apache.org