Skip to content

Assignment: preserve open asks until answer delivery is accepted #812

New issue
New issue
Closed
#840
Closed
Assignment: preserve open asks until answer delivery is accepted#812
#840
Labels
area:backendHost-side implementationbugSomething isn't workingfeature:assignmentOrchestrator and Assignment collaborationready-for-humanRequires human implementationscope:tracerHuman-testable implementation slice
Milestone
v1.0

Description

@DoodleBears
DoodleBears
opened on Oct 4, 2026

Parent: #81. Related: #194 (Attention acceptance remains separate).

Observable problem

An Assignment's open ask is cleared before the DSH adapter accepts its addressed answer. On main 647fbe958f72053c1b85d45cc05996a92603a658, create a waiting-human ask, finish its turn, then fail answer delivery before acceptance: no answer arrives, but the open ask disappears. Retrying the same answer_to no longer addresses an open ask.

Outcome

An answer is considered resolved only after the owning delivery boundary establishes its accepted outcome. Proven pre-acceptance failure leaves the question actionable and retryable; ambiguous execution must remain visible for repair rather than be silently answered or blindly replayed.

Acceptance

  • A synchronous pre-acceptance refusal or failure preserves the original ask reference, waiting state and Human source navigation; retry can answer that same ask.
  • A successful answer clears the matching ask once and resumes the same Assignment.
  • A delayed failure while starting an idle/cold Session does not silently lose the original question; establish honest accepted/failed/uncertain semantics using current DSH facts.
  • Concurrent/newer questions are not erased by settlement of an older answer. Preserve Grant and immutable permission/model boundaries.
  • Focused tests cover failure, retry, success, stale/newer ask and restart/uncertain settlement as applicable.
  • A real isolated DSH answer/recovery path is Human-operable; capture real screenshots or recording, open a PR, and pause for Human QA.

Boundaries

Use the current Host Assignment Runtime, durable Directory and native DSH execution facts. Do not require the historical Delivery Intent implementation by name. No duplicate Attention system or generic retry scheduler; #194 remains independently scoped.

Activity

  1. DoodleBears
    added this to the v1.0 milestone on Oct 4, 2026
  2. DoodleBears
    added
    bugSomething isn't working
    ready-for-agentFully specified, ready for an AFK agent
    area:backendHost-side implementation
    feature:assignmentOrchestrator and Assignment collaboration
    scope:tracerHuman-testable implementation slice
    on Oct 4, 2026
  3. DoodleBears
    added a parent issue on Oct 4, 2026
  4. github-project-automation
    added this to Roadmapand Bot Activity & Avatar Presenceon Oct 4, 2026
  5. github-project-automation
    moved this to Todo in Bot Activity & Avatar Presenceon Oct 4, 2026

  6. DoodleBears commented on Oct 4, 2026

    @DoodleBears
    DoodleBears
    on Oct 4, 2026
    ContributorAuthor

    Agent work claim

    • Agent: Codex
    • Task: codex/local/01a0f25f-2150-75e3-8895-23d35394b8d8 (not a DSH Session)
    • Issue scope: preserve original Assignment asks until native DSH Inbox acceptance, distinguish proven pre-acceptance failure from uncertain/post-acceptance execution, and verify real same-Session recovery.
    • Branch: codex/812-answer-acceptance
    • Started: 2026-10-04 19:38 UTC
    • State: active

    Human authorized merge and continuation. #821 is merged; the approved #832 final integration is in CI. This issue's isolated implementation/reproduction can proceed during that check, while its PR will follow #832 merge. Preserve #194's independent Attention scope; reuse existing Directory and native Session facts. This task will pause after its PR for Human QA.

  7. DoodleBears
    added
    agent:activeOne or more coding-agent tasks currently claim this issue; see claim comments for task IDs
    on Oct 4, 2026

  8. DoodleBears commented on Oct 4, 2026

    @DoodleBears
    DoodleBears
    on Oct 4, 2026
    ContributorAuthor

    Agent work outcome

    • Agent: Codex
    • Task: codex/local/01a0f25f-2150-75e3-8895-23d35394b8d8 (not a DSH Session)
    • State: paused — Human QA
    • PR: #840
    • Head: 8e7db6a42508a2d1fe38137de3fa865e6cfbe6ce
    • Delivered: original asks settle only after native Inbox acceptance; proven synchronous/asynchronous refusal preserves idle waiting state and canonical same-ask retry proof; uncertain/post-acceptance failures remain repair-visible. Older runs cannot erase newer asks or ambiguity, and competing Human retries retain a single winner.
    • Verification: real pinned DSH + DeepSeek Flash E2E reproduced the same native cold-resume refusal on base and implementation, then completed a real Human Inbox form retry in the original Assignment. Exactly one additional native Inbox message was accepted, permissions/model were unchanged, and completion remained closed after restart. The PR embeds 8 verified GitHub-rendered light/dark and recovery screenshots plus allowlisted native facts. Final changed-surface tests: 98 passed; separate Browser environment tests: 21 passed; independent Standards/Spec reviews passed.
    • CI: full verification passed on the exact PR head 8e7db6a42508a2d1fe38137de3fa865e6cfbe6ce.
    • Human QA path: the isolated preview is left with the original preserved ask, an enabled retry form, and the test fault removed. Open Bot mode → Activity center → Inbox → Actions → reply to the Assignment with choice A. Verify the original Session completes and the action disappears.
    • Remaining scope: Human QA and explicit merge approval. Assignment: preserve open asks until answer delivery is accepted #812 and parent Foundation：Assignment Runtime / Assignment Directory / Orchestrator tools #81 stay open until merge and final closeout verification. No Assignment Attention: causal dedupe, escalation and recovery acceptance #194 Attention work was included.
  9. DoodleBears
    added
    ready-for-humanRequires human implementation
    and removed
    ready-for-agentFully specified, ready for an AFK agent
    agent:activeOne or more coding-agent tasks currently claim this issue; see claim comments for task IDs
    on Oct 4, 2026

  10. DoodleBears commented on Oct 5, 2026

    @DoodleBears
    DoodleBears
    on Oct 5, 2026
    ContributorAuthor

    Agent work claim — Human QA follow-up

    • Agent: Codex
    • Task: codex/local/01a0f25f-2150-75e3-8895-23d35394b8d8 (not a DSH Session)
    • Issue scope: Human-requested Inbox QA layout correction on PR fix(core): keep Assignment asks open until native answer acceptance #840: wider detail presentation and full-width title with a second row for summary/actions in the split Inbox list.
    • Branch: codex/812-answer-acceptance
    • State: active — address Human QA feedback, then return to Human QA without merge.
  11. DoodleBears
    added
    agent:activeOne or more coding-agent tasks currently claim this issue; see claim comments for task IDs
    on Oct 5, 2026
  12. DoodleBears
    added 2 commits that reference this issue on Oct 5, 2026

    fix(client): unify Inbox details and preserve full-width titles

    7c5f64e

    docs: capture Human Inbox layout QA and inline answer delivery

    628ea32

  13. DoodleBears commented on Oct 5, 2026

    @DoodleBears
    DoodleBears
    on Oct 5, 2026
    ContributorAuthor

    Agent work outcome — Human QA layout follow-up

    • Agent: Codex
    • Task: codex/local/01a0f25f-2150-75e3-8895-23d35394b8d8 (not a DSH Session)
    • State: paused — Human QA
    • PR: #840
    • Head: 628ea32471a099a94fe01319a967a0c6155ed40a
    • Delivered: Activity Center row and primary action share the existing inline split detail; each Inbox item has a full-width title on the first row, with summary/actions on the second. Compact Overview retains the native Modal, widened to 760px with native viewport limits and scrolling.
    • Verification: 72 related Client regressions passed, together with lint, format, typecheck, ledgers and build. Real DSH inline-form retry completed the original Assignment with exactly one additional native accepted answer. Independent Standards and Spec reviews passed. All 15 before/after, light/dark and recovery images in the updated PR loaded successfully on GitHub.
    • CI: full verification passed at the exact head above.
    • Human QA: isolated Host data is restored to the original preserved ask, with the test fault removed. The final browser automation reconnect stalled although the authenticated Inbox query still returned the expected action; reopen the authenticated preview if the existing tab remains at Loading Inbox. Capture evidence reflects the actual successful inline interaction before restoration.
    • Remaining scope: Human QA and explicit merge approval; Assignment: preserve open asks until answer delivery is accepted #812 and Foundation：Assignment Runtime / Assignment Directory / Orchestrator tools #81 remain open. No merge was performed.
  14. DoodleBears
    removed
    agent:activeOne or more coding-agent tasks currently claim this issue; see claim comments for task IDs
    on Oct 5, 2026
  15. DoodleBears
    added a commit that references this issue on Oct 5, 2026

    fix(core): keep Assignment asks open until native answer acceptance (#…

    490ac03
  16. DoodleBears
    closed this as completedin #840on Oct 5, 2026
  17. github-project-automation
    moved this from In Progress to Done in Bot Activity & Avatar Presenceon Oct 5, 2026

  18. DoodleBears commented on Oct 5, 2026

    @DoodleBears
    DoodleBears
    on Oct 5, 2026
    ContributorAuthor

    Agent work outcome — completed after Human QA

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

    area:backendHost-side implementationbugSomething isn't workingfeature:assignmentOrchestrator and Assignment collaborationready-for-humanRequires human implementationscope:tracerHuman-testable implementation slice

    Type

    No type

    Projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions