Skip to content

Blocked: qualify native exact-operation continuation for one Orchestrator root #1220

New issue
New issue
Open
Open
Blocked: qualify native exact-operation continuation for one Orchestrator root#1220
Labels
feature:messagingMessaging module and external providersneeds-infoWaiting on reporter for more informationscope:researchEvidence-gathering or mechanism spike
Milestone
v2.0

Description

@DoodleBears
DoodleBears
opened on Oct 8, 2026

Parent and gate

Part of #1019; discovered by #1036. Project 10 · Milestone v1.2.

Verified gap

On official DSH 0.2.0-rc.1, revision 4878cdabd87d4041bdaff61d04c966883b9fd07a, a single Orchestrator Agent waiting on its own native tool approval or ask_user_question cannot process unrelated Inbox input until that pending call resolves. steer accepts next-step input; the driver remains inside the awaited current tool step. An independent Assignment approval can leave the Orchestrator available, but does not provide same-root continuation or release an Assignment running permit.

The real isolated #1036 experiment obtained a model DM baseline, reproduced both Orchestrator waits, observed no unrelated native user-message claim/model reply for over 20 seconds, then used existing Web controls. The original exact call completed successfully in the same Session, and the unrelated message was claimed and replied to only afterwards. Native approval IDs/call IDs, tool results, model route and Channel receipt correspondence are retained in the candidate branch codex/1036-native-wait-continuation under docs/evidence/issue-1036/. Source analysis: docs/research/1036-native-wait-source-analysis.md.

Primary source: Agent driver, step tool wait, public Agent contract.

RC2 question frontier (2026-10-09)

Merged PR #1227 now contains a real Web Client DM card tracer on isolated official DSH 0.2.0-rc.2, revision 639ed015397290b3745d163aafe02ffee4aa3f84, application df380a9599277f858e29adb02856dc21d12b044a. Browser E2E report, sanitized timeline, pinned source frontier.

  • The actual browser composer requests a timed question. After its foreground Tool returns pending, the original card remains answerable; the same Session replies to unrelated ordinary input and its Turn fully ends. The Human then clicks the original card: one qualified native reply settles the original call, the model sends the selected answer with a committed Channel receipt, and the card shows answered. Wrong-call and duplicate settled answers refuse; browser console has zero warnings/errors.
  • The application binds original Source Event/Session/DM context and serializes late delivery through the existing owning Orchestrator runtime, rechecking current authority immediately before native admission and retaining the run through native idle. The native Service/Projection remain answer and settlement authority. No extra ordinary answer input, second executor, question reissue or Agent restart is used; the process-local correlation does not implement cold recovery.
  • Historical negative evidence is preserved: the original native-only baseline cancelled the application card; a later real card run admitted the answer after idle but could not send because its application run had ended. The PR fixes both observed gaps and retains the failed timeline. 76 focused regressions and application/static/docs checks pass; CI reports the pushed revision separately.
  • This is two-settlement question semantics, not suspension of an open Tool Promise or a permission Grant. Production dependencies remain RC1. Permission approval, bounded running capacity, cold recovery and same-group privacy acceptance are not qualified; Wait tracer: Orchestrator formal requests do not stop other Inbox work #1038 still owns the latter.

The original RC1 result remains valid for its pinned runtime. #1220 and #1036 remain open; the overall same-Orchestrator and Group continuation gates remain blocked. See the later Assignment slice and authorized upstream feedback below. No production rollout occurred.

Approval frontier and upstream feedback (2026-10-09)

Merged PR #1239 qualifies the bounded RC1 independent root Assignment capacity slice: quiescent original native approvals release an application running permit, accepted calls reacquire it and recheck current authority, and a revoked Grant prevents the original effect. Assignments with descendants retain their permit. This does not provide same-Orchestrator native approval continuation or Group privacy availability.

Concrete existing upstream tracker: deepseek-harness Discussion #8916. With explicit Human authorization, this task published an actual-model/browser evidence supplement linking the RC1 approval reproduction, RC2 original question-card continuation and merged Assignment capacity evidence, plus exact-operation/current-authority/no-replay and same-group privacy requirements. Publication was read back and matched against the prepared text. No maintainer-supported mechanism has yet been established; this feedback does not clear the completion gate.

Rechecked official master/latest release at 5badb15009ae1756c3afe0ae0cef1faafc290ccc / dsh-v0.2.1-alpha.1: the approval Service and default Agent loop sources remain unchanged from the investigated implementations. Approval has no pending outcome and still requires an open Turn. This is source comparison, not a new alpha runtime qualification. Production pins stay RC1 and no deployment occurred.

Required resolution

  • Preserve downstream Wait tracer: Orchestrator formal requests do not stop other Inbox work #1038 conversation availability: a pending question/permission holds only its protected operation; permitted same-group conversation remains possible without protected reads/disclosure, implicit approval or loss of the original pending identity. Same-group privacy qualification belongs to Wait tracer: Orchestrator formal requests do not stop other Inbox work #1038 and is not demonstrated by the current DM experiment.

  • Obtain an upstream-supported exact pending-operation suspension/continuation contract (or another maintainer-supported mechanism that preserves one dispatch root), retaining original Session/call/owner and pending tool arguments.

  • Qualify native question and permission approval separately. A supported timed question may finish its original Tool truthfully with pending while preserving the original answerable question; require a real unrelated model reply before decision, qualified original-call answer admission and actual model processing afterwards. For permission approval, preserve the exact protected operation and arguments and require a successful original authorized result only after a valid decision. Neither path may treat ordinary chat as a decision or permission.

  • Revalidate current operation/actor/Grant authority; changed/revoked scope executes nothing. Reacquire bounded running capacity; retain native cancellation/stop/restart semantics without replay.

  • Retain pinned runnable evidence and reconcile ADR/architecture before clearing the gate. A later DSH release or source claim alone is insufficient.

Do not implement a second executor/Orchestrator/mailbox or decision authority, fabricate native APIs, treat Admission as model processing, or cancel/restart as suspension. #1036 stays open and blocking #1037; #1038 remains downstream of #1037. The feasibility report is not production delivery.

This is the concrete local upstream-capability tracking issue. Existing upstream Discussion #8916 now has this task's Human-authorized evidence supplement; an upstream fix or accepted contract has not been established.

Completion gate

