Skip to content

Slice: render inbox after prepare in the orchestrator turn #351

Closed

Description

@DoodleBears

Parent

#350

What to build

As a Human talking to a PersonaBot, I want every turn message assembled exactly as today, so that moving the inbox render later changes nothing observable. As a future memory notice, I want the render to happen after the turn's worktree observation, so that freshly observed changes can join the same turn.

Acceptance criteria

  • Turn messages render byte-identical to today across DM, group, digest, report, and resume paths.
  • The inbox render consumes the same pending admissions as before; no admission is dropped or duplicated by the move.
  • Existing turn-message suites pass unchanged.

Blocked by

None (can start immediately).

Activity

  1. added
    ready-for-agentFully specified, ready for an AFK agent
    area:backendHost-side implementation
    feature:memoryPersonaBot Memory Repository and Memory Service
    feature:messagingMessaging module and external providers
    scope:tracerHuman-testable implementation slice
    on Sep 27, 2026
  2. DoodleBears commented on Sep 27, 2026

    @DoodleBears
    ContributorAuthor

    Agent work claim

    • Agent: opencode (interactive session, not a DSH Session)
    • Task: opencode/local/2026-09-27-inbox-render
    • Issue scope: slice Slice: render inbox after prepare in the orchestrator turn #351 — move the Bot Inbox render after prepareTurn in the orchestrator wake path, byte-identical output
    • Branch: opencode/351-inbox-render-after-prepare
    • Started: 2026-09-27 06:38 UTC
    • State: active
  3. added
    agent:activeOne or more coding-agent tasks currently claim this issue; see claim comments for task IDs
    on Sep 27, 2026
  4. DoodleBears commented on Sep 27, 2026

    @DoodleBears
    ContributorAuthor

    Agent work outcome

    • Agent: opencode (interactive session) · Task: opencode/local/2026-09-27-inbox-render
    • State: completed (implementation pushed, PR open, merge decision left to Human)
    • Delivered: #runOrchestratorTurn now receives pending report InboxUnit[] and renders the Bot Inbox block right after prepareTurn; #collectInbox returns units only. PR: refactor(runtime): render Bot Inbox after Memory prepareTurn (#351) #354 (commit 73ac2f8)
    • Verification: full packages/core suite failure set byte-identical to the pristine baseline (33 pre-existing environment failures across 7 files, all Workspace Grant fixtures); DM, group, digest, report, resume, inbox-ignore, and memory-annotation suites pass unchanged; typecheck and lint clean.
    • Remaining: review + merge; the moved seam becomes observable coverage in Slice: deliver external Memory changes through Inbox #352 (admission replaces take-once).
  5. removed
    agent:activeOne or more coding-agent tasks currently claim this issue; see claim comments for task IDs
    on Sep 27, 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:backendHost-side implementationfeature:memoryPersonaBot Memory Repository and Memory Servicefeature:messagingMessaging module and external providersready-for-agentFully specified, ready for an AFK agentscope:tracerHuman-testable implementation slice

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions