Repository navigation
Prototype: verify a supported native wait and continuation seam #1036
Description
Parent
What to build
Exercise real native Assignment approvals and Orchestrator questions/approvals in an isolated pinned DSH Profile, identifying a supported exact-operation continuation that can leave unrelated Bot Inbox handling available.
Acceptance criteria
- Reproduce current wait behavior and distinguish durable Admission from actual model processing; use the existing Web decision surface so IM pairing is not a prerequisite.
- Exercise both an Assignment-owned approval and an Orchestrator-owned formal question/tool approval; one passing case cannot establish the other.
- Validate exact native Session/call ownership, decision acceptance, subsequent authorized result and changed-scope refusal; cancellation is not a suspension substitute.
- Return a runnable bounded experiment, actual model/native event evidence, and the supported mechanism or a reproducible upstream capability gap.
- If upstream work is required, record and attach the concrete blocking issue before closing this gate/unblocking production continuation tickets. A negative research result is not a usable resume implementation.
- Document necessary ADR/architecture reconciliation without inventing a second executor, mailbox or native API.
- Retain sanitized native/model/runtime evidence and a runnable experiment; no credential exposure or production service changes.
- Keep research outcome distinct from production delivery and update concrete blocking relationships before implementation selection.
Blocked by
- Blocked: qualify native exact-operation continuation for one Orchestrator root #1220 — verified same-Orchestrator native continuation capability gap; negative feasibility evidence does not clear this gate.
Activity
DoodleBears commentedon Oct 8, 2026
Agent work claim
codex/local/01a11c24-31cb-7fa3-86d8-98e13f81a0b4(not a DSH Session)codex/1036-native-wait-continuationDoodleBears commentedon Oct 8, 2026
Agent work outcome
codex/local/01a11c24-31cb-7fa3-86d8-98e13f81a0b4(not a DSH Session)Official DSH
0.2.0-rc.1/4878cdabd87d4041bdaff61d04c966883b9fd07awas qualified through task-owned isolated Hosts and realdeepseek-official/deepseek-flashmodel replies. Assignment-owned approval allowed its independent Orchestrator to reply to unrelated Inbox work before decision; Web Allow once then returned the original call's exact stdout. This does not release the waiting Assignment's running permit or deliver bounded wait/reacquisition.The Orchestrator's own native approval and formal question both blocked unrelated native input claim/model processing for over 20 seconds despite accepted Admission/steer. Existing Web controls resolved the exact original same-Session call, followed by the unrelated real model reply. Changed/revoked Grant cases refused the stale Web decision and returned native
unavailable/error without executing the pending command. Five sanitized timelines retain original native identity/arguments/results and model-send/Channel-receipt correspondence. No cancellation or restart was used as continuation.Concrete local upstream-capability blocker #1220 is a native sub-issue of #1019 and native blocker of #1036. The chain remains #1220 → #1036 → #1037 → #1038. #1036 stays open; #1037/#1038 are not implemented or unblocked. A future supported mechanism needs fresh real native/model/scope qualification and explicit gate review. No upstream issue was posted; upstream contribution-rule review and Human authorization remain necessary before posting.
Build, lint/source-policy/bilingual ledger checks, formatting, type checking and 34 focused tests passed. The full suite encountered failures in unchanged modules; a standalone single-worker Registry case reproduced Windows temporary-directory cleanup
EPERM, while other timeout causes remain unproven. This is not a green full-suite result. Failed experiment attempts and read-only evidence recovery are documented. Both exact task-owned Hosts were stopped after evidence capture; no shared IM or production service was changed.Human QA should rerun both Orchestrator cases from the report, inspect exact original results and unrelated reply ordering, and review #1220's capability requirements. This handoff includes no automatic merge or deployment.
3 remaining items
test: require exact native wait results
DoodleBears commentedon Oct 8, 2026
Final verification supplement for draft PR #1223:
EPERM; other timeouts remain unproven. This does not qualify a green local full suite.spawnSync pnpm ENOENTon Windows.Task:
codex/local/01a11c24-31cb-7fa3-86d8-98e13f81a0b4; state remains handed-off for Human QA.DoodleBears commentedon Oct 8, 2026
Agent work claim resumed: task
codex/local/01a11c24-31cb-7fa3-86d8-98e13f81a0b4, branchcodex/1036-native-wait-continuation. Scope: Human-requested clarification of #1038 group-conversation availability during pending native questions/permissions, reconcile the experiment report and draft PR; no production implementation or gate change. State: active.docs: clarify conversation availability during permission waits
DoodleBears commentedon Oct 8, 2026
Human clarification recorded
Task:
codex/local/01a11c24-31cb-7fa3-86d8-98e13f81a0b4; state: handed-off for Human QA.The requested behavior is already owned by #1038: a pending Orchestrator question or permission request must hold only its original operation, while the same PersonaBot remains available for permitted conversation. #1038 now explicitly requires the same-group private-content scenario: keep the request pending, obtain real model replies to the requester and another eligible member, disclose no protected content or private approval details, and verify rejection leaves dialogue available. Existing admission/visibility/authorization policies still apply; chat and group membership cannot grant permission.
Draft PR #1223 and its experiment report now distinguish this required future behavior from the observed RC1 limitation. The retained DM experiment is not group-privacy qualification. #1220's supported native capability remains prerequisite; the #1036 → #1037 → #1038 gates stay unchanged. No production runtime change, new upstream post, merge or deployment is included.
docs: qualify native Human waits and gate continuation (#1223)
DoodleBears commentedon Oct 8, 2026
PR #1223 merged after the final verify CI passed, following explicit Human authorization. Task
codex/local/01a11c24-31cb-7fa3-86d8-98e13f81a0b4: experiment/documentation delivery completed; overall #1036 continuation gate stays open and blocked by #1220. Continuing a bounded #1220 investigation on branchcodex/1220-native-deferred-question; no deployment or upstream posting.DoodleBears commentedon Oct 8, 2026
The authorized #1223 experiment is merged. The bounded follow-up is now draft #1227 under #1220: official RC2 timed questions can truthfully return pending, leave the original question answerable, and process a real unrelated model reply plus a qualified late answer in the same Session.
This does not qualify an open approval Tool, application Channel authorization, running-capacity release/reacquisition or the required same-group privacy behavior. The current application question card cancels at the native deadline; that integration gap is retained in the evidence. Production remains RC1 and #1036 → #1037 → #1038 gates remain blocked. Report and exact native evidence.
DoodleBears commentedon Oct 8, 2026
Question-path progress for this still-blocked gate: PR #1227 now contains a real browser/model DM tracer. The original timed question remains answerable while the same Session replies to unrelated ordinary input; after that entire Turn ends, clicking the original card admits the original-call native answer and produces an actual selected-answer Channel reply. The PR fixes both deadline cancellation and the observed missing application run after idle, and revalidates current authority immediately before native delivery.
Runnable report and evidence. This is isolated RC2 question behavior; production pins stay RC1. Permission approval, bounded capacity, cold recovery and same-group privacy remain unqualified. #1220 and #1036 stay open; #1036 → #1037 → #1038 remains blocked. No upstream post or rollout.