Activity

  1. DoodleBears
    added this to the v1.2 milestone on Oct 8, 2026
  2. DoodleBears
    added
    needs-infoWaiting on reporter for more information
    feature:messagingMessaging module and external providers
    scope:researchEvidence-gathering or mechanism spike
    on Oct 8, 2026
  3. DoodleBears
    added this to IM Identities & Messagingon Oct 8, 2026
  4. DoodleBears
    marked this as blocking on Oct 8, 2026
  5. DoodleBears
    added a parent issue on Oct 8, 2026
  6. github-project-automation
    added this to Roadmapon Oct 8, 2026

  7. DoodleBears commented on Oct 8, 2026

    @DoodleBears
    DoodleBears
    on Oct 8, 2026
    ContributorAuthor

    The reviewable experiment is now draft PR #1223, with pinned source analysis, runnable report and five sanitized exact-operation timelines.

    This local issue is linked as a native child of #1019 and native blocker of #1036. The downstream gates remain blocked. No upstream issue or implementation is claimed; Human review of the capability requirements and upstream contribution rules must precede any authorized upstream post, followed by real supported-mechanism qualification before clearing #1036.

  8. DoodleBears
    added a commit that references this issue on Oct 8, 2026

    docs: qualify native Human waits and gate continuation (#1223)

    e1c1b43

  9. DoodleBears commented on Oct 8, 2026

    @DoodleBears
    DoodleBears
    on Oct 8, 2026
    ContributorAuthor

    Agent work claim

    • Agent: Codex
    • Task: codex/local/01a11c24-31cb-7fa3-86d8-98e13f81a0b4 (not a DSH Session)
    • Issue scope: investigate and locally qualify the native opt-in deferred question mechanism introduced after RC1, including original-request correlation, late-answer ownership, existing Web/Channel authorization and actual model conversation during the wait; keep permission approvals separately blocked. No production rollout or upstream posting.
    • Branch: codex/1220-native-deferred-question
    • State: active
  10. DoodleBears
    added
    agent:activeOne or more coding-agent tasks currently claim this issue; see claim comments for task IDs
    on Oct 8, 2026
  11. DoodleBears
    added 2 commits that reference this issue on Oct 8, 2026

    Merge main into native timed-question qualification

    397f874

    test: verify answer enqueue occurs after unrelated reply

    b4665f8

  12. DoodleBears commented on Oct 8, 2026

    @DoodleBears
    DoodleBears
    on Oct 8, 2026
    ContributorAuthor

    Agent work outcome

  13. 7 remaining items

  14. DoodleBears
    added 2 commits that reference this issue on Oct 8, 2026

    test: qualify late question cards through real browser and model

    8faaa51

    test: include native answer discard consumer in generated reference

    c8199b1

  15. DoodleBears commented on Oct 8, 2026

    @DoodleBears
    DoodleBears
    on Oct 8, 2026
    ContributorAuthor

    Agent work outcome — real DM card tracer

    • Agent: Codex
    • Task: codex/local/01a11c24-31cb-7fa3-86d8-98e13f81a0b4 (not a DSH Session)
    • State: handed-off — the bounded live DM card behavior is implemented and reviewable; the native-capability issue remains open.
    • PR: fix: preserve RC2 timed question cards through late replies #1227 (draft), head c8199b1563c615839b551e7afef7bef2e679b852; final real application/model baseline df380a9599277f858e29adb02856dc21d12b044a.
    • Actual E2E: real browser composer → native timed question → foreground pending → unrelated real model reply → ordinary Turn fully ended → original visible card selection/submission → original Session/call native admission/settlement → actual selected-answer Channel reply and answered card. Wrong-call/duplicate answers refuse; no restart, reissue or synthetic ordinary answer input. Browser console: zero warnings/errors.
    • Fixed observed failures: the deadline previously cancelled the application card; after idle, native answer admission alone could leave model Channel tools without an owning application run. Late delivery now binds the original Source Event context, enters the existing serialized Bot Runtime, checks current ownership/DM/source authority immediately before delivery, and keeps that run through native idle. Native Service/Projection remain decision and settlement authority.
    • Evidence: report and runnable path, sanitized success, retained lifecycle failure. Before/after screenshots in both themes are embedded in the PR; all six GitHub-rendered images return HTTP 200/image/png.
    • Validation: 76 focused regressions pass; the final exported real proof also revalidates. Lint/source policy, type check, format, both bilingual ledgers, application build, Chinese OG font regeneration and direct Astro build (416 pages) pass. One existing Windows Host Inbox pagination test exceeded its default 15-second limit (four others passed); full Windows repository tests are not claimed. Final Linux CI passes the full repository test suite and build. The first CI run exposed one stale generated-reference consumer assertion; its native discard event entry is now covered by three passing documentation tests.
    • Remaining: production RC1 is unchanged; permission approval, bounded capacity, cold recovery and same-group privacy acceptance remain separately unqualified. Blocked: qualify native exact-operation continuation for one Orchestrator root #1220 → Prototype: verify a supported native wait and continuation seam #1036 → Wait tracer: pending Assignment approvals free running capacity #1037 → Wait tracer: Orchestrator formal requests do not stop other Inbox work #1038 stays blocked. No upstream post, rollout or PR merge.
    • Cleanup: task-owned isolated Host was stopped after final capture; credentials and raw evidence remain private. The next slice must be selected against the still-open native approval/capacity boundary, with same-group acceptance tracked by Wait tracer: Orchestrator formal requests do not stop other Inbox work #1038.
  16. DoodleBears
    removed
    agent:activeOne or more coding-agent tasks currently claim this issue; see claim comments for task IDs
    on Oct 8, 2026
  17. DoodleBears
    added a commit that references this issue on Oct 8, 2026

    fix: preserve RC2 timed question cards through late replies (#1227)

    0036c73

  18. DoodleBears commented on Oct 8, 2026

    @DoodleBears
    DoodleBears
    on Oct 8, 2026
    ContributorAuthor

    Agent work outcome — merged

  19. DoodleBears commented on Oct 9, 2026

    @DoodleBears
    DoodleBears
    on Oct 9, 2026
    ContributorAuthor

    Agent work claim — approval continuation follow-up

    • Agent: Codex
    • Task: codex/local/01a11c24-31cb-7fa3-86d8-98e13f81a0b4 (not a DSH Session)
    • Issue scope: after authorized merge of Release running capacity during live Assignment approval waits #1239, refresh the exact upstream approval/driver capability check, inspect existing upstream feedback, and prepare a public-safe maintainer-ready approval-continuation reproduction and contract request. No production dependency upgrade, substitute executor or upstream posting.
    • Branch: codex/1037-assignment-approval-capacity (read-only source review and ignored follow-up artifacts; no implementation changes)
    • Started: 2026-10-09 UTC
    • State: active
  20. DoodleBears
    added
    agent:activeOne or more coding-agent tasks currently claim this issue; see claim comments for task IDs
    on Oct 9, 2026

  21. DoodleBears commented on Oct 9, 2026

    @DoodleBears
    DoodleBears
    on Oct 9, 2026
    ContributorAuthor

    Agent work outcome — existing upstream blocker identified

    • Agent: Codex
    • Task: codex/local/01a11c24-31cb-7fa3-86d8-98e13f81a0b4 (not a DSH Session)
    • State: handed-off — maintainer-ready evidence supplement prepared; no upstream post made.
    • Human-authorized PR #1239 is merged as 652410b578077446a5265875c512c238125a2a8e. Its independent Assignment capacity slice does not solve same-root approval waiting.
    • Concrete existing upstream tracker: deepseek-harness Discussion #8916 — pending approvals block the entire step, opened by another contributor on 2026-10-05. Read the complete discussion on 2026-10-09: no comments, accepted answer or supported continuation contract was present. Related #9214 concerns ending wait_agent waits; it does not establish approval continuation.
    • Rechecked the official latest release and default branch: dsh-v0.2.1-alpha.1 / master at 5badb15009ae1756c3afe0ae0cef1faafc290ccc. Approval Service blob 9a14f04d0b3c7f6dbcacb1fd2537186b1213f02e and default driver blob 2f68565cef052f82ef6f2a740141962507654e02 are unchanged from the investigated sources. The current approval outcomes are allowed-once/rejected/cancelled/unavailable, without pending; request remains Turn-enclosed. This check is source evidence, not a new alpha Host E2E.
    • Prepared a sanitized supplement for that existing discussion, incorporating the merged RC1 negative reproduction, RC2 real question-card E2E and RC1 Assignment capacity/revocation evidence, plus exact-call/current-authority/no-replay and same-group privacy requirements. Publication awaits explicit Human authorization to contact upstream maintainers.
    • Blocked: qualify native exact-operation continuation for one Orchestrator root #1220/Prototype: verify a supported native wait and continuation seam #1036/Wait tracer: Orchestrator formal requests do not stop other Inbox work #1038 remain open. No production dependency upgrade, second executor, deployment or gate clearance occurred.
  22. DoodleBears
    removed
    agent:activeOne or more coding-agent tasks currently claim this issue; see claim comments for task IDs
    on Oct 9, 2026

  23. DoodleBears commented on Oct 9, 2026

    @DoodleBears
    DoodleBears
    on Oct 9, 2026
    ContributorAuthor

    Agent work outcome — authorized upstream feedback published

  24. DoodleBears
    modified the milestones: v1.2, v1.3 on Oct 11, 2026
  25. DoodleBears
    modified the milestones: v1.3, v2.0 on Oct 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    feature:messagingMessaging module and external providersneeds-infoWaiting on reporter for more informationscope:researchEvidence-gathering or mechanism spike

    Type

    No type

    Projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions