Skip to content

Wait tracer: pending Assignment approvals free running capacity #1037

Open

Description

@DoodleBears

Parent

#1019

What to build

An Assignment waits for a Human approval without occupying a running Assignment permit, while unrelated work continues and accepted approval resumes only the exact permitted operation.

Acceptance criteria

  • Use the positively verified native mechanism and application-owned bounded waiting state; preserve the current native authority and Assignment report/request model.
  • With an unresolved real native approval, prove another admitted message reaches a model reply and another permitted Assignment can execute.
  • Waiting capacity is finite and distinct from the running limit; approving several waits reacquires permits without exceeding that limit.
  • Check current actor/native decision and operation scope before start; denied, changed or revoked scope executes nothing.
  • Stop, owner cancellation, expiry and restart retain truthful work history but never replay a pending effect or masquerade cancellation as pause.
  • Expose waiting/running/needs-repair state through the existing work/attention surfaces and retain real cross-Bridge evidence.
  • Test through checked Provider and authenticated management/owning service boundaries; keep existing canonical persistence and no parallel content/decision authority.
  • Retain real sanitized screenshots/step evidence and maintain the affected English/Chinese tutorial section; UI changes include matched baseline/changed light/dark evidence and no private secrets.
  • Provide the exact-version runnable review path and focused behavioral coverage; pause for Human QA before expansion, without automatic merge/deployment.

Blocked by

Activity

  1. added this to the v1.2 milestone on Oct 6, 2026
  2. added
    ready-for-agentFully specified, ready for an AFK agent
    area:fullstackEnd-to-end Host and Client implementation
    feature:messagingMessaging module and external providers
    scope:tracerHuman-testable implementation slice
    on Oct 6, 2026
  3. DoodleBears commented on Oct 8, 2026

    @DoodleBears
    ContributorAuthor

    Agent work claim

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

    @DoodleBears
    ContributorAuthor

    Assignment approval capacity — real Host UI evidence

    Task: codex/local/01a11c24-31cb-7fa3-86d8-98e13f81a0b4. Exact current-main base: f1e6fc6182abe74f004dca528b68ccf5c48a6766; candidate includes that mainline. DSH RC1, real DeepSeek Flash, Chinese, 1500 × 1100. Separate isolated Profiles use the same harmless commands, with generated Bot/Grant IDs; machine-local paths are redacted.

    base-pending-light
    candidate-pending-light
    base-approved-light
    candidate-capacity-light
    base-pending-dark
    candidate-pending-dark
    base-approved-dark
    candidate-capacity-dark

  6. DoodleBears commented on Oct 8, 2026

    @DoodleBears
    ContributorAuthor

    Assignment approval capacity — interrupted execution card

    Same RC1 build and harmless command, Chinese, 1500 × 1100. The Human decision is retained, but Grant revocation during the capacity wait prevents the original effect; the actual native result is an error and the existing card projects needs-repair. Test-only Bot identities and local task paths are isolated/redacted.

    candidate-repair-light
    candidate-repair-dark

  7. DoodleBears commented on Oct 8, 2026

    @DoodleBears
    ContributorAuthor

    Agent work outcome

    • Agent: Codex
    • Task: codex/local/01a11c24-31cb-7fa3-86d8-98e13f81a0b4 (not a DSH Session)
    • State: handed-off for the first slice's Human QA; the issue remains open.
    • PR: Release running capacity during live Assignment approval waits #1239 (draft, no automatic merge/deployment).
    • Head: 1afab6c91040ab91a662f564751b6911400efbf0.
    • Scope delivered: quiescent independent Assignment approval releases its application running permit; the original native Promise/call reacquires capacity before continuation. Waiting Sessions have a separate bound of 32. Prepared calls/tool bodies retain permits; roots with any descendants conservatively retain them.
    • Verification: real authenticated RC1 Host, native Settings Service, real DeepSeek Flash and browser approval controls. Exact current-main baseline (f1e6fc61) refuses the competitor; candidate admits its actual command and an unrelated model reply while the original waits. The original resumes only after capacity; Grant revocation while waiting yields an actual error, no original effect and a needs-repair card. Public proof preserves exact native call/Turn and canonical Channel receipt correlation. 134 focused feature tests and 3 generated-reference tests passed locally. Final CI: Linux CI passed on the final head: 3,498 tests passed, 9 skipped; lint, format, typecheck, build, docs and generated-file checks are green..
    • Evidence: matched Chinese 1500 × 1100 light/dark screenshots embedded in the PR, with all 12 displayed image elements confirmed loaded in the authenticated GitHub page; sanitized proofs and bounded failure history are in docs/research/1037-assignment-approval-capacity.md and docs/evidence/issue-1037/. Test RPC connection reuse was qualified with 3/120 versus 0/120 read failures; the runner uses fresh connections without operation retries.
    • Remaining: Human QA on the bilingual Workspaces tutorial's runnable path before expanding this slice. This PR does not unblock a same-Orchestrator approval, finish Group privacy acceptance, or clear Prototype: verify a supported native wait and continuation seam #1036/Wait tracer: Orchestrator formal requests do not stop other Inbox work #1038's overall native-contract gates. Native production pins stay on RC1.
    • Cleanup: task-owned isolated Hosts are stopped; their Profiles and private raw evidence are retained machine-locally. No pending effect is replayed or reconstructed.
  8. removed
    agent:activeOne or more coding-agent tasks currently claim this issue; see claim comments for task IDs
    on Oct 8, 2026
  9. DoodleBears commented on Oct 9, 2026

    @DoodleBears
    ContributorAuthor

    Agent work outcome — merged

    • Agent: Codex
    • Task: codex/local/01a11c24-31cb-7fa3-86d8-98e13f81a0b4 (not a DSH Session)
    • State: completed for the bounded independent root Assignment approval-capacity slice.
    • PR: #1239, squash merged with explicit Human authorization as 652410b578077446a5265875c512c238125a2a8e.
    • Verification: final head 1afab6c91040ab91a662f564751b6911400efbf0 matched at merge; full Linux CI passed with 3,498 tests and 9 skipped. Final independent Standards and Spec reviews found zero merge blockers. This does not claim a separate Human runtime QA or GitHub approval review.
    • Real E2E: pinned RC1, actual DeepSeek model replies, browser approvals and native command execution prove unrelated dialogue, competing execution, accepted original waiting for capacity, exact-call resumption and revocation without the original effect. Cold recovery is covered by the working-snapshot regression rather than a live Host restart E2E.
    • Remaining: Assignments with descendants retain their permits. Same-Orchestrator native approval continuation and same-group privacy availability are not implemented; 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 stay open, and this bounded merge does not clear the overall gates. Production DSH pins remain RC1. No deployment or upstream post occurred.
  10. modified the milestones: v1.2, v1.3 on Oct 11, 2026
  11. 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

    area:fullstackEnd-to-end Host and Client implementationfeature:messagingMessaging module and external providersready-for-agentFully specified, ready for an AFK agentscope:tracerHuman-testable implementation slice

    Type

    No type

    Projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